Tweet
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
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
Comment