-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Crash in autobpm plugin / Docs incomplete #5185
Labels
bug
bugs that are confirmed and actionable
Comments
JOJ0
changed the title
Crash in autobpm plugin
Crash in autobpm plugin / Docs incomplete
Apr 10, 2024
@tandy-1000 Hi :-) Just a heads up. Maybe you have seen this issue? And also note that we should improve the docs a little here. Please clarify if my |
Looks like a simple bug in |
3 tasks
snejus
added a commit
that referenced
this issue
Aug 26, 2024
Fixes #5289 and #5185 Tried using the `autobpm` plugin and found a couple of issues: 1. #5185 `librosa` dependency was missing in `pyproject.toml` 2. Simply including the plugin in the configuration made `beet` take over 4 seconds to start up. 3. BPM detection failed due to another missing dependency, `resampy` 4. #5289 Librosa `beat_track` function returned unexpected type which made the plugin and the entire import process fail. Addressed each of the above, slightly refactored the plugin and added tests.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sorry for being brief. A quick report on a crash I'm experiencing with the rather new autobpm plugin. Something with librosa. I'm on Python 3.11.
Problem
Running this command in verbose (
-vv
) mode:Led to this problem:
Here's a link to the music files that trigger the bug (if relevant):
difficult to provide....
Setup
Also a quick note on the existing docs: https://docs.beets.io/en/latest/plugins/autobpm.html
The installation requirements could be better. We need to
pip install librosa resampy
as far as I figured it out. That correct? We should explicitely state that in the docsThe text was updated successfully, but these errors were encountered: