"Issue" with crash recovery and CCE and CRC errors

Ok - I did a search and didn't find anything about this. So here goes. I have, a number of times, canceled a CCE conversion AFTER the VAF file was created. Most of the time I can "crash recover" with no problem, but sometimes I would get the famous "CRC" error. I was going to try the "Patch" but decided to look into the matter more. I tried running CCE by itself and reload the ECL file. When I did this there was no CRC error. So I copied the ECL file and then ran a crash recovery. DVD2SVCD recreated the ECL and when CCE ran - CRC errors. I compared the two ECL files and guess what - they were different by ONE character. The following line was changed Original ECL file top_first=0 New ECL file top_first=1 As you can see the setting for this has been changed when DVD2SVCD recreated the ECL file. This brings up two issues. 1) When you do a crash recovery and you keep the VAR file - perhaps DVD2SVCD should not recreate the ECL, but just load the one that is already there. 2) If you restart from video encoding, there is a chance that DVD2SVCD will change this setting and you would not even know it. I would have to guess that this would change the outcome of the encode? The second item above might be a bigger problem than I think??? My solution will be to run CCE by itself and load the original ECL file. Once conversion is done I will then crash recovery from the next step. Bryan

The patch works just fine, there's no reason to devise workarounds, using the patch fixes CRC errors in mere seconds.

Uhh - I think you missed the point 

The point being that if you do a crash recovery then DVD2SVCD recreates the ECL file that is used by CCE. There is a chance that the ECL file that is recreated is NOT the same as the one that was orginally created. THIS is what is causing the CRC errors. The workaround is because there is a "ISSUE" with the way crash recovery recreates the ECL file. The CRC patch is ABSOLUTELY the wrong way to fix this "issue".

Perhaps I did miss the point, but I highly doubt that if your findings were truly troublesome, that this would be the first post concerning it. Maybe it's worth further investigation...

Besides the reason in this thread, if you are getting CRC errors its because the data is wrong. If you apply the patch you are encoding the wrong data. When I had CRC errors I worked on the problems untill I was able to encode with no CRC errors.