When saving to a MOV file, Topaz sets the framerate incorrectly. This can be seen in the screenshot from ffmpeg
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from ‘PART-1_4_prob4.mov’:
Metadata:
minor_version : 512
major_brand : qt
compatible_brands: qt
videoai: Enhanced using prob-4; mode: relative to auto; revert compression at 0; recover details at 0; sharpen at 50; reduce noise at 0; dehalo at 0; anti-alias/deblur at 0; focus fix Off; and recover original detail at 20. Changed resolution to 3840x2160
encoder : Lavf61.7.100
Duration: 00:02:29.98, start: 0.000000, bitrate: 2315100 kb/s
Stream #0:0[0x1]: Video: prores (HQ) (apch / 0x68637061), yuv422p10le(progressive), 3840x2160, 2315094 kb/s, 59.95 fps, 59.94 tbr, 60k tbn (default)
All DTS in the file are ok, but in the container/stream the wrong fps is set to approx. 60fps (instead of 59.94fps). Because of this, programs open such a file with a bad framerate. Does anyone know a way to repair such a file? Because Topaz will probably never correct this error.
Yes this happens when you choose ProRes, h264/h265 gives constant frame rate. I thinks it is because they drop one or more frames and the beginning/end, but its not that worse VFR you get when doing TVAI frame interpolation.
You can fix your already done encodes by droping/copy frames to reach excactly 59.94, with Avisynth or use builtin Avidemux “Resample”
To gather logs, please select Help > Logging > Get Logs for Support and attach the zip file to your reply.
You can securely submit your file(s) to our Dropbox using the link below. Please be sure to send me a note to let me know you sent something and include the file name. Submit File to Dropbox
When saving to a MOV file, Topaz sets the framerate incorrectly. This can be seen in the screenshot from ffmpeg
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from ‘PART-1_4_prob4.mov’:
Metadata:
minor_version : 512
major_brand : qt
compatible_brands: qt
videoai: Enhanced using prob-4; mode: relative to auto; revert compression at 0; recover details at 0; sharpen at 50; reduce noise at 0; dehalo at 0; anti-alias/deblur at 0; focus fix Off; and recover original detail at 20. Changed resolution to 3840x2160
encoder : Lavf61.7.100
Duration: 00:02:29.98, start: 0.000000, bitrate: 2315100 kb/s
Stream #0:0[0x1]: Video: prores (HQ) (apch / 0x68637061), yuv422p10le(progressive), 3840x2160, 2315094 kb/s, 59.95 fps, 59.94 tbr, 60k tbn (default)
All DTS in the file are ok, but in the container or stream the wrong fps is set to approx. 60fps (instead of 59.94fps). Because of this, programs open such a file with a bad framerate. Does anyone know a way to repair such a file? Because Topaz will probably never correct this error.
40GB → impossible.
But you can do it yourself - just save any file in ProRes422. Each one is broken. Then just load the source file and the processed file into Magix Vegas and you will see how the frames start to fall apart from a certain point.
So I’m not sure it is just wrong fps flaged/read out or really not “linear”, means when you have real variable framerate and video lenght must fit exaclty, there is no other way filling it up with copy frames/or drop some, as described above.
Yes, I accidentally discovered that VirtualDub can also copy ProRes streams
The source file is CFR, the output is also CFR, the frames have correct DTS points. Topaz Video simply inserts the wrong fps information in the stream info and some programs don’t know which information to use.
Yes, I accidentally discovered that VirtualDub can also copy ProRes streams
The source file is CFR, the output is also CFR, the frames have correct DTS points. Topaz Video simply inserts the wrong information about fps in the stream info and some programs do not know which information to use.
Yes, I accidentally discovered that VirtualDub can also copy ProRes streams
The source file is CFR, the output is also CFR, the frames have correct DTS points. Topaz Video simply inserts the wrong information about fps in the stream info and some programs do not know which information to use. I do not know if this error does not come from Topaz sending the last frame with the wrong duration (“Duration_LastFrame : -17 ms”)
Duration_LastFrame : -17 ms
So yes it’s a correction and I think could be per defintion VFR (VFR is when time intervals between the frames are not absolutely identical), but very slightly VFR which is very close to CFR…so my MediaInfo says it’s VFR when I use ProRes in TVAI V6
However, you can remuxe the source is quickly done and see what happens and check with MediaInfo. I recommend TVAI V5.3.6 there this problem does not exist.
