-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Specify max amount of retries per sector #30
Comments
What you suggest - limiting the maximum number of rereads or rereads/per specific sector, makes sense, especially if put under a flag. My suggestion then is to code this up and try it. If that seems to work fine we can then put it here and let people try it. If there are no objections, then put out a release. With respect to cdparanoia, I don't have any more insight or inside information than you do. |
So after many hours of hitting my head against the wall, I found out that Why is that mod even there? Anyway, with that removed, I can now play with different |
That code hasn't been changed from cdparanoia-III-10.2. I haven't a clue as to why it's there other than what's in the comments which also pretty much go back to the original cdparanoia. Actually, I do see a comment add a little above the line you cite:
|
I've replied to the paranoia mailing -- not sure if you're on the list: https://marc.info/?l=cdparanoia&m=158763276007524&w=2 |
I am not on that list. If you don't get any response there, you might also try [email protected] which is low volume but a little more active. Thanks to spammers you have to join the list in order to post, but as I said, there is very little mail and of course you can ask people to email you directly and unsubscribe in a little while. |
Subbed. |
I wrote this mail to the cdparanoia-users list as a while ago:
https://marc.info/?l=cdparanoia&m=158566693027322&w=2
Basically, I am interested in getting this in place for both libcdio-paranoia and cdparanoia.
Do you have any pointers / places to look?
Keep in mind that the above mail is written with cdparanoia in mind, not libcdio-cdparanoia, but I assume the same paranoia logic applies.
The text was updated successfully, but these errors were encountered: