Open barestides opened 6 years ago
The other thing we should store in a state are values tied to midi controls, which are currently only used with player/live-player
.
The player right now isn't especially useful. It can just play a bunch of tracks given to it. It's not interactive at all. Its tracks should be stored in a sort of state, that can be accessed by both the user and other code. It should also be capable of playing from a time in the tracks, say 2 bars in.
I think this is necessary, at least to manage available instruments. We need to say which programs (qsynth, drumkv1) we're using, and what instruments are set to which channel in those programs.
I also think organizationally, it would be better to just specify a keyword for an inst in a track; and then the player would look up the fn in the state.