|
Well, I've tried asking at vcdhelp.com, but nobody's bothered to respond, so I'm hoping you guys can help.
Here's the deal:
Up until the other day, I've ripped probably 100 DVDs to VCD following the same procedure and haven't had a single problem. I rip with SmartRipper, assemble with DVD2AVI, load in TMPG.
The other day, I was in the middle of an encoding job when my PC's power supply decided to crap out, causing the system to lose power. After getting things back up and running, I tried to start the project again and ran into the problem that continues to plague me.
At any given point in the encoding process, the thing may crash and give a "Read Error in dvd2avi.vfp" message. Usually the system begins slowing down before this happens, i.e., TMPG begins encoding very slowly and there is very little hard disk activity. However, this system slowdown doesn't seem to ever happen unless TMPG is open, so I don't think it's just something amiss with the PC.
This has happened on at least five different movies, usually never in the same place twice. The most recent time it did this, it had made it to probably 70-ish percent, but I don't know what the error message was because it just shut down the whole PC.
I've deleted and reinstalled both TMPG and DVD2AVI more times than I care to count, tried using different versions of both, and have even gone as far as to scour the registry for any traces of it to clear them out before a reinstall. I'm convinced the problem lies solely with TMPG and not with DVD2AVI, since it happens with other, non-D2V files too (except then, the read error is in tmpgenc.d2v).
I've defragged, I've virus-scanned, I've adjusted the priority settings, nothing's worked. I read somewhere that these read errors can sometimes be caused by faulty RAM, but after using the RAM testing program recommended at the site, everything came up okay. Nothing happens in the Event Log when these crashes occur, either.
I've Googled around enough to tell that I'm not the only person this has happened to, but unfortunately, if the other folks have ever figured out their problem, they didn't post the answer. It just doesn't make sense, especially since everything worked beautifully up until this point.
If it helps, my system is an Athlon XP+ 2000 with 512mb RAM running XP Home.
Any help you could give me would be greatly appreciated. I'm practically losing sleep over this, it's become a mission to figure out what the hell's causing it.
Thanks in advance.
|
