TMPGEnc Error

[BobK]

When I use TMPGEncPlus (30 day trial) and try to encode more than 10-15 minutes at one time I keep getting errors like 'Read error occured at address 0009A16A of Module TMPGEnc .exe with 0B89DC2C'.

Any ideas what's causing it and/or how to fix whatever the problem is?

The source is a mp2 file and a wav file for sound.

[Tommyknocker]

Try to read another file. If you get the same error, you may want to reinstall it. If it reads other files okay, you may have a corrupted file. Then you have to capture it again, or use Source Range in TMPGEnc to encode past the corrupted part.

[jlurgee]

i had the same/similar problem and came to find out that i had bad memory. if you continue to have the same problem, i'd suggest looking into this.

[BobK]

I thought bad memory might be a problem when I had touble with another program a few months ago. The only way I know to check it is to get another memory chip and switch it out with mine to see if the problem clears up, but I have to find another chip to borrow before I can do that.

[Cho~KinG]

I have been having this problem since I started using TMPGEnc (around March 2003) even when continually upgrading. This is not to say TMPGEnc is bad, its still my tool of choice. I think I may have a workaround.

I have only encountered this 'Read error' when encoding .mpg (VCD) to SCVD. After fiddling with different parameters I have found it only occurs when I use 'highest quality (very slow)' motion search precision. Even if I do use highest quality I only encounter this error about 60% of the time, and it usually occurs in the first 15% of encoding.

The problem isn't related to my hard-drive because I just got a new one. It may be my RAM but I haven't had any other read problems in other programs, and I haven't overclocked my CPU so it can't be that either.

To avoid this error I just use 'high quality (slow)' motion precison search. For those who say there is no difference between highest and high motion precision search, IMHO, the action sequences (fast moving foregrounds, etc) look clearer and have fewer artifacts.

This workaround works 100% of the time for me, and is independent of what functions I use (but I mainly use it for .mpg (VCD) to SCVD), so I haven't tried authoring DVDs as such, or using different sources.

I hope this helps some people, for now I just deal with the problem.