MuLab 10.2.29 beta

[FabBad]

Love this!!

• Modular Areas: Cable editors now have an integrated signal monitor for quickly monitoring/diagnosing the signal flow.

[pljones]

But the project's main module can be any module, and as of M10.2 it can be a module on any modular level. Changing the project's main module will update the project editor to show the editor of that new main module.

Does this clarify it?

No, the problem I see is changing the project main module sometimes causes the project editor to fail to open and the main display to show "Main Module" and "Modular Area" boxes only. Nothing after that can restore the editor to display the right thing except closing and reopening MuLab. Except it rarely happens and I can't tell why. It might have gone away in 10.2, though - I've not tried it so much (not had much time for trying it out, and the plugin version is what I use mostly).

Please see this doc page:
https://www.mutools.com/info/M10/docs/m ... uting.html

I couldn't see how that clarified the behaviour I described. Why should an event monitor module in connected to an Event Input show events where the new signal monitor on that cable shows nothing?

[MuTools]

No, the problem I see is changing the project main module sometimes causes the project editor to fail to open and the main display to show "Main Module" and "Modular Area" boxes only. Nothing after that can restore the editor to display the right thing except closing and reopening MuLab. Except it rarely happens and I can't tell why. It might have gone away in 10.2, though - I've not tried it so much (not had much time for trying it out, and the plugin version is what I use mostly).

When you can repeat it please let me know the steps.

[MuTools]

Please see this doc page:
https://www.mutools.com/info/M10/docs/m ... uting.html

I couldn't see how that clarified the behaviour I described. Why should an event monitor module in connected to an Event Input show events where the new signal monitor on that cable shows nothing?

When you have "Automatic MIDI Input Focus" enabled and you click the Event Monitor module, then MIDI Input focus goes to that Event Monitor and so MIDI Input is dispatched to the event input jack of the Event Monitor. Hence the Event Monitor shows the events but the cable connected to its input jack does not.

Does that clarify it?
If not, please send a simple MuProject demonstrating the case you encounter.

[pljones]

Sorry, that's not making sense: if I focus on a module, you're saying I can no longer monitor the events on the cable going to that module? Isn't that exactly the scenario when I'd want to monitor the cable?

[MuTools]

The cable monitor monitors what's going thru the cable.
MuLab's MIDI Input dispatcher sends MIDI input to the first event input jack of the module that has MIDI Input focus. So in your above example that's just beyond the cables connected to that Event Monitor's event input jack, hence the cable doesn't show any events, but the Event Monitor does. Hope you see the picture.

Tip: If your goal is to monitor the very source MIDI input coming into MuLab, i.e. before the MuLab's MIDI input dispatching, see Project menu -> Tools -> Monitor MIDI Input Events.

[pljones]

My goal is not to have to cable in event monitor modules each time I want one. But... it's reliable, it shows everything regardless of focus later down the signal chain, which is what I want.

[MuTools]

My goal is not to have to cable in event monitor modules each time I want one.

That's what the new built-in cable monitors do.

But... it's reliable, it shows everything regardless of focus later down the signal chain, which is what I want.

I don't understand your point, sorry.
Please explain me your point in the simplest way possible, preferably with a simplest possible real life example / muproject.

[pljones]

You've going around in circles like talking to an AI now.

I explained above.

[MuTools]

I did not understand your explanation.
I would appreciate if you would share a screen video demonstrating what you mean.

[pljones]

EventCables.mp4

Opened a Factory->New (composer), added an event input and an event monitor. Connected input to monitor and through to the Composer. Focused on Monitor, monitor shows events. I'd expect editing the input cable to show me what's arriving. It doesn't. Looking at the event cable input to the Composer shows what's output by the monitor.

I was hoping I guess that it would let me monitor Event Input 1 - it's generally the input side of things I want to see when debugging. If the input's right but the behaviour is wrong, I've done something wrong. If I can't see the input, I don't know where the problem is.

[MuTools]

Thanks for the video and additional info on the issue you encounter.
It shows that it's not yet clear to you how MIDI input works in MuLab and i take that on me, as it proves the relevant documentation is insufficient or unclear. I've already made some quick edits to that doc page i mentioned before, but will do my best to further improve the info soonish. Here's the link again: https://www.mutools.com/info/M10/docs/m ... uting.html

