Quote:
Having not taken the time to read and understand the AviSynth core but i think it would require a major rewrite. Maybe this would be good to beg the Devs, into adding to AviSynth 3.
|
That's true, it's require a major rewrite and IMHO an unreasonable one, since it will break the logic of all temporal filters (who assume CFR).
So b) is refused, but c) is still possible.
As for functions i'd see:
MKVSource(filename, videotrack = 0, audiotrack = 0)
no forcedframerate, it just uses the average (users can AssumeFPS after if they want)
MKVUndoVFR(filename, videotrack = 0, audiotrack = 0, threshold)
scan for an acceptable common framerate and add dupes to fill in the gaps
the threshold param controls how close the predicted timecode must be from the real one to be an acceptable match
MKVEmuleVFR(filename, videotrack = 0, audiotrack = 0)
same as MKVSource, but mark frames with a timecode properties, so filters who want to consider them could.
MKVInfo...