Summary
The old slopsmith-plugin-editor shipped a dedicated chord_analysis.py module (Krumhansl-Schmuckler key detection + chord naming from pitch-class sets) and an analyze_chords route (routes.py). The current editor has no chord_analysis.py and no analyze_chords/detect_key route anywhere in pakr/.
Ask
Reintroduce key detection + chord naming as editor tooling — useful both as an authoring aid (auto-suggest a chord name for an authored note cluster, per the chord-model work already landed in #1/#3/#4/#5) and as a possible input to the audio-to-MIDI transcription path (#361) for turning transcribed notes into named chords.
Context
Found via a comparison audit of old slopsmith-plugin-* forks vs current feedBack-plugin-* plugins, done to identify features lost when Slopsmith was scrapped (DMCA/PSARC) and rewritten as feedBack. Verified not a duplicate of any open issue (searched "chord analysis", "key detection", "krumhansl").
Summary
The old
slopsmith-plugin-editorshipped a dedicatedchord_analysis.pymodule (Krumhansl-Schmuckler key detection + chord naming from pitch-class sets) and ananalyze_chordsroute (routes.py). The current editor has nochord_analysis.pyand noanalyze_chords/detect_keyroute anywhere inpakr/.Ask
Reintroduce key detection + chord naming as editor tooling — useful both as an authoring aid (auto-suggest a chord name for an authored note cluster, per the chord-model work already landed in #1/#3/#4/#5) and as a possible input to the audio-to-MIDI transcription path (#361) for turning transcribed notes into named chords.
Context
Found via a comparison audit of old
slopsmith-plugin-*forks vs currentfeedBack-plugin-*plugins, done to identify features lost when Slopsmith was scrapped (DMCA/PSARC) and rewritten as feedBack. Verified not a duplicate of any open issue (searched "chord analysis", "key detection", "krumhansl").