More > Pono Music

PMW vs EAC for Ripping

<< < (3/5) > >>

BrianKW:

--- Quote from: Awesome Donkey on June 19, 2015, 06:39:02 pm ---No, (most) modern ripping software including Pono Music World, JRiver Media Center, Exact Audio Copy, XLD, dBpoweramp, etc. all have secure ripping as an option. AccurateRip was useful back in the days when drives were unreliable but if you use secure ripping you shouldn't need AccurateRip. Read this for more information on secure ripping.

--- End quote ---


Cheers!

Cheezmo:

--- Quote from: JimH on June 19, 2015, 04:06:11 pm ---Accuraterip isn't needed for modern drives.  If you're doubtful about quality, use Secure Rip.

--- End quote ---

I completely disagree.  I have several computers with "modern" drives and often have a CD with a scratch or something that one can accurately rip and another can not.

If you don't use AccurateRip, you are probably fine 99% of the time, but down the road when you play a track though headphones and hear a click, you'll wonder how many of your rips are messed up and never know, until you rip them all and verify with AccurateRip.  Do it right the first time.

Awesome Donkey:

--- Quote from: Cheezmo on June 19, 2015, 08:12:26 pm ---I completely disagree.  I have several computers with "modern" drives and often have a CD with a scratch or something that one can accurately rip and another can not.
--- End quote ---

That's what secure ripping is for - it reads the disc multiple times to test/verify before copying. If it encounters errors during either the test or copy phase, it'll tell you.

Awesome Donkey:

--- Quote ---Secure ripping is the process of making sure there were no errors during the extraction of audio from a CD. It normally involves attempting to get consistent results from successive re-reads of the same sectors, and is sometimes combined with other strategies, such as


* using the drive's own error reporting (after its own error correction fails) to know which sectors to re-read
* defeating caches (some drives cache audio data during DAE)
* and comparing checksums of extracted audio with those obtained by others.
The basic function of ripping software is to get the CD's table of contents (an index of track start positions), and then for each track to be ripped, it tells the CD drive to go to the beginning of each of the track's data blocks (sectors) and read them in, one at a time. On an ordinary audio CD, each block is 2352 bytes and corresponds to 1/75th of a second of sound. The software saves that incoming data into an audio file (WAV or AIFF format, usually, as those formats are almost identical to the data coming in from the drive), or the software streams the data into another audio encoder "on the fly", so the user doesn't have to convert it to another format like MP3 in a separate step.
This sounds simple, but it becomes complicated when parts of the CD can't be read accurately, for example due to scratches. And there's actually a lot of variation in whether each drive can reliably and accurately go to the spot it's told to read, and in the way it detects, reports, and handles errors, such as those caused by scratches. That is, every CD drive will give the ripping software 2352 bytes of data for each block the drive is told to read, but that data might be different each time, due to physical problems with the disc or limitations of the drive's hardware. Or the data might be the same each time, but is different when obtained from a different drive.
Ripping software that claims to have "secure ripping" will take into account the capabilities and limitations of the drive, and will make the drive read each sector multiple times. Then it will use various methods of analysis and re-reading to ensure that the data was read as correctly as possible. A bit-perfect rip may not always be possible, and so these programs will report on any errors that could not be corrected, allowing you to examine or attempt to correct the problems, such as by generating a log of suspicious positions or doing some kind of automatic "glitch removal".
The term "secure ripping" is usually used in opposition to "burst mode", which implies the drive is simply told to read a range of blocks just once, and the incoming data is accepted without any extra error detection or correction by the software. Since it doesn't involve re-reading of data (other than what the drive might always do automatically), burst mode is naturally faster than secure ripping.
--- End quote ---

Cheezmo:
OK, as long as Pono's secure ripping feature lets you know if there is any kind of error, I would agree it is just as good.

But, I notice in that definition of secure ripping, the 3rd step is basically AccurateRip, comparing against a known good checksum.

I'm just saying that is a prudent step to be 100% sure you haven't got any errors.

Navigation

[0] Message Index

[#] Next page

[*] Previous page