GNOME Bugzilla – Bug 366183
Wrong "maximum" burn speed
Last modified: 2007-03-30 18:01:45 UTC
I burned the xen live-cd iso using brasero yesterday, writing speed set to "max". I noticed the burn process was actually at about 4x speed, where the same process using nero uses 40x speed. Is thsi a bug with brasero or perhaps the libburn backend?
If you used, libburn backend, then maybe. But it could also be a problem with the speed chosen by brasero as the max one. It's hard to say. Do you have a reliable way to trigger this bug ?
I have disabled libburn now. Had do burn a few discs yesterday but I used nero for that because I needed it to be fast. I will try again with brasero as soon as I have something to burn. I *think* triggering this would be as easy as burning a CD with brasero (at least with libburn). I'll update the bug with more information as I get them.
Ok, I got myself a bunch of CD-Rs and used brasero to burn a bunch of ISOs. Not using libburn, the speed was normal. So this bug seems to only affect brasero+libburn...
I think the problem is in fact in HAL itself. HAL sets the speed of a drive just once (possibly when it starts). Now if you read mmc specs, they state that a drive reports its speeds (write/read) according to the media inside. That is, if you have a CDRW inserted, the drive reports 10x, a CDR around 30x (at least) for modern drive, and so on. So if you have, say, a CDRW when HAL starts up, the speed will remain at 10x whatever the media you insert afterward because HAL doesn't poll for the new speed when the media changes for a drive. An easy test is to use hal-device-manager, and start HAL with a CDRW inside. HAL reports 10x or 4x (according to the speed of your CDRW) whatever the media you insert. Two solutions: fix it in HAL or write a small scsi library for 0.6.X.
Speed detection has been worked on in SVN of libburn, and works quite reliable now.
I have the same problem. The maximum burning speed of my drive is 56x, but when I insert some old rewritable CD (4x or 10x) Brasero still shows 56x as maximum speed. Perhaps, this is the same bug that #359258. (In reply to comment #5) > Speed detection has been worked on in SVN of libburn, and works quite reliable > now. Well, at least in Ubuntu Feisty, the version 0.5.2 doesn't depend on libburn anymore, so this is not the solution :(
I fixed this bug in brasero. Thanks to the new SCSI library it can retrieve the right speeds by itself. I also sent a bug report to HAL but no answer so far. Once it is fixed in HAL I'll see if this fix should be kept.
I forgot to mention this is fixed in trunk and will be fixed in trunk only so don't expect improvements in stable except if it is fixed in HAL in the mean time.