AviSynth and/or VirtualDub error

[MaximRecoil]

This issue involves both AviSynth (version 2.5.8) and VirtualDubMod, but it seems to be AviSynth that is causing the issue.

My hard drive recently crashed and I had to reinstall everything on a new hard drive. Now when I try to open video files in VirtualDubMod via AviSynth scripts, I get the following error in VirtualDubMod:

Error decompressing video frame 0: The source image format is not acceptable. (error code -2)

This happens with every video file I try except for .MPGs (using DirectShowSource), whether .AVI files using AVISource, or other types (e.g. .WMV) using DirectShowSource. This is happening with video files that I know for a fact that I've opened before in VirtualDubMod via AviSynth scripts, without issue. Also, VirtualDubMod will open the .AVI files directly without issue, which is why I suspect the problem is AviSynth related.

Or it might be codec related, since it is opening .MPGs and nothing else. The only additional codecs I have installed on this system are Xvid and FFDShow. I don't know if it is relevant, but I did a complete install of FFDShow (like always) which includes "AviSynth scripts serving" and the AviSynth and VirtualDub "Application plugins".

[StainlessS]

Perhaps an AVI splitter is required.
Maybe Halli AVI splitter or maybe Helix YUV codec
Not sure which but I think one of them.

EDIT: Above probably wild goose chase.

[MaximRecoil]

Perhaps an AVI splitter is required.
Maybe Halli AVI splitter or maybe Helix YUV codec
Not sure which but I think one of them.

