Hi Daniel.
I think it was myself that you'd probably referred to below as
recommending
that one should rip with "on the fly" unchecked. You've asked a few
questions below so I'll try to answer them as best I can.
Firstly, the speed at which you rip can be changed in the CDEX settings so
it may be worth trying this first before you decide to do anything
differently. The thread priority setting has 5 or 6 values that vary from
below normal to fastest. There's a balance to be had here as if you rip
at
the fastest speed you may find that you can't use your computer
effectively
while ripping because it's taken so much resource.
With regards to using "on the fly" in general, this really refers to
processing a direct data stream right from your CD-ROM rather than
extracting data first and then processing it when it's been safely read
and
stored on your hard drive.
When ripping on the fly, it is possible that you will find slight
imperfections with the finished product usually manifesting itself in pops
and crackles. This is generally as a result of jitter but could be just
down to the process of extractign and converting a direct data stream.
If you've used CDEX you may have seen on the list of tracks that there's a
right hand column called status. This can have 3 different values:
dash meaning that the track has not yet been ripped.
OK meaning that the track was ripped with no jitter errors.
X followed by a number meaning that there were a number of jitter errors
found; the number representing the number of errors in the track in total.
These values are retained by CDEX so even if you haven't noticed them
before, you can put in a CD that you've ripped previously and see the
status
results.
The reason why I mention this is that I too take great care of my CD's but
I
have been surprised by jitter errors when ripping my CD's. Some I've been
able to remove by cleaning the CD with a special CD cleaning cloth but
others I've been unable to remove. The number of jitter errors generally
dictate how noticeable the errors will be to you.
A standalone CD player usually is far better built than a CD-ROM and in
general have far better error correction capabilities. So, if you put
your
CD in your standard player you might not notice jitter errors because of
this error correction and the quality of the transport build.
With regards to burning on the fly, well, the same applies in terms of the
possible impact on the final product but there is another danger here. If
you're burning on the fly, again you're taking a direct data stream from
your CD-ROM and passing it straight to your rewriter. If there is a read
error on the source CD and you're burning, the burn could actually fail
and
then you are going to end up with a CD that cannot be played and is good
only for using as a coaster or tying together with other ruined CD's and
Robbie Williams CD's to scare birds from your vegetable plot in the
garden.
Like most things, personal preferences dictate whether you will use "on
the
fly" or not but I see it as a guarantee that is worth a little extra time
on
that rip or burn.
Hope this helps.
Regards.
Kevin
E-mail: [EMAIL PROTECTED]
----- Original Message -----
From: "Yardbird" <[EMAIL PROTECTED]>
To: "PC-Audio" <[email protected]>
Sent: Friday, May 27, 2005 11:36 PM
Subject: On the fly ripping and burning
Lately, I've been downloading and exploring a number of programs for
ripping, burning and copying music. And one thing I've noticed while
reading the documentation for these applications. That's that they don't
all agree with, who was it, I think Keith, who in the course of
describing
how to best configure the ripping settings in CDex, said that on the fly
ripping was to be avoided in favor of the slower method of writing a file
(or "image," or whatever is right to say; I've seen it put both ways
now).
as I understand it, this is so that if there's some sort of flaw in the
material being ripped, then the program will catch it and somehow rectify
the error prior to writing the track to disk. I think that's the idea,
right?
Well, in at least one of the programs I've been trying-- I think it's the
Easy CD-DA Extractor that everyone's been speaking highly of, the
developer
himself, in the instructions, recommends the on-the-fly method,
explicitly,
as he explains how to set everything for optimal ripping quality.
A moment ago, I used CDex to rip all the tracks from a CD to disk, and
was
reminded as I waited, and waited, and waited, just how much extra time
the
slower method required. I could enjoy having this procedure go faster.
What I'd like to know is, just what sorts of errors are supposed to be
avoided by using the slower method, and where in the sequence are those
errors expected to come from? I mean, if it's in case your CD is faulty
in
some way, then I'm going to just set it for on the fly. Because I know
the
condition of most of my music CDs, and have little reason to suspect that
CDex is likely to be ripping faulty tracks to disk without my knowing
that
there's something wrong with that CD.
Any advice Any ideas on this? Am I not understanding that it's common in
this ripping procedure for CDs to be corrupted or damaged in ways you
can't
know if you've only been hearing it on your stereo or computer? Or are
flaws and errors introduced at some other stage that I don't understand
about?
Thanks. I'd love to speed the process up.
And if anyone can speak to the same idea in relation to *burning* CDs,
this,
too, would interest me.
Thanks,
Daniel
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.322 / Virus Database: 267.1.0 - Release Date: 5/27/2005
_______________________________________________
PC-Audio List Help, Guidelines, Archives and more...
http://www.pc-audio.org
To unsubscribe from this list, send a blank email to:
[EMAIL PROTECTED]
_______________________________________________
PC-Audio List Help, Guidelines, Archives and more...
http://www.pc-audio.org
To unsubscribe from this list, send a blank email to:
[EMAIL PROTECTED]
