Question

In terms of a practical real world workflow, I think extracting chords to the chord track should read the chords / calculate the chords POST any transposition selected in the inspector etc. The idea here is that I've already got the event sounding the way I want it to. Assuming a user needs to know the chords that are HEARD and not the chords that ARENT heard (why on earth someone would prefer that, I don't know) then the order of operations should accomodate that.

Answer 1

Good idea, and if I may add:
- normal extract to chordtrack for a clip, on menu also working
- transpose on entire track in Inspector - also take transpose into account when extracting chords

so what plays comes on chord track.

Since non-destructive  very convenient if working.