Megui - There is no function named 'LoadVirtualDubPlugin'

[enchant1]

I'm using Megui V2507, but I'm having a problem. I have this line of code in my script:

LoadVirtualDubPlugin("F:\videos\Logo.vdf","Logo",0)

It's to burn a watermark logo into the video. This works fine if I don't have the "Always use the included AviSynth" option selected. If I DO check that, it generates this error:

Script error: There is no function named 'LoadVirtualDubPlugin'

So it must be finding this script someplace in the installed AviSynth 2.5 that I have, but I can't find it.

I'd like to continue using Megui using the included AviSynth, because it seems to encode MUCH faster, but I'd really like LoadVirtualDubPlugin to work.

[hello_hello]

I thought you upgraded to Avisynth 2.6? In my experience Avisynth+ is only very marginally faster than Avisynth 2.6, but anyway.....

There's no script to find. Avisynth+ doesn't natively have the ability to load VirtualDub plugins as the official versions of Avisynth do. However there's a plugin that gives it the ability to do so. You'll find it buried in MeGUI's tools folder. You'll need to load it first, like this.

LoadPlugin("C:\Program Files\MeGUI\tools\avs\plugins\VDubFilter.dll")
LoadVirtualDubPlugin("F:\videos\Logo.vdf","Logo",0)

[enchant1]

That worked perfectly. I think I'm back to 100% now.

Yes, I did load in Avisynth 2.6, but I think the default directory it chose for the install was Avisynth 2.5. But I'm ok with Megui using its internal version. Very very fast.

[enchant1]

Aha - it's not internal vs external that makes the speed difference. It's loading the vdub plugin. Even using the internal avisynth, it takes twice as long to encode the video using it as without. Oh well... It's STILL faster than I was getting before upgrading my machine.

Thanks again for the help.

[hello_hello]

For some reason the interaction between MeGUI, Avisynth and ffms2 can be a bit odd when using the script creator and MKV is the source. Changing the cropping or resizing too quickly can cause errors/crashes. I don't know why, but it's much worse using the official/installed Avisynth, which is the main reason I mostly use the portable version supplied with MeGUI.

If filters are a bottleneck when encoding (check CPU usage and if it's not all that high) I make a copy of the script and use each copy to encode half the video, then run the encodes simultaneously. That keeps the CPU pretty busy. Of course if you're already encoding more than one video you can just run them two at a time, but for a single encoding job splitting it in half instead works. Just make sure you check --stitchable in the x264 encoder configuration so you won't have any problem appending the encoded video. It's easy enough to append it with MKVMergeGUI.

Trim() is easy enough to add to a script for encoding just sections of it, or the AVS Cutter under the Tools menu will do it for you.

[enchant1]

Thanks for the tips. I really have no cause to complain about the encode time. A few weeks ago on my old 32-bit XP machine, a 45 minute video encode took 3-4 hours. Now it takes 50 minutes with LoadVirtualDubPlugin or 30 minutes without.