Avisynth + TMPGEnc 2.56/2.57 = Frustration

[bewley]

Just recently I updated my machine to:

Athlon XP 1800+
512 PC2700 DDR RAM
EpoX 8K3A Mobo (Apollo KT-333)
Avisynth 1.06
TMPGEnc 2.56

Running Windows 98 SE.

In the past I was able to capture video with my DC10+ card, frameserve with Avisynth, and encode with TMPGEnc. With the above setup, I either receive an Illegal Floating Point or Read Error In Module TMPGENC.EXE. At first I figured it was the new rig, but then I went back to version 2.54 of TMPGEnc and everything worked like it did on my old machine. Today I upgraded to TMPGEnc 2.57 and the same errors occur as in 2.56.

I have tried mucking with all the VFAPI Plugin settings in TMPGEnc-- disabling Directshow, setting ReadAVS (version 0.1 -- is there a higher version?) to a priority of 2, setting the AVI plugin priorities higher, and even frameserving through Vdub and VFAPIConv. I have turned off power saving, screen savers, closed all running programs, and tweeked my cache settings. Nothing is working at ALL and the errors persist!

Is anyone having success using Avisynth with TMPGEnc version 2.56 or above? Any recommendations for versions of Avisynth or ReadAVS? At this point I can't think of anything else to try!

Any and all help is appreciated.

[MoovyGuy]

What version of D2VAvi are you using ?

If you are using the new 1.77xxx then this is your problem as the format if the .D2V file changed.

If your .AVS script is referencing a .D2V file, then the .D2V file needs to be gernerated with v1.76 of D2VAvi. This is the last version that Avisynth will understand.

[bewley]

Thanks for the reply, however, I am not using D2VAVI -- but I am using the mpeg2dec plugin.

After another weekend of all nighters, I have made some headway. I clocked my PC2700 RAM down to PC2100 and things run better. The Floating Point errors are gone and now it blows up with a Read Error at xxxxxx in module TMPEG.ENC at memory FFFFFF. This happens in the 3 - 5 hour mark.

I think I am going to try swapping out my memory and see if it works with a new stick...?

[TomSem]

i ve the same problem
and i m using dvd2avi 1.76
this is my script

LoadPlugin("c:\winnt\system32\mpeg2dec.dll")
mpeg2source("c:\dvd\thx.d2v")

i ve tried all diferent versions of mpeg2dec.dll found on the net
and i m using avisynth 1.6.
TEMPG gives me an error while opening the avs file
and mediaplayer tries to download a codec ... cant not find codec

please help

[mb1]

Tmpeg cannot open YUV-Format (like CCE).

Add the line
ConvertToRGB24
to the end of your script and it should work.

@ bewley
PC 2700 RAM was a bad bought as it is slower than PC 2100 RAM atm on all KT-333 Boards.

Clock your RAM down to CL333 for testing purpose (and don´t overclock your cpu).

regards
mb1

[VidGuy]

Per my post in the other thread - It's not true that CCE or TMPGEnc can't handle YUV - I use DVD2AVI 1.82, AVISynth 1.0 beta 6, CCE 2.5 or TMPGEnc 2.56 Plus on WinXP and have no issues - I always rip to YUV
and both CCE and TMPGEnc can load and use the *.avs file.

[mb1]

CCE of course can handle YUV. "Like CCE" was meant the way that CCE can and Tmpeg cannot.

In fast I didn´t find the info in Tmpeg site (and Tmpeg help file) but Edwin from Videotools.net did a lot of research work on opening YUV material.
Take a look at the lines written at the bottom ...
http://www.videotools.net/guides/guide_testing_the_wrapper_client.php

In some cases tmpeg can open YUV. For example if the appropriate codec is installed, like a dv codec. PAL dv is YUV 4:2:0 and NTSC dv is YUV 4:1:1. Both can be opened directly by Tmpeg but they are converted internally to RGB for encoding purposes.

As far as I know, only Windows Media Encoder v8 (YUY2, YV12) and Cinema craft SP (YUY) encoder are able to encode to encode YUV

