MuLab 10.2.29 beta

[Palunto]

Hi, will send by email, not allowed to attach .txt it seems.

[MuTools]

Email is fine, thx.
Just FYI: You can also attach zipped files here on the forum.

[MuTools]

Thx for the 2 log files.
I see that you're mixing the use of MuLab 10.1.23 (latest official release) and MuLab 10.2.23 (latest beta).
Note that projects are never downward compatible, only upward compatible, ie. older MuLab versions don't support files saved by newer versions.

[tiger001]

10.2.23:
i get an error message when starting up

[MuTools]

Nothing serious, it's because that function has changed name to "Monitor MIDI Input Focused Target". Just recreate your custom shortcut.

[MuTools]

In the next update that alert will show some extra info:

Shortcut to unknown function X.
Most probably this function has been renamed or removed.
Try recreating the shortcut.

Sometimes functions are renamed for good reasons but it invalidates existing shortcuts and that's what this alert says. I think it's best to notify the user about this, rather than silently removing an existing invalidated shortcut. Right?

[tiger001]

Roger

i must add that i only get the error message once
on subsequent starts, it doesn't show anymore
probably because ML deletes the (original) shortcut
(so now i don't remember what key it was assigned to)

[tiger001]

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

MuLab Plugin M10.2.22 beta for Win64 is available:
https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed:

• Drum Note Processor: Fixed a bug that caused exhausting an event processing resource which stalled event processing after some time.
• Level Meter Headroom preference: Default value lowered from 6 dB to to 3 dB.
• Extra level meter color: "Over Level Color" which is used for levels above 0 dB.
• Other small improvements.

Below pic shows 3 dB meter headroom and the new default "Over Level Color".

so,

the headroom is the 'empty' space in the metering ?
the over level color is the orange one?

[MuTools]

i must add that i only get the error message once
on subsequent starts, it doesn't show anymore
probably because ML deletes the (original) shortcut

Indeed.

(so now i don't remember what key it was assigned to)

The alert text has been further improved: It will include the original shortcut.

[MuTools]

the headroom is the 'empty' space in the metering ?
the over level color is the orange one?

I propose you create a new rack and insert a test sine generator, that's the best answer to your questions, imho.

[MuTools]

I can also report this:
Using the above test i tried to repeat the issue by playing MIDI input using a Impact LX 25+.
When rapidly playing random notes and also moving the mod wheel at the same time, from time to time i got a hanging note. I double-checked the raw MIDI input data with the debugger and indeed sometimes MIDI note messages were simply not coming into MuLab. That's at the very raw midi input that comes from the device driver. Then i checked in 3 other daws, the very same issue. It is independent from MuLab and i assume it's a bug in the MIDI driver, maybe related to running status. Then i checked the device driver for Impact LX 25+ and Windows tells it's up to date, and i saw the device driver is made by Microsoft. So maybe this is a more widespread issue in Windows MIDI? Anyone who knows more about this?

I repeated this test on the Mac, using MuLab 10.2.23 and using that same Impact LX25+, and no hanging notes at all, even when really playing the keyboard wildly while sliding the pitch bend and modulation wheels. On Windows it does generate hanging notes, not only in MuLab, but also in other DAWs. Conclusion: This is an issue in the Windows MIDI driver.

[tiger001]

using save preset as and choosing to name new, this pops up:

2026-05-17 09_00_34-MuLab App _ Grid247.png

rather confusing: when choosing save as, i'd expect to input a new name anyway (also why select new name again) , then what i choose?
keep as is doesn't keep my input and reverts to original name but doesn't save as (anything)
rename overwrites the original? (in name and file?)

[tiger001]

how to select multiple tracks at the same time to adjust some of it's properties (e.g. width):

2026-05-17 09_40_34-MuLab App _ Grid247.png

one thing that really annoys & worries me:
every time i select a track, it arms record
-wasn't there a preference orso to turn this off?

can i define these kind of tracks (modulation) default width?
can i define every type of track a default width (and maybe even other properties)

2026-05-17 09_45_26-MuLab App _ Grid247.png

-sorry, with width i mean ̶h̶i̶g̶h̶ height

and then, suddenly recording a new subtrack, the width is in no relation (to it's own main track, or to tracks of same type)

2026-05-17 10_07_57-MuLab App _ Grid247.png

[tiger001]

something doesn't add up here:
which preset is used ?
-the one in the master or the one in the (master) effect ?

2026-05-17 10_43_50-MuLab App _ Grid247.png

or is it the preset in the preset ?

[MuTools]

using save preset as and choosing to name new, this pops up:
2026-05-17 09_00_34-MuLab App _ Grid247.png
rather confusing: when choosing save as, i'd expect to input a new name anyway (also why select new name again) , then what i choose?
keep as is doesn't keep my input and reverts to original name but doesn't save as (anything)
rename overwrites the original? (in name and file?)

I'll explain that case, which only happens if the user uses different names for MUX Patch and the corresponding Preset File Name.

Lets start from a new project with the default Basic Synth.
Now i tweak that Basic Synth sound and i like it.
Inside MuLab i rename it to "My Basic Synth".
Now i also want to save it as a preset and click Save As and use the new file name "Basic Synth 1".
So i have chosen a different name for the preset file name and the patch file name which is a rather confusing situation. That's what that popup alerts about, and it gives the option to resolve it by clicking "Rename This MUX Modular". If you do "Keep As Is" however then the different names will be preserved and the result is this:

P7.png