Avisynth "Cannot Open" Error -- a Solution!

[easymenu]

There have been a couple of threads on the problem of not getting AviSynth to work ... sometimes even on the same system after an O.S. reinstall.

My own experience suggested some kind of missing codec problem. In pursuing that direction, I discovered advice by sh0dan, in the official AVS bug report forum, that the Huffyuv codec usually helped to fix that problem.

I DL'ed Huffyuv from http://math.berkeley.edu/~benrg/huffyuv.html, installed it, and, suddenly, AviSynth worked!

[CheronAph]

Thanks for the info!

[Tutankhamun]

Hey easymenu thanks for the post but I have tried everything such as install Huffy, Nimo and uninstall and reinstall avisynth and it still wont open in tmpgenc 2.53, 58, 59 and 510. I did a search on my system and made sure no other avisynth.dll anywhere. I had another post about my issues as I have two computers and the new one is soley for dvd rip and my other one has downloaded episodes that I am wanting to work on. After creatig script, I try to load and keep getting error. I then tried the ReadAVS.dll and it wont stay recognized by tmpgenc. But I wont give up! Spring break next week and I will have more time to figure it out!

[easymenu]

Sorry to hear that the "huffyuv install" is "a solution", not "the solution".

You've probably tried anything I could suggest, but allow me to suggest one basic test:

Make a script with only the word version in it. Name the file something like test.avs . Open it in TMPGEnc (doesn't matter which version, but for the sake of testing, always use the most recent versions of everything) and see if AviSynth version information is displayed. If so, then you know at least that your AviSynth is working.

EDIT ADDED -- The "version" script will show up ONLY in "media player 6.4" (MPLAYER2.EXE). It will NOT show up in either "media player 4" (MPLAYER32.EXE) or "windows media player" (WMPLAYER.EXE). So be warned if you are using Windows player(s) for this test.

BTW, AviSynth 2.0.7 is the latest release of the 2.0.x series. That is probably the best place to start. Also, if you've tried a number of different versions, uninstall them, and delete the leftover file avisynth.dll from your windows\system or windows\system32 directory (can't find it? do a search). Then install the new version of software.

Run out off ideas? Post a bug report (very informal) over at the official website and maybe the author(s) will suggest something more.

[Tutankhamun]

Hey easymenu, I did a search of my system and no avisynth.dll but I did find one avisynthEX.dll !! Not sure what, when or how I got that in there. So I just deleted from the system folder, actually did a copy to floppy incase it is needed for something else, and going to install avisynth 2.07 again. Hopefully that is or was the problem. I'll see what happens

[Tutankhamun]

For all of those that read this thread with the same problems as I, this is how I finally fixed it. I deleted every read me file and every sample script that loads when you unzip a filter to the plug-ins folder. I then deleted the configuration setting file that Tmpgenc drops after the first time you open the program. Next I installed the read avs patch per the instruction. I then opened Tmpgenc and it dropped a new configuration file. Now when I open tmpgenc and check the settings under environmental settings it still shows the readavs. And finally, now it will read my scripts