Cannot open or unsupported - error message from TMPGEnc
 

I keep getting this error message when trying to read a .avs script into TMPGEnc. I don't know why. I'm using version 1.76 of DVD2AVI and verion 2.56 or 2.54 of TMPGEnc. I get this from either version. Here's my script:

LoadPlugin("C:\unzipped\mpeg2dec_dll\MPEG2DEC.dll" )
mpeg2source("D:\Videos\pokemon5\pokemon5.d2v")
BilinearResize(704,480,8,0,704,480)
TemporalSmoother(2,2)
AddBorders(0,0,0,0)
#Trim(0,99834).FadeOut(150)
#ResampleAudio(44100) # CCE 2.5 'crashfix' for Athlons
#== If you want this 'fix' permanently, edit the INI-file:
#== Under [AVSscript] set the CCEcrashfix-option to
#== CCEcrashfix=1

Help please.

Andy

You did install the avisynth.dll. Did you register the .dll?
By clicking in the INSTALL.REG file.

kwag

Thanks for replying, Kwag. Yes, I installed the dll and ran the install. Oh, well. Maybe I'll try uninstalling and reinstall?

Andy

Oh, also, I could read the sample .avs files that came with the avisynth.zip download. I did get a message in the TMPGEnc preview window that it couldn't find the necessary mpeg2source d2v file, but that wasn't unexpected. At least I didn't get the "could not open" error dialog box. Hmmm.

Andy

i'm trying to install avisynth on my friends computer and i'm having the same problem. I have installed everything on my computer at it works fine. I have done everything the same on his computer as i have done on mine, but i am unable to load an avs script with tmpgenc. Any help would be appreciated. Thanks

Check where your avisynth.dll is installed.
I believe if you're using Win98 or ME, there's no system32 folder ( I think, don't remember now ). So they would go in system folder. Not sure about that though 8O . I'm on XP.

kwag

i have windows 98, and so does my friend, and on both computers i put the avisynth.dll into the system folder. On mine it works, on his it doesn't. Also windows 98 has both folders, system, and system32.

Well, I'm about ready to give up on avisynth. I moved the .dll to my windows\system file. No change. I'm using windows 98SE. I've downloaded an avi_synth patch from doom9 as suggested in another thread. No change. I can read the 3 sample .avs files that came with the avisynth download zip file, without this error message. Is it possible that there is a compatibility problem with my .d2v file or the audio file?

:cry:

Thanks to all for your suggestions.

Andy

Andy are you 100% sure that the .d2v you created was done with DVD2AVI version 1.76?
If it was 1.77.x, it won't work with AviSynth, because they changed the .d2v structure.

-kwag

Thanks to Kwag and all others for your help with this problem.

Kwag - I'm 99.44% sure I'm using ver. 1.76 of dvd2avi. I'll triple check when I get home.

Andy

well, my friend and i went so far as to reformat and reinstall windows on his system in an attempt to get avisynth to work. We didn't have any luck. I installed TMPGenc, avisynth, dvd2avi....everything else i could think of and it still didn't work.

Did u try this ??? It could be the answer to all your prayers :-


http://www.doom9.org/Soft21/SupportUtils/avs_patch.zip

Unzip it and install into your tmpgenc directory. Close the program and restart.....your troubles are over :D

what is the avs_patch for anyway? i didn't use it on my system.

I tried the avs_patch, but it didn't seem to do much of anything and I couldn't find any explanation of what it's supposed to do.

I'm 100% sure I'm using DVD2AVI ver. 1.76 - I checked last night.

I've placed the avisynth.dll in the \windows\system directory. I'm using Windows98 SE.

MGEG2DEC.dll is in it's own directory.

I tried recreating the .d2v file from the ripped .vob files - no change.

I did, however have some trouble ripping all 4 vob files from the dvd. It was rather dirty and cleaning it allowed me to rip all 4 vobs completely. Any chance that this may be causing me trouble?

I have been able to just load the .d2v and audio files into TMPGEnc and encode the video with the KVCDx2 templates and since it's just a 4:3 full screen NTSC Pokemon video for my son, that's fine, but I'd like to get this to work for real movies.

Thanks to all for your suggestions.

Andy

AVS workaround
 

If your having trouble with the AviSynth mpeg2dec.dll a quick work around is "VFAPIConv"...

Since AVIsynth uses various type of inputs, try converting your "Movie.d2v" from DVD2AVI to an "Movie_d2v-vfapi.avi" ext. using "VFAPIConv-EN.exe". This actually just takes a second and only changes the d2v extention to .avi....
http://www.digitalfaq.com/archives/i.../2002/07/2.jpg

If you want to try an .avs script, just load this new "Movie_d2v-vfapi.avi" in FitCD and your script will now have your source as "AviSource":

Script example:
#LoadPlugin("C:\Codec\MPEG2DEC.dll")
AviSource("C:\Movie_d2v-vfapi.avi")
BilinearResize(704,352,0,0,720,480)
#TemporalSmoother(2,2)
AddBorders(0,64,0,64)
#Trim(0,101263).FadeOut(150)

If it takes it..save and load xxx.avs into TMPGEnc...Now if you have problems in TMPGEnc, check your "Environmental setting=>VFAPI plug-in for right .dll and priority settings)this should allow you to work with .avs scripting...


You can download it Here. 8)

Why does the color look more dull and and the contrast is off when you use vfapi to make an avi file in avisynth so tmpgenc can read it? Is there any way to correct this? I added the ConvertToYUY2() line to the avisynth script, but the color still looks off compared to when i use the d2v file in avisynth.

You don't need to create a pseudo avi file from a .avs with VFAPI for use with TMPEG. Just open the .avs script directly with TMPEG.

-kwag

well, not to sound like a smart ass :? ....but, the whole point of this thread is that we can't get avisynth to work with the d2v file in tmpgenc....so slab suggested using vfapi converter to change the d2v file to and avi file because aparently tmpgenc will open avs scripts the with avi files as the source, but not d2v files.

You don't sound like a smart ass at all Smoochie3!, I'm the idiot that didn't read the subject carefullly 8O
So maybe I should get some sleep ZZzzzzzz.... :lol:

-kwag

Hi Smoochie,

Yep, it's just a work around for using avs scripting...I don't really see how accessing the source(vob) files whether it's by ".d2v" (ie... mpeg2source("D:\MyMovie.d2v") or a "d2v-vfapi.avi" (ie... AviSource("D:\MyMovie_d2v-vfapi.avi") makes any difference, they both accomplish the same thing in my book... Choose whatever works for your system, unless I'm missing something magical about the Mpeg2dec.dll, or the way the vfapi.avi converts a .d2v to a virtual .avi file?

Anyway, as for color and contrast saturation, I prefer checking "Output YUVdata as Basic YCbCr not CCIR601". Just a personal taste for my TV...Try some test clips.... 8)

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!