|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
207.216.246.51
In Reply to: Re: I noticed the same thing.... posted by BrassTeacher on February 27, 2007 at 17:14:01:
Brassteacher:EAC does implement error correction, and can be set up to "permit lower extraction speed" I find that with these enabled you get extraction speeds of around 2.5 times, and "zero glitch" rips.
If "permit lower extraction speed" is disabled, the speed jumps up to about 10 times, but glitches can be had in the hundreds if not thousands. Very bad.
This setting is a must for EAC IMO.
Follow Ups:
I can't seem to find "permit lower extraction speed" in my EAC "Options". Where do I find it?
Gerry
....thanks, Presto. So much for instant plug-and-play, as we would love to expect. Whether it's iTunes or EAC, there are specific operations details all of us need to know before proceeding with hard disc playback.
It's my understanding that the Glitch Removal is simply a wav editing processing that removes pops and clicks. In other words, it should only be used on a track that is very scratched and damaged and you could not extract a better rip (and has audible pops and clicks). The Glitch Removal is not error correction and will not give you a more accurate rip. In fact it is known that EAC's implementation will find a lot of false positives. (Sounds within a song that it thinks are pops and clicks)As for the difference in the ripping speed. The best way to determine your optimal rip speed is to rip a track at multiple speeds. Then use the "Compare WAVs" tool. If the one ripped at 10X is identical to the one ripped at 2.5X then there is no need to use the slower speed. (Unless of course you have a scratched/damaged disc)
I recent used the compare wavs tool on the same files except on was ripped faster (I to just re-did eac). Anyhow, it took a while, and then it just reported a blank screen.THe screen had something like "errors found" on the top line, but nothing below them. It was just blank.
I guessed tha there were no errors, but it wasn't specifically clear if this was the case, or if this was an glitch.
Yes, when the screen comes up blank, that means they are an exact match. No errors. If there were any discrepancies, they would be listed by error (such as "different samples") and then the position (time).
This post is made possible by the generous support of people like you and our sponsors: