Design UX for creating actions for a song

[mickmister]

While cretaing the issue https://github.com/jamtools/jamtools/issues/4, I was thinking about how the user would be able to declare music actions to multiple instruments at once, and I want to expand on the "legend" concept. Where you first define your variables for the song, then arrange them.

An action can be an aggregate action containing many actions. For example, I can have a "Play A major chord" action, that does 3 things:

• Plays specific voicings for the chord on synth 1
• Plays some melody or arpeggio on synth 2
• Plays bass notes on synth 3

Then the action used in the step can be another aggregate action that contains a WLED action:

Chords: "A D Em G"

These are unique identifiers for the chords defined earlier. You can output this into a midi file to see how it sounds.

Steps:

• 1:
  • Trigger A1:
    • Chord: AMajor
    • WLED: Next Preset
  • Trigger B1:
    • Chord: AMajor
    • WLED: Random Color
• 2:
  • Trigger A1:
    • Chord: DMajor
    • WLED: Next Preset
  • Trigger B1:
    • Chord: DMajor
    • WLED: Random Color

It would be cool to be able to have this in a YAML file. Possibly TOML file.

https://www.npmjs.com/package/midi-file

Lots of cool info on midi file format here https://mido.readthedocs.io/en/latest/midi_files.html

[mickmister]

Would be cool to have a midi clip that's meant to loop indefinitely through a given section. May not make sense to have it change per chord/step.

[mickmister]

Would also be cool to have a button trigger a midi clip on demand, so not necessarily mapped out to a specific part of the progression ahead of time. Just a midi trigger to a given sample, midi or audio. Get weird with sound effects etc