I never had a separate splitter for AVI files installed (I'm pretty sure Windows already has one by default). However, this did remind me that I had Haali Media Splitter installed previously in order to open .MKV files in VdubMod via DirectShowSource (because of this (http://forum.doom9.org/showthread.php?t=131139) thread), but I installed that in 2007, and I had been opening .AVI, .WMV, etc. files in VdubMod via AviSynth for years prior to that. In fact, I never had a problem doing that before; it always just worked without doing anything more than installing AviSynth and VdubMod. I've even done it on other people's computers just by downloading/installing those two programs (plus Xvid, because that is what I normally use to encode in Vdub) and doing it, never any problems before now.

In any event, I did just install Haali Media Splitter (and I checked the option during the install to enable AVI splitting), and no change.

ETA: Here are screenshots from GraphEdit, for what it's worth:

.AVI file:

http://img189.imageshack.us/img189/5059/graphedtavi.png

.WMV file:

http://img267.imageshack.us/img267/5776/graphedtwmv.png

[Groucho2004]

I'm pretty sure that you would not have that problem if you were using VirtualDub.
VDubMod is outdated and should be avoided.

Hint: Dump your error message into google.

[MaximRecoil]

I'm pretty sure that you would not have that problem if you were using VirtualDub.
VDubMod is outdated and should be avoided.

Hint: Dump your error message into google.

I've been using VDubMod with AviSynth for nearly a decade, without issue. The issue I'm having now is clearly not inherent to VDubMod. "Outdated" is a meaningless term in this context. It does what I need it to do, therefore I'm not going to avoid it.

I searched for this error message in Google before making this thread. None of the results were relevant.

ETA: You are correct that I don't have this problem with regular VirtualDub (I just downloaded it and tried it), which is bizarre. VirtualDubMod hasn't changed, AviSynth hasn't changed, so how can it not be working?

[Chikuzen]

It is very difficult to keep the same state.
Your environment is continuing changing like every month.
Have not you applied Windows Update?

VirtualDubMod has no maintainer.
If you want to use old things forever, just leave the internet!

[StainlessS]

Have not had to set up my machine (from scratch, Ghost image usually) for a couple of years,
but this is a problem that always used to show its face:

http://forum.doom9.org/showthread.php?p=1570422#post1570422

and the registry path on my XP32:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32

EDIT: From the back of my mind, I think this one might have been the main problem for me:

VIDC.YUY2 REG_SZ msyuv.dll

It usually had to be hand edited from the above.

EDIT: Also see here:
http://forum.doom9.org/showthread.php?t=62566

[MaximRecoil]

It is very difficult to keep the same state.

It is plenty easy to keep the same state as it pertains to certain things. For example, I used VDubMod with AviSynth without issue for about a decade. Obviously none of the countless system changes over those years (or the differences on totally different machines) made a bit of difference, because they obviously weren't even remotely relevant to what makes VDubMod tick. Imagine if it were a common thing that after every system state change, all of your software got broken. PCs wouldn't be very popular if that were the case.

Your environment is continuing changing like every month.
Have not you applied Windows Update?The updates are no different than the ones I had on my old hard drive two days ago before it crashed.

If you want to use old things forever, just leave the internet!

Absurd. VDubMod does things that VDub doesn't, things that I use. Additionally, the internet is what enables the use of old things. Without the internet, old things would be harder to find, and it would be harder to find help pertaining to said old things.

[Keiyakusha]

Absurd. VDubMod does things that VDub doesn't, things that I use.
Not an absurd. This is because you never learned better ways of doing the same things. VDubMod would never be abandoned if it would be really useful. New devs usually come to continue someone's work if the old ones can't do so for whatever reason. But none come to work on VDubMod because everyone realize it is useless waste of time.
Also by your logic we all should leave our comfortable chairs and go back to caves.

[MaximRecoil]

Have not had to set up my machine (from scratch, Ghost image usually) for a couple of years,
but this is a problem that always used to show its face:

http://forum.doom9.org/showthread.php?p=1570422#post1570422

and the registry path on my XP32:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32

EDIT: From the back of my mind, I think this one might have been the main problem for me:

VIDC.YUY2 REG_SZ msyuv.dll

It usually had to be hand edited from the above.

EDIT: Also see here:
http://forum.doom9.org/showthread.php?t=62566

Thank you. I installed an older version of Xvid and that solved the problem.

[MaximRecoil]

Every sentence that you typed here is a logical fallacy:

Not an absurd. This is because you never learned better ways of doing the same things.

You have no idea what I've learned, thus your attempted crystal ball reading is dismissed.

VDubMod would never be abandoned if it would be really useful. New devs usually come to continue someone's work if the old ones can't do so for whatever reason.

Your false dilemma is dismissed.

But none come to work on VDubMod because everyone realize it is useless waste of time.

Your baseless assertion / attempt to speak for "everyone" is dismissed.

Also by your logic we all should leave our comfortable chairs and go back to caves.

Your false analogy is dismissed.

[the_weirdo]

@MaximRecoil
You should use AVISource as source filter for AVI container instead of DirectShowSource.
May I ask: What specific features of VirtualDubMod which you need?

Remember that you can do whatever you want with your things. We can't and won't force you to do something you don't like. It also doesn't have any benefits for us to do that. So if you like to stick with old softwares, it's your choice. That's it.

[MaximRecoil]

@MaximRecoil
You should use AVISource as source filter for AVI container instead of DirectShowSource.

I do. I mentioned that I used AVISource for AVIs in the OP (and DirectShowSource for other types, like .WMV).

May I ask: What specific features of VirtualDubMod which you need?

I like the layout, I like that I can add an .AC3 audio stream by default, I like that it has a built-in AviSynth script editor, I like that it can automatically create a basic AviSynth script in the "Open video file" dialog box ("Use AviSynth template" option), and perhaps various other things that I only notice when I'm using regular VDub and they are made conspicuous by their absence.

Remember that you can do whatever you want with your things. We can't and won't force you to do something you don't like. It also doesn't have any benefits for us to do that. So if you like to stick with old softwares, it's your choice. That's it.

I don't know why anyone made an issue out of it in the first place. The video files that VDubMod produce work, so what's the problem? And even if there were a problem, how would it affect anyone but me?

[StainlessS]

MaxRecoil, I'm with you on VDMod, use it all the time.
Cant beat the AVS script editor, and eg trim in VDMod, CTRL/I to insert entire trimset, easy as pie.
If only current VD had the script editor, I would change in a instant.
I do use VD current, in fact I have 5 version of VD in-situ, but for avs editing, there is no VD alternative.

[GMJCZP]

I also use the VDubMod to edit the script in real time, and while I can still use it I will.
Several people ask VirtualDub developers add these and other functions VDubMod. The least that can be done in the case of the scripts is to use something like AvsPmod, and muxing tracks using AviDemux, for example.
Lately I used VirtualDub to encode only (at least with Lagarith, output in YV12), for I have noticed that do a little better (subjective view) by adding at the end the script ConvertToYUY2(), which his brother in the case of adding at the end the script ConvertToRGB24(). What do you think?

If you want a version with corrections see here:

http://forum.doom9.org/showthread.php?p=1607607#post1607607

There you will get the latest versions of VDubMod (1.5.10.2 build 2542 and 1.5.10.3 build 2550).