Quote:
Originally Posted by r0lZ
As far as I know, only the Java versions are affected by that bug. The ++ version sets correctly the FPS Target to the same frame rate as the FPS Source, and therefore there is no need to force the conversion of the frame rate to avoid the small timecode changes due to the alignment of the timecodes to the video frames.
IMO, there is nothing to fix here.
|
I agree.
But as I am using both versions I sometimes forget or get confused what version has what bugs to take into account. So, to avoid problems I got myself used to always do this framerate setting. Thanks for the reminder r0lZ.