View Full Version : Ripped one track twice on two different rippers (inaccurate)

04-14-2008, 03:01 PM
Hey, I am getting

Track 17: Ripped LBA 252600 to 265930 (2:57) in 0:36. Filename: Z:\My Music\311\Greatest Hits '93-'03\17- First Straw.m4a
AccurateRip: Inaccurate (confidence 13) Secure [Pass 1, Ultra 1 to 1]

on both my brand new plextor 2301 and my sony crx320ee. Any ideas?

04-14-2008, 04:34 PM
Have a real issue now. Ripping a double disc ACDC back in black and the drive disappears yeilding an error on the last two tracks. (plextor 230a)

04-14-2008, 06:59 PM
yielding whoops. misspell. Seems to work better if I individually rip the problem tracks one by one. Might have just needed a reset since I just recently updated the firmware to 1.03. However I am still curious about why one track on my 311 cd is inaccurate on 2 drives, but nothing else is wrong on it.

04-14-2008, 07:35 PM
Nope drive still locks up sometimes and then just disappears from my computer

04-14-2008, 08:39 PM
What version of dMC are you using, haibane?

04-14-2008, 08:53 PM
the latest stable release... 12.4 I believe. It seems to be ripping fine now as its going frame by frame on the same track as before, but I don't understand what happened earlier. I did change it over to a master isntead of a slave to my sony drive. Aside from that nothing has changed.

04-14-2008, 09:19 PM
Alright so clearly appears to be working and needed to be on the master slot, but what's the deal with the 311 track? Should I try my HP dvd burner even though it doesn't have support for any external features?

04-14-2008, 10:02 PM
damn... locked up after an hour and a half of ripping one track... I feel disappointed in my plextor drive :(.

04-14-2008, 11:51 PM
Looks like the plextor doesn't do read out... hmm

04-15-2008, 03:10 AM
If 2 different drives give the same CRC then the track will be fine.

04-15-2008, 02:47 PM
Cool. Any idea why the drive would seemingly unmount itself after a long error repair?

04-15-2008, 03:06 PM
Cool. Any idea why the drive would seemingly unmount itself after a long error repair?

Drive firmware bug in the drive if connected via IDE/SATA...

...or either drive firmware or bridge firmware bug if connected via USB/firewire.


04-15-2008, 11:28 PM
Now its just locking up on my eric clapton unplugged cd. track 13 freezes at about 53% and last time it gave me a BSD and then shut down

04-16-2008, 12:20 AM
after reset appears to be working. Running a bit slow, but nothing to cry home about.

04-16-2008, 12:26 AM
nope BSOD returns, but at 98% read

04-16-2008, 12:32 AM
So I switched to track 14 cause track 13 is now giving me just ERROR... and track 14 is ripping at x0.1. What is going on?

04-16-2008, 03:31 AM
No computer should BSOD doing any CD Ripping, I would try programs which stress test the computer.

04-16-2008, 08:35 AM
Well I did just recently switch to the beta. Should that be an issue? I have ran many stress test programs recently that have had no issues.

04-16-2008, 11:30 AM
No, or put another way, on my computer there is no code I could write that would cause a BSOD, even if I tried (as long as I don't write a driver).

04-16-2008, 01:03 PM
hmm. Well I am running on vista 32 bit. I have two cd drives. The plextor is the second. I upgraded the firmware to 1.03 via the compatability test on plextor's page. I let vista install the driver. What else? Could it be a faulty drive? The eric clapton cd does have some sort of ring around it towards the edges. Is this copy protection? Is it possible since I have been ripping it all day yesterday it needed a break?

04-16-2008, 01:09 PM
One thing I wonder though is why is it dropping to 1.5x and such on the disc...?

04-16-2008, 02:34 PM
Appears to have made it to frame by frame ripping. It might be working ok then.

04-16-2008, 02:57 PM
No CD disc should effect a cd drive, but I am sure there are bugs in drive firmwares which causes them to drop out.

04-16-2008, 06:46 PM
Guess that disc just had a few bad scratches. Its weird cause the track plays fine till the last 10 seconds or so then skips throughout that whole part, but the last track just after that is shot bsically. Odd how the first of the two had something like 7000 frames to repair. Oh well it didn't finish anyhow