Created attachment 2006 Backtrace of crashes after burning an audio CD Burning some ogg's to a CD-RW is extremly slow (speed 0,1x and less) and when the burn process has finally finished, xfburn segfaults. A maybe not very helpful backtrace is attached. I'm using xfburn from SVN, r6222 and libburn 0.5.0 from Debian Sid. Regarding the speed issue: I verified that it is not related to the CD-RW itself by burning an ISO image which succeeded with a speed of 8x.
The crash might be caused by libburn. A new version was released that addresses that problem. A question for you: does it only display 0.1X, and burn at somewhat regular speeds, or is it really taking forever to burn? If 0.1X was true, burning only 30min of audio should take you 10x as long, so around 5 hours....
Another question: Does the speed go back down to 0X when it starts to burn the next track? This might be hard to observe if the speed stays at 0.1X most of the time, but it'd be great if you could check.
It seems it burns actually with much more than 0.1X, I think my drive supports something like 8X or 10X and this could be actually reached (I didn't measured it). I took a screencast to show what's happen: http://www.uvena.de/tmp/xfburn_bug4659.ogv Additionally, it looks like only at the start everything is damn slow. Once the first track has burned, it continues faster. But I don' think it's related to the first file which is burned, at least it always hangs at the first track regardless of which file that is.
Ah, so I think what's happening is that the drive does a formatting of the cdrw first. That's why it is stuck for so long at 1% - obviously the speed is 0X at that point. If you look at the video (great idea btw), the progress starts at around 2:30, and it's done at around 4:00. So 1:30min to burn 13min of audio is pretty fast. Now I think libburn tells me when the drive is doing the formatting, and I'll look into why that isn't shown in the GUI.
So I'm puzzled. First of all, the code to show the correct status when the drive is formatting is there, see http://svn.xfce.org/index.cgi/goodies/xfburn/trunk/xfburn/xfburn-perform-burn.c?revision=6049&view=markup at line 259. Second of all, this code is in use for both data and audio burns. Why you only see the slow startup with audio and not with data is still a mystery to me. I assume you blanked the CD in the same way before both tries, right?
(In reply to comment #5) > So I'm puzzled. First of all, the code to show the correct status when the > drive is formatting is there, see > http://svn.xfce.org/index.cgi/goodies/xfburn/trunk/xfburn/xfburn-perform-burn.c?revision=6049&view=markup > at line 259. > > Second of all, this code is in use for both data and audio burns. Why you only > see the slow startup with audio and not with data is still a mystery to me. I I just blanked the disc, burned some data files (around 80megs) and all went fine as expected, no delay. Then I blanked the disc again and burned a few audio files as audio cd and I got the weird delay at startup again. > assume you blanked the CD in the same way before both tries, right? Yes, with xfburn's blank dialog, using the fast method without ejecting the disc.
The reported segfaults were caused by libburn and are already fixed in newer releases. The reported delay seems to be related to the hardware I used as I couldn't reproduce them with another drive. So this report is invalid.