Quote:
Originally Posted by foxyshadis
Every suggestion I've seen so far will lead to broken interpolation, by duplicating or dropping frames and confusing the hell out of Interframe. How about this: Use DSS to import a Graphedit .grf instead, one in which you start with your mp4 source and connect SVP. Let the VFR be taken care of in a VFR domain instead of importing it into avisynth.
If Interframe is ever ported to VapourSynth, it would just work, since VS natively supports VFR. But it's not available yet.
|
colours' final suggestion of running interframe as normal and then just making a new timecodes file for it would actually work just fine. If it's mainly one framerate with a couple oddball segments, a v2->v1 converter and just doubling the rates would be pretty easy. If it's messier you can just read every timecode line, divide it by two, and insert that twice into a new file. Maybe alternate rounding up and down for safety. It's easy to script, though lol please don't do it by hand. Vapoursynth would surely make it trivial, but it's not necessary.