It solves what i am requesting, but needs extra patching after you map your midi controller
after you map your midi to button or switch, connect this patch to it.
inputs:
- current value - connect it to switch/button output
- off value - connect it to the off value of switch - this is used to compute velocity. usually on the controller the led is controlled by NOTE_ON NOTE_NUMBER NOTE_VELOCITY controlls the LED, with velocity=127 -> LED ON, and velocity=0 -> LED OFF
-control num - note number, should be connected to control_num
- control type - should be connected to control type - right now it supports just NOTE ON event type as i use NOTE event on the buttons so for me there is no need to support any other control type, but this can be easily patched
- channel - channel of your midi device - this is used to create MIDIBUS name to which the events are sent. (MAPMIDIBUS-channel)
the midi event which is created is created on channel 1.
then you need to add to your MIDI OUT device midibus selector and choose your MAPMIDIBUS
probably pictures will explain more how it works
Patch contents:
Example how is the midi controller maped.
Example how is midi feedback patch connected to mapped switches
Example how the midi out device should be patched (in this case it is the "OUT MIDI MIX 1" device
Statistics: Posted by drakh — 31 Aug 2015, 09:10
]]>
]]>
]]>
so please add "led" mode for midi mapping - like when i press the physical button that mapped software element will send to midi output its state and the midi device will reflect that change immediatly. and it would be nice feature as well when open some workspace with this kind of mapping that elements will on load of the workspace send its state to the mapped midi device.
Statistics: Posted by drakh — 28 Aug 2015, 20:39
]]>