Tweet
First off, I like to use accuraterip in burst mode, then re-rip the files that are inaccurate using secure mode.
Anymore, I've just been using secure mode from the start, but this isn't a good idea as I have to sit there and watch the progress because it seems like half my tracks anymore "need" to be re-ripped.
And if more than a few frames need re-ripped, it could potentially take hours, maybe a day! to rip a CD.
Without errors (which rarely happens), I can burn a whole CD in just a minute or two, even with secure mode.
Problem is that I am getting these "inaccurate" errors and "re-rips" of files that sound perfectly fine.
I know this because if a typical track needs to re-rip 100 frames, I obviously cancel or skip it. Then I'll burn these same "tainted" tracks in burst mode to ignore errors and they usually sound fine!
I have found that about 9.5 out of 10 files that are inaccurate or need re-ripped actually sound OK. For testing purposes, I do listen to the tracks carefully all the way through, listening for errors, usually not finding them.
I've found that, for example, if a typical 3 minute track needs like 1,000 frames re-ripped, then it is more likely to have a couple little skips in it. But if maybe 50 frames need re-ripped, then the track usually sounds fine, even in burst mode without going through with the re-rip.
My settings are mostly default (I am a noob with this program and there are a few settings I don't totally understand). In the secure settings, I don't use the ultra secure mode. The only setting I have checked that wasn't checked by default was the "C2 error pointers" option, since my drive supports it. But even before I checked that option I seemed to have these issues.
So my problem is that I want to use secure mode, but it is just so unreliable. Does anybody else have this issue?
I'm thinking that the ripper is simply oversensitive. Yeah, most of my CDs have at least a slight scratch. However, even heavily scratched and damaged CDs usually play well on my computer, rarely a skip even on my worst CDs.
Perhaps the ripper is detecting scratches that it thinks is having are impact on how the file will turn out?
I would be happy with always using burst mode, but at least in secure mode, I am made aware of potential damaged files. Even though 1 out of 10 inaccurate tracks might have a skip, I can't keep listening through 9 other entire tracks listening for a skip and not finding one. Know what I mean?
Also, is there an option that (in secure mode) if a track needs to re-rip more than 10 frames, for example, then is there any way to have the program automatically switch to burst mode for that track or have some way of just finishing the track without re-ripping the frames?
That would be really helpful. Like I said, I have interest in waiting for 600 frames to be re-ripped on a track that is likely to sound fine to my ear.
Any help? Thanks.
Anymore, I've just been using secure mode from the start, but this isn't a good idea as I have to sit there and watch the progress because it seems like half my tracks anymore "need" to be re-ripped.
And if more than a few frames need re-ripped, it could potentially take hours, maybe a day! to rip a CD.
Without errors (which rarely happens), I can burn a whole CD in just a minute or two, even with secure mode.
Problem is that I am getting these "inaccurate" errors and "re-rips" of files that sound perfectly fine.
I know this because if a typical track needs to re-rip 100 frames, I obviously cancel or skip it. Then I'll burn these same "tainted" tracks in burst mode to ignore errors and they usually sound fine!
I have found that about 9.5 out of 10 files that are inaccurate or need re-ripped actually sound OK. For testing purposes, I do listen to the tracks carefully all the way through, listening for errors, usually not finding them.
I've found that, for example, if a typical 3 minute track needs like 1,000 frames re-ripped, then it is more likely to have a couple little skips in it. But if maybe 50 frames need re-ripped, then the track usually sounds fine, even in burst mode without going through with the re-rip.
My settings are mostly default (I am a noob with this program and there are a few settings I don't totally understand). In the secure settings, I don't use the ultra secure mode. The only setting I have checked that wasn't checked by default was the "C2 error pointers" option, since my drive supports it. But even before I checked that option I seemed to have these issues.
So my problem is that I want to use secure mode, but it is just so unreliable. Does anybody else have this issue?
I'm thinking that the ripper is simply oversensitive. Yeah, most of my CDs have at least a slight scratch. However, even heavily scratched and damaged CDs usually play well on my computer, rarely a skip even on my worst CDs.
Perhaps the ripper is detecting scratches that it thinks is having are impact on how the file will turn out?
I would be happy with always using burst mode, but at least in secure mode, I am made aware of potential damaged files. Even though 1 out of 10 inaccurate tracks might have a skip, I can't keep listening through 9 other entire tracks listening for a skip and not finding one. Know what I mean?
Also, is there an option that (in secure mode) if a track needs to re-rip more than 10 frames, for example, then is there any way to have the program automatically switch to burst mode for that track or have some way of just finishing the track without re-ripping the frames?
That would be really helpful. Like I said, I have interest in waiting for 600 frames to be re-ripped on a track that is likely to sound fine to my ear.
Any help? Thanks.
Comment