MuLab 10.0.85

[Jonathan Shepherd]

Hey-oooh! Looks like I'll be making a new template. To quote the great fictional character Oscar Goldman:
We can rebuild him. We have the technology. We can make him better than he was. Better, stronger, faster.

All hail the man Jo!

[audiojunkie]

MuLab App M10.0.8 alpha for Windows 64 bit is available here:
https://www.mutools.com/mulab/app/lates ... -win64.zip

This a full installation zip file and it's strongly recommended to make a separate new subfolder for it, thus keeping your MuLab 9.5 installation folder intact.

What's changed compared to the last M9.6.7 alpha:

• Racks have become plain standard MUX Modular patches.
  The thing that defines whether a MUX patch is regarded a rack or not, and thus whether it's included in the rack desk, simply is the existence of at least one Rack Slot module in the MUX patch.
  Thanks to this new modularity, racks can now have any number of slots instead of the fixed 6.
  Also thanks to this new rack modularity, racks are fully editable from modular side, which is handy when you want to use more complex rack routing like side-chain, multi-output synths, multi-input effects etc.
• As racks now can have an variable number of slots and thus a variable height, the user gets control over the rack desk height which also makes it possible to have larger rack faders & meters.
  Consequently also rack desks in front panels can now have a custom height.
• Rack presets now are standard .Mux preset files.
  The default location for rack presets is the "Library/MUX/Racks" subfolder, aside the Effects and Instruments subfolders.
  If that folder contains a "New Rack.Mux" then this is your default user rack.
  If there also is a "New Rack Templates" subfolder there, then this can contain several rack templates, and when clicking the + rack button, you can choose which new rack you want.
• As racks have become plain MUX Modular patches, no more need for separate MuRack presets.
  Of course MUX Modular supports loading such legacy MuRack presets.
  To show your legacy MuRack presets in the project browser, select Which = MUX Presets and Where = the appropriate folder with .MuRack files.
  For quick access you could save that as a browser preset.
  Alternatively if you have any custom rack presets in your user library ( = at least 1 .MuRack file), then there is a helper function in the Browser -> MUX Presets -> Options menu: "Move Legacy MuRack Presets".
  This will move your legacy .MuRack presets to your M10 user library MUX/Racks subfolder.
• As racks have become fully modular, rack freezing now also supports the use of Freeze Points inside the rack modular structure so that users who have edited the rack's modular structure have precise control over how a rack should be rendered frozen.
  If no such Freeze Points exist then the default freeze points are the rack fader input (or if no rack fader then the main output) and the aux outputs, as in M9.
  So if the user keeps using a rack the same way as in M9, freezing will also work the same way as in M9.
  Only when making more complex modular racks, adding explicit Freeze Points may be useful.
• "Default Rack Width" preference renamed to "Default Rack Slot Width".
  This preference now also works a bit different:
  Previously this pref was only used upon creating a new rack.
  But now when this pref is changed, this will affect all existing racks that use the default rack slot width.
• Enhanced Rack Freezing avoids irrelevant silent tracks.
• Setup Side Chain: Source list now includes all rack outputs as well as all relevant rack slot outputs. (before only the main rack output and the 2nd and up slot outputs were included)
• New "Delete Side Chain" function, which complements Setup Side Chain.
• When removing a rack, then undoing that, the original rack order was not preserved. Fixed.
• As the rack layout has changed, this is a relevant point in time to drop the "Legacy Slot Ver. Margin" support which was installed in M9.1 to ease the transition from legacy layout to new layout where slots have a a bit more spacing.
  This means you might have to finetune custom front panels that include Racks or Module Slots.
• New "ME_Q" equalizer / filterbank module.
• New "Module Input/Output Selector" front panel component.
  This front panel component lets you choose the input or output for a certain module.
  Upon adding such component, click with the pointing hand on the module you want to control.
