Skip to content
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

Hang on cd rip #326

Closed
YaLTeR opened this issue Nov 7, 2018 · 4 comments
Closed

Hang on cd rip #326

YaLTeR opened this issue Nov 7, 2018 · 4 comments
Labels
Duplicate Duplicate of another issue Expected Behaviour Bug report of intended functionality

Comments

@YaLTeR
Copy link

YaLTeR commented Nov 7, 2018

Whipper hangs after printing the matched release info. This is the last line in the log:

DEBUG:whipper.program.cdrdao:executing ['cdrdao', 'read-toc', '--device', '/dev/sr1', u'/tmp/tmpduaxWy.cdrdao.read-toc.whipper']

My drive is spinning up and stopping every couple of seconds until I Ctrl-C out of whipper.

Earlier I was able to whipper offset find successfully with the same CD, which as far as I can tell involved ripping the tracks too.

whipper.log from whipper cd rip

Arch Linux x64, whipper 0.7.2.

@JoeLametta
Copy link
Collaborator

My drive is spinning up and stopping every couple of seconds until I Ctrl-C out of whipper.

Thanks for the issue report.
How long have you waited before saying that whipper hangs? The phase preceding the actual ripping of the audio tracks, phase which is handled by cdrdao, may take a few minutes as the entire CD is scanned to detect pregaps, disc layout and subcode flags.
Please try to rip the same CD again and report if whipper remains in that phase for more than 30 minutes.

Cheers,
Joe

@YaLTeR
Copy link
Author

YaLTeR commented Nov 8, 2018

Oh, I waited for about 5 mins since the offset find started so quickly. Sorry, I'm very new to ripping, I will try waiting more tomorrow.

@YaLTeR
Copy link
Author

YaLTeR commented Nov 9, 2018

Yep, after a longer wait it started. Thanks! Perhaps it would be a good idea to print a message right before this long process which says it might take a long time?

@JoeLametta
Copy link
Collaborator

JoeLametta commented Nov 9, 2018

Yep, after a longer wait it started. Thanks!

Glad to hear this 👍

Perhaps it would be a good idea to print a message right before this long process which says it might take a long time?

That's a good suggestion: we're already discussing something similar in #299 😉

@JoeLametta JoeLametta added Expected Behaviour Bug report of intended functionality Duplicate Duplicate of another issue labels Nov 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Duplicate Duplicate of another issue Expected Behaviour Bug report of intended functionality
Projects
None yet
Development

No branches or pull requests

2 participants