Michael Lange writes: [...]
I discovered then that, unless I missed something, that verifying the success of the burning procedure appears to be surprisingly (to me at least) non-trivial. For data-discs I finally found a recipe that seems to work in the archives of debianforum.de : $ cat whatever.iso | md5sum 50ab1d0cba4c1cedb61a6f22f55e75b7 - $ wc -c whatever.iso 8237400064 whatever.iso $ dd if=/dev/sr0 | head -c 8237400064 | md5sum 50ab1d0cba4c1cedb61a6f22f55e75b7 -
I usually go for this kind of command:
cmp whatever.iso /dev/sr0
If it reports "EOF on whatever.iso" its fine :)
This method does not, however, check the speed or any soft errors that the
firmware and driver were able to correct. You could run a `dmesg -w` in
parallel to find out about them in a qualitative way (if there are many
"buffer IO errors" the burn quality could be bad?).
[...]
I could not find any way to verify the success after burning audio-CDs though, except of course of carefully listening (the first one burned with the new drive seems to sound ok at first glance, I haven't found the time and leisure yet to listen attentively to 75 min. of weird Japanese jazz-music though :) So, does anyone know about a way to verify the integrity of burned audio-CDs?
[...] Can you mount it and view the individual tracks as files?Did you supply the .wav files exactly as they were going to be burnt unto the disc?
If both is yes, might it make sense to compare the individual track files against your supplied sources?
I have not tried to verify audio discs this way, though. HTH and YMMV Linux-Fan ΓΆΓΆ
pgpPPQlh6zJ8m.pgp
Description: PGP signature
