QUOTE(Dex4now @ Jun 19 2003 - 04:11 PM)
If I could expand on this question a bit, this thread is talking about
encoding, but does the same hold true relative to ripping?
I was under the impression that you shouldn't ask the cpu to do
much, if anything else, while actually extracting the data from the CD.
Thanks, Dex
This should be easy enough to test. Simply rip a wav file under heavy load (i.e., tons of stuff going on, like mp3 encoding, ape decompressing, internet downloading, word documents loaded up, etc...), and then rip the same wav file under very low/no load (after a clean boot). Compare the two files using EAC to see if there are any differences. I doubt there will be, but you never know.
On the related topic, prior to buffer underrun protection on most modern CD-R/W drives, it was common practice to burn under a low load environment. Ripping under heavy load never caused me any problems, but I always made sure when I was burning to keep other activity at a minimum. With today's buffer protection, that's no longer necessary (on most drives). Today I rip/encode/burn without worrying too much about CPU load.
Daffy