missing MIDI controller support in MuLab

Official support for: mutools.com
RELATED
PRODUCTS

Post

mutools wrote:Ok, so the problem is that certain MIDI devices sent out their buttons as MIDI CC value 0 = off and value 127 = on and when you map that MIDI CC to a mute it will go on when you press the button and off when you release the button, right?

Question 1: Can't you program your MIDI device so the button switches between on and off with each press?
i don't realy know, but i think MIDI controller object should know button press status and send switch button light on or off to MIDI controller. this make sence to keep the same status in DAW and MIDI controller
mutools wrote: Question 2: Does anyone have tips for me how this is well handled in other apps?
brainstorming for CC on/off and Note on/off MIDI controller button handling

"Mute" CC on/off:
===> MIDI-OX Version: 7.0.2.372
===> Log Opened: Fri 28-Sep-2012 07:30:48 ===>
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
00000C48 1 2 B0 1F 7F 1 --- Control Change
00000CD5 1 2 B0 1F 00 1 --- Control Change
<=== MIDI-OX Log Closed: Fri 28-Sep-2012 07:30:58 <===

can configured in MuLab and nothing must changed.
controller handling should compare last pressed button command with previous.
if only DATA2 byte is different this command have to be ignored and last pressed button command compare memory can initialised.


"Mute" Note on/off
===> MIDI-OX Version: 7.0.2.372
===> Log Opened: Fri 28-Sep-2012 07:29:53 ===>
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
00000B78 1 2 90 10 7F 1 E 0 Note On
00000C02 1 2 90 10 00 1 E 0 Note Off
<=== MIDI-OX Log Closed: Fri 28-Sep-2012 07:30:01 <===

Note on/off assignement should be only possible for MIDI controllers in MuLab.
controller handling should compare last pressed button command with previous.
if only DATA2 byte is different this command have to be ignored and last pressed button command compare memory can initialised.
Note play should prevented for MIDI controllers.

Post Reply

Return to “MuTools”