I noticed an issue on both 2025 versions (31550 and 31760), and checked both on Windows 10 and 11.
When trying to read a video file it reads correctly but at the wrong frame rate. All my files are 50fps and they read at a random weird rate like 50.0117 or something around this.
The “Override Sample Rate” does work so that’s a workaround, but it’s still a weird bug.The same file reads perfectly fine in versions 2023.11760 and 2023.12600.
For information the file i’m trying to read is Prores 422HQ, 8192*4096, 50fps. I checked with MediaInfo, the framerate of my file is 50.000 fps and correctly set to constant.
I could send a small sample if that’s of any help.
So I did realise some interesting things while trying to make a 10s sample of one of our files.
All our final files come from Topaz Video AI, if I make a 10s sample using Adobe Media Encoder it reads correctly at 50fps. But if I export only 10s directly from Topaz I get this bug.
I did some more testing and noticed this :
The file, before going through Topaz is read at 50 fps correctly
In MediaInfo the 10s sample says it’s 10s and 1ms long, but the framerate is correct at 50.000 fps
In Resolve the file shows indeed 500 frames and a framerate of 50.000fps
In Adobe Premiere Pro, the file is fine, showing 10s exactly and 50.000fps
So I would say Topaz is doing something weird with the framerate here, as it has a history of doing so in older versions.
But something clearly changed in Touch 2025 versions because we never saw this bug before. And it is the only software in which we don’t have a correct framerate.
I’m sending the sample to you by DM at the moment, thanks for your help!
Interestingly VLC also shows the slightly not-50 value for the FPS. I see where this is coming from, it’s from the ‘average FPS’ calculation that FFmpeg goes. I assume this means the timestamps in the generated file aren’t quite perfect 50.
I had a bug in my code where I was using this average FPS when I shouldn’t be. This will be fixed in builds 2025.31962+