CD Ripper bug on silent track?

[Agharta]

Re: CD Ripper bug on silent track?

@Agharta

Doesit show 32 tracks on the main page? and does it do the overwrite bug for all cds?

On the regular CD ripping screen it shows the correct number of tracks.

I have encountered this bug when ripping any CD to either WAV or FLAC. I haven't tried other formats. The work around is simple, manually delete the files before re-ripping. But it is very annoying.

[Agharta]

Re: CD Ripper bug on silent track?

I have another question...

I have ripped some CDs that are detected as being in the AccurateRip database. However often I prefer to slightly modify the titles (for example, changing "disc 1" to "(CD1)". I find that when I do this, the disc is no longer considered part of the accurate rip database. Is this intentional, because I am changing the naming scheme of the files?

[Spoon]

Re: CD Ripper bug on silent track?

Editing the meta data should not effect the results of AccurateRip (it will not say the disc is in the database if the disc has been ripped once).

[Agharta]

Re: CD Ripper bug on silent track?

Editing the meta data should not effect the results of AccurateRip (it will not say the disc is in the database if the disc has been ripped once).

I've just ripped some CDs where it initially detects the disc as being in the AccurateRip database (the Accurate Rip icon shows at the bottom) but after editing the text, and then clicking rip it doesn't use accurate rip, it goes straight to the secure mode...

[Spoon]

Re: CD Ripper bug on silent track?

Which version of Windows do you have? (you are getting very strange errors which no one else seems to get).

[Agharta]

Re: CD Ripper bug on silent track?

Which version of Windows do you have? (you are getting very strange errors which no one else seems to get).

Windows XP Pro Service Pack 2.

Is it possible that the overwriting error is related to the fact I'm ripping to a RAID array?

Is it possibly my drive is causing the last sector no-rip problem? I haven't read anyone else using an LG4167, so I have no one elses experiences to go on.

I have managed to rip about 10 CDs with no problems. However it has failed to use AccurateRip, even when the disc initially says it is in the database.

Also I found another CD that could not rip the last track because it again choked on the very last sector (same as with the Buckshot LeFonque CD).

Hopefully none of this will matter, I bought a Plextor PX-230A, and intend on using that as my primary ripping drive.

[Spoon]

Re: CD Ripper bug on silent track?

AccurateRip identifies a CD from the CD Table of Contents, this is straight from the CD. Meta data (such as tracks), have nothing to do with a Table of contents, but everything might be related - it could be something on your system that is reading the TOC wrong and giving x2 the tracks. It mgiht be RAID related, see what happens when the Plextor arrives, also perhaps change the communication method.

[Agharta]

Re: CD Ripper bug on silent track?

AccurateRip identifies a CD from the CD Table of Contents, this is straight from the CD. Meta data (such as tracks), have nothing to do with a Table of contents, but everything might be related - it could be something on your system that is reading the TOC wrong and giving x2 the tracks. It mgiht be RAID related, see what happens when the Plextor arrives, also perhaps change the communication method.

I've tried so many things. Turning C2 on or off, switching to the Nero ASPI layer. Changing the IDE cable to my drive. I've also run Memtest86 to test my RAM (brand new), and run two instances of Prime95 for 6 hours straight to make sure I didn't have generally stability issues. Everything seems to be fine

Tonight something new happened, I was ripping with dBpoweramp and my entire system shut down.

One thing I didn't check is my power-supply. Maybe my the current power supply is right near full capacity (450 watt from memory).

[bhoar]

Re: CD Ripper bug on silent track?

I've tried so many things. Turning C2 on or off, switching to the Nero ASPI layer. Changing the IDE cable to my drive. I've also run Memtest86 to test my RAM (brand new), and run two instances of Prime95 for 6 hours straight to make sure I didn't have generally stability issues. Everything seems to be fine

Tonight something new happened, I was ripping with dBpoweramp and my entire system shut down.

One thing I didn't check is my power-supply. Maybe my the current power supply is right near full capacity (450 watt from memory).

Apologies if I missed that you've already some of these, but:

1. Have you tried moving that drive to another machine and retrying it there? How about in an external firewire enclosure on a different machine (if you don't want to open other machines up)?

2. Is the drive and anything else on the same IDE 80-pin cable properly jumpered?
a) If one drive on cable, jumpered for master or cable select and placed at the end of the cable.
b) If two drives on cable, EITHER both jumpered for cable select OR end-cable unit jumpered for master and mid-cable unit jumpered for slave.

3. Is there a firmware update available for the drive and, if so, have you applied it?

-brendan

[Agharta]

Re: CD Ripper bug on silent track?

Sorry I didn't reply, I've been too busy with other things, and decided to just wait for the Plextor PX-230A to arrive.

One of the first things I did was try to rip the Buckshot Lefonque CD. It had no problems ripping the last track. So the problem must be an issue with my old LG4167 drive.

However there are some confusing things when using the PX-230. Firstly, the ripper says that the drive doesn't cache, however EAC says the drive does cache. Secondly, the I'm surprised that the drive doesn't seem to support C2 pointers. I've tried all sorts of CDs, including a completely scratched CD from a library, but still it doesn't detect C2.

The drive features database here:
http://www.daefeatures.co.uk/ says that it does support C2. So should I turn C2 on, even though neither DB or EAC say that it supports pointers?

[Spoon]

Re: CD Ripper bug on silent track?

I have a px-230a and it does use c2 pointers. It is as though there is some SPTI layer installed on your machine which is messing up things (ie sitting between dbpoweramp and the cd drive).

[Agharta]

Re: CD Ripper bug on silent track?

I have a px-230a and it does use c2 pointers. It is as though there is some SPTI layer installed on your machine which is messing up things (ie sitting between dbpoweramp and the cd drive).

Which communication method is preferred? I just left it on the default value at installation.

Also, should I select "read into lead in or lead out"?

Edit: Which firmware version is your drive, mine says 1.02.

[Spoon]

Re: CD Ripper bug on silent track?

STPI is best. The PX-230 cannot overread. I think 1.02 is the latest firmware. Make sure you have the drive on an ide not a USB enclosure.

[Agharta]

Re: CD Ripper bug on silent track?

STPI is best. The PX-230 cannot overread. I think 1.02 is the latest firmware. Make sure you have the drive on an ide not a USB enclosure.

Yeah it is on the master IDE, there is no slave device (I have 2 IDE controllers, the other has a DVD drive, all my hard drives are on SATA).

I've turned on C2 and Caching, even though I can't get it to detect C2 automatically, and it still says that the drive doesn't cache.

I found firmware version 1.03 here:

http://www.plextor.com/english/support/downloads/firm_230.htm

I'm not really game to try it though, for fear that it will reduce ripping speed / quality, which is my main purpose for owning this drive.

It still seems to revert to Ultra Secure ripping, even though the CD is detected int he AccurateRip database. This is very annoying...

[dougbrough]

Re: CD Ripper bug on silent track?

Re my post #275, in the Alpha thread

Having a small problem using the ripper on both Alpha 7 & 8, in that I always have an error on the last track of every CD eg

"Unable to read CD, check CD disc (frame LBA 214784) [clRipperBurst::Rip]"

All CDs rip fine using 11.5 and other rippers

Doug

Still having the same problem with Beta 1 ie like the other guys, the rip errors out on the last track in the CD - even with brand new CDs.

Doug