MuLab 10.2.29 beta

[tiger001]

when sending a MIDI controller here -and activating the MIDI learn button- nothing is learned/mapped
this is the rack MIDI controller map (right click on a rack)
(you'd think when you are in this window, there's a connection made from the event input)

2026-01-06 18_21_49-Edit Mapping.jpg

[pljones]

Why? You have a modular area - you make your connections as you see fit. If you don't want a connection, it would be ... odd ... to force you to have one.

[MuTools]

when sending a MIDI controller here -and activating the MIDI learn button- nothing is learned/mapped
this is the rack MIDI controller map (right click on a rack)

I don't have a MIDI controller available atm so can't doublecheck this atm.

[tiger001]

Why? You have a modular area - you make your connections as you see fit. If you don't want a connection, it would be ... odd ... to force you to have one.

i want a fool proof mode for newbies and people who are not that into modular
all good and so, but what about a basic mode where everything works as it should / as described
-leave the modular to the experts

specifically in this case : why have a MIDI learn button if / when you need to make lots of connections first/before to make this work ?
(put the MIDI learn button in the modular area then)

[MuTools]

specifically in this case : why have a MIDI learn button if / when you need to make lots of connections first/before to make this work ?

You don't need to make connections for this MIDI Learn.
I'll doublecheck this case when i'm back in the office with all equipment around.
Until then, simply select the CC manually,that will get you going making music.

[pljones]

I just tried this:

* Open MuLab, use the Template Composer project (one track, Basic Synth in the rack)
* Right-click the Basic Synth rack header and choose Edit MIDI Controller Map
* Double click to add an entry, then double click to edit the entry
* Move a controller
* Set the Parameter to Mute, click OK, click Done

It just worked. (Now I have a rack mute button, just like that.)

[tiger001]

yes, probably it will work with a basic setup/start-up

but it is not working as should in my project :
setup up & playing is, recording that info is not

[pljones]

OK but you said it didn't work. Can you give a stepwise example of it not working? Or are you saying it does work? You've a separate thread about recording. If that's the only issue, then fine.

[MuTools]

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

What's changed:

• Plugins now have the option to set a global preference for the Smart Bypass.
  Now the Smart Bypass is definable per plugin instance, per plugin item in the plugin database, or globally in the app preferences.
  Existing projects and presets will keep the same Smart Bypass setting as before.
  New projects and presets will use "Default" for plugin instances, "Default" per plugin database item, and "Off"in the app preferences.
  That way it's easy to change the app preference to whatever you want and this will affect all plugins in the project.
  And you can still overwrite that per individual plugin, when needed.
  Note that when a plugin goes into Smart Bypass mode, its green power led dims subtly, as an indication.
• New "Plugin Silent Output Threshold dB" preference, both in the app preferences and per plugin item in the database.
  This is used to optimize the audio output from plugins, as some plugins output very low, unhearable audio to avoid floating point denormals, but these redundant values consume cpu.
  By default all audio output from plugins below -200 dB will be silenced (zeroed), which will help in optimizing cpu usage.
  But you have full and precise control over this threshold value, if needed.
• In some specific cases of trashing modules, there were a couple of issues. Fixed.
• Other small improvements.

Beta version!
Test reports appreciated!

[pljones]

• Plugins now have the option to set a global preference for the Smart Bypass.

Is there a "Reset everything below this level to current parent setting" option? If you've an existing project where you want to change all settings for existing plugins - or maybe everything for one MUX, etc, or one plugin everywhere - being able to do so without hunting it down by hand would be good. (In the current project only, of course.)

• New "Plugin Silent Output Threshold dB" preference, both in the app preferences and per plugin item in the database.

So -200dB is into the 32bit internal depths (my sound card "only" does 24bit) -- I could probably raise it to -150 without loss of quality: if any signal gets that quiet in the processing chain, I'd probably want to consider it silent. Nice to have it configurable! Does it smoothly round off the low level signal to zero to prevent edge effects? Or is it simply not processed further (and left at whatever low level it was until turned back into 24bit)?
EDIT: OK, Gemini's explained the idea to me now.

[tiger001]

annoying: you have to double-double click a value to edit a value in the event editor
(before you can edit it through the keypad)

[MuTools]

Is there a "Reset everything below this level to current parent setting" option?

No.

So -200dB is into the 32bit internal depths (my sound card "only" does 24bit) -- I could probably raise it to -150 without loss of quality

This silence threshold is only applied on the output of plugins, which all is in 32 bit float land. It has nothing to do with the output to your sound card.

[pljones]

annoying: you have to double-double click a value to edit a value in the event editor
(before you can edit it through the keypad)

This is because you don't have to edit it through the keypad, you can drag the value up/down with the mouse whilst you're listening to the effect. (Personally, I'd like an option to skip that step.)

[tiger001]

indeed, but you can edit it through the keypad so i'd like a less convoluted way where i just punch in my values

other places you just can hover over parameters and change them with the mouse wheel, why add 1 more step here? (in the event list editor)

[mgiambro]

Test reports appreciated!

Looks good to me.