AviSynth conflict

[GoogleCodeExporter]

"I hope I explain the following correctly since I just experienced this while 
looking around for solutions to the color shifting:

I had to try the above avisynth method in a different Vdub folder because in 
the 1.10.0 experimental version I couldn't open AVS scripts because the 
FFinputDriver was put into plugins32 folder. There seems to be a conflict with 
opening AVS file with that driver included. I verified this by removing those 
driver files out from that Vdub directory and I was able to load AVS files once 
again.

The only thing that came to mind was that the FFinputDriver accepts only RGB32 
format but by drag/dropping the file the video should open regularly since I'm 
using AVIsource in the script. Just for ha-ha's I entered the ConvertToRGB32() 
line to see if the FFinputDriver was in fact loading the AVS script but I still 
got the error?

Update: I just copied the FFinputDriver files to Vdub 1.9.9 and the same error 
happens. When I put the files into Karl's Vdub directory there is some extra 
information such as "failed loading ffavisynth.dll" (ffavisynth.avsi, line 1)" 
Happens with AVIsource and DirectShowsource.

Does this mean that the FFinputDriver is taking over when it is put into the 
plugins32 directory or is there a conflict going on?"

http://forums.virtualdub.org/index.php?act=ST&f=5&t=20155

Original issue reported on code.google.com by aka.xzi...@gmail.com on 27 Jun 2011 at 1:27

[GoogleCodeExporter]

Removed AVS file type support.

Original comment by aka.xzi...@gmail.com on 28 Jun 2011 at 2:37

• Changed state: Fixed

[GoogleCodeExporter]

Removed AVS file type support.

Original comment by aka.xzi...@gmail.com on 28 Jun 2011 at 2:37