• Composer: When changing the length of a clip and multiple clips with different lengths are selected, you now get the options "Change Clip Lengths -> Absolute / Relative / Proportional / This 1 Only", just as with note events.
• Modular Area: Term "Connection" renamed to "Cable".
• Modular Area: New "Reconnect Selected Cables" context function when right-clicking a jack.
  Using this function it's easy to reconnect all selected cables to a certain jack in 1 step.
• Modular Area: New "Select Cables" and "Unselect Cables" context function when right-clicking a jack.
  Note that this does not clear any existing cable selection so this can also be used to extent/finetune an existing cable selection.
• Modular Area now also supports lasso-selecting cables only.
• Modular Area: When dragging a cable over a module and there only is 1 matching jack, the drag snaps to that jack for extra user comfort.
• Refined VST3 plugin hosting, especially a bit more relaxed handling of plugins that report unexpected though most probably innocent results when reloading plugin data. (eg MBSI plugin returning false for its EditController->setState with its reported data size 0)
• Draw new clip -> Popup clip type button for stream clip was drawn wrong. Fixed.
• When dropping audio files on the composer, music stopped playing while choosing the drop method. Fixed this recent new M9.6 bug.
• GUI -> Sliders now have a Minimum and Maximum Handle Size in pixels. These can be used to keep the handle size within a range even for big sliders.
  And when setting both Minimum and Maximum Handle Size to the same value, the handle gets a fixed size in pixels, independent from the slider size.
• Upon start editing certain MUX Modular front panels, an alert could popup wrongly stating "Had to move/size N components to ensure visibility". Fixed.
• Front Panel Parameters: Widget, Name and Value Fore Color can now be set to "No Specific Color" and then it will use the relevant "Top Color".
  For racks the Top Color is an accented version of the rack color.
• Front Panels -> Group Frame -> Optimize Size was not working right when the group frame title is at left or right or omitted. Fixed.
• Front Panels: When dropping a parameter from another front panel, now the panel looks of that parameter are also copied.
• Front Panels: New parameter knob/slider layouts:
  * Knob with only name at bottom.
  * Knob with only name or value at left or right.
  * Knob with only name or value at left or right with vertical text.
  * Hor. Slider. (no name nor value)
  * Ver. Slider. (no name nor value)
• Front Panels Parameters: Copy-Paste Looks now also copies-pastes the editor type and widget.
• Sequence Editor: Copy/Paste Time Zoom now uses clipboard text to copy-paste the zoom factor, so it's even editable before paste.
  These 2 functions now are also included in the time bar context menu.
• There was a recent new (as of M9.6.3) microbug in the bezier curve system for X values that are very close to or over 100%, they resulted in imperfect Y values.
  This could be heard in eg. the "Jim Electro" demo, the Cybell sound was a bit off pitch due to that imperfect curvation. Fixed.
• In some cases (eg. shortcut target funtion list) list items could wrongly show an unfold subgroup triangle. Fixed.
• Sequence Editor: Editing a note length using the Length field at the bottom did not work correct when the sequence clip has a tempo factor. Fixed.
• Audio Sequence Editor: "Split At Nearest Marker" and "Set Audio Start/End Here": These functions did not take the clip tempo factor into account. Fixed.
• Composer: When looping automation clips with points on the loop start, it could happen that the automation was looped with a wrong value. Fixed.
• Composer: Audio sequence clips with a tempo factor were not drawn correctly. This was especially noticable for longer audio events. Fixed.
• Composer -> Export functions: When rendering projects that exceed 100% cpu usage on playback, it could happen that the rendering process was unexpectedly stopped. Fixed.
• Composer: When recording a new sequence clip and there was no track yet for that clip's target module, the new clip could be placed on the tempo track, which was not ok. Fixed.
• Composer: When recording new clips and undoing that action, any newly created track stil remained. Fixed.
• When dropping a parameter on the composer to create a new automation clip, now also an initial envelope point is created with that aparameter value.
• Rack Title Fore Color preference did not work. Fixed.
• There was a little mem leak when using the Event Pad in a Front Panel. Fixed.
• Some more color preferences.
• Other small improvements.
• More to come.

If you already have a MuLab user key, you can request a M10 test user key via email to
(Personal M10 user keys will be sent out later, around M10 release)

