MuLab 9.1.27 [released]

[robert_p]

I used Logic 5 on an old 800Mhz G4 iBook. I had to freeze/render each individual track as I completed it. If I had to touch up any fx, it was a pain to unfreeze and refreeze. My latest MBA is about 100x faster! No more freezing, even if I run something like Diva. Now, if they'd only make Neon for the ARM processor...

Haha, I'll think about it

P.S. Track freezing has some advantages: if you open your project next year and find it's no longer compatible with the latest version of MuLab plugin - you still have your "frozen" audio tracks;)) And there is an option to freeze instruments leaving insert fx's untouched, so they still can be tweaked;)

[MuTools]

if you open your project next year and find it's no longer compatible with the latest version of MuLab plugin...

That doesn't happen.
Even MuLab 1.0 projects can still be loaded into MuLab 9.
Really old projects (many years old) only take a one-time intermediate upgrade step, but then they're still alive and kicking in the latest version of MuLab.

[robert_p]

That doesn't happen.
Even MuLab 1.0 projects can still be loaded into MuLab 9.
Really old projects (many years old) only take a one-time intermediate upgrade step, but then they're still alive and kicking in the latest version of MuLab.

Yes, this is true if it's MuLab project. If we have Studio One/Logic/Cubase/Reaper project containing MUX 7/8 vst tracks - they won't open if only MuLab9 plugin is installed.

[whyterabbyt]

Sorry to be a pain, jo, but since it looks like you're regularly updating this thread's first post's subject to indicate there's a new version, would it be possibly to edit the first post and put the links in there as well? Its a bit frustrating having to dig back through multiple pages looking for the actual post with the links...

[robert_p]

Sorry to be a pain, jo, but since it looks like you're regularly updating this thread's first post's subject to indicate there's a new version, would it be possibly to edit the first post and put the links in there as well? Its a bit frustrating having to dig back through multiple pages looking for the actual post with the links...

Don't be sorry - I'm the only "Pain in the Ass" here Digging back through multiple pages is mandatory to prove you're not a robot;)

[MuTools]

Sorry to be a pain, jo, but since it looks like you're regularly updating this thread's first post's subject to indicate there's a new version, would it be possibly to edit the first post and put the links in there as well? Its a bit frustrating having to dig back through multiple pages looking for the actual post with the links...

Done

[MuTools]

Don't be sorry - I'm the only "Pain in the Ass" here

Seriously, a big thanks to you Robert for helping with testing and streamlining MuLab 9.1!

Digging back through multiple pages is mandatory to prove you're not a robot;)

Good one

[MuTools]

That doesn't happen.
Even MuLab 1.0 projects can still be loaded into MuLab 9.
Really old projects (many years old) only take a one-time intermediate upgrade step, but then they're still alive and kicking in the latest version of MuLab.

Yes, this is true if it's MuLab project. If we have Studio One/Logic/Cubase/Reaper project containing MUX 7/8 vst tracks - they won't open if only MuLab9 plugin is installed.

That's a DAW issue. In MuLab, when a plugin cannot be found, the user gets a chance to locate it and resolve the 'missing plugin' issue. In those DAWs you mention, the user doesn't get such chance and so those DAWs lack this necessary functionality.

Anyway, there still is a way around it: Open your M8 based DAW project using MUX Modular 8.
In MUX Modular 8 -> main options menu -> Save Plugin Project. You can open that project in both MuLab 9 App and Plugin. And as MUX Modular 8 also supports MUX 7 the same way can be used to upgrade MUX 7 based DAW projects.

[robert_p]

Anyway, there still is a way around it: Open your M8 based DAW project using MUX Modular 8.
In MUX Modular 8 -> main options menu -> Save Plugin Project. You can open that project in both MuLab 9 App and Plugin. And as MUX Modular 8 also supports MUX 7 the same way can be used to upgrade MUX 7 based DAW projects.

[MuTools]

I still can't understand why running Reaper, Cakewalk and Bitwig makes task manager figures similar to Studio One results.

I've updated MuLab's Audio Setup doc page, elaborated the "MuLab CPU meter vs System Process Monitor" section:
https://www.mutools.com/info/M9/docs/mu ... setup.html

[MuTools]

Anyway, there still is a way around it: Open your M8 based DAW project using MUX Modular 8.
In MUX Modular 8 -> main options menu -> Save Plugin Project. You can open that project in both MuLab 9 App and Plugin. And as MUX Modular 8 also supports MUX 7 the same way can be used to upgrade MUX 7 based DAW projects.

I've added this info to the relevant doc page:
https://www.mutools.com/info/M9/docs/mu ... jects.html

[robert_p]

Front panel parameter (Numeric Type Editor) - the default height is 40px. The only way to change it to 20px is to create 20px Text Frame and copy/paste size. Not sure if it's related to some specific application settings - I noticed this issue months ago.
---

Numeric_Parameter_Editor.jpg

[MuTools]

Front panel parameter (Numeric Type Editor) - the default height is 40px.

When Name = Left, default height is 20 pix. (always assuming 100% scale)
When Name = Top, default height is 40 pix. (there is a bug here, will be fixed in M9.1.25)

The only way to change it to 20px is to create 20px Text Frame and copy/paste size.

Currently the above heights are fixed. That's why the "H" property is greyed.

[robert_p]

When Name = Left, default height is 20 pix. (always assuming 100% scale)
When Name = Top, default height is 40 pix. (there is a bug here, will be fixed in M9.1.25)

Both - Name Left and Name Top have the same default 40px height:
---

Name_Left.jpg

[MuTools]

The greyed out value is to be ignored.