Error's while ripping, what to do
Posted by: Bert Schurink on 08 February 2014
When one is faced with a synchronization or reading error......
1. How problematic is this (as it still completes the rip) ?
2. What can one do to correct it ?
When one is faced with a synchronization or reading error......
1. How problematic is this (as it still completes the rip) ?
2. What can one do to correct it ?
Hi Bert
someone suggested to me that copying the cd first to a cdr helps. I tried this with a few cds i had trouble with and it worked about 75% of the time. Ive no idea why or how but give it a try.
Graeme
>someone suggested to me that copying the cd first to a cdr helps.
All this does is conceal the errors from the secure ripper, the process of reading to CD-r will encode the errors as though they are no longer errors, but they are there.
>someone suggested to me that copying the cd first to a cdr helps.
All this does is conceal the errors from the secure ripper, the process of reading to CD-r will encode the errors as though they are no longer errors, but they are there.
If that was the case, which is exactly what i thought it would do, how does dbpoweramp return the correct accurip value. Surely it would return an inaccurate rip if the cdr had errors.
Hmm, this is an interesting thread ...
Hmm, this is an interesting thread ...
Any idea Simon how this can be?
How about cleaning the CD and rip again?
How about cleaning the CD and rip again?
Did this already - it did fix it in some 2 cases, in one case I couldn't fix it at all. I hope the experts in the forum still have a solution....As I assume the errors might lead to artifacts.
How about cleaning the CD and rip again?
Cleaning very rarely helped with mine i have to say.
Foxman no I don't. If the Accurip checksum matches, the chances of it matching with errors in the data would be incredibly small, or I have mis understood how Accurip works.
Simon
Foxman no I don't. If the Accurip checksum matches, the chances of it matching with errors in the data would be incredibly small, or I have mis understood how Accurip works.
Simon
What i find even stranger, well if it is copying correctly, is that dbpoweramp tries to rip at various speeds without success. Yet when copying to cdr, copying is done at a rapid 50 times rate, which you would think would cause even more errors.
Foxman no I don't. If the Accurip checksum matches, the chances of it matching with errors in the data would be incredibly small, or I have mis understood how Accurip works.
Simon
What i find even stranger, well if it is copying correctly, is that dbpoweramp tries to rip at various speeds without success. Yet when copying to cdr, copying is done at a rapid 50 times rate, which you would think would cause even more errors.
to be some way scientific
- same drives used for ripping and burning?
- did you ever check the original CD again after burning it to CDR (in the drive it was read from for burning)
I have a few CDs with CD rot that I had moved to CDR and while the CDs are recognised they are described as not in the accurate rip database which would tie in with what spoon says. I am getting an secure rip of a inaccurate burn.
Interesting indeed.
SJB
Foxman no I don't. If the Accurip checksum matches, the chances of it matching with errors in the data would be incredibly small, or I have mis understood how Accurip works.
Simon
What i find even stranger, well if it is copying correctly, is that dbpoweramp tries to rip at various speeds without success. Yet when copying to cdr, copying is done at a rapid 50 times rate, which you would think would cause even more errors.
to be some way scientific
- same drives used for ripping and burning?
- did you ever check the original CD again after burning it to CDR (in the drive it was read from for burning)
I have a few CDs with CD rot that I had moved to CDR and while the CDs are recognised they are described as not in the accurate rip database which would tie in with what spoon says. I am getting an secure rip of a inaccurate burn.
Interesting indeed.
SJB
Hi John
to answer your questions.
1. i have two identical cd drives in my pc. Have tried ripping from both with dbpoweramp, when i have a dodgey cd. However when copying i copy on the fly, so the cd in one drive and the cdr in the other.
2. On the occasions the cdr didnt rip either then yes, but otherwise no. However i usually try to get them to rip 3 or 4 times.
once ive copied to cdr, accurip finds them correctly in the database and rips them with a correct accurip checksum. I believe secure rip just means its copied the cd correctly without errors, which is what i expected dbpoweramp to do with my cdr's.
Interesting indeed... I had assumed accurate rip was a secure hash, so even a single bit error would yield a radically different result. Must look at the accurate rip algorithm.
Can't see a way that a CD to CDR copy could fix errors seamlessly. I can believe if rewrites CRC checks to cover up ripping errors, but surely in this case the accurate rip would be different.
Hmmmmmmm.......
A single bit error would not match the AccurateRip CRC.
You can be certain if the CD-R rip matched AccurateRip then it was correct. Ripping when there are a small number of errors is like a game of chance, sometimes you are lucky, sometimes not. It could be the CD-R writing program got lucky. You can also try ripping without C2 pointers, as on some CD drives these can actually cause errors.
>someone suggested to me that copying the cd first to a cdr helps.
All this does is conceal the errors from the secure ripper, the process of reading to CD-r will encode the errors as though they are no longer errors, but they are there.
I use a program for pc's called EAC (Exact Audio Copy). I had 1 cd that wouldn't play in any player (severely scratched). I used Eac to copy it to my hard drive then re-burned it. It works fine now and it took 7 hrs to recover,
That said it is possible that the cd drive is going bad too. I had 2 burners and my primary one took longer to read and write than the other. Replaced the drive and all was well.
I haven't seen so far the magic answers for this problem. I had for some time no problems what so ever - had a new DVD drive at my PC. But now this afternoon a lot of problems with Brad Mehldau CD's in both drives. So anybody with solutions besides buy a new CD or boy it online when available ?
I haven't seen so far the magic answers for this problem. I had for some time no problems what so ever - had a new DVD drive at my PC. But now this afternoon a lot of problems with Brad Mehldau CD's in both drives. So anybody with solutions besides buy a new CD or boy it online when available ?
Haven't had this so much yet - seems to be a specific Brad Mehldau problem - or my drive deteriorated massively now......
I basically have 3 different drives in my PC from different manufacturers (one being a Plextor Premium 2), so I always have more drives to try when I come across problem discs
I also tend to play around with the dbPoweramp settings and change the speeds to specific values and try that as well.
I've only had about 5 CDs that i couldn't rip accurately out of c.1600, which isn't a bad ratio
Nick
I have now an interesting new problem. A rip which led to an accurate rip - but doesn't sound ok - with a lot of noise.......
Just fixed it the hard way. I bought this one song on Qobuz and now it's fixed. I know people might say waht about this one song while you have 3000+ albums..... I am in that sense a strange guy, things need to be correct for me and I would always annoy myself about missing that song..... The title is funny "Knives Out''
Just an in between status. I am now at close to 1700 albums and had three hard ones which have not been correctable. I am still fearing a bit what is coming as I have ripped mainly the collection which was relatively new and hadn't played so often (including the car CD player). Now I will get to the tough part of my collection with a lot of very often played prog CD's so I might now face a couple of other problems which require drastic solutions - again buying the same CD or download.....
While I possibly rip with two drives....., that sometimes solves the problem - but not always.