KVCD: BlockBuster.dll problem
 

Hi all,

KVCD is great. I've had quite a bit of success after trying lots of different things to get around any problems!

I do have one problem currently, and have searched around on the board for people with the same problem, but haven't been able to find the solution, so I'm sorry if my question is one that has been asked before...

What I am trying to do is add BlockBuster to my AVS's. I have downloaded the latest Blockbuster.dll from SansGrip's Avisynth filters webpage http://www.jungleweb.net/~sansgrip/avisynth/. I have v2.52 of Avisynth loaded. I am using ToK v0.0.5.3 and VirtualDub 1.5.7. Now, when I add LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\Blockbuster-2.5.dll") to my .avs script, I get the following error message in a "VirtualDub Error" window: "Avisynth open failure: Plugin C:\blahblahblah\Blockbuster-2.5.dll is not an AviSynth 2.5 plugin..." This error also occurs for Bockbuster.dll.

So, what am I doing wrong? Is what it saying true? Is the Blockbuster-2.5.dll not a AviSynth 2.5 plugin? Or maybe there is something else I need to update, like my registry or another .dll file?

Any help appreciated.

Cheers!

Hi I-dunno,

Blockbuster has been written for AVS 2.0x only.
Use a plugin called LoadPluginEx.
Info and download here:
http://www.avisynth.org/index.php?page=LoadOldPlugins

No Krassi, BLockbuster-2.5.dll is for avs2.5 as its name said it :-)

I do not understand your problem dunno. Everything always work fine for me.

Just do not put both version of blockbuster in you plugin directory but only the one you need. That can be that.

Sorry I-dunno, thanks Phil.
Had an old version on my desktop...
Can you make sure you have imported only the 2-5.dll to the plugins folder or if you use LoadPlugin define the path to the 2.5-dll.

And by the way ... I also heared of these problems about plugIn incompatibilities at doom9-avisynth forum.

Maybe its not the problem in this case, but ..... as I know that many people use that (IMHO horrible confusing making )"AVS switcher" sometimes they forget to switch back! :oops: 8O

As mentioned in the AVS Guides there's a very very easy and comfortable way to just perform every avs 2.0 plugin you need in a AVS 2.5 script without everytime typing that boring "LoadPlugin("C:\Programme\AviSynth 2.5\Temp\LoadPluginEx.dll")".

Write an AVS script including the following lines:

##################################
LoadPlugin("C:\Programme\AviSynth 2.5\Temp\LoadPluginEx.dll")
LoadPlugin("C:\Programme\AviSynth 2.5\Temp\Dustv5.dll")
LoadPlugin("C:\Programme\AviSynth 2.5\Temp\My other often needed AVS2.0 PlugIn.dll")
LoadPlugin("C:\Programme\AviSynth 2.5\Temp\Also a needed AVS2.0 PlugIn.dll")
##################################

Safe this script using a *.avsi istead of .avs and safe this .avsi file into your AVS 2.5!! PlugIns Folder

So this .avsi doc will be seen by AVS 2.5 like a .dll which will be loaded on every startup ... so the generally needed AVS 2.0 .dll's will be present and you just have to type within an AVS 2.5 script the command of the used AVS 2.0 FIlter ;-)

Example:

########################
Avisource("D:\Xvid.avi")
BlindPP(CPU=4)
Deen("a2d",1,10,12)
ConverttoYUY2()
Pixiedust()
...... and so on ....
########################

But!! Do not put the "LoadPluginEx.dll" in the same folder like your AVS 2.5 Plugins!!! Just create for example as shown in the path within the script a "temp" Folder within your AVS 2.5 Root Folder on your HD and put your "LoadPluginEx.dll" and the other AVS 2.0 Plugins there.
Second!! Only use AVS 2.0 Plugins which you do not already use as 2.5 Plugins!!! So it could be dangerous to have a STmedianfilter.dll activated as AVS 2.0 dll and also as AVS 2.5 dll cause the command "stmedianfilter(xx,xx,xx,x,x,xx,) will call the needed Plugin and by existing 2 loaded dll which will be called by the same command could cause problems!

And that "easy way" leads you to work in YUY2 because there is no avs2.0x plugin that handle YV12.

Longer time to encode (sure), lesser quality results (not so sure). It does not worth it at all. Even if you are a die hard fan of DustV5 (there are a lot of filters in 2.5 that can replace FaeryDust).

Note: If you are in avs2.0x and don't want to put all the loadplugin lines, you can also do a text file with "Loadplugin(...)" for all your plugins, save it a "filters.h" for instance and start your scripts by "Import("filters.h")". That's all.

Yes but you only have to work in YUY2 WHEN using the AVS 2.0 Filter as you also have to when putting the mentioned "LoadPlugin("C:\Programme\AviSynth 2.5\Temp\LoadPluginEx.dll")" manually and using afterwards the AVS 2.0 command in your script.

This is no Sign "Feel free to use AVS 2.0 Plugins" but in very rare cases its useful just to add the AVS 2.0 filtercommand line to your script .... IF REALLY NEEDED! And there I agree with you.

I installed a .avsi like mentioned above and no problems no less speed when NOT working with avs 2.0 Commands but comfortable IF AVS 2.0 PlugIns are needed in very rare cases.
;-)

Fixed
 

I fixed my problem! :D So I am posting the solution in the hope that other people with a similiar problem might benefit...

Well, as it turned out, the Blockbuster-2.5.dll probably isn't what it says it is... :evil: The blockbuster.dll that I got from http://www.avisynth.org/users/warpenterprises/ happens to work with Avisynth 2.5 just fine.

Well, this explains everything :)