MIDI learn - 2nd control parameter

[parityflux]

It would be so awesome if one could set the second control number on buttons and switches. As it stands, if I MIDI learn a switch and set the control type to NOTE ON, every time I trigger it, the midi-learned-control sends out the programmed note at a fixed velocity of 127. If I could set the velocity to any number, it would help me send back velocity (button lighting info in this case) to my control surface (I use mackie control mode + motorized). Since this midi-learned object mechanism is hidden (e.g. cannot be modified in the patch editor) the only way to control it is via the exposed midi learn section of the button, and velocity (or a second control number) is unfortunately missing.

[oli_lab]

I guess you can always patch a midi in/midi filter to command the switch and as well a midi create on the output of the switch.
all this could be encapsulated in a subpatch (and make good use of polyphony for multiple switches need)

seems complicated but I reckon midi learn should keep simple and more complex fonctions should be done in patching as to cater for each user special needs.

at least it's what I love in Usine compare to "prefabricated" music softwares witch tend to herd musicians into a uniform mindset.

my two cents

[parityflux]

Oli,

Yah you are right that it can be patched another way by not using MIDI learn. My line of thinking was that this doesn't seem to be a complex change to MIDI learn, involves 1 more byte field for NOTE messages and it could have other uses than my use-case scenario. It may very well be a pain to code, as these things go (I'm a .NET developer and understand how things can play out in real code).

The ease of use of MIDI learn solves a substantial number of control problems and I love how it works. Soooo much easier than wiring up things every time. I change my physical control surface layout often to be specific for a gig. The colored buttons really really help. I mostly use Usine when setting up for a gig or for song inspiration and not for leisure programming joy. So anything that makes it a little quicker for me is awesome. I figured that the suggested change would not make it more complicated other than adding one more parameter that is available in many of the other MIDI modules and that it would be an intuitive change.

I will work on making a suitable solution another way as time permits. Doing it in a subpatch is a good idea. I also want to dig into fastscript, then SDK, and I might just do it with this particular problem.

-j