Posted 17 May 2008 - 03:12 AM
I have more info and it really is complete voodoo. I already mentioned that I've already seen "error -39" in Toast8 once, but that other thread was closed, so I now post the update here.
I get error -39 (unable to read some .vob file) *very* frequently when compiling several mpeg-1 files into a DVD with Toast 9.0.2
Several observations:
1) The error is getting worse after Toast was "used" before - like setting up DVD menus, importing/moving files, renaming titles etc. As a matter of fact, after using Toast for more than 4-5 actions it is actually *impossible* to burn a DVD (or export to a disk image) without the error.
2) As a result, I do this: First set up the disk, then save it. Quit Toast. Launch Toast and then export to a disk image *immediately* without using anything else in the Toast GUI. This works in 98% of all attempts.
3) If it fails, quit Toast again, try it again - it usually works *then*
4) The "failure" has different variations - most of the time it is "error -39", but very often the writing to the disk image stops "silently" - meaning that Toast just stops at some percentage and returns to the GUI - without any error message! The disk image, of course, doesn't exist afterwards.
5) Sometimes it also starts to re-encode a single file instead of multiplexing... I always stop it, quit Toast, restart. It then *never* tries to re-encode again and just multiplexes.
6) Finally, the oddest thing. I now got a DVD that failed 10 times in a row - Toast9 always cancelled "silently", but at different percentages - once at 20%, then at 67%, then at 50%...
I tried Toast8 (twice) and it crashed during the writing. *Then* I tried Toast9 once more - and *then* it worked!
Conclusion: The errors have nothing to do with the specific files, otherwise the errors would show at the same times/percentages. It sounds *very* much like initialization errors of variables. If you launch Toast and just start to export, the RAM is still zeroed. If you work with Toast before, the memory is flled with previous data and then - obviously - it goes crash boom bang.
Of course it's not my business to give technical advice to Roxio, but I would seriously check the compiler optimization, compiler directives and all class constructors - including the Toast8 sources.
1
