-
Notifications
You must be signed in to change notification settings - Fork 92
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
Issues with finding offset #182
Comments
cdparanoia doesn't force overreading into the lead-out on drives that don't support doing so. This will cause issues verifying the rip offset on the last track. the AUR package cdparanoia-overread adds a workaround for this. Try replacing cdparanoia with this package and running ripping with If that doesn't work, please try running with the environment variables |
With |
Seems to go fine until the last track
I'll get some output with the debug options after this times out or I cancel it heh. EDIT: Yep no go
I'll get some debug output now. |
Here's the full log. It ended at the same result of failing to rip track 12 5 times. http://ix.io/z6e |
Can you try it with libcdio's cd-paranoia? See #175 |
Also, with the overread cdparanoia, you also need to specify -x to cdparanoia, and there's no flag in whipper to do that right now. |
Seem's I already had libcdio-paranoia installed (Actually both)
Could something possibly be conflicting? (No conflicting files so I assume whipper is just picking one of them) |
Whipper currently always just takes 'cdparanoia'. I will try to make a PR that changes this ASAP. |
The option @parkerlreed did it work using cd-paranoia? @MerlijnWajer I'm in a position where I have a lot more time on my hands now, so if you need to hand off something let me know. I have a local branch where I've refactored most of the accuraterip code (as part of the larger cleanups), and am going to spend this week & weekend getting ARv2 support finalised and PR'd. edit: I know this venue isn't the right comment thread for the above comment. shrugs |
@RecursiveForest The log I posted above was from paranoia-overread. EDIT: If you were referring to trying with libcdio, I don't know exactly what to change in the whipper code to make it do that. Was waiting for a PR to try it out. |
Could you try ripping again using whipper with
Thanks |
Will do. I'll be back at that computer in a couple hours. |
Sorry for the late response. Without the
Interestingly enough if I check the V1 database the files seem to match.
|
Do the v2 checksums from the ripped tracks match the database? |
How do I tell exactly? The whipper log only seemed to check V1.
|
Seems to be working great with 2 drives now
Already had a a 100% RIP from one and testing offset of the other right now. |
whipper-git 0.5.1.r45.g3f248bf-1
Arch x86_64
I tried the offset of 6 as mentioned in the database but that fails.
I let it scan for offsets and it's on a seemingly unending journey
The text was updated successfully, but these errors were encountered: