TWIMC,
As a guitar player, I've successfully implemented some of the changes I
need to remotely control phrases in the "sequence mode" of NS. At this
point, I'm at a crossroads as to how best to move forward.
I've modeled the midi cc pattern toggling methods by adding another cc
that enables adding a phrase (== cc value #) to the *end* of the
sequence list. So theoretically, there could be 128 phrases defined and
arbitrarily chosen to be added to the playlist. Unfortunately (or maybe
fortunately!), no pedal controller I know of has 128 buttons.
I'm considering adding a similar ability to *insert* after the current
playing phrase, and also enabling some other discreet midi control like
*delete* next phrase, and *delete* from end-of-playlist, back-to-top
(home_button) and toggle_transport.
My question\crossroad is how best to implement this control. I've added
CC 21 for insert-at-end-of-playlist. I could add CC 22 to
insert-after-current. I could add CC 23 and start mapping the discreet
functions to CC 23 values, etc, etc..
Personally, as a guitar player, I'm not gonna use\trigger 128 phrases
(nor could I keep those in my head). So I don't need to devote an entire
CC to that. But it seems that since NS stores 128 phrases, that it makes
sense to map a CC to that potential. And if I was using NS for other
things, having 128 "cues" might be useful\necessary.
On the other hand, for discreet controls, one CC should handle just
about everything NS can toggle.
The other thing is that the midi [foot] controllers aren't always that
smart\extensible. Personally, because I'm using a couple of hardware
controllers, midi hardware devices and several apps, I'm going thru
mididings as a midi smart router to convert midi note values to CCs,
route to specific devices\apps, etc., etc..
But most musicians (especially us guitar players!), wouldn't be able to
approach even something like mididings to route\munge\map midi. So
whatever is done in an app like NS, should keep in mind, if at all
possible, that most users don't code. I mean even mapping note numbers
to CC values is mind blowing.
Using CCs is efficient use of the midi spec. I like that. But it would
be wise to make using it in this app as consistent as possible. So I'm
looking for input on what the original thoughts were with respect to
remote midi control and where i'm currently headed with this. And, what
do others want to see in midi performance control (at the sequence level)?
Thanks for your thoughts and consideration,
rickbol
