recording external (MIDI) events

[tiger001]

Finally it worked!

so what was wrong was that i had assigned the MIDI cc control in 3 different places:

globally, on project level and on track level
only when i removed (or re-configured ; listen on another MIDI ch) the first 2 the MIDI was recorded as documented

questions:
can the recorded MIDI track get the name of the MIDI control instead of the name of the MAIN track?
can the "Show MIDI Focused Module" be a / a little bigger and disappear the cursor (you -almost- don't see it pop up, and blocks it ) b/ maybe highlight the concerned target (track/module/)

it is a nice parameter to shortcut

2026-01-10 06_33_08-MuLab App _ Breakbeats_2.jpg

[tiger001]

FYI: In fact a track target is defined by 2 things: The target module and the MIDI channel.
That's why you can choose a MIDI channel for a track.

Ah, right. I guess I'd still be happier if the track was a module getting input from the composer and wrapping a recorder (which stored the clip references), with the composer displaying the clips held per track. Not seeing tracks as modules themselves given the overall modular nature throws me now

then what if you move those (wrapped recorded/references) clips later to a different track/target?
-i think that's why it is designed the way it is now

then why the MIDI ch is not included in the list editor (if such an important parameter)
-is it because a track can only hold MIDI information from 1 channel?

2026-01-10 07_20_50-AssiDrums(2).jpg

[MuTools]

Finally it worked!

can the recorded MIDI track get the name of the MIDI control instead of the name of the MAIN track?

You can rename tracks as you want: Right-click a track -> Rename

[MuTools]

then why the MIDI ch is not included in the list editor (if such an important parameter)
-is it because a track can only hold MIDI information from 1 channel?

When a track is set to channel 5 all events on that track will be sent to the target module on channel 5.
When a track is set to channel "Per Clip" it's the clip which defines the MIDI channel.
In that case event sequence clips can also be set to "Per Event" which means that each and every event can have its own MIDI channel. Only in this last case the MIDI channel will be visible + editable in the list editor.

[pljones]

then what if you move those (wrapped recorded/references) clips later to a different track/target?

You can do that anyway, nothing prevents you changing which track in which composer at what position holds a clip. The clip or track target determine where the events are routed.

(So, in my head a clip is a module that stores audio or events (and, for me, "either or both" - but I can see the advantages of the distinction outweigh any benefits of flexibility), with an input and output and a "play" control, a "record" control and a timeline position control; a track is a module that holds clips at positions on a timeline, having inputs and outputs per clip and "play", "record" and timeline position controls; and a composer is a module that contains tracks and other modules, has the project inputs and outputs and overall "player", "record" and timeline position controls. As each track has outputs per clip, this allows routing each clip to any module in the containing composer (or other) module.

But these still aren't modular components.)