Thanks @GJeffrey for that clarification. Its as I suspected VP is handling the Nvenc file different, now looks like its in the encoding.
@NickHope maybe hold off on the definition just for a little while, there are 2 other Nvenc variable frame rates to consider that maybe should really be constant, 24fps and 59.94fps. As V (see my breakdown in previous post) maybe they’ll exhibit this issue too. If so they need to be included in any definition.
Later i’ll attempt to get a more exact “length” where the issue starts from, so far it doesn’t occur at less than 3 seconds.
I hadn’t but did just now, no issues, and Mediainfo reports as constant.
The clip length cutoff is 199 frames 6s 19 f up to this length the clips frame rate mode is constant and no duplicate issue.
At 200 frames 6s 20f, the clip now has a duplicate frame issue, its still also of constant frame rate mode. From here on the duplicate issue is present. From frame 201 onwards the clips frame rate mode becomes variable and the duplicate frame issue exists.
I tested the 24fps and 59.94fps and I don’t think there’s a duplicate frame issue, the difference test does show anamolies because of the frame mismatch.
So @NickHope maybe just add the cutoff length to your definition.
Something like this ...
In a 29.970 fps project, the 87th frame of a longer than 199 frame clip in a 29.970 fps NVENC-rendered AVC file is repeated, unless the project properties are matched to the NVENC-rendered file.
@Former user Thanks for the comprehensive info. I'll add it to the known issues post.
Anytime.