Originally posted by Spoon
I loaded the last 800 CDs of my sister's ~2000 CDs into one of my machines last month. I set the unit to reject discs that were damaged or missing metadata. Over a day and a half, it ripped about 650 of them and rejected about 150 (I was manually clearing the reject pile and also right-click rejecting discs that were ripping for over an hour with no progress).
I then had 150 discs that might have been rejected due to one of several reasons: a) missing metadata, b) disc damage, c) disc needs cleaning, d) temporary network outage between me and metadata providor(s) or e) unknown and/or unrepeatable cause (e.g. transient problem due to drive firmware bug). I manually check the read sides to put b and c type discs into my clean/buff pile and take care of those, returning them to the reject stacks when done.
However, I don't want to manually run the CD Ripper on the remaining 150, I want to use an automated process. And, of course, I don't want to have to pay to re-lookup these 150 either when using premium metadata.
Of course, what I want and what I get aren't always the same.

But I suspect that ripping services will have a similar workflow: first let the device sort out the problematic discs in the first run, do some quick hit cleaning/buffing (if service offered), resubmit rejected discs and then...(decision tree will differ here)...
-brendan
Leave a comment: