Sporadic failure to auto-eject after successful accurate rip

[siegel]

Hello,

I am running Release 2023-06-26 (2) on a 2021 MacBook Pro (M1 Max, 64GB RAM) with macOS Ventura 13.5.1.

I've been doing multi-drive manual ripping ("Rip from multiple drives" on the File menu) using two drives: an older Pioneer DVR-221L and a new Pioneer BDR-213M. Each is in a USB-3 enclosure connected to the computer through a Thunderbolt/USB dock.

Both drives are successfully configured for AccurateRip, using Burst mode, and both drives are configured to "Eject CD Only if Accurate" after rip.

In spite of the eject setting, I am finding that quite frequently, one drive or the other (it varies; it's never the same drive) will not eject the ripped CD. This is in spite of all of the tracks on the CD having ripped accurately (according to the display).

So far I have not been able to identify a pattern to explain which drive will fail to eject.

When auto-eject fails, I can manually eject; but that interrupts my workflow a bit. And since the setting is to auto-eject after a successful rip, I would certainly expect it to do so as long as the conditions for auto-eject have been met (which, as far as I can tell, they are).

Is this a known issue with a solution; or is there something I can do that would help diagnose this?

Thanks for any advice you (individually or collectively) can provide.

[Spoon]

Re: Sporadic failure to auto-eject after successful accurate rip

It is likely a low level conflict between the 2 drives and USB. Try ripping on one drive only, does it fully work then? then try the other drive only.

[siegel]

Re: Sporadic failure to auto-eject after successful accurate rip

It is likely a low level conflict between the 2 drives and USB. Try ripping on one drive only, does it fully work then? then try the other drive only.

Thanks for the suggestion; the experiment is in progress now. I set up a multi-drive rip, but am using only one of the drives at present. So far, in about 20 discs ripped, there has been one failure to eject after an accurate rip. I'll continue testing, and then switch to the other drive.

[siegel]

Re: Sporadic failure to auto-eject after successful accurate rip

After ripping a few more discs without incident on the DVR-221L, I switched to the other drive (BDR-213M). It too behaved as expected and auto-ejected after each successful accurate rip.

So, I started ripping from both drives again, and sure enough, I started getting sporadic failure to eject again. *Mostly* on the Pioneer DVR-221L, but occasionally on the BDR-213M.

This supports your hypothesis that something's happening at a low level that might be interfering with communication with the drives, though of course there's no way to guess what that might be. (And it is certainly not likely a problem that lends itself to easy diagnosis.)

I've got an LG WH16NS40 drive in hand that is considerably newer than the DVR-221L. I'll be putting it into service soon; and I'll be curious to see whether things behave any differently.

[siegel]

Re: Sporadic failure to auto-eject after successful accurate rip

...so, with a third drive connected (now running two LG WH16NS40 and one Pioneer BDR-213M, there's no substantive change in behavior. Sporadically, but frequently, one (sometimes two) drives will fail to eject after an accurate rip is completed. It's not consistently any particular drive.

Granted that this is all likely down to USB gremlins and/or a timing issue of some sort, but I wonder if there's anything that the ripper can do to work around this? For example, after sending the eject request, check again in a couple of seconds, and if there's a disc present, and it's the same one that was just ripped, try ejecting again? (That would be a total hack, of course, but some times that's what it takes...)

I'm getting the sense this isn't a known or frequently encountered issue; so I'll be happy to provide any diagnostics you like, in the event this is something you are interested in investigating further. (And if not, that's totally OK. The ripper is doing a fantastic job overall and I am quite happy with it.)

[Spoon]

Re: Sporadic failure to auto-eject after successful accurate rip

Certain drives always report a disc is loaded, even though it is not, once work arounds are implemented they can have other unintended consequences.