Secure ripping: Difference between revisions
mNo edit summary |
|||
| Line 2: | Line 2: | ||
==What is Secure Ripping?== | ==What is Secure Ripping?== | ||
Secure ripping is making sure there were no errors during the extraction of audio from a CD. Popular CD rippers, such as [[CDex]] and [[EAC]] try to ensure a bit-perfect rip for every track by checking the results, and re-reading any bad areas (from scratches) as many times as needed using offsets, etc. [[Max]] and [[Rubyripper]] provide similiar results as alternative secure rippers for Mac OS/X and Linux respectively. | Secure ripping is making sure there were no errors during the extraction of audio from a CD. Popular Windows CD rippers, such as [[CDex]] and [[EAC]] try to ensure a bit-perfect rip for every track by checking the results, and re-reading any bad areas (from scratches) as many times as needed using read offsets, etc. [[Max]] and [[Rubyripper]] provide similiar results as alternative secure rippers for Mac OS/X and Linux respectively using their own effective correction mechanisms. | ||
A bit-perfect rip may not always be possible, and so these programs ([[EAC]] especially) will report on any errors that could not be corrected, taking advantage of specific hardware features on your drive like C2 error pointers, etc allowing you to examine or attempt to correct the problems by analyzing a log file. | A bit-perfect rip may not always be possible, and so these programs ([[EAC]] especially) will report on any errors that could not be corrected, sometimes taking advantage of specific hardware features on your drive like C2 error pointers, AccurateStream, etc allowing you to examine or attempt to correct the problems by analyzing a log file. | ||
Revision as of 09:09, 23 December 2006
This article is a stub. You can help the Hydrogenaudio Knowledgebase by expanding it.
What is Secure Ripping?
Secure ripping is making sure there were no errors during the extraction of audio from a CD. Popular Windows CD rippers, such as CDex and EAC try to ensure a bit-perfect rip for every track by checking the results, and re-reading any bad areas (from scratches) as many times as needed using read offsets, etc. Max and Rubyripper provide similiar results as alternative secure rippers for Mac OS/X and Linux respectively using their own effective correction mechanisms.
A bit-perfect rip may not always be possible, and so these programs (EAC especially) will report on any errors that could not be corrected, sometimes taking advantage of specific hardware features on your drive like C2 error pointers, AccurateStream, etc allowing you to examine or attempt to correct the problems by analyzing a log file.