I thought Toast allowed for exact copies. The info is digital, is it not? If I make a disc image and then burn that image to a new disc, should not this new disc contain exactly the same set of 1's and 0's? Confused?
He's saying that the CDs are scratched, causing "pops". If this is the case, Toast will copy the missing data exactly as well, i.e., "missing," faithfully reproducing the pops.
With some very scratched CDs, Toast extracted with no problems when iTunes couldn't, and since then I've only used Toast. But having only worked with a few scratched CDs I can't say for sure that Toast is the best solution.
Toast 3 used to stop if it came to an error. Even a minor skip would cause it to halt completely. So I always kept a copy of 3.5.7 handy but after installing 5 it didn't do this anymore. Even after I deleted 5, 3 wouldn't stop copying if it came to skip on my iBook. I thought I'd never be able to rip scratched CDs again without errors. Then I came across this CDParanoia thing. I found it in FireStarter FX. I highly recommend this app for "overburning" since most divx movies on the net seem to be a few megs bigger than what a CD can hold. I haven't used FireStarter FX with CDParanoia to rip yet but I'll try when I come across scratchy CD. How does CDParanoia work?
explain this. i have a cd that plays fine but everytime i try to make a copy, the copy has clicks on 3 tracks. i even tried recording it to my HD with Audio Hijack, same thing happened. i was burning it at 1x. i even tried copying the tracks directly to the HD, still no luck.
I thought Toast allowed for exact copies. The info is digital, is it not? If I make a disc image and then burn that image to a new disc, should not this new disc contain exactly the same set of 1's and 0's? Confused?
yes it makes exact copies, so i assume it's an exact copy
Sorry for being a bit late to the thread, but I believe the problem with importing a scratched CD and getting "pops" is really down to the speed which the drive is ripping at.
A CD played at normal speed on a player will not usually skip because CD-audio players use blanking, or muting, of a defective part of the audio program to overcome errors.
An alternative is interpolation whereby the player inserts its best estimate of the missing information. The human ear does not notice such events that usually occupy only a few thousandths of one second of the audio program.
I have had countless rips from scratched Cds with skipping and pops and giving the source CD a really good clean before hand does help.
Find a way of slowing down the speed of the drive for a rip is one sure fix.
So I guess CDParanoia repairs skips by interpolating. Yes Matsu since Toast 3 IIRC Toast supports Digital Audio Extraction which means the same exact data.
So I guess CDParanoia repairs skips by interpolating. Yes Matsu since Toast 3 IIRC Toast supports Digital Audio Extraction which means the same exact data.
Actually, having used the stuff now for a bit, I'd say cdparanoia 'repairs' skips first by a brute force approach: read the same sectors over and over again and compare the results. If you get the same result enough times, you are in business. If not, I don't really know what happens. I'd say interpolating an average value would be the most logical, but I haven't found this described nowhere.
See http://www.exactaudiocopy.de/ for a good discussion of the problems of digital audio extraction on CD-ROM drives and what EAC does that's better. I'm pretty sure CDParanoia does the same thing. There's also a discussion board w/ lots of useful info.
I used EAC and LAME to rip a lot of my CDs but I ended up reripping them in iTunes because EAC/LAME combo (at least the way I config.ed it) didn't put a Xing header onto the VBR MP3s I made, so iTunes and my iPod got the times all wrong.
Comments
Originally posted by Matsu
I thought Toast allowed for exact copies. The info is digital, is it not? If I make a disc image and then burn that image to a new disc, should not this new disc contain exactly the same set of 1's and 0's? Confused?
He's saying that the CDs are scratched, causing "pops". If this is the case, Toast will copy the missing data exactly as well, i.e., "missing," faithfully reproducing the pops.
With some very scratched CDs, Toast extracted with no problems when iTunes couldn't, and since then I've only used Toast. But having only worked with a few scratched CDs I can't say for sure that Toast is the best solution.
I use toast by the way.
what happens if i use 'extract' in toast?
Originally posted by Matsu
I thought Toast allowed for exact copies. The info is digital, is it not? If I make a disc image and then burn that image to a new disc, should not this new disc contain exactly the same set of 1's and 0's? Confused?
yes it makes exact copies, so i assume it's an exact copy
A CD played at normal speed on a player will not usually skip because CD-audio players use blanking, or muting, of a defective part of the audio program to overcome errors.
An alternative is interpolation whereby the player inserts its best estimate of the missing information. The human ear does not notice such events that usually occupy only a few thousandths of one second of the audio program.
I have had countless rips from scratched Cds with skipping and pops and giving the source CD a really good clean before hand does help.
Find a way of slowing down the speed of the drive for a rip is one sure fix.
Originally posted by Aquatic
So I guess CDParanoia repairs skips by interpolating. Yes Matsu since Toast 3 IIRC Toast supports Digital Audio Extraction which means the same exact data.
Actually, having used the stuff now for a bit, I'd say cdparanoia 'repairs' skips first by a brute force approach: read the same sectors over and over again and compare the results. If you get the same result enough times, you are in business. If not, I don't really know what happens. I'd say interpolating an average value would be the most logical, but I haven't found this described nowhere.
I used EAC and LAME to rip a lot of my CDs but I ended up reripping them in iTunes because EAC/LAME combo (at least the way I config.ed it) didn't put a Xing header onto the VBR MP3s I made, so iTunes and my iPod got the times all wrong.