I use Shotcut to inspect 240FPS videos (shot in MPEG4 H264 using Open Camera on my Google Pixel 9a). I use the #frame# in the Text: Simple filter field to see the frame count.
I have been using version 23.[something] for a couple of years, tonight I thought I would upgrade to the current version (25.05.11).
Version 23 was working as expected, showing 240FPS. However, v.25 is showing 1920FPS for the same video files. I know this as my subject includes an accurate clock that shows the time to 0.1s.
Is there a setting I might have forgotten about? I’m not even sure whether or not previous settings are kept during the upgrade process.
No. Settings do not affect this. Software changes (to improve it for the majority of cases) does.
One way to deal with an incorrectly higher detected FPS is to ignore it. A higher than correct FPS simply repeats frames. If you set the Video Mode FPS correctly, the extra frames are ignored.
Alternatively, you could remux the file with ffmpeg (Shotcut includes that executable), which you can search the Web or ask an AI about how to do it.
Many thanks for your reply. Following that, I can see that each frame is indeed repeated (& thus counted) 8 times, I had not noticed that before. I can easily have my spreadsheet (where I record my results) divide by 8 as a workaround, but it was important to know what is going on, thankyou.
I should clarify that Shotcut v.25 does report the FPS correctly in the properties view (with Video Mode FPS set to automatic), i.e. “240.000000 (variable)”. The only issue is the repeating frames. The #frame# field is doing its job correctly, based on the frames it is counting.
As mentioned, I had Video Mode FPS set to Automatic. I tried a custom one for 240FPS but it made no difference to the repeating frames or #frame# count.