DBPA Batch / Nimbie - Process hangs after ripping error reported

[MCM30114]

I've seen a consistent behavior out of the batch ripper where once a CD is deemed to have a ripping error, the process seems to hang.

Observed behavior:
1) DBPA Batch Ripper reports Ripping error
2) Disc does not eject into failed pile
3) errored disc remains in the CD Drive
4) DBPA Batch then reports "No CD after Load"
5) Process hangs. Does not eject CD, does not load a new one.

Desired Behavior:
1) DBPA Batch Ripper reports ripping error
2) Disc is ejected into the bad read pile
3) next disc is loaded
4) operation on the next disc proceeds

In the case where there is NO METADATA associated with a Disc, it does the eject process and proceeds as expected. It appears that this hang process is related to a disc read error.

I have been able to clear the jam, evaluate the objected to disc (while the disc visually to me looks ok, i will clean the surface and run it back through as the 2nd CD in the upcoming queue) Usually a clean and re-run will cause a successful rip (as long as it can find the metadata)

Image attached .. Let me know if you want me to pull logs next time this happens ..

Mike

[Spoon]

Is there a disc in the drive? if you look in Windows explorer can you browse the CD disc and it shows cd tracks?

[MCM30114]

1) Disc in the drive -- Yes (I have to clear it out manually to get the batch ripping process to start again)
2) On Fail, does Windows Explorer see the CD and is it browsable -- Good question, didn't check. Will check and report back on next failure instance.

[MCM30114]

It does appear that when this state happens, I see the drive connected to the computer in the file explorer, but the CD that is in the drive does not appear. and then it hangs in this state until I clear it.

Once I clear it, I need to re-insert the "zombied" disc back in the queue about +1 or higher in the stack for it to try to read that CD again. If I put it immediately back in, it gives the "same as last disc" condition and then ejects the disc. (this is assuming there is nothing wrong with the disc that would cause a read failure like excessive scratches or damaged media).

For me and the collection of CDs I'm trying to rip, it happens 1-2x about every 125-150 discs (randomly, not really apparent what causes the Alzheimer's issue there.)