Secure ripping: Difference between revisions

From Hydrogenaudio Knowledgebase
m (Eventually we can create guides for each of these programs individually at least that is my line of thinking)
mNo edit summary
Line 6: Line 6:
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 for various reasons, allowing you to examine or attempt to correct the problems by analyzing a log file, using [[AccurateRip]], or by looking at other drive databases.  
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 for various reasons, allowing you to examine or attempt to correct the problems by analyzing a log file, using [[AccurateRip]], or by looking at other drive databases.  


==Secure Ripping Guide==
===Secure Ripping Guide===
==EAC==  
===EAC===  
==dbPowerAMP==  
===dbPowerAMP===  
==CDex==  
===CDex===  
==Max==  
===Max===  
==Rubyripper==  
===Rubyripper===  


==External links==  
==External links==  

Revision as of 20:58, 12 August 2008

What is Secure Ripping?

Secure ripping is the process of 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/BSD 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 for various reasons, allowing you to examine or attempt to correct the problems by analyzing a log file, using AccurateRip, or by looking at other drive databases.

Secure Ripping Guide

EAC

dbPowerAMP

CDex

Max

Rubyripper

External links