[SATLUG] cd audio burning
geoff at w5omr.shacknet.nu
Fri Feb 8 10:43:36 CST 2008
Jeremy Mann wrote:
>> Using cdrecord (wodim) I'm attempting to burn some audio cd's as s-l-o-w
>> as I can, so that the CD player in the vehicle will play them. (if you
>> didn't know, when burning an audio CD, burn as slow as you can go, to
>> create less 'skips' on your CD while driving down the road. The slower
>> the burn speed, the 'deeper' the burn into the cd)
>> supported by the drive. *If you use speed=0 with
>> a MMC compliant drive, wodim will switch to the lowest possible speed
>> for drive and medium.* If you are using an
>> old (non MMC) drive that has problems with speed=2 or speed=4, you
>> should try speed=0.
>> (between the *'s [should be in bold] is what interests me.)
>> SO, I up-arrowed till I found the command again, changed the speed=1
>> statement to speed=0, and burned another disc.
>> THIS time, it burnt the same amount of data (same files), but in like
>> half the time. In fact, in the output info the program was spitting out
>> (that I can't paste), it reported that it was attempting to burn at 48x.
> Believe or not, most newer drives have problems burning at slow speeds
> if they can at all go below 4x. wodim answered your question right
> there, "when set to speed=0 it will burn at the slowest possible speed
> that the drive supports".
Ah, but it didn't! I -set- speed=0 in the command, and if you'll go back and re-read my message, you'll see where I said that the same amount of data was burned to the CD in half of the time as having the variable 'speed=1' set. Hence my confusion.
> SO, I up-arrowed till I found the command again, changed the speed=1
> statement to speed=0, and burned another disc.
> THIS time, it burnt the same amount of data (same files), but in like
> half the time.
More information about the SATLUG