Log in

View Full Version : Avisynth 32-bit in Windows x64?


Ferux
2nd October 2006, 10:57
I never found any information on this, and the search didn't work either.. I'm trying to run the normal Avisynth (version 2.5.6a, october 28, 2005) on Windows x64, but every time I try to open an .avs file, I get an error.

AVSEdit says: 'An error occured while opening the AviSynth script.'.
Virtualdub says: 'Avisynth open failure: Avisynth: script open failed!'.

Is there a solution for my problem?


thanks

actionman133
2nd October 2006, 23:39
Post your script... it might be a syntax error, rather than a system problem.

nibbles
5th October 2006, 08:37
Type this one line script in notepad, save it and open it in VDubMod. What happens?

Version()

I have both 32bit and 64bit avisynth running on x64 at the moment.

Ferux
14th November 2006, 16:00
When I try to open it with

- Virtualdub 32-bit, I get the same error
- Virtualdub 64-bit, I get 'AVI Import Filter error: (Unknown) (80040154)
- VirtualdubMod, I get 'Microsoft Visual C++ Runtime Libary, Runtime Error!, Program: E:\Program Files\VirtualDubMod\VirtualDubMod.exe, abnormal program termination'.


I have installed the latest AVISynth 32-bit version (RC1).

It really can't be a syntax error since the only line in the script is 'Version()'. I also tried it with 'Blankclip()', same errors..

zambelli
15th November 2006, 00:53
What are you opening it with? If you VDub is 64-bit too, it won't be able to open the script because a 32-bit Avisynth DLL can't be linked inside a 64-bit VDub process.

Ferux
15th November 2006, 02:35
With my previous post I wanted to say that it doesn't work, with whatever program I try to open it.. Actually my goal is to open it with MeGUI, but that doesn't work, just like the other programs mentioned above.

Short: I try to open it with Virtualdub 32-bit

Ferux
18th November 2006, 21:18
Maybe there is a problem with a codec I installed. But is there a method to see all the codecs installed, a way that I can see wether they are 32-bit or 64-bit? Or can't the codecs be te problem?


Short: up :)

squid_80
23rd December 2006, 07:44
"script open failed!" errors are normally caused by plugins that fail to auto-load. Move everything out of the \program files (x86)\avisynth 2.5\plugins directory and try opening a script with one line:
version()
If that works, add the files back one at a time and keep re-opening the script until the error occurs.