Closed GoogleCodeExporter closed 9 years ago
Awesome. Again, my apologies that this ffmpeg backend turned out to be much
less mature than I originally thought. Unexpected variations in the way the
FFmpeg CLI behaves can cause weird problems like this.
To begin fixing this, can you help narrow this down to the file that's causing
the crash? The best way to do this is probably to disable threading (put
"threading: no" in ~/.beetsconfig) and import a few suspect albums in verbose
mode ("beet -v import ..."). This way, you'll see exactly which file is being
fingerprinted at the time of the crash.
Original comment by adrian.sampson
on 26 Mar 2012 at 6:39
Well this is annoying. I've tried to import some stuff now, and it's crashed
twice on two different places. I can't consistently reproduce this problem. :/
Original comment by akegata@gmail.com
on 29 Mar 2012 at 5:29
Argh; that's frustrating. I just pushed two new changes to audioread that (a)
might make the timeout more robust and (b) will dump out FFmpeg's stderr output
if a timeout occurs. This way, we should be able to see what's going wrong in
the FFmpeg CLI utility to cause this.
Original comment by adrian.sampson
on 29 Mar 2012 at 8:12
Alright, that sounds good. I'll try it out when I have some time.
With that version I wouldn't have to use the -v flag, right? It makes the whole
import process very messy. :P
Original comment by akegata@gmail.com
on 29 Mar 2012 at 8:40
Nope, -v isn't required to get that output. Here's hoping.
Original comment by adrian.sampson
on 29 Mar 2012 at 8:54
Thought I should give this a try now, but I'm a bit confused about getting the
latest version of audioread. Downloading the zip from github gives me
sampsyo-audioread-0.5-4-g16e1deb.zip, but the change log says 0.6 is the
version with this fix.
Original comment by akegata@gmail.com
on 4 Apr 2012 at 8:31
I'm pretty sure that's the latest version -- I think 0.5 shows up in the
filename because it's the most recent tag (I haven't tagged & released 0.6
yet). I think the 4 in there means that the tarball is 4 commits ahead of the
tag (and 16e1deb is the hash of the most recent commit).
Original comment by adrian.sampson
on 5 Apr 2012 at 3:22
Any news on this? Did the latest versions of audioread clear this up?
I'll close this ticket for now but we can reopen if the problem persists.
Original comment by adrian.sampson
on 20 May 2012 at 6:45
Original issue reported on code.google.com by
akegata@gmail.com
on 24 Mar 2012 at 7:14