this is one of those times where we realise that we will have to get relatively deep into the music theory weeds for “good-sounding guitar chords” to make sense
according to some chord identifier web app, this is Em7 -> Esus4 -> Dmaj7sus2\E ^^;;
this is one of those times where we realise that we will have to get relatively deep into the music theory weeds for “good-sounding guitar chords” to make sense
according to some chord identifier web app, this is Em7 -> Esus4 -> Dmaj7sus2\E ^^;;
@steve @hikari are we talking chord recognition (from audio) or “suggest some nice chords” tools? Both might share some components (e.g., transition probability matrices), but they are applied in very different ways.
I happen to have more experience on the recognition side, but am happy to try and answer questions about either.
(Edit: on second read, it might be neither! 😂)
@steve @hikari Yeah—context is everything. A bag of notes, even when you arrange them by “pitch height”, cannot be reliably named. Rootless voicings, dropping the third, and other such changes to chords in practice make this a fool's errand.
FWIW, chord recognition infers symbols within a fixed vocabulary, and your performance/accuracy is helped if you allow it to say "not in the vocab.” A polyphonic note detector that names the output pitches would be painful to use in practice.