As reported by a beets user, using the fpcalc command-line backend can result in a bunch of diagnostic messages printed to stderr when fingerprinting fails. We should probably (optionally) capture and ignore this output instead of letting it leak through to the terminal.
As reported by a beets user, using the fpcalc command-line backend can result in a bunch of diagnostic messages printed to stderr when fingerprinting fails. We should probably (optionally) capture and ignore this output instead of letting it leak through to the terminal.
http://code.google.com/p/beets/issues/detail?id=465