So, what you are suggesting is a command which lets you define a different sequence depending on the chord being used.
Sure, it'd be possible ... but since there are about 100 different chords defined by MMA, that means you'd really need about 100 different sequence patterns to do it properly ... and then you'd really need to multiply that by 12 for each possible key ... and then by another 3-7 for each octave. Now, you can argue "but I don't use all those chords" and that's legit ... but the minute you do something with you limited chord set the next fellow or your next song will come along needing "just one more". And, that's all fine 'cause you're suggesting to do this in a user-mode type of situation. Right?
That's why MMA relies on voicing for it's chord patterns so that the different notes can be munged into something that "probably sounds good"
I'm not closing the door on this, at all. But: That is why plugins exist! It should be relatively easy to create a plugin:
- call it PlectrumSequence
- load it with Plugin @PlectrumSequence
- In your MMA code have something like this: @PatternSequence Am / Bm
- The plugin would read that and return the Am and Bm as a chord line for other tracks to use. Internally it would need to set up a call to create the needed internal sequence
- Or, in the about you might just set it up as a Riff?
I'm flying on no coffee right now, so I have no idea what might or might not work. But, when we get into real specific stuff like this request I'm reminded that this is why the plugin idea was created.
Now, it might not be feasible to do this with a plugin. Does that mean we need to change internal MMA define behaviour and add more commands ... or do we need to fix or expand the way plugins work?