-
Notifications
You must be signed in to change notification settings - Fork 108
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
ffmpeg backend mucks with standard input on close()
#32
Comments
That seems to fix it on my machine. It's still a bit of a mystery as to why this didn't appear before—it may have arisen only in recent (3.0?) versions of FFmpeg. |
If this fix was incorporated in beets v1.3.19 just sharing here that the condition still exists. |
Hi! Have you upgraded audioread? |
I executed a Appreciate the hand-holding. . . |
You'll needs upgrade audioread explicitly because it's not a beets dependency—it's only used for the chroma plugin. |
Ah makes sense, thanks so much. Many thanks! |
Woohoo! |
As discovered in beetbox/beets#2039, we appear to cause problems on
f.close()
in with the FFmpeg backend. Specifically, subsequent calls to read from standard input (i.e.,raw_input()
calls) no longer receive any keyboard input.This is easy to reproduce with this tiny test script:
I was able to narrow down the problem to e31af0b, which was our fix for #9. If I change that line to send SIGTERM instead of SIGKILL to the ffmpeg process, everything works fine.
The text was updated successfully, but these errors were encountered: