adamjakab / BeetsPluginBpmAnalyser

A beets plugin for obsessive-compulsive music geeks to add BPM information to their songs.
MIT License
22 stars 3 forks source link

BpmAnalyser not outputting BPM Values #18

Open OannesGPT opened 1 month ago

OannesGPT commented 1 month ago

Problem

Running your command in verbose (-vv) mode:

beet bpmanalyser --dry-run title:Tripura - Wizard Project

Led to this problem:

bpmanalyser: BpmAnalyser exec threads: 6
bpmanalyser: Done.

Setup

My configuration (output of beet config) is:

directory: C:/Users/Hannes/Desktop/Test
library: C:/Users/Hannes/AppData/Roaming/beets/library.db
import:
  copy: yes
  write: yes
  move: no

plugins:
  - bpmanalyser

bpmanalyser:
  auto: no
  dry-run: no
  write: yes
  threads: "AUTO"
  force: no
  quiet: no

logging:
  level: DEBUG

My plugin version (output of beet bpmanalyser -v) is:

bpmanalyser: Bpm Analyser(beets-bpmanalyser) plugin for Beets: v1.5.9
OannesGPT commented 1 month ago

I added an import into the library manually now: "beet import "C:\Users\Hannes\Desktop\Test\Tripura - Wizard Project.mp3""

After which I had to go through a process of identifiying tags? I made my way through and tried running dry analysis again: "beet bpmanalyser --dry-run" After which I seem to have got it to process the first time, but with error:


bpmanalyser: BpmAnalyser exec threads: 6
bpmanalyser: Error(3221225477): Unknown error! Unparsable response.
bpmanalyser: Done.

Any help would be very appreciated. I tried multiple audio analysis tools with varying results but not reliable enough to count on for an entire library. It looks like this module does more accurate readings and I'm willing to try it out properly. Thank you all

adamjakab commented 1 month ago

@OannesGPT - I will take a look. We need to get the raw response from the analysis so we can understand why it is not possible to parse. In the meanwhile you could do the following: