18 Sep
2011
18 Sep
'11
6:31 p.m.
Hope someone can help me on this. I've got 2 LD DVD r/w drives.
Neither one will burn an audio CD for me. When I try it gets to around
track 8 to 10 of 22 and then it craps out. Tried a bunch of different
media and have a nice stack of coasters!
Attempt to create using wodim/cdrecord:
cdrecord dev=/dev/cdrom speed=4 -audio *wav
wodim: No write mode specified.
wodim: Assuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identification : 'DVDRAM GH22NS50 '
Revision : 'TN02'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Speed set to 2822 KB/s
Starting to write CD/DVD at speed 16.0 in real TAO mode for single session.
Last chance to quit, starting real write in 0 seconds. Operation starts.
Track 01: Total bytes read/written: 43551984/43551984 (18517 sectors).
Track 02: Total bytes read/written: 36408960/36408960 (15480 sectors).
Track 03: Total bytes read/written: 29230656/29230656 (12428 sectors).
Track 04: Total bytes read/written: 39424224/39424224 (16762 sectors).
Track 05: Total bytes read/written: 17870496/17870496 (7598 sectors).
Track 06: Total bytes read/written: 23806944/23806944 (10122 sectors).
Track 07: Total bytes read/written: 32775120/32775120 (13935 sectors).
Track 08: Total bytes read/written: 18616080/18616080 (7915 sectors).
Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
CDB: 2A 00 00 01 D9 54 00 00 15 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 03 00 00
Sense Key: 0x0 No Additional Sense, Segment 11
Sense Code: 0x00 Qual 0x03 (setmark detected) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 41.296s timeout 40s
write track data: error after 40452048 bytes
wodim: A write error occured.
wodim: Please properly read the error message above.
The drives in question are (from hdparm):
/dev/cdrom:
ATAPI CD-ROM, with removable media
Model Number: HL-DT-ST DVDRAM GH22NS50
Serial Number: K00998K1011
Firmware Revision: TN02
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev
2.5, SATA Rev 2.6
Standards:
Likely used CD-ROM ATAPI-1
Configuration:
DRQ response: 50us.
Packet size: 12 bytes
cache/buffer size = unknown
Capabilities:
LBA, IORDY(can be disabled)
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
And for the other drive:
/dev/cdrom1:
ATAPI CD-ROM, with removable media
Model Number: HL-DT-ST DVDRAM GH24NS50
Serial Number: K00AB5E3326
Firmware Revision: XP02
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev
2.5, SATA Rev 2.6
Standards:
Likely used CD-ROM ATAPI-1
Configuration:
DRQ response: 50us.
Packet size: 12 bytes
cache/buffer size = unknown
Capabilities:
LBA, IORDY(can be disabled)
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
And my linux is Ubuntu 11.04, kernel 2.6.38-11-generic-pae
I've checked my cables and all seems to be fine. I don't think it's a
simple hardware thing ... my guess is something to do with irqs. This
is a lightly loaded system. Lots of RAM (7gig) and a dual core AMD
processor.
Suggestions welcome.
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
18 Sep
18 Sep
10:33 p.m.
On Sun, Sep 18, 2011 at 09:31:14AM -0700, Bob van der Poel wrote:
Hope someone can help me on this. I've got 2 LD
DVD r/w drives.
Neither one will burn an audio CD for me. When I try it gets to around
track 8 to 10 of 22 and then it craps out. Tried a bunch of different
media and have a nice stack of coasters!
Did they ever work? Are they new? Did you
try DAO mode?
Cheers,
S.M.
19 Sep
19 Sep
2:44 a.m.
Did they ever work? Are they new? Did you try DAO
mode?
Yes, both worked fine in the past. I suspecting that the latest kernel
might have been the problem ... or the PAE mode? I'm going to try to
boot with an older kernel if I still have on the computer and see.
Any other ideas? I saw some stuff on the web about /etc/modprobe.d
files, but they were a few years old and I'm figuring that whatever
they fixed has been fixed. Besides, can't find the link anymore.
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
3:33 a.m.
This is slowly driving me nuts!
I booted with an older Ubuntu, 10.04. Same problem.
So, rebooted and tried once more, but this time I removed tracks 8 and
9 (it was hanging at the end(?) of track 8 ...) And, guess what? Yes,
the burn was 100% successful.
I've copied the files to an alternate directory and the same problem,
so I'm thinking it's not a flaky sector in the file.
So, what in the world could be wrong?
The tracks are an album of recorder music I got of the net in flac
format. I converted the flac files to wav using sox. If I use 'file'
on the files they all appear to be the same:
RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, stereo 44100 Hz
Is it possible/probable that there is bit pattern in the file causing
this to happen?
Oh, and yes, I tried this in both TOA and DOA modes. Both fail ... but
in DOA one doesn't know just where.
I think that k3b and brasero both use cdrecord, which is a link to
wodim. Is there an alternate burner that I could try?
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
3:42 a.m.
Wild guess - is it possible that the resulting track image it's trying
to burn is just a song or two too long for the media you're using? Like
trying to fit an 80-minute track onto 70-minute media?
Bob van der Poel wrote:
This is slowly driving me nuts!
I booted with an older Ubuntu, 10.04. Same problem.
So, rebooted and tried once more, but this time I removed tracks 8 and
9 (it was hanging at the end(?) of track 8 ...) And, guess what? Yes,
the burn was 100% successful.
I've copied the files to an alternate directory and the same problem,
so I'm thinking it's not a flaky sector in the file.
So, what in the world could be wrong?
The tracks are an album of recorder music I got of the net in flac
format. I converted the flac files to wav using sox. If I use 'file'
on the files they all appear to be the same:
RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, stereo 44100 Hz
Is it possible/probable that there is bit pattern in the file causing
this to happen?
Oh, and yes, I tried this in both TOA and DOA modes. Both fail ... but
in DOA one doesn't know just where.
I think that k3b and brasero both use cdrecord, which is a link to
wodim. Is there an alternate burner that I could try?
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
3:53 a.m.
On Sun, Sep 18, 2011 at 6:42 PM, david <gnome(a)hawaii.rr.com> wrote:
Wild guess - is it possible that the resulting track
image it's trying to
burn is just a song or two too long for the media you're using? Like trying
to fit an 80-minute track onto 70-minute media?
I don't see that. I could be wrong of course, but I've got 22 tracks
in total. I removed 8 and 9 from the directory and it works. The crash
was happening at the end of track 8 (if one believes the report from
cdrecord) ... and the total size was about 600 meg. I'm going to
restore one track, try again; restore both and try; and maybe rename
#8 to something else to force it to the end of the disk.
But, yes, size is an issue I guess. I have no idea how cdrecord does
allocation of space, but I assume it's from the center out just like
tracks are when played. Allocation table overflow? Seems unlikely.
Ideas are welcome! I feel like I'm in the twilight zone :)
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
6:22 a.m.
Bob van der Poel wrote:
On Sun, Sep 18, 2011 at 6:42 PM, david
<gnome(a)hawaii.rr.com> wrote:
And my wild guess is about all I'm good for. Although maybe drive speed
makes a difference? As the track goes outward, the disk media itself
changes rotation speed, yes? (Sorry, just vague recollections of what
little I knew about optical drive mechanics, something about
constant-angular-velocity?) Of course, the chance of this effecting TWO
different optical drives simultaneously is pretty slim. That's why I
thought of the next element they had in common: the media (particularly
capacity).
I did have problems at one time burning CDs on a particular drive.
Turned out that drive burning mostly worked until the laser head reached
a particular point, then the laser head lost alignment and started
spitting out errors. Mechanical problem with the drive itself.
I don't remember - did you try disconnecting one of the drives and
burning on the other?
Anyway, definitely the Twilight Zone!
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
Wild guess - is it possible that the resulting
track image it's trying to
burn is just a song or two too long for the media you're using? Like trying
to fit an 80-minute track onto 70-minute media?
I don't see that. I could be wrong of course, but I've got 22 tracks
in total. I removed 8 and 9 from the directory and it works. The crash
was happening at the end of track 8 (if one believes the report from
cdrecord) ... and the total size was about 600 meg. I'm going to
restore one track, try again; restore both and try; and maybe rename
#8 to something else to force it to the end of the disk.
But, yes, size is an issue I guess. I have no idea how cdrecord does
allocation of space, but I assume it's from the center out just like
tracks are when played. Allocation table overflow? Seems unlikely.
Ideas are welcome! I feel like I'm in the twilight zone :) 
6:51 a.m.
Le 19/09/2011 03:53, Bob van der Poel a écrit :
On Sun, Sep 18, 2011 at 6:42 PM,
david<gnome(a)hawaii.rr.com> wrote:
Hum, when you burn an audio cd the point is not the total size but the
total duration,
to be sure you can put all your tracks inaudacity and check this !
HTH,
Fred
Wild guess - is it possible that the resulting
track image it's trying to
burn is just a song or two too long for the media you're using? Like trying
to fit an 80-minute track onto 70-minute media?
I don't see that. I could be wrong of course, but I've got 22
tracks
in total. I removed 8 and 9 from the directory and it works. The crash
was happening at the end of track 8 (if one believes the report from
cdrecord) ... and the total size was about 600 meg. I'm going to
restore one track, try again; restore both and try; and maybe rename
#8 to something else to force it to the end of the disk.
But, yes, size is an issue I guess. I have no idea how cdrecord does
allocation of space, but I assume it's from the center out just like
tracks are when played. Allocation table overflow? Seems unlikely.
Ideas are welcome! I feel like I'm in the twilight zone :)
4:50 p.m.
Hello,
On Sun, Sep 18, 2011 at 06:33:18PM -0700, Bob van der Poel wrote:
(EXCERPTS)
This is slowly driving me nuts!
Yeah, those are
the worst bugs:the elusive ones. :)
9 (it was hanging at the end(?) of track 8 ...) And, guess what? Yes,
the burn was 100% successful.
I've copied the files to an alternate directory and the same problem,
so I'm thinking it's not a flaky sector in the file.
So, what in the world could be wrong?
The tracks are an album of recorder music I got of the net in flac
format. I converted the flac files to wav using sox. If I use 'file'
on the files they all appear to be the same:
What if you burn another full length
CD with different material? What if
you burn those remaining tracks on a CD separately?
(You'll have lots of frisbees to play with!)
Another, admitedly wild, guess would be that the problem is time
dependent and occurs after N minutes have elapsed in the burning
process. As David said, it seems impossible that two drives would
develop the same flaky behaviour at the same time.
I think that k3b and brasero both use cdrecord, which
is a link to
wodim. Is there an alternate burner that I could try?
cdrdao is the only other one
I know of.
As others have suggested, make sure the total play length does not
exceed the medium's capacity, although I seem to recall wodim will throw
an error and ask for an override option if that is the case.
Cheers,
S.M.
8:21 p.m.
On Monday 19 September 2011, Bob van der Poel wrote:
So, what in the world could be wrong?
Maybe the file names contain characters outside the usual 8-bit charset? you
are probably using UTF-8 in your file system. Have you tried renaming the
files?
I think that k3b and brasero both use cdrecord, which
is a link to
wodim. Is there an alternate burner that I could try?
Yes. That wodim or cdrkit thing is a lame fork of the original cdrtools:
http://cdrecord.berlios.de
cdrtools has published versions and fixed many bugs since 2006, when the fork
happened, while the fork didn't. K3b has explicit support for the original
cdrtools. You will probably need to compile cdrtools from sources, unless you
change your distro.
Regards,
Pedro
8:58 p.m.
Thanks for the input on this guys. Getting nuttier here.
My latest test was to reorder the tracks. Just to recap, I have a 22
track audio CD I'm trying to burn. The tracks are named like this:
01 - Verbruggen - Concerto in D major, RV 95 La Pastorella- Allegro.flac.wav
etc.
The total duration of the tracks is 65 minutes. So, should be lots of
room on the disk.
The results I get are consistent: burning stops/crashes at track 09.
I checked the name with emacs and no "odd" chars in the name.
I checked and the file plays fine with aplay.
now, here's the interesting part. I just reordered the tracks with
barsero so that the order is 8,9,10,1,2...22 (skipping 8,9 10 or
course). Now the burn stops with the 2nd track (the original 9).
So, there is definitely something odd about the track.
My next test is to convert the track to mp3 and then back to wav and
see if that makes a difference.
And I thought that computers could make my life simpler!
Oh, what's the deal with cdrkit? I thought brasero used cdrkit and
even though I have it installed it appears to use cdrecord/wodim.
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
20 Sep
20 Sep
12:20 a.m.
Isn't getting any saner here. I converted track 9 to mp3 with lame and
then converted it back to wav with mpg123.
And, volia, the CD burned just fine.
This makes absolutely no sense.
Is there some way a flac file can be copy protected when it is
converted to wav? I don't think so :) My only remaining idea is some
nefarious bit pattern.
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
6:41 a.m.
Bob van der Poel wrote:
Isn't getting any saner here. I converted track 9
to mp3 with lame and
then converted it back to wav with mpg123.
And, volia, the CD burned just fine.
This makes absolutely no sense.
Is there some way a flac file can be copy protected when it is
converted to wav? I don't think so :) My only remaining idea is some
nefarious bit pattern.
Sounds like it to me. You might see about putting in a bug report for
the CDR software with a copy of the bad file attached, so they could
maybe figure out what caused it and fix things.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
10:53 a.m.
Excerpts from Bob van der Poel's message of 2011-09-20 00:20:48 +0200:
Isn't getting any saner here. I converted track 9
to mp3 with lame and
then converted it back to wav with mpg123.
And, volia, the CD burned just fine.
This makes absolutely no sense.
Is there some way a flac file can be copy protected when it is
converted to wav? I don't think so :) My only remaining idea is some
nefarious bit pattern.
You could try flac --test or --analyze or sndfile-info (also on the wav)
maybe it tells you something useful.
19 Sep
19 Sep
6:25 p.m.
Excerpts from Bob van der Poel's message of 2011-09-18 18:31:14 +0200:
Hope someone can help me on this. I've got 2 LD
DVD r/w drives.
Neither one will burn an audio CD for me. When I try it gets to around
track 8 to 10 of 22 and then it craps out. Tried a bunch of different
media and have a nice stack of coasters!
Attempt to create using wodim/cdrecord:
cdrecord dev=/dev/cdrom speed=4 -audio *wav
wodim: No write mode specified.
wodim: Assuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identification : 'DVDRAM GH22NS50 '
Revision : 'TN02'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Speed set to 2822 KB/s
Starting to write CD/DVD at speed 16.0 in real TAO mode for single session.
Last chance to quit, starting real write in 0 seconds. Operation starts.
Track 01: Total bytes read/written: 43551984/43551984 (18517 sectors).
Track 02: Total bytes read/written: 36408960/36408960 (15480 sectors).
Track 03: Total bytes read/written: 29230656/29230656 (12428 sectors).
Track 04: Total bytes read/written: 39424224/39424224 (16762 sectors).
Track 05: Total bytes read/written: 17870496/17870496 (7598 sectors).
Track 06: Total bytes read/written: 23806944/23806944 (10122 sectors).
Track 07: Total bytes read/written: 32775120/32775120 (13935 sectors).
Track 08: Total bytes read/written: 18616080/18616080 (7915 sectors).
Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
CDB: 2A 00 00 01 D9 54 00 00 15 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 03 00 00
Sense Key: 0x0 No Additional Sense, Segment 11
Sense Code: 0x00 Qual 0x03 (setmark detected) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 41.296s timeout 40s
write track data: error after 40452048 bytes
wodim: A write error occured.
wodim: Please properly read the error message above.
The drives in question are (from hdparm):
/dev/cdrom:
ATAPI CD-ROM, with removable media
Model Number: HL-DT-ST DVDRAM GH22NS50
Serial Number: K00998K1011
Firmware Revision: TN02
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev
2.5, SATA Rev 2.6
Standards:
Likely used CD-ROM ATAPI-1
Configuration:
DRQ response: 50us.
Packet size: 12 bytes
cache/buffer size = unknown
Capabilities:
LBA, IORDY(can be disabled)
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
And for the other drive:
/dev/cdrom1:
ATAPI CD-ROM, with removable media
Model Number: HL-DT-ST DVDRAM GH24NS50
Serial Number: K00AB5E3326
Firmware Revision: XP02
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev
2.5, SATA Rev 2.6
Standards:
Likely used CD-ROM ATAPI-1
Configuration:
DRQ response: 50us.
Packet size: 12 bytes
cache/buffer size = unknown
Capabilities:
LBA, IORDY(can be disabled)
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
And my linux is Ubuntu 11.04, kernel 2.6.38-11-generic-pae
I've checked my cables and all seems to be fine. I don't think it's a
simple hardware thing ... my guess is something to do with irqs. This
is a lightly loaded system. Lots of RAM (7gig) and a dual core AMD
processor.
Suggestions welcome.
Hi Bob,
which backend do you use for burning? cdrtools or cdrkit?
If you used cdrkit, the first thing I'd try is to switch to cdrtools.
Yes, there was some licensing trouble but I'm pretty sure that from a
pragmatic perspective cdrtools is the thing to use.
Other things: use DAO mode
How do you burn the CD? As ISO or by using CUE files, TOC files? If I
remember correctly then those files, if they're wrong in some subtle
way (markers not at the correct boundaries or something), won't burn
the CD correctly. In my case it was simply something like a missing
last track.
I got a few more or less coasters too recently because I wanted to have
proper CDTEXT, but that's a different story...
Hth,
Philipp
4814
days inactive
4816
days old
linux-audio-user@lists.linuxaudio.org
14 comments
6 participants
participants (6)
-
Bob van der Poel -
david -
fred -
Pedro Lopez-Cabanillas -
Philipp Überbacher -
S. Massy