Hi, AGAIN, can’t believe this is still is an issue, the VFR bug is still there.
Are you using 6.0.4.0? I stayed on 6.0.3.0 since latest version removes newly added “force CFR” option for some reason. Try reverting to 6.0.3.0
In V6.0.4 the VFR bug is only there when changing frame rate into TVAI, when you use frame interpolation. But I have only tested model AION Interpolation, if Chronos also produces VFR has to be tested
When you do no frame (AION) interpolation, I get constant frame rate for all models, except when output codec is ProRes, then there is VFR, but slightly, and I think this comes from TVAI is dropping last frame.
We should also test the frame by frame output, if there are no double frames generated or inverting frame orders happens. Maybe I do this later or someone else can do it, would be interesting because they removed the force CFR flag and the question is it’s finally solved or just the cheap force cfr trick.
1 Like
You’re wrong, at least in MAC users the VFR bug is produced when exporting in any flavor of ProRes regardless of the processing, exporting in HEVC doesn’t change the frame rate.
ok then it’s worser on MAC, I don’t have a mac my test was with Windows
VFR bug is not happening for me. I have iMac M3 and version 6.0.4. I upscale using codec ProRes Std or even XQ and no VFR bug. I only upscale to FHD Default setting with Proteus. It was pretty bad before and I stayed with 5.3.6 until 6.0.4 came out that fixed that issue. So far so good for me.
iMac Hardware Overview:
Model Name: iMac
Model Identifier: Mac15,5
Model Number: Z19E000ZFLL/A
Chip: Apple M3
Total Number of Cores: 8 (4 performance and 4 efficiency)
Total Number of Cores GPU: 10
Total Number of Cores Neural Engine: 16
Memory: 24 GB
System Firmware Version: 11881.61.3
OS Loader Version: 11881.61.3
Mac OS: 15.3.1
You’re correct, I just tried it. Upscaling to FHD and exporting in ProRes doesn’t cause the VFR bug.
As soon as you upscale higher than FHD and export in ProRes the VFR bug strikes back.
Basically it’s a mess. FIX THIS! its been almost a year of useless clips
2 Likes
Bump to prevent this thread from closing, as its still an issue in 6.2.0.
Interpolating to 60fps often outputs 59.94fps.
Even if output is 60fps it is variable (based on track timecodes and NOT container metadata)
1 Like
Come on Topaz, pause all other feature updates and figure this one out once and for all. The exact frame timing going in should match frame-for-frame what comes out. It is affecting my workflow to the point I can’t reliably use this software anymore
3 Likes
I did another test. Source MPEG2 Interlaced 23.976fps → apo-8 60fps & prob4 2x upscale, Output ProRes-HQ, the result:
Then I have remuxed this into MKV, result:
So yes is WORSE! maybe we’ll find out all cases when this happens
2 Likes
