GNOME Bugzilla – Bug 438852
Add ability to chain integrity checking
Last modified: 2018-09-21 16:23:25 UTC
When you master a big DVD project it would be great if brasero offered the ability to chain integrity checking Right now you start the burn, go do something else and return to see the stupid dialog proposing integrity checking (so everything was not done and you've earned another go do something else while brasero works) Sometimes fully unattended it the right thing to propose brasero-0.5.2-1.fc7.x86_64
Yes, I know; I'll have to re-order the "after burning" part anyway when I'll add a dialog to create disc jacket so I'll keep that in mind.
I completely agree that this failure to auto-verify is a HUGE disincentive to using Brasero. But it is not a single change, there are a few consequential minor issues to clean up at the same time: 1. Make the data integrity check of a burn operate automatically after a burn. 2. If worried about situations where the user is in a rush, allow an 'ESC' key or (to avoid Alt-Tab - Esc in quick sequence, a button to be clicked) to early-terminate the data integrity checking process. 3. Whether terminated early or not, ask the question 'Burn another copy? Yes/No' immediately afterwards, as otherwise Brasero will allow another Data CD or DVD to be burnt, but it again loses the text you input to use as the volume name. 4. If the user clicked 'No', and you return to main Brasero data CD/DVD screen, keep other inputted variables the same, such as volume name, which drive to use, burn speed, buffered etc, as user may wish to adjust contents, and even edit volume name to suit, but best to start with his/her last-used, than Brasero's default (non-descript) volume name. 5. While performing data integrity check change the wording at start of dialogue/progress box from "BURNING" to something which conveys "CHECKING" as it is unclear... and one's propensity to use computer for other tasks differs based on this feedback. 6. At end of such changes, re-check how tick-box for 'Eject at Conclusion' works, as currently, setting it to NOT eject results in an ejection mid-way through burn+check process, but no ejection at end. With burn+check processes chained, only ejection or non-ejection should be at very end. 7. Only other suggestion I'd make is if you tick 'Maximise Windows Compatability' and some file names are longer than 64 characters, either show an example from the first found instance of how the truncation would look (ie before and after filenames) or show a whole scrolled list of before and after, so people get an idea of what it will look like, and indeed how many such problematic instances are within their selected data. 8 Otherwise good/simple program which works reliably... just some polishing needed in interface. Graeme Harrison (prof at-symbol post.harvard.edu) - 30 years IT experience
Thanks for the ideas. Some of them are already implemented in 0.8.3 (latest one). 1. done, now brasero doesn't even need to reload the disc; we bypass kernel cache by reading straight from the disc 2. True an escape key could be useful in addition to the already existing cancel button 3. done as well, the number of copies spinbutton shown in the option dialogs was removed. Instead, a "Burn Another Copy" button shows up in the burn dialog when last burning operation was successful (that avoids having an intrusive dialog box). 4. that should be also done 5. I need to check that 6. as said above we don't need to eject before checking now so if the box is not ticked, no ejection should be performed now 7. Yes, good idea, that could indeed be improved. Thanks
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/brasero/issues/9.