Warning: If your encoder is able to encode "video_only_YUY2.AVI" or "video_only_YV12.AVI" you do not know for 100% that your encoder is encoding the YUV format as other installed codecs could convert YUV to RGB for the encoder

Quote from your other reply

always use DVD2AVI (1.82) in YUV mode, and use the *.avs file with either TMPGEnc Plus or with CCE 2.5 and have had no problems at all.

If you select YUV in dvd2avi options this affects only direct avi output or d2v loading per mpeg2dec(2).dll
All other ways are processed in RGB no matter what you select ...

regards
mb1

[bewley]

@ bewley
PC 2700 RAM was a bad bought as it is slower than PC 2100 RAM atm on all KT-333 Boards.

Clock your RAM down to CL333 for testing purpose (and don´t overclock your cpu).

Actually, I clocked my PC2700 (DDR333) RAM down to PC2100 (DDR266) and the Illegal Floating Point errors went away... And I have never overclocked my CPU!

Anyway, last night I made the following two changes:

* Click on the Do not use cache function by OS under the "General" tab

* Disable saving 2 Pass VBR analysis to a reference file under the "CPU" tab

I ran the project using "High Quality" and it completed successfully. I then re-ran the project using "Highest Quality" and it errored in the last few seconds with a "Stream Read Error". However, since I use "Blackness(240)" as my last statement, cutting a couple of seconds off is not a problem. I am now running a third test where I have re-disabled the Do not use cache function. So far so good.

If I was a betting man, I would say that having TMPGEnc build the 2 pass file is the problem. Sadly, not using this option makes the encode take about 25% longer... But I suppose I rather wait a little longer than have no encode at all!

[Truman]

I always work with YUV sources, either MPEG-2 or huffyuv. I use dvd2avi 176 and Avisynth 106 at the moment. Encoders are ccesp250 and TMPGEnc 257plus. I have no problems to encode with TMPG. If you have huffyuv installed, maybe it helps to add VIDC.YUY2 "huffyuv.dll" to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32.
If you are running win98, you may edit the system.ini ([drivers32] section).

[Cooly-O]

In the past I was able to capture video with my DC10+ card, frameserve with Avisynth, and encode with TMPGEnc. With the above setup, I either receive an Illegal Floating Point or Read Error In Module TMPGENC.EXE.

Start Avisynth before TMPGEnc tries to find the file.

You might want to re-read the "Problems" section of How to convert to VCD with TMPGEnc (I know you've tried some of these already).

A partial list:
If TMPGEnc freezes or crashes when converting or you receive errors such as
Unexpected decimal point calculation
Illegal floating decimal point calculation order
Try first to change the codec reader settings in TMPGEnc under Option->Environmental settings->VFAPI plug-in and right click on the DirectShow Multimedia File Reader and increase the priority to 1 or 2 and try open the video.
Or try to convert the audio to wav before converting.
Or try to repair the AVI,DivX or the ASF.
Or try to use avidefreezer to fix your video source.

[bewley]

You might want to re-read the "Problems" section of How to convert to VCD with TMPGEnc (I know you've tried some of these already).

Thanks... But I did ALL of those things first. Also, searched this forum and TMPGEnc's forum...

As I posted later on in this thread, I resolved the Floating Point by tweaking my memory. I guess it is true that you get what you pay for... I should have spent a little extra and bought some high quality memory.

[lpn1160]

sometimes newer isn't always better. I'm frameserving with huffy into tmpgenc 12a, mpeg2 support doesn't time out, never an error and a 2 hr. film takes 4 and a half hours, plus the quality kicks ass over later versions of tmpgenc.

[sterno]

sometimes newer isn't always better.

Heh, I have to agree. I just went through an entire evening of work trying to figure out why any even slightly busy scene in an encoded movie looked horrible, and fixed it by dumping tmpgenc 2.57 for something older. I didn't take the time to narrow the problem down to the encoding or the new MPEG2 reader (I had to install a new codec to load MPEG2), I just loaded the file in the old version and it worked flawlessly.