Completely ignore Mister Hatt
. Firstly, this is not the 1990's! Variable Encodes
are quite common and they will through your picture-sequence timing-off!!!!
. would it not be easier to just load it into AviDemux
and Get To Work On It -- the right way?AviDemux
was designed to work in the Y2K ERA, use it!
. it understands AVS, MKv, MP4, Xvid and Divx + variable timings and X264 and Ignores "Alpha 3.11" .. .
. it can work with FLAC, Mpa, MP3, MP2, ACC .. variable timings and AC_5+
. it knows the difference between Constant and Variable encodes and detects "that" while its loading the file.
Virtual Dub, Virtual Dub NAB & MOD never had those as options from the start and, like Mr. Hatt, Never Will!
Your fighting a loosing battle using out-of-date-software to fix that issue
and a lot of good it is using AviSynth as an editors helper ..
.. what screen do you see with AviSynth to let you see how well things are going?
don't make the same mistake twice
Dump Virtual Dub
and the GHOST
; use a real editor/converter -- the people from SONY will thank you.
post-it, I can understand everybody has their point of view and ways of doing things, but at least don't pretend to be in the right when you can't even make sense of what you write.
Saying wrong things due to ignorance or bad assumptions is not the correct way to make a point.
For starters, I hardly think that avisynth, a project started in 2002 and still alive, is the "1990's".
I'm not sure what "they will through your picture-sequence timing-off" is supposed to mean, can you clarify? The only thing that can seem to be implying is that Mister Hatt is encouraging a costant bitrate encoding method, which is quite amusing since he's always out there to encourage the usage of x264's Constant Rate Factor (or Constant Quality), so quite the opposite.
Avidemux might have a point on OSX, but on windows there are better solution. The primary gripe that I (and many others) have with it is that it doesn't allow quite as much freedom on what you do as avisynth does. Avisynth's IVTC tools are simply superior, for instance, and actually allow for an easy way to do VFR too, even manually, if need be. I'm not sure avidemux allows for quite the same level of freedom.
Avisynth can load any container and any codec (I don't see .m2ts, .ts, or .mov, for example, in that list, but they are quite common containers which one might need to use depending on what his source is). There are many different filters and indexers for it. You have ffvideosource which can load like anything, but for some things you have even better choices, like for example DGDecNV for indexing and loading sources from DVD and Blu-ray.
By variable timings I assume you mean "vfr" as in you're implying vfr is not possible with avisynth. You're correct in saying that avisynth itself is cfr but the point is that the framerate can and should be set at the container level. Avisynth feeds the frames, and then you can feed the proper timecodes to the matroska container just fine. If you know how vfr is done, it should be trivial to you.
Difference between constant and variable encodes... the only way that could be a matter is for mp3 audio. You are not supposed to be loading audio in avisynth, really, and when you load audio in virtualdub, it actually warns you about this, so I'm not seeing what point you're trying to make. I mean, it clearly shows that virtualdub does have the option, so I'm not seeing how you can even say "never had" or "never will".
Clearly, to be editing avisynth, you should be working on the script itself with AvsP or, depending on what you're doing, let YATTA help you create the script.
I don't have anything against you personally, but if you continue to make bad statements that risk to get people following a bad path from an encode point of view, do not expect people to NOT call you out on it, as it's for a purpose.
PS: Your links for VDub and AviSynth aren't the ones that they should be; virtualdub.org
are more like it.