MuLab 10.2.29 beta

[MuTools]

I have no clue.
Anyone else who can repeat what tiger001 describes?

[tiger001]

if you want to see it in action i can do a teams

w10 64b, Novation Remote controller to sent MIDI's universal language

[MuTools]

A quick extra question:
Click Project menu -> Tools -> Monitor MIDI Input Events.
Do you see the MIDI CC coming in as expected?

[pekbro]

I can not replicate that either, the cc number is shown automatically for me.

This is the first time I've ever tried to use midi learn in mulab, I don't use controllers
for midi cc, only use that for modulation, I'm only setting channels up manually
all these years.

[tiger001]

A quick extra question:
Click Project menu -> Tools -> Monitor MIDI Input Events.
Do you see the MIDI CC coming in as expected?

yep, works as expected:

2026-06-01 20_48_08-Project MIDI Input Event Monitor.png

strangely, when i switch to MIDI ch 2 that is not recognized/changed either
so ML recognises MIDI input but don't pinpoint MIDI channel and defaults to channel 1:

2026-06-01 20_53_23-MuLab App _ New.png

further, i thought these defined which input MIDI channels were allowed to be received by which devices - but even when i send notes or MIDI cc on MIDI channel 9 from my RemoTe controller, these are recognized and played (notes for exemple)
-or should i see these ports as full 16 channel MIDI busses ? (times 16 devices then)

2026-06-01 21_16_57-MuLab App _ New.png

[MuTools]

further, i thought these defined which input MIDI channels were allowed to be received by which devices - but even when i send notes or MIDI cc on MIDI channel 9 from my RemoTe controller, these are recognized and played (notes for exemple)

Oops i see a big misunderstanding: You've selected the same MIDI input device multiple times. Only choose a MIDI device max 1 time. Each chosen MIDI device always works on all 16 channels. A MIDI port = a MIDI device, not a MIDI channel.

-or should i see these ports as full 16 channel MIDI busses ? (times 16 devices then)

Yes indeed.

So as a test with a simplified setup remove all MIDI input devices except 1 and retry the Map MIDI controller test thus with just a single MIDI device selected. Does that work ax expected? Do you see MIDI input coming in as expected on all channels? If that works fine you can add *other* MIDI input devices.

[MuTools]

MuLab App M10.2.29 beta is available:
https://www.mutools.com/mulab/app/lates ... /beta.html

What's changed:

• Import MIDI file now automatically removes empty bars. This results in a much better overview of imported MIDI composition structure.
• Import MIDI file: When an imported clip ended with an event other than note, eg. MIDI CC, then the resulting clip length was not appropriate which caused that last event to be disabled. Fixed.
• Importing MIDI files could generate events with microticks. Although this is technically correct, it's not practical and not necessary, so this has been tuned. FYI: More info on microticks on https://www.mutools.com/info/M10/docs/m ... ticks.html
• When loading MUX presets while a related sequence clip editor is open, the Note Key Names were not immediately updated. Fixed.
• When adding or removing racks there could be an unpleasant gap in the audio output. This has been optimized. There still can be a little click upon adding/removing racks (as in some other DAWs) but now it's much less.
• Merge Selected Sequence Clips didn't work right for lengthless events (eg. MIDI CC) on the very start of a clip. Fixed.
• Removed "Remove Empty Slots" from MUX menus where it is not relevant.
• Internal optimization of how audio clips are streamed.
• Other small improvements.

[tiger001]

further, i thought these defined which input MIDI channels were allowed to be received by which devices - but even when i send notes or MIDI cc on MIDI channel 9 from my RemoTe controller, these are recognized and played (notes for exemple)

Oops i see a big misunderstanding: You've selected the same MIDI input device multiple times. Only choose a MIDI device max 1 time. Each chosen MIDI device always works on all 16 channels. A MIDI port = a MIDI device, not a MIDI channel.

-or should i see these ports as full 16 channel MIDI busses ? (times 16 devices then)

Yes indeed.

So as a test with a simplified setup remove all MIDI input devices except 1 and retry the Map MIDI controller test thus with just a single MIDI device selected. Does that work ax expected? Do you see MIDI input coming in as expected on all channels? If that works fine you can add *other* MIDI input devices.

unfortunatly exactly the same behavior, even with only 1 MIDI port active (or a few, see below)

send controller on MIDI channel 2 (same on MIDI ch 1), parameter is not displayed, MIDI channel learnt is 1

2026-06-03 21_21_40-MIDI Setup.png

2026-06-03 21_22_31-Project MIDI Input Event Monitor.png

2026-06-03 21_11_30-MuLab App _ New.png

[tiger001]

another thingie i find confusing (and stressing at times) is that in many checkboxes you can right (mouse) click to up 1 (choice) but you can never use left click to down 1 / return

-could be the other way around, that confusing thus

[MuTools]

unfortunatly exactly the same behavior, even with only 1 MIDI port active (or a few, see below)
send controller on MIDI channel 2 (same on MIDI ch 1), parameter is not displayed, MIDI channel learnt is 1

Puzzling issue. Maybe something setup specific..?
As another test: Try another single MIDI input device. (try typical test to narrow down steps)
I'm afraid i'm without answer to this.

[MuTools]

another thingie i find confusing (and stressing at times) is that in many checkboxes you can right (mouse) click to up 1 (choice) but you can never use left click to down 1 / return
-could be the other way around, that confusing thus

Please give a concrete example.

[tiger001]

e.g., in above windows (MIDI setup) you can [ left]click on an input port to go through all choices [up], but you cannot [right] click to go down all choices

[MuTools]

That's indeed how it works.
The left-click steps thru the available list values.
Right-click is reserved for context menus.
If you don't like the left-click behavior in that case, click the drop down button to choose from the list.

[tiger001]

it steps through the available values but it doesn't (really) ; it doesn't cycle through (when last value reached it just stops)

[sl23]

Yeah that is a little annoying. I would like it to cycle back to first item too. But this should be global. There are other areas I noticed this too.