GNOME Bugzilla – Bug 137099
Use burnfree when available
Last modified: 2009-01-19 20:22:00 UTC
Package: nautilus-cd-burner Version: 0.5.3-2 Severity: wishlist It would be excellent if nautilus ran "cdrecord -driveropts=help - checkdrive" to detect if BurnFree is available, and to use it if it is. This would increase the reliability and lessens the chance of failure in burns on machines with other things going on. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=215196
AFAIK, burnproof is not enabled in cdrecord by default, because it is known to create lesser quality CDs (ie. you can get CDs that wouldn't be readable on some players, etc.). You can check details on the cdrecord-developers mailing-list. It might be an idea of something to add, but would only be available via GConf.
2004-07-29 Bastien Nocera <hadess@hadess.net> * cd-recorder.c: (cdrecord_stderr_read), (cd_recorder_write_cdrecord): * cd-recorder.h: * nautilus-cd-burner.c: (burn_cd), (main): * ncb.schemas.in: Implement "burnproof" as an option, as it is necessary to burn CDs on some systems (Closes: #137099). Display an error when cdrecord tells us that the system is too slow (Closes: #148749)
*** Bug 152427 has been marked as a duplicate of this bug. ***
« AFAIK, burnproof is not enabled in cdrecord by default, because it is known to create lesser quality CDs (ie. you can get CDs that wouldn't be readable on some players, etc.). » Does it degrade quality for all cd burnt with this option set, or only when you get a buffer underrun and burnproof kicks in to avoid getting a coaster? If this is the latter, the choice between a cd which may not be read properly by some readers and a cd which won't be readable by any reader is a quick one imo...
I can't seem to be able to find the original post, so here's a few references: http://lists.debian.org/cdwrite/2003/11/msg00120.html and http://lists.debian.org/debian-user/2003/02/msg04680.html My guess is "enable it automatically if there's only data". Should fit most needs.
That sounds right to me. Which means that it enabled for everything that goes through the nautilus-cd-burner GUI. Other libnautilus-burn clients will have to enable it specificallly. I've made this change in CVS HEAD.
From launchpad https://launchpad.net/ubuntu/+source/nautilus-cd-burner/+bug/79301: "... The changelog for nautilus-cd-burner v. 2.11.4 mentions enabling this by default. Between 2.15.1 and 2.15.2 a bunch of code was merged and during this merge, the change from 2.11.4 was lost. The fix in 2.11.4 was kludgy anyway (hardcoded use of burnproof), so I propose the attached fix (set the the gconf value to enable) as a resolution. ..." reopening
I'm not sure that this is correct. We should always use it for anything burned from n-c-b using the cdrecord backend: if (TRUE) { operation->priv->record_flags |= NAUTILUS_BURN_RECORDER_WRITE_BURNPROOF; } if (flags & NAUTILUS_BURN_RECORDER_WRITE_BURNPROOF) { g_ptr_array_add (argv, "driveropts=burnfree"); } Can you include the debug output when running to show that it isn't getting set?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!