Warning: Warpsharp.dll in plugin dir causes CCE 2.50 to fail and other wmp probs

[DDogg]

Title says it all. My CCE problems that cropped up were due to the warpsharp.dll (from the package that includes LoadPluginEx.dll - warpsharp_2003_0121.cab) being in the plugin directory for avisynth 2.51 (March 19 CSC version from Sh0dan's sig).

So, remove BOTH LoadPluginEx.dll and warpsharp.dll from your plugin directory if you wish to use CCE.

Thanks to JuanC for getting me started in the right direction in this thread: http://forum.doom9.org/showthread.php?s=&threadid=49384

Because of the severity of this problem and the difficulty finding it I elected to start this thread with a clear title. /edit Please forgive my several other disjointed threads on the subject. It was confusing and difficult to trace these seemingly random problems down as you can see from the list below.

Other problems caused from this plugin were:

1> WMP 6.4 crashing on EXIT.
2> Crashing on "new" in Graphedit after an avs script (using directshow) was rendered.
3> CCE 2.66.01.07 - Scripts using test versions of Avisynth BMP Loader.dll for avisynth 2.5x used in DVD2SVCD test versions crashed.
4> Using DirectShowSource in an AVS script problems (not completely verified yet)
5> CCe 2.50 Poof and vanish act.
6> Causes Gabest's MediaPlayerClassic (MPC - 6.4.3.1) to crash instantly when attempting to play an avs script.
7> From seewen's thread below, Crashing in VDub, VDubMod, DVX

/Edit: the warpsharp and loadpluginEx.dll are incredibly useful and fine work from the programmer who did it. Perhaps he will do an upgrade that will not have these problems (version with problems are in warpsharp_2003_0121.cab). Until then, they just need to be in a separate directory so that they will not autoload. Use loadplugin ("") to use.

[seewen]

I'm happy to read this, beccause when I asked about it, I thought that the problem comes from my comp.

http://forum.doom9.org/showthread.php?s=&threadid=49270

[DDogg]

I updated the list above. I suspect quite a few random problems reported may have been caused from autoloading this plugin. I wonder how one plugin could cause all this. Sh0dan, could you comment?

[mrwho]

Looks like the same old problem as with version 911a :(

http://forum.doom9.org/showthread.php?s=&threadid=39185

[Ookami]

Ok, here's a part of the mail I got from GuiltyX:

(...) only way to solve the problem is "DO NOT USE Avisynth2.5x's AUTOLOAD"(means don't put WarpSharp.dll on plugins dir)

i think this is cause of the function that warpsharp.dll can load 2.5x
plugins on 2.0x system and load 1.0x/2.0x plugins on 2.5x system, using
"LoadPluginEx.dll".

(...)

# WarpSharp.dll have 2 Interface(v1 & v2, default Interface is v2) to
load itself.
# e.g.
# load on 2.0x system
LoadPlugin("LoadPluginEx.dll")
LoadPlugin("warpsharp.dll")
WarpSharp()

# load on 2.5x system
LoadPlugin("warpsharp.dll")
WarpSharp()

newest version is the link below.
http://www.geocities.co.jp/SiliconValley-PaloAlto/2382/


Hope this helped.

Cheers,

Mijo.

[DDogg]

Ookami, thanks for posting the verification of the problem.

I hope the author puts a warning in the docs. Also, if he has not, maybe Wilbert can put something with the Dust example on avisynth.org This really caused me some lost hair and I suspect many others.

This plugin is really useful and well worth living with this one odd anomaly.

To anybody not reading this whole thread, if you are using Avisynth 2.5x, don't put Warpsharp.dll or loadpluginex.dll it in the plugin dir because when it autoloads it causes strange and unusual problems. Just use loadplugin in the script to load either of them from their own directory and everything is great.

[Wilbert]

maybe Wilbert can put something with the Dust example on avisynth.org
I already planned to do this. But I'm incredible busy right now, and I don't have time to update the faq. Maybe on friday ...

[AS]

Well, another alternative to warpsharp is MarcFD's awarpsharp, which doesn't have this problem and uses the 'original algo', as he calls it