tmpgenc read error can't solve

[ElAguila]

I have searched through this forum and some others about the problem I am having. I have installed the latest version of tmpgenc. When I try to encode avi's I get the read error at various points during the encoding. I have tried the solutions listed here but no help. I have rebuilt my machine with a fresh install of Windows XP and installed tmpgenc once again. Still having the same old problems. It seems to be worse with xvid avi's.
I have tried changing the priority for the directshow filter and I have even tried frame serving from virtualdub with no luck. Sometimes it gets 80% done and then gives me the read error and other times it gives me the error after 5%. Everything was working fine few weeks ago. I don't what could have changed in my system but the rebuild should have corrected it(at least I thought it would.)

[ElAguila]

An update for others who may be having the same problem. I am unable to do divx as well as xvid. I am retesting after making some changes. I have removed the divx 5.03 codec and reinstalled the 5.02 codec. I also removed the tmpgenc and installed 2.58. We'll so how this goes. After retesting I have discovered that the problem I am having is with the inverse telecine. I only have the read error when going from a film type and never when using a video type source. I am going to test removing the telecine with virtualdub and then frame serving.

[Cabadam]

I get same error (I think anyway - you didn't give the exact error). It happens as soon as I hit Start to encode. Have tried this with both an older version I had. Also just tried to download the new version demo, but it did the same thing.

http://cabadam.homeip.net/tmpg2.gif


"Read error occured at address 00402F40 of module 'TMPGEnc.exe' with 20656850."

[ElAguila]

Well it is also non telecine as well. It is not just downloaded files either. I used dvd2avi and it crashed using it as well. It is not due to corrupt files. The same files will process all the way on another system. They are ones that processed on my previously. I don't know what is happening with tmpgenc.