I've just uploaded raw file with the new build 0924 here:I'm happy to try any raw footage from various sources on MacOS to try and narrow down what's going on
Sent from my SM-G965F using Tapatalk
Now that's very interesting thank you - if they work fine it at least proves something changed in the firmware between then and now [emoji106][emoji106]Downloaded the samples TonyM had shared 2 months back, playback is jerky. They ran fine when I'd downloaded them back then.
I think he means that the exact same files that played OK before now play jerky, something has changed in the Apple stuff.Now that's very interesting thank you - if they work fine it at least proves something changed in the firmware between then and now [emoji106][emoji106]
Sent from my SM-G965F using Tapatalk
Possibly - to be fair though if MacOS had an issue for weeks with some dashcam video not playing right in the MacOS or default media player you'd have seen it all over the internet by now as a lot of creative types use it and would be shouting about it - it's very strange if it's just affecting the A129 Pro.I think he means that the exact same files that played OK before now play jerky, something has changed in the Apple stuff.
Might be a good idea to update your codecs with the K-Lite Codec Pack.In my case(windows PC and laptop) the only one that play the file correctly is MPC...VLC,WMP and others are jerky..
That's bizarre thank-you - so the same file causing issues on other Macs is working fine on your iMac in Quicktime at full 30fps?Work fine on my iMac 2019 with Catalina
Colour space hasn't actually changed, it is just now flagged correctly. Before some players and a lot of editors were losing the shadow detail due to reading it as yuv420p when it was actually yuvj420p.I did notice the A129 Pro is using a slightly different colour space which is flagged as yuvj420p(pc, bt709) - most of the other test files I have are
yuv420p but the latest A129 Duo firmware also uses that and the files from that work fine in QuickTime.
I also noticed when testing with the A129 Duo that on the shipping firmware it came with (I think 1.2 or 1.3) that was using yuv420p but then when I upgraded to 1.9 it also changed to yuvj420p(pc, bt709) so either a design choice or a default changed in the SDK.
If you can play the H265 files OK then use H265, it should be the better option, and gives longer loop recording time due to lower bitrate, but a lot of people have computers that are too slow to play it so the default is H264.Ok, so just before I boxed the cam up to send back I've had a proper look through my SD Card to see what the files are on there and what I've got recorded. It looks like I've got a mix of H264 and H265 files. The H264 files show a 59Mbps and the H265 HEVC at 51Mbps. The H264 play as a slide show whilst the H265 work perfectly. So maybe an issue with the way the files are encoded at H264?
How come you're sending it back?Ok, so just before I boxed the cam up to send back I've had a proper look through my SD Card to see what the files are on there and what I've got recorded. It looks like I've got a mix of H264 and H265 files. The H264 files show a 59Mbps and the H265 HEVC at 51Mbps. The H264 play as a slide show whilst the H265 work perfectly. So maybe an issue with the way the files are encoded at H264?