My TMPGEnc won't open .avs scripts with either OpenDML or DirectShow anymore.
I am 99% sure it once did, but for some reason it doesn't work anymore.

I can open the .avs script file with MediaPlayer, no problem there.

If I chose AVI VFW compatibility reader it works, but either AviSynth or the file handler work some bad magic on the colors. It's got to be the VFW reader, since the the synth'ed video looks all good in WMP...

I guess it's time for a fresh windows soon. I have installed, tested, and deinstalled so many codecs/filters in the last months that there must be junk all around in the system directories...

Hi b00n:

Increase the priority of the DirectShow Multimedia file reader in TMPEG.

-kwag

Ah thanks. Tried that already.

I had ffdshow installed, perhaps there are some problems due to that.
It's a direct show "plugin", and can be used to optimize post-processing of DivX XVid and some other movie types (Including Luma and Chroma level fixes).

Perhaps the uninstall left some parts of it...

greetings,
b00n

my friend got avisynth to work with the d2v files. He said he downloaded the latest DirectX (DirectX 8 i guess). Once he installed that, he said TMPGEnc would open the avs script but the colors were all weird and messed up. Then he got the Huffy codec and everything working fine. Hope this helps someone else.

"Cannot open or unsupported" error message from TM
 

I've had the same problem, can't open film.avs from Tmpgenc. Try to uninstall avisynth and then install dvd2svcd (download it from doom9.org).
I use win ME and now it works.

The dvd2svcd trick worked for me too!

Cannot open or unsupported" error message from TM
 

I don't know if this has been suggested or not.

Have you tried loading the .d2v file directly into TMPGEnc? Did you move the file from it's originial directory? Is the avisynth.dll located in the system32 directory and registered correctly?

G

I was pulling my hair out on this one for several days :angryfire: , so I'll post my solution, hoping someone will run across it with search.

I knew AviSynth worked on my Windows XP box, as I had tested the Version.avs and other samples.

It was an older version though, so I unregistered avisynth.dll, deleted the directory and reinstalled with latest 2.07 installation file.

But I kept my Plugins directory, with the various plugins I had already downloaded. And I set the registry key to point to the directory.

And then I couldn't open any .avs files in anything, not even WMP. I tried three solutions involving a TmpGenc patch, AviSynth patch, and changed to the VFAPI environment settings, nothing worked.

Turns out I also kept a few of the sample .avs files that had come with a recent plug-in download -- they were in my plugins directory. Bad news!

The lesson?

:!: Don't keep any .avs scripts in your plugins directory, or AviSynth scripts won't load in any app! :!:

(Thanks to Zep's post on Doom9, I figured this out from that...)

PS: One error I got in Windows Media Player (WMP) when opening .avs files was "your computer is running low on memory"; even though there was over 300 MB free at the time. That could be a hint to check the plugin dir...

I spent a good 6 hours trying to figure out why Media Player suddenly started reporting that it was low on memory when it wasn't. I reinstalled AviSynth, codecs, commented all the lines out of my script and everything. Being a systems engineer, my thoughts first turned to corrupts apps or DLL's causing a problem and I fought the problem as though it was a system problem. Although I did a few searches, this thread didn't show up until I put the right keywords in.

Turns out that I had the oldplugins.avsi file in my plugins folder that was causing it. (put there from reading another thread on this site for autoplugins loading that I never implemented) It's been there the whole time, but today my system decided it wasn't cool.

So, it doesn't have to be a file with an AVS extension. AVSI will kill it too.

There went 6 hours of available encoding time!