Avisynth 2.5.5. does not recognise the script.

[vcmohan]

A few days back I downloaded the new 2.5.5 and installed. I find that it has reporting avisynth script errors for the same script which I have been using for 2.5.3. Is there any change for this version?
OOps! Going thru the 2.5.5 thread I find that I need to use a prefix for my plugin function name. Since DirectShowSource() is also a plugin does it also require a new notation? Does DVX automatically correct for the new notation?

[stickboy]

Originally posted by vcmohan
A few days back I downloaded the new 2.5.5 and installed. I find that it has reporting avisynth script errors for the same script which I have been using for 2.5.3. Is there any change for this version?Post your script.
OOps! Going thru the 2.5.5 thread I find that I need to use a prefix for my plugin function name. Since DirectShowSource() is also a plugin does it also require a new notation? Does DVX automatically correct for the new notation?The prefixes are not required. They're optional and are there to resolve namespace conflicts.

(For some reason, they also are used only for auto-loaded plug-ins, not for plug-ins loaded explicitly by LoadPlugin. <grumble grumble>)

[vcmohan]

I later tried some of the example scripts given along with Avisynth and they also gave same problem. I installed Avisynth 2.5.5 over 2.5.3 without deleting it first. I remember in some earlier version installation instructions one need to delete the dll manually. I dont think that applies now.
the script used by me earlier and now is below:
loadPlugin ("E:\Program writeups\Avisynth\my attempts\TransAccord\Release\TransAccord.dll")
AviSource("F:\temp\sudha\sudh001.avi").trim(4001,4050)
Left=ConvertToRGB24(last)
vid=AviSource("F:\temp\sudha\sudh001.avi").trim(2001,2050)
Right=convertToRGB24(vid)
#Left=BlankClip(length=100,height=480, width=720, color=$000000ff)
#Right=BlankClip(Left,length=100, color = $ffff0000)
TransAccord(Left,Right, "hor",true,true)

[stickboy]

And exactly what is the error you get?

[lark]

might be a good idea to check the autoload plugins (especially scripts)...

regards
t :)

[Mug Funky]

there's only a couple of internal filters that have changed behaviour recently. offhand i can only think of GeneralConvolution (this only works in RGB, so really it's not something you'll want to use if you want speed and quality).

[vcmohan]

Originally posted by stickboy
And exactly what is the error you get?

The error message is :-
Avisynth open failure:
Avisynth: script open failed

If I switch back to 2.5.3 it works fine.
I have been trying to send this reply since yesterday, but some reason not getting posted.
regards
mohan

[Mug Funky]

try it without "transaccord"... i don't know what this plugin does, but everything else in the script seems okay.

[stickboy]

Originally posted by vcmohan
The error message is :-
Avisynth open failure:
Avisynth: script open failed

If I switch back to 2.5.3 it works fine.
I have been trying to send this reply since yesterday, but some reason not getting posted.Since it doesn't give you a specific error message with a specific line number, it's probably some auto-loaded plug-in or script that is causing the problem. Try emptying your plug-in directory.

[vcmohan]

I recently installed DVX. It has installed a number of plugins in the plugin directory. All these I understand are supported/ tested I assume.The 2.5.3 vesion has no problem with them.
I will empty one by one and check and report back.May be theres conflict of names.
mohan

[vcmohan]

I could trace the problem to a plugin "AntiBlink.dll" which was installed by DVX and which I do not use.

I have read in the manual of Avisynth that one is not supposed to put in this plugin folder anything except the dlls and function scripts. But DVX has put in this folder html, xtml, exe , instal and uninstal stuff. Since DVX I understand is developed in close coordination with Avisynth, I am shocked at this.

[Wilbert]

Since DVX I understand is developed in close coordination with Avisynth, I am shocked at this.
DVX itself is not developed in close coordination with Avisynth, only its editor is.

[vcmohan]

May be you will formally caution them about this

[vcmohan]

I have recently developed a plugin FanFilter and it has been working well on my system even if I keep in the Avisynth plugin folder or outside. Just a few days back a user from Japan reported that he gets an Avisynth error similar to one reported by me above and when he moved it out to another folder it worked fine. It is not clear what exactly causes this error? Is it calling function names clash? Or something other? I often use a older version of my plugin in the avisynth plugin folder and newer version outside without any problems.

[Wilbert]

It is not clear what exactly causes this error? Is it calling function names clash? Or something other?
No idea. I also would like to know this.

[tsp]

if you have to many plugins in the autoload folder avisynth will refuse do run at all. I don't know what's causing it(might be some kind of overflow) but moving some of the plugins away from the autoloading folder solves it. So if the problem disappears by moving any plugin out it might be the cause.

[Wilbert]

Yes, that's also a problem. But it's a separate problem though.

[vcmohan]

I could get over the problem as reported by me above by moving antiblink.dll. However later I have placed several of my plugins additionally in that folder. Its working fine. Therefore atleast here overflow is not the problem. I vaguely remember that some one reported that be moving out some other plugin it worked fine. So just antiblink.dll may not be the problem per se. It may be a combination that may be causing it. The developers of Avisynth may throw some insight into this.

[sh0dan]

There is an OS limit on how many dll's a single process can open. I seem to remember Avery Lee writing about this a long time ago, when it was a problem with Virtual Dub. Can anybody remember some of this?

[Wilbert]

@vcmohan,

So, if you have only antiblink.dll in your plugindir, does that work fine?

[vcmohan]

Originally posted by Wilbert
So, if you have only antiblink.dll in your plugindir, does that work fine?

No. Not in this case. I find that on my system even if antiblink is the only plugin it does not work.

[vcmohan]

A problem of similar nature is reported by ADLANCAS in thread http://forum.doom9.org/showthread.php?s=&threadid=94312

It appears some explanation or reason to be found

[cweb]

I got the same message as the original poster with avisynth 050505.
I had just installed repairsse2.dll in my plugins directory. I then moved it to a subdirectory for the moment, which solved the problem. (I was not going to use repairsee2 after all) It may be the number of dll's in my plugins directory after all like vcmohan reported.