So about the case you're describing:
I assume you have all 16 MIDI Input Channel Targets set to Focused Target and that Automatic MIDI Input Focus is on. So it means that MuLab will update the MIDI Input Focused Target to the module you're working with.
When you click that Event Monitor module in the project modular area, it becomes the Focused Target and so MIDI Input is routed to the event input jack of the Event Monitor, hence the Event Monitor shows the events, but the upstream event cable before the Event Monitor does not show any events.

Note that, in MuLab App, a "Project Event Input" module in the project modular area is a bit ambiguous because you might expect it to receive the MIDI input but it will not receive any MIDI input unless you explicitly define that in the Project MIDI Input Channel Targets map, or if it happens to become the MIDI Input Focused Target.
The Project MIDI Input Channel Targets map is the main thing that defines how MIDI Input is routed.

Does this clarify it better?

[MuTools]

MuLab App M10.2.9 beta for Windows 64 bit is available:
https://www.mutools.com/mulab/app/lates ... /beta.html

What's changed:

• Drum Note Processor now supports choke groups. Upon choking a pad, MuLab not only sends out all pending note offs for a choked pad, but also a CC 120 = All Sounds Off. MuLab's PolySynth does react on CC 120 by instantly ending all voices so it has the desired result. If you would have a VST/CLAP plugin connected to a drumpad, then it depends on that plugin whether it supports CC 120.
• Drum Note Processor can now be switched to a 24 pads version. The multiple of 12 still is maintained because it neatly maps to the number of keys in an octave.
• Drum Note Processor now plays out octaved versions of the drum keys. For example, using a 12 pad version: When C4 is received it maps to pad 1 and it sends out a C4 on output 1. When D4 is received it maps to pad 3 and it sends out a C4 on output 3. That's how it used to work and how it still works. But now when C3 is received it maps to pad 1 and now it sends out a C3 on output 1. (previously that was still C4) When G5 is received it maps to pad 8 and now it sends out a C5 on output 8. (previously that was still C4) Also the drum labels reflect this. This feature simply gives more musical options. Attention: This impacts already projects or presets using a DNP receiving notes outside the [C4-B4] range. This attention note is shown in an alert when opening a possible impacted project or preset.
• Audio Dispatcher now has both full input and output control. So you can do 1->N, N->1, N->N and N->M. Attack, release, solo mode are all separately controllable for input and output.
• Fixed a practical issue when using a non-mirrored cycled curve with no start phase offset as curve in a modulation cable.
• MIDI Input Focus: When the MIDI Input Focus is on a modular Event Input module, then nothing happened as the modular Event Input module has no event input jack. Now the MIDI Input dispatcher has been improved so that, if it is about the first event input of a MUX, then it uses the event input jack of that MUX, and so the events will stream out of the Event Input module.
• The "Show MIDI Input Target" display has been finetuned now showing more relevant info and in a more neat way. This function has been removed from the top piano keyboard context menu to unbloat that context menu as this option is too technical for that UI location. This diagnostic tool function still is available via Project menu -> Tools. It can also be used via a shortcut.
• Modular editor now supports Ctrl+A to select all modules.
• Changing the note key names for a module inside a rack slot did not immediately refresh a sequence clip editor on a track to that rack MUX. Fixed.
• Other small improvements.

[MuTools]

MuLab App M10.2.10 beta for Windows 64 bit is available:
https://www.mutools.com/mulab/app/lates ... /beta.html

What's changed:

• New "Audio Gate" module: It's a simple audio pass/mute module controlled by note on/off events. This was already possible using other modules, but this compact module is more quick and easy to use, and more efficient.
• Project -> Tools -> Monitor MIDI Input Focused Target now uses a non-modal floating window, which makes it much easier to better understand how MuLab updates the MIDI Input Focused Target while clicking around in a project.
• Fixed an issue with the MIDI Channel filter property in the Audio Dispatcher.
• The "Attention: modified operation" alert upon loading pre-M10.2.9 files with an Audio Dispatcher or Drum Note Processor has been muted.
• Other small improvements.

[oldcastle]

Thanks, Jo.

Quick UX observation: The save dialog appears every time I quit, even if I've just saved. If I save and then immediately use the 'X' button, Ctrl+Q, or the menu to exit, I expect ML to close without prompting me again.