-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transport error when using --force-overread #17
Comments
After much more reading... Appears to some other sources the SH-S223X series of Samsung/TSSTCorp drives don't support overread, so if that's the case then I doubt libcdio-paranoia will be of help here. |
Is there a way to detect whether a drive supports overread? Perhaps there is a MMC command you can send to the drive to have it report that it supports or doesn't support overread? |
Don't know but there should be a way to detect if a drive supports overread in some form (EAC does it) I know with the EAC tests for HTOA (similar) a yes is a maybe, a drive can return silence for a non-silent HTOA on a disc and EAC interprets it as supporting reading of HTOA but a no is a certain no. |
Drive: Samsung SH-S223L (flashed patched firmware years ago to remove DVD region code and riplock)
OS: Ubuntu 18.04 running in an LXC container due to avoid dependency problems on host, block device passthrough, this works.
CD tested: Mark O'Connor "Heros"
I use whipper to rip the CD's, but when testing the overread feature, after the last track of this disc, it would get stuck at ripping stage at 99%. I manually ran cd-paranoia with the same arguments as whipper used and it does rip the selected portion of the disc and then spits out "transport error" at the end.
Here was the command ran.
If I remove the
sample-offset
there is no more transport error, but this imply anything useful?Or is this whole issue implying my drive doesn't support
--force-overread
in the first place?Thanks.
The text was updated successfully, but these errors were encountered: