We all know it's true. Nero Vision Express will drive you crazy if you let it. I know I've pulled my hair out more than once, due to NVE... The biggest (and most frustrating) problem I have experienced is with transcoding. Not only does it take forever, but if your avi file has even one frame corrupted, the entire transcoding process will fail - often after running for hours - and you are left with no DVD burned. AAAARRRRRGGGGHHHH!!!!!!!! I have found a solution. I am happy to share my new knowledge with all of you. Read carefully. You will need to repair your avi file. It's not hard to do. You need two programs: G Spot (I have version 2.52) and Virtual Dub (I have version 1.6.11). Once you have downloaded both programs, here's what you do: First, determine which file caused Nero Vision Express to crash. If you don't know, it's easy to find out. Save the session log if offered an opportunity to do so. When reading the log, you will see a long list of events with time stamps on them. Read it to see which file was the last to start being transcoded. That's your culprit! Sometimes you don't get the opportunity to save a log after a crash. Don't worry, Nero Vision Express always saves a log of its most recent session. This log file is always saved without any user interaction. It will save the log file to the directory of the program. You can find it by looking in the following location: <Systemdrive>\Documents and Settings\<user>\Application Data\Ahead\NeroVision The file name is NeroVisionLog.txt. Copy this file IMMEDIATELY out of this folder when the error occurs. Otherwise the log file will be overwritten if you restart Nero Vision Express. If you cannot find the log file in this folder, check this setting: In Windows Explorer select Tools > Folder Options > View > Hidden Files and Folders > Show hidden files and folders. Confirm this change with "apply" and "OK". Now the log should be visible. After you know which file has a corrupted frame, start up Virtual Dub. Select "Video" and then "Compression." A dialog box marked "Select Video Compression" will open. Select "ffdshow Video Codec" if you have that one installed. If not, either get it or choose something else and cross your fingers. I have only tried this system using ffdshow, so I can't guarantee that any others will work - but they might. After you select "ffdshow Video Codec," click the button labeled "Configure." A new dialog box will open. You need to set the "Encoder" and "FOURCC" values both to match the encoding which was used when creating the file originally. For example, Xvid or DivX 3 etc... To find out which values were originally used, open the file using G Spot. In the "Video" section of G Spot's display, it will identify the type of encoding your file has. Set the two values in Virtual Dub to match whatever G Spot says it is. At this point, you are done with G Spot. Close it any time you want to. Click "OK" on each of the two Virtual Dub dialog boxes, and return to Virtual Dub's main menu. Select "File" and then "Open video file." Browse to the file which is causing Nero Vision Express to fail, and open it. Remember, you have already set Virtual Dub to match the proper codecs for this file... Select "File" again, and then "Save as avi." Choose a file name for the newly repaired file which you are about to create. Then click "Save" and let the program run. Repairing a file takes about the same amount of time as watching it... so, a 90-minute movie will take about an hour and a half to run in Virtual Dub. When Virtual Dub is finished, run Nero Vision Express using the new repaied file. You can delete the old one at any time. You don't need it any more. Your DVD should now transcode with no more problems! Disclaimer: I am not a computer expert. I simply found something which worked for me. It should work for you too... but I offer no guarantees. If your problem is being caused by something different than mine, then this may not solve it for you. Give it a try anyway. It's worth a shot! Good luck.
thanx for your effort in sharing this with us. but once you've determined which file takes forever to transcode, the easiest way around it is to export the said file individually onto your hard drive and then reload it & replace it with the original offending file. i'm not an expert either but i stumbled across this workaround while i was ezperiencing the same transcoding probs.
