MuLab 10.0.85

[syntonica]

stop fussing.

That's it.
We need to draw a line when we spend more time serving the computer
I will connect my current Mini as a slave when I get another, one of these days . . . . .

Here's an interesting tidbit for Mac users. I just updated my MBA M1 from Sequoia 15.4->15.5. Just for grins, I ran Geekbench and got a significant speed bump, ~6%. I did the same with my dad's same model, but the Intel i3 version. Got a ~15% bump! I wish I could use OpenCore to update, but it would wipe my plugins I can no longer reinstall.

Anyway, back to the juicy Mulab-y goodness...

[tiger001]

MuLab App 10.0.67 beta for is available on https://www.mutools.com/mulab/app/lates ... /beta.html

MuLab Plugin 10.0.67 beta for Windows 64 bit is available on https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed:

• Virtual MIDI Keyboard now can properly be minimized into the Minimized Windows Bar.
• Important sonic bug fix in the Mixer Strip when Stereo Width < 100%.
• New curve system: Fixed a couple of issues.
• Had another play with the MuLab 10 startup window.

the links on the DL page still point to 10.0.64

i can change the link(s) and download alright

[dayvyg]

MuLab App 10.0.67 beta for is available on https://www.mutools.com/mulab/app/lates ... /beta.html

MuLab Plugin 10.0.67 beta for Windows 64 bit is available on https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed:

• Virtual MIDI Keyboard now can properly be minimized into the Minimized Windows Bar.
• Important sonic bug fix in the Mixer Strip when Stereo Width < 100%.
• New curve system: Fixed a couple of issues.
• Had another play with the MuLab 10 startup window.

the links on the DL page still point to 10.0.64

i can change the link(s) and download alright

You just need to refresh the page.

[tiger001]

yes, sorry about that

[tiger001]

2025-06-13 15_19_55-.jpg

is it because we (always) have the possibility to open a file through a new/different external audio editor that there's 2 references for externally working with audio?

or will 1 reference suffice ?

[pljones]

Tiny issue: horizontal zoom to fit seems to come up with a weird idea of what "fit" means. The "Start" demo is four bars long and five tracks high. If I (full) zoom to fit, I see the five tracks zoomed evenly -- but the four bars get squashed so I can see 30 bars. Horizontal zoom to fit does the same -- at least it's consistently weird.

[dayvyg]

Somehow most of the VST3-2 have issues with the virtual keyboard on my windows machine:

If I interact (adjusting parameters, changing presets) with instruments such as Pigments, Zebra, Massive-x etc, the Virtual Keyboard loses the input/focus and the only way to get it back to the plugin is to click the plugin's title bar.

Serum 1 and 2 never have this issue... why?

Surface Pro W-10. All and latest MuLab version.

Yup, I'm having this same problem.

Also, I've had to reconnect the audio cable from some tracks to the master to get audio to play through the master track. Seems fairly random though. I've only had this happen on one project so far.

[pljones]

Also, I've had to reconnect the audio cable from some tracks to the master to get audio to play through the master track. Seems fairly random though. I've only had this happen on one project so far.

Are these projects (or singular, as it's just the one) updated from earlier versions of MuLab? Maybe related to the rack system rewrite.

[liquidsound]

Somehow most of the VST3-2 have issues with the virtual keyboard on my windows machine:

If I interact (adjusting parameters, changing presets) with instruments such as Pigments, Zebra, Massive-x etc, the Virtual Keyboard loses the input/focus and the only way to get it back to the plugin is to click the plugin's title bar.

Serum 1 and 2 never have this issue... why?

Surface Pro W-10. All and latest MuLab version.

Yup, I'm having this same problem.

Also, I've had to reconnect the audio cable from some tracks to the master to get audio to play through the master track. Seems fairly random though. I've only had this happen on one project so far.

For me it's constant. The only instruments not effected by this issues are Serum, Omnisphere, Spire and Reaktor so far. All other instruments needs to be refocused by clicking the instrument's title bar each time tweak a parameter or preset.
Absolutely a nightmare to work on sound design...

[syntonica]

Keyboard focus follows the focused window. This is by the OS's design and should allow for a mouse-free workflow, if desired. Plugins have to do a lot of extra jiggery-pokery to circumvent this behavior, such as reject focus requests when controls are clicked on. Which raises the question, when does the user want their mouse click to raise focus on the plugin? Does it want keyboard focus as well? Unfortunately, there's no standard answer here. Some plugins annoyingly capture all keyboard input, some pass unused keystrokes through to the host so that the spacebar will still start/stop playback, for example.

[liquidsound]

Keyboard focus follows the focused window. This is by the OS's design and should allow for a mouse-free workflow, if desired. Plugins have to do a lot of extra jiggery-pokery to circumvent this behavior, such as reject focus requests when controls are clicked on. Which raises the question, when does the user want their mouse click to raise focus on the plugin? Does it want keyboard focus as well? Unfortunately, there's no standard answer here. Some plugins annoyingly capture all keyboard input, some pass unused keystrokes through to the host so that the spacebar will still start/stop playback, for example.

There is a standard: All the 13 DAWs I own, 12 (IIRC from time past) behave the same way: I can work on the instrument parameters and simultaneously use the computer keyboard to play the instrument.
As I listed, some of the plugin works that way in MuLab while other do not. Those that do not work in Mulab do work in other DAWs...

Something is off here...

EDIT Add: When the DAW reserves a selection of keys on the keyboard for the MIDI notes input, the rest of the keyboard behaves as a regular keyboard. So the the DAWs answer is set.

[dayvyg]

Also, I've had to reconnect the audio cable from some tracks to the master to get audio to play through the master track. Seems fairly random though. I've only had this happen on one project so far.

Are these projects (or singular, as it's just the one) updated from earlier versions of MuLab? Maybe related to the rack system rewrite.

No, I've been using the beta version of Mulab for a while and the projects affected we're created in version 10.

[MuTools]

I've had to reconnect the audio cable from some tracks to the master to get audio to play through the master track. Seems fairly random though. I've only had this happen on one project so far.

No, I've been using the beta version of Mulab for a while and the projects affected we're created in version 10.

Is it 1 or more projects?
Please send me the smallest project that repeats this issue.

[pljones]

Not sure if this is new (I think it's been around forever, probably, and I've not noticed). I've got two displays on Windows 11. If I drag the MuLab window from my main display to my secondary display and hit maximise... it snaps back to the main display and maximises there, rather than on the current display.

[MuTools]

Not sure if this is new (I think it's been around forever, probably, and I've not noticed). I've got two displays on Windows 11. If I drag the MuLab window from my main display to my secondary display and hit maximise... it snaps back to the main display and maximises there, rather than on the current display.

Odd, don't see a reason in the code. Next update will log relevant data when doing Maximise so pls email me the complete log file after having repeated that case using the next update.
You can catch the log file while MuLab is running, or do MuLab -> Tools -> Keep Log to keep it after quit.