MuLab 10.0.85

[pljones]

Should the rack modular area meta parameters match the rack control settings..? I remember there's some divergence somewhere -- and I've understood it before now...

Screenshot 2024-12-21 183143.png

[MuTools]

When loading pre-M10 projects/presets then the legacy racks will indeed have some predefined meta-parameters, but that's just a left-over from the past, to maintain compatibility.
In M10, these rack meta-parameters are fully customizable, just like any MUX Modular.
Does this answer your question?

[PelletProject]

I like how you're expanding on the use cases for sub-racks, and I'll definitely toy around with using them in Audio Sequences a lot

I wonder how you feel about making adding sub-racks easier in any way. I was thinking maybe a right-click function for racks to add one sub-rack within it and having its own audio input to start, with that sub-rack's output going to the main rack's first slot by default. Or maybe the inverse where it turns a selected rack into a sub-rack?

I could see it being intuitive either way. I personally would go the former.

[pljones]

When loading pre-M10 projects/presets then the legacy racks will indeed have some predefined meta-parameters, but that's just a left-over from the past, to maintain compatibility.
In M10, these rack meta-parameters are fully customizable, just like any MUX Modular.
Does this answer your question?

It was the Rack MetaParameter values I was asking about -- they don't match the controls on the Rack front panel. So I take it the front panel controls aren't driving the MetaParameters but are directed to the Mixer Strip itself?

[MuTools]

I wonder how you feel about making adding sub-racks easier in any way. I was thinking maybe a right-click function for racks to add one sub-rack within it and having its own audio input to start, with that sub-rack's output going to the main rack's first slot by default. Or maybe the inverse where it turns a selected rack into a sub-rack?

Thinking draftly: I doubt whether that would be the one and only desirable routing for a new sub-rack. I rather think that IF there would come some shortcut to add a sub-rack then the routing of new sub-racks then should be customizable, but i don't immediately see how. Maybe lateron some idea pops up.

[MuTools]

When loading pre-M10 projects/presets then the legacy racks will indeed have some predefined meta-parameters, but that's just a left-over from the past, to maintain compatibility.
In M10, these rack meta-parameters are fully customizable, just like any MUX Modular.
Does this answer your question?

It was the Rack MetaParameter values I was asking about -- they don't match the controls on the Rack front panel.

I see now, thanks for elaborating.
Will be fixed in the next update.

I also see now that even new default racks still have these 4 meta parameters mapped to the Mixer Strip but as far as i see that's not necessary anymore and this can be removed in M10.0.25.

So I take it the front panel controls aren't driving the MetaParameters but are directed to the Mixer Strip itself?

Indeed.

[focusrite]

Omnisphere above 1 x magnification bug

[MuTools]

Please repeat this issue on your computer and after it happened goto your MuLab/User/LogFiles folder and email the most recent log file to

[MuTools]

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

Now also the complete MuLab 10.0.25 Plugin beta zip package is available: https://www.mutools.com/mulab/plugin/la ... -win64.zip

What's changed:

• Audio stream clip -> Convert To Audio Sequence: When the audio clip did not start at the start of the audio, then after saving-reloading such converted clip the start point was wrong. Fixed.
• Legacy racks: Initially there could be a visual mismatch between the values of the rack mixer strip and the premapped meta-parameters. Fixed.
• When saving an audio sequence with multiple outputs as a MuClip and then previewing that MuClip in the browser, then the extra outputs were not audible. Fixed.
• MuLab 10 Plugin: Includes all enhancements since M9.5.34, thus including the new modular racks, the new EQ/Filterbank, etc...
• MuLab 10 Plugin: In some hosts (eg Audacity) MuLab's own plugin editor was not shown, only a generic list of knobs/sliders for the meta parameters. Fixed.
• Other small improvements.

If you already have a MuLab App / Plugin user key, you can request a temporary MuLab 10 Plugin beta test user key via email to

[syntonica]

<- me suffering from lack of Mac version.

Is there an ETA on when it might be ready?

[pljones]

Reaper says "MuLab Plugin Demo - Couldn't load preset file" -- it found the plugin.
- also, the host window doesn't follow the plugin window size.

Audacity scan didn't find the plugin. ... Hm, let me double-check that ...

Ah.... The plugin ZIP has both 9 and 10 in -- maybe that causes some confusion...

Biggest problem is the "MULAB" menu doesn't pop open, so it's not possible to enter a user key. (That's in MuLab 10 as host.)

[nenneb]

I miss the right-click-menu on the collapse-buttons and by that the possibility to "Auto Collapse/Expand"

[MuTools]

Removed M10.0.26.

[serpsy]

Hi Jo, sorry if this is a little off topic, but I would like to know / request one thing that really helps me arrange…

Is it possible to add a preference to highlight every x bar chunks on the arranger &/or sequencer background? Like a two tone contrast affair that’s configurable. Ableton handles this dynamically based on zoom level.

This would be great for my tiny brain to visually see each 8/16 bar block along the timeline.

Peace and love

[pljones]

Definitely wrong topic but definitely a neat idea! Configurable phrase and sub-phrase lengths; if multiple phrases are visible, highlight alternately, else highlight alternate sub-phrases, else alternate bars? (e.g. for 12bar blues, 12 bar phrases, 4 bar sub-phrases.)