Been playing with the public channel midi bindings which are pretty great. I just made a patch for the nanokontrol studio (below) and tried to do the same for my APC40. In doing, I’ve had some thoughts. (numbered for easier response)
-
Before using the programmatic binding I was doing the midi learn (channel browser) version. For when one might need that version instead, it could be quite nice if there was a one-click per channel option, because doing a who controller with three mouse clicks for each learn gets quickly tedious - I would think maybe a top-bar “learn” and then click per channel?
1a. For really efficient learning, although likely harder to implement, an autoselect-next-channel with each new control change would be sweet (ie you only need to click learn for, say, the first fader and then just move each successive fader down the line). -
For the APC40, the pads behave as notes on/off, so having the bindings to “note on” or “note off” exclusively means they don’t work. Not sure if I just don’t realize the right way of doing this, but what happens now is if I do “note on”(or off) binding, it flips true and stays forever, not having the ability to recognize the inverse. Could there be a binding to “note” and the on/off toggles the bool appropriately? is there already and I don’t understand?
other quick thoughts
3. small binding gripe: clicking the configure/add new binding can sometimes place the lower parts of the dialogue box out of frame, and scroll doesn’t shift it.
4. Any chance of having a way of learned/configured binding keep when changing a channel’s name?
5. In the view panel, “expand all” only expands two levels deep. was that a design choice?
6. When a channel has subchannels, but also a value - the value monitor doesn’t monitor.
7. Any possibility for “MidiIn” to not lock out “MIDI” to be able to use a tandem approach to handle some controls of a given controller via channels, and some via traditional midiIn?
8. Continuous controllers (faders/dials) seem to be halting the frame updates, even when not affecting anything?
Anyways, if anyone else is using a korg nanokontrol studio… here’s the vl. Depending on which mode it’s in, you may have to update all the CCs. The firmware settings for the device as I have them set up are in the zip.
NanoControlStudio.vl (123.8 KB)
settings.zip (805 Bytes)