Curious for your thoughts & feelings about this first MuLab 10 alpha and for any bug reports.

Here is a quick intro video to the new modular racks:

Very nice! When I get my Linux machine rebuilt, I'll have to test this in WINE!

[FabBad]

This is amazing! amazing list! so many things, many bugfixes, many changes and of course the new rack system is top notch!
Congratulations to all us! of course Mr. Jo included.

Just one question, is there gonna be a bugfixed new version for 9.x? some of the listed bugsfixes could be applied on the earlier version.


Regards.

[oldcastle]

Very nice! When I get my Linux machine rebuilt, I'll have to test this in WINE!

Hey @audiojunkie, I got version 9.6 working with this patch:
https://bugs.winehq.org/show_bug.cgi?id=52974#c14

[audiojunkie]

Very nice! When I get my Linux machine rebuilt, I'll have to test this in WINE!

Hey @audiojunkie, I got version 9.6 working with this patch:
https://bugs.winehq.org/show_bug.cgi?id=52974#c14

Nice! But the WINE developers aren't going to add a true fix to the main WINE?! That's unfortunate... Have you tested v10.0.8 to confirm that it works? What we really, really need is a native version!!

By the way, Jo, what programming frameworks and libraries are you using for MuLab? Are the frameworks all cross platform compatible to include not only Windows and MacOS, but also Linux? If not, it may be a good idea to start evaluating available frameworks and libraries for the future....

[oldcastle]

Yeap.. unfortunately they will not add the fix to the main branch. I will test v10 later.

The fix itself is quite simple. I will try to replicate that using KDE Windows Rules.

[shorty]

great, the DAW with the highest fun-factor gets better and better

[MuTools]

Just one question, is there gonna be a bugfixed new version for 9.x?

No. Lets focus on M10 and forward.

[RichardSemper]

Really looking forward to using the new M10 - so many new enhancements. Nice one Jo

When loading an old project (from 9.5) with vst3 plugins not yet added in the database, the dialog says simply "missing vst3 plugin" without identifying which one. Missing vst2 and CLAP plugins are identified in their missing plugins dialog box. In version 9.5 they were all identified.
This was also an issue in version 9.6

[fde101]

If that was coupled with limiter/compressor for the bands

Why not a per-band plugin slot so you could add your own?

[focusrite]

Does anyone know. Can each lane now have its own audio output in the rack mux?

[pekbro]

Nice! The modular racks seem perfectly natural to me so far.

[RichardSemper]

moving the fader position on the rack front panel does not currently work:
- the little pointer arrow cannot be dragged to a different position as used to happen in earlier versions.
- clicking it offers the following options (pointer currently between slot 4 and 5):-
"Move Fader After Rack Slot 4", and "Move Fader Before Slot 5" - both of these options have the result of leaving fader exactly where it is.
Of course the pointer position can be moved by editing the position of the mixer strip in the Rack Modular Area, or by inserting and deleting slots on the Rack Front Panel.

[liquidsound]

- clicking it offers the following options (pointer currently between slot 4 and 5):-
"Move Fader After Rack Slot 4", and "Move Fader Before Slot 5" - both of these options have the result of leaving fader exactly where it is.
Of course the pointer position can be moved by editing the position of the mixer strip in the Rack Modular Area, or by inserting and deleting slots on the Rack Front Panel.

Just click with your mouse on the spot you want to move the little triangle and it will move where you just clicked.
I like this way better.

[RichardSemper]

- clicking it offers the following options (pointer currently between slot 4 and 5):-
"Move Fader After Rack Slot 4", and "Move Fader Before Slot 5" - both of these options have the result of leaving fader exactly where it is.
Of course the pointer position can be moved by editing the position of the mixer strip in the Rack Modular Area, or by inserting and deleting slots on the Rack Front Panel.

Just click with your mouse on the spot you want to move the little triangle and it will move where you just clicked.
I like this way better.

Got it, thanks! I see - it is better
Still - those options are a bit odd though