Live Play Matrix issue

[pljones]

It's easy enough to add MIDI through - just link the Event Input to an Event Output and hit save.

[Braserox]

mulabrackmidi.png

Just made picture .
Left midi input target
Middle down modified mux instrument with midi thru
Right up Composer module aera to verify midi data in monitor
Renamed rack to fit midi channel
Ch1 has modified mux instrument with in out
Ch2 is with Dexed vst only one have found with built in Midi thru
Ch3 has no plugin
In monitor result midi data showed up on ch1 ch2 ch3 when changing midi channel on external midi gear,
Strange that midi channel 4 with event input in Composer module aera dont work (no midi data).

Addon have found the problem.
Dont use Event inputs directly in Midi input target list .
Use Composer container.
Input event inside composer container can be connect to Rack 1 or Mux.

Midi wiring is. Main composer > Main input event connected to Composer container.
Midi device > Midi input target list > Composer container > Event input > track container (best for mixing ) or other event related mux.

This way live matrix is working from external gear.
Carrefull : use large keyboard on edge and dont use random key because live matrix is stealing keynotes.

[pljones]

Hm... interesting.

I've two racks, each with just an event monitor, plus an event monitor off the composer input. Composer input goes to the two racks.

I've set ch2 to go to rack 2 and ch3 to go to rack 3. Fine, those channels only go to rack 2 and rack 3, as expected.

First test: leave all other channels at "Focused Module" and click "Composer" in the project modular area. Now ch1 and ch4 to ch16 go to all three monitors with no filtering. That's because they hit the composer event in and it's routed to all three monitors.

Second test: add another rack ("Rack 1") with a monitor and link the other event inputs to that rack. Apart from ch2 and ch3, all channels now display only on the added rack's monitor, not the composer monitor.

Third test: add a monitor to Project modular area and link to MIDI In. Allow ch1 to go to focused module. Nothing appears on the project monitor still.

However... despite my thinking Rack 1, 2 and 3 are the same, I get nothing appearing on Rack 1 monitor. Which is odd.
Here's my project ZIP file:

MuLabMonitorRouting.zip

EDIT
And here's the reason for me:

MuLabMonitorRouting-theError.png

Unlike the other racks, I'd not linked the new rack to composer event in.

[pljones]

So, open the project in Reaper and set ch1 to Composer, Event Input.

The problem here is that an "Event Input" has no event input connector. So the traffic goes nowhere.

Indeed, several of the listed "MIDI Input Channel Target" modules have no event input connector...

MuLabMonitorRouting-theSecondError.png

Ideally, only modules that can receive Event Input would be displayed as targets.

[MuTools]

Addon have found the problem.
Dont use Event inputs directly in Midi input target list .
Use Composer container.
This way live matrix is working from external gear.

Exactly

That was what i tried to explain in my earlier reply, but maybe it was not clear enough.
I've updated the docs so to make this more clear:
https://www.mutools.com/info/M9/docs/mu ... n-map.html

That doc page now includes:

The Note Action Map works on the main event input jack of a composer. Any events that are effectively mapped and taking action are processed and filtered out, thus these events do not reach the respective Event Input module in that composer's modular area.
So if you want, for example, play a composer's Note Action Map from external MIDI gear, make sure to target the composer itself, not the Event Input module inside the composer.

[MuTools]

The problem here is that an "Event Input" has no event input connector. So the traffic goes nowhere.

Correct.

Indeed, several of the listed "MIDI Input Channel Target" modules have no event input connector...
MuLabMonitorRouting-theSecondError.png
Ideally, only modules that can receive Event Input would be displayed as targets.

Good point, thx.
The next update will take that into account.