MTG/essentia.js

Incorrect Key Signature Analysis Output

Opened this issue · 0 comments

What is the issue about?

  • Bug
  • Feature request
  • Usage question
  • Documentation
  • Contributing / Development

What part(s) of Essentia.js is involved?

  • essentia.js-core (vanilla algorithms)
  • essentia.js-model (machine learning algorithms)
  • essentia.js-plot (plotting utility module)
  • essentia.js-extractor (typical algorithm combinations utility)

Description

I’m utilizing essentia.js as a means to analyze song metrics (finding BPM, key signature, and mode of songs) and while I get correct output for the most part, I’ve been regularly getting incorrect key signatures. Below, you’ll find screenshots of the output that essentia.js is producing compared to the accurate song metrics (cross-referenced the accurate song metrics through multiple different websites to make sure the website I got the screenshots from weren't the source of the incorrect song metrics). I've also added the file that utilizes essentia.js for additional context.

Steps to reproduce / Code snippets / Screenshots

BW Web
BW Analysis

PJ Web
PJ Analysis

RHCP Web
RHCP Analysis

https://github.com/henryc007/music-analysis

System info

-macOS
-Node 18.18.0
-Firefox & Google Chrome
-Essentia.js 0.1.3