VirtualDub unable to open avisyth scripts

[suroit]

OK, I am getting really frustrated. I have been using VirtualDub/VirtualDubMod and avisynth for years, and processed hundreds of videos but today, I am stuck. I suspect the problem comes from my recent installation of MediaMonkey and the CCC codec pack.
I was before using the K-lite codec pack. I have spent a lot of time searching the web, Doom9, the VirtualDub forum, VideoHelp. No solution so far.
I have un-installed and re-installed (several times) avisynth 2.5.85, VirtualDub 1.9.10, VirtualDubMod, the K-lite codec pack, ran CCleaner, rebooted.
I am at the same point: I can't open even a very simple avisynth script with VirtualDub, such as:

DirectShowSource("L:\MyVideo.avi").

(What I am really trying to do is run

MPEG2Source("L:\MyMpgVideo.d2v")

but I am trying to do something basic at this point.)
When I try to open it with VirtualDub, the VirtualDub window opens for a fraction of a second, and closes. With VirtualDubMod, I get the error:

AVI Import Filter error: (Unknown) 80040154

On the other hand:

• Media Player Classic can open the script, as well as Windows Media Player, which tells me that avisynth seems to work normally.
• At the same time, VirtualDub or VirtualDubMod can open and play the video directly. So it looks like the only type of file they don't like is the avs script.

It looks like some kind of new incompatibility between avisynth and virtualDub.
The problem is that I installed, configured these applications with all the plugins I needed 3-4 years ago, and I am not able to go through the same exact process any more.
I tried to run VirtualDub with minimum plugins, no success.
I would REALLY appreciate any help. I love VirtualDub, and I think I need it to edit my avisynth scripts prior to encoding.
Thank you.

[jagabo]

DirectShowSource() isn't a good starting point for debugging because it relies on installed DirectShow components. Start with AviSource(). For Mpeg2Source() make sure you have all current DgMpgDec components installed.

[AlanHK]

I would REALLY appreciate any help. I love VirtualDub, and I think I need it to edit my avisynth scripts prior to encoding.
Thank you.

Can't help with the codec problem, but on editing AVS scripts, I also use VDubMod's built-in editor for simple edits.
Also, there is a "patched" VirtualDub at http://tongari.at/
This has the AVS editor of VDubMod, but is based on VDub 1.78, where VDubMod is based on 1.5.1
(Very frustrating that the maintainers of the official VDub refuse to incorporate the AVS editor.)


But AvsP is a much more powerful Avisynth editor, especially the slider support for filters -- only lack is it only shows frames, doesn't play videos, though you can launch them.

[suroit]

DirectShowSource() isn't a good starting point for debugging because it relies on installed DirectShow components. Start with AviSource(). For Mpeg2Source() make sure you have all current DgMpgDec components installed.

You're right. But same issue with AviSource(). Thanks for the help, though.

[suroit]

But AvsP is a much more powerful Avisynth editor, especially the slider support for filters -- only lack is it only shows frames, doesn't play videos, though you can launch them.

Thanks for the idea. I just checked AvsP, which I had tested a while back, but never much used. It works with my one-line script , and I could possibly use it instead of VirtualDub .
One reason I liked VirtualDub was to start with a basic script, then try some Vdub filters (e.g, cropping, logo removal, denoising, etc.) and immediately see the effect on the video prior to writing the actual avisynth lines. I guess I could do almost the same thing with AvsP, with the advantage of the more powerful script editing features.
But I really want to get VirtualDub up and running with Avisynth again , or at least understand what is happening!

[guns1inger]

Have you tried rolling back to 2.5.8 ?

[AlanHK]

One reason I liked VirtualDub was to start with a basic script, then try some Vdub filters (e.g, cropping, logo removal, denoising, etc.) and immediately see the effect on the video prior to writing the actual avisynth lines. I guess I could do almost the same thing with AvsP, with the advantage of the more powerful script editing features

Even better, you don't have to translate VDub filters into Avisynth. Once you get the effect you want, just save and you're done.There aren't exact corresponding filters in many cases anyway; and many very useful, but cryptic, Avisynth filters become much easier to use when you can slide their variables and compare different settings in different windows.

[Gavino]

I have un-installed and re-installed (several times) avisynth 2.5.9

Is this a typo?
I've never heard of 2.5.9 - latest official full release is 2.5.8.
What does it show if you open the following script in AvsP, WMP, etc:

Version()

[suroit]

Even better, you don't have to translate VDub filters into Avisynth. Once you get the effect you want, just save and you're done.There aren't exact corresponding filters in many cases anyway; and many very useful, but cryptic, Avisynth filters become much easier to use when you can slide their variables and compare different settings in different windows.

I have been playing a little more with it and I can see the greater ease of use. There is one thing I like with VDub, though, it's the option of using the actual VDub filters in Avisynth. For example, I use from time to time the VDub delogo filter, define all its parameters in VDub and copy its configuration in the avisynth script (see this post).

[suroit]

Is this a typo?
I've never heard of 2.5.9 - latest official full release is 2.5.8.

Yes, sorry. I meant 2.5.8 -- version() actually returns 2.58

[jagabo]

maybe something in this thread: https://forum.videohelp.com/threads/302249-VirtualDub-AVI-Import-Filter-error-%28Unknown%29-80040154

[suroit]

maybe something in this thread: https://forum.videohelp.com/threads/302249-VirtualDub-AVI-Import-Filter-error-%28Unknown%29-80040154

Yes, I had seen that, thanks. I don't know how to identify the unregistered filter but I am trying, just in case.
What puzzles me is that an avs script as simple as this single command: version() is rejected by VirtualDub. I don't understand how any filter needs to be involved to run that script!

[AlanHK]

There is one thing I like with VDub, though, it's the option of using the actual VDub filters in Avisynth. For example, I use from time to time the VDub delogo filter, define all its parameters in VDub and copy its configuration in the avisynth script (see this post).

Well, you can just make an Avisynth function as a wrapper for the Vdub filter call.
(Your Doom9 link doesn't work, at least for me now.)

I mostly use Nologo and Xlogo filters in Avisynth.
I just have to make an appropriate mask, which is pretty quick -- especially if I can find the logo on a black background.

One of these days I'll work out how Inpaint works. It seems to be more powerful, but not trivial to use.

What puzzles me is that an avs script as simple as this single command: version() is rejected by VirtualDub. I don't understand how any filter needs to be involved to run that script!

What does "rejected" mean? What is the exact error message?

[sambat]

I had a problem with VirtualDub/Avisynth when I migrated all of the AviSynth filters to a new PC.
VirtualDub would not open your basic script.
I found that when I uninstalled Avisynth and manually removed the filters, then reinstalled Avisynth, it worked.
I then added groups of filters until I found two that caused a recur of the problem.

[suroit]

Have you tried rolling back to 2.5.8 ?

Sorry for the confusion. I mistyped. I am actually at 2.5.8.

[suroit]

(Your Doom9 link doesn't work, at least for me now.)

I see that, for some reason, it is somewhat capricious. The link is http://forum.doom9.org/showthread.php?p=142909.

What does "rejected" mean? What is the exact error message?

What I meant is that when I run that version() script (or apparently any simple Avisynth script) in VirtualDub, it seems to open for a fraction of a second, and then closes without any error message. VirtualDubMod on the other hand also closes, but with an error message:

AVI Import Filter error: (Unknown) 80040154

The error message is the same, whether the script is to just to provide the version number, open an avi file, or a MPEG-2 file.

[suroit]

I found that when I uninstalled Avisynth and manually removed the filters, then reinstalled Avisynth, it worked.
I then added groups of filters until I found two that caused a recur of the problem.

Do I understand correctly that you identified two Avisynth plugins that were the cause of the problem?

[suroit]

I had a problem with VirtualDub/Avisynth when I migrated all of the AviSynth filters to a new PC.
VirtualDub would not open your basic script.
I found that when I uninstalled Avisynth and manually removed the filters, then reinstalled Avisynth, it worked.
I then added groups of filters until I found two that caused a recur of the problem.

That's it, thanks a lot Sambat!

I think I resolved the issue.
Following your advice, I re-did what I tried to do before: remove all the avisynth plugins and add them back progressively. Except this time, I used this very simple avs script: just the command version(), to eliminate other potential sources of error.
Bingo, VDub started working with the script!
I found out I had an extra copy of avisynth.dll in the plugin folder. Removing it resolved the problem .