CZroe
13th February 2008, 06:36
What's your preferred solution to this simple and common problem? Problem: One applications output files to be burned to a DVD5 disc is reportedly "too big" for a DVD5 according to the application that you want to use it with.
This scenario happens often enough and I usually find some long-way around it, but I'm wondering how you guys usually do it. For instance, if I took the output files from DVDShrink or any number of other "X-to-DVD" applications and tried to burn them using IMGburn, I usually get a message like that telling me that I am trying to squeeze too much on a DVD5 when, if I had let the original app do the burning, it would've fit just fine. I'm usually working with ISOs as output files and all the overhead storage that that requires, so it often said to be too large by several hundred MBs. IIRC, this is sometimes almost half a GB and always far more than I feel I could get away with from overburning.
One more-specific scenario:
DVDShrink successfully burns a disc. I then determine that I needed a second copy and DVDShrink has no way to just load those temp files and burn again, though they were presumably left for this purpose. Doing so anyway, it re-analyzes and wants to re-shrink it unless I do the whole "reauthor" thing again, tell it not to compress and, of course, it generates NEW output. If I want to take a shortcut and use a burning app that I am more comfortable with than the out-dated one DVDShrink uses, I'd like to be able to just load it in IMGburn and burn away, but IMGburn says that my files are too large to fit on a DVD9... though it would, and DID have fit just fine when burned with DVDShrink (these are the "shrunken", already processed files).
Is it just a bad estimate on IMGburn's part due to ISO overhead data taking more space than a file dump? Is it safe to ignore and burn something that reports a significant overburn?
This scenario happens often enough and I usually find some long-way around it, but I'm wondering how you guys usually do it. For instance, if I took the output files from DVDShrink or any number of other "X-to-DVD" applications and tried to burn them using IMGburn, I usually get a message like that telling me that I am trying to squeeze too much on a DVD5 when, if I had let the original app do the burning, it would've fit just fine. I'm usually working with ISOs as output files and all the overhead storage that that requires, so it often said to be too large by several hundred MBs. IIRC, this is sometimes almost half a GB and always far more than I feel I could get away with from overburning.
One more-specific scenario:
DVDShrink successfully burns a disc. I then determine that I needed a second copy and DVDShrink has no way to just load those temp files and burn again, though they were presumably left for this purpose. Doing so anyway, it re-analyzes and wants to re-shrink it unless I do the whole "reauthor" thing again, tell it not to compress and, of course, it generates NEW output. If I want to take a shortcut and use a burning app that I am more comfortable with than the out-dated one DVDShrink uses, I'd like to be able to just load it in IMGburn and burn away, but IMGburn says that my files are too large to fit on a DVD9... though it would, and DID have fit just fine when burned with DVDShrink (these are the "shrunken", already processed files).
Is it just a bad estimate on IMGburn's part due to ISO overhead data taking more space than a file dump? Is it safe to ignore and burn something that reports a significant overburn?