Video is jumpy and out of focus when editing.

[Angeteen]

I tried it out, and while the .avs script runs fine on VirtualDubMod, I get another "AVI import filter error" whenever I try to use it with VirtualDub. So the good news is the script works it's just that it doesn't want to work with VirtualDub. I think it may be the limitation of VirtualDub not being able to handle .mkv files, so would that mean I should use another program to do the converting?

[Mister Hatt]

Actually I'm gonna play devil's advocate and say there totally is a reason to use VDM still, two in fact, but I'm not going to say what they are. One of them is also THE reason to use NanDub though.

There is no such limitation of VDub not handling matroska files seeing as you're loading an AVI file (which is really a decoded matroska file with other things done to it but that is not the point.) Avisynth files are literally interpreted as uncompressed AVI files; they output raw bitmap frames into a cache which you are able to access in your playback setup.

[Mister Hatt]

By the way, there is no logical reason for it to work in vdm and not regular vdub seeing as everything access avs the same way, so unless that method itself is a problem (and if it is, you have far bigger issues to deal with), something else is going on and it is most likely vdm doing something stupid while you have a completely broken avs file.

[post-it]

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.

[Enigma]

BUAHAHSHHAHAHAHAHAHHAHAH

[Angeteen]

I've tried to use AviDemux, and while it was able to recognize the file, it wasn't however able to remove any of the jumpiness from the video. Also it seems that AviDemux is having problems with the above .avs script. I tried one that worked in VDM, but all I got was an error message saying that it could not open the file (ditto for Vdub...as usual VDM accepted the same file with no problem). As a test I created a new .avs script to open a .avi file, and turns out I got the same issue both on AviDemux and Vdub.

So it looks like that out of the three programs VDM is the only one that seems to be accepting .avs scripts. In short, until I figure out why the scripts aren't loading, I can't use AviSynth. So far the only two lines of code being used are to load the necessary plug-in I'm using, and to input the video file. Not a lot to go wrong there. :S

Also, as for what screen I'm using to monitor AviSynth, can you please be a little more clear? As far as I know AviSynth is basically used to create script files, that are then dragged and dropped into a video editor/converter. Since I do all my editing in Premiere AVISynth is only used as a way to try and convert files.

As for AviDemux I've tried the various video settings (YV12 raw), copy, DV, etc, but have so far had no luck.

[Cannonaire]

Angeteen: It sounds like there are problems with your avisynth install or maybe even deeper problems with your vfw (video for windows) configuration. You could try manualy uninstalling avisynth, which involves going into your system32 directory (or syswow64 on 64-bit windows) and removing avisynth.dll and replacing it with a new one; I recommend the 32-bit avisynth 2.6a. Another thing you could try is renaming your plugins directory in your avisynth folder and reinstalling avisynth with just the basic plugins and seeing if plugin conflicts are your issue. Finally, if your vwf installation is foobar'd you could try uninstalling any codecs/codec packs you have and installing just the CCCP and a few other required codecs (no other packs!!!). If that doesn't work, I don't really know what would help.

Also, I've had nothing but headaches from Avidemux. I did find a decent use for it - muxing mpeg2 files without using pay software - but it tends to crash and fail on even the most basic operations, when everything else works fine. It fails hard on UTVideo, a great codec with fast encoding/decoding and excellent compression, and also seems to die whenever I try to feed it lagarith. I'm sure it has potential, but the developer needs to make the damn thing actually work for what it's intended to do and be stable, like VirtualDub.

[Mister Hatt]

Avidemux does EXACTLY what it is supposed to correctly like 99% of the time. The one exception is for indexing AVC tracks. What it doesn't do is 99% of the stuff people ask of it, as for some reason people seem to think it is an alternative to virtualdub which it isn't.

@post-it: seems you have no idea what NanDub is even capable of then. Re avidemux, last I checkd, it blows at VFR, which has nothing to do with the content at hand in the first place. Please stop spreading misinformation, even your links were of poor choice.

[mirkosp]

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 and avisynth.org are more like it.

[post-it]

.. I just state, with what I've experienced, should give anyone the cleanest results.

AviDemux .. yup; more like 92% of the time on VFW stuff. NAB dub .. quite useful
for Angel Potion ( both versions were HACK's ) but not really useful to the Majority of encoders!

.. picture-sequence timing-off .. I have no "name" for Frames "not-being locked in place."
This concept, which is "all that it is to me", totally defeats evenly-spaced Frame-By-Frame animation:

.. I do things from a Frame By Frame understanding. Having someone "not" load a Video which is Evenly-Spaced
just sounds like "their using someone elses 2nd-pass Divx material" instead of something that they
ripped from a DVD or Captured on camera.

Virtual Dub was quite useful around the 13a release.
AviSynth has no value in Hand Drawn Production at any time!
AviDemux I trust as far as I can kick-it!
however, AviDemux has solved more problems than it has created. as such, its my choice.

. . lets back-up to the original question, before you block-me-out, and kindly explain
to the person asking the question How The Video Lost Its Timing In The First Place!??

Bye!