Brasero defaults to --read-raw, creates bad-quality disks

Bug #391193 reported by Thomas Guyot-Sionnest
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: brasero

This bug apply to the brasero application in Ubuntu Jaunty

When creating an audio disc copy (probably apply to any disks though) braserro uses cdrdao with the --read-raw
parameter. As stated in the manual, --read-raw reads data and P-W subchannels uncorrected, which mean that any correctable errors is copied as-it to the image file.

If the CD burner supports writing R-W subchannel data, the resulting CD therefore contains any read-errors (that are normally corrected) burnt in the copied cd.

This usually works as cd players can still use the error correction data to correct there errors, however these CDs are weaker since the have errors burnt-in and may not work on some poor-quality players.

For instance I created two copies from a CD and none of them would work on one of my cd players... for testing I re-copied the "broken" cd using cdrdao with the "--read-subchan rw" option instead and the resulting cd was perfectly readable on all my players.

The "--read-subchan rw" option makes a similar images but creates corrected data and R-W subchannel data. This results in a better quality reproduction without any subchannel data loss (ISRC, CD-TEXT, etc.). The --read-raw option is generally used when working with intentionally damaged disks bundled with copy protection systems.

description: updated
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, that's something to send directly upstream at http://bugzilla.gnome.org by someone experiencing the issue, for forwarding instructions please read http://wiki.ubuntu.com/Bugs/Upstream/GNOME, Thanks in advance.

Changed in brasero (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Any news about this? did you sent the bug upstream? may you tell us the bug number there? Thanks.

Changed in brasero (Ubuntu):
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in brasero (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.