Thread: VFRtoCFR
View Single Post
Old 29th May 2012, 16:37   #9  |  Link
Aktan
Registered User
 
Join Date: Feb 2002
Posts: 303
I still think that choosing a frame under the timestamp is still incorrect as the original playback would not have the chosen frame shown at that time. Take for example a source area of 30000/1001 FPS. Lets say the timestamps of frames in ms were:

Code:
...
29963
29997
30030
30063
30097
...
Let's say the extreme case of setting the CFR to be 1 FPS so there would be a frame at timestamp 30000ms. With FFMS2, the frame at timestamp 29997ms would be chosen, but I say any frame from timestamp 30000ms - 39999ms would be better off since at 1 FPS the frame at timestamp 30000ms is shown from 30000ms - 39999ms. Currently, VFRtoCFR unfortunately chooses the frame at 30998ms, which is a pretty bad choice when the frame at 30030ms is clearly a better choice (I mention this in the limitations above and may fix this in the future). Though there are a ton of dropped frames in this example, so really practically in terms of view, as long as it is consistent, probably all are okay (lol).

I think I can see how this is of opinion which is why, TheFluff, since you consider this a feature request, instead of a bug, it was a good thing I wrote my own then, right?

Last edited by Aktan; 29th May 2012 at 16:43.
Aktan is offline   Reply With Quote