MuLab 9.0.59 App + Plugin

[MuTools]

It's something different from what we discussed previously. And i don't regard it as a bug. Thing is that if you drop a module on the rack desk it creates a new rack for it. Dropping it on empty space of a rack is the same as dropping it on the rack desk. Ok, maybe that's a little bit unexpected, but it's not a bug, and it's also not a musical workflow issue, imho. So i don't think it needs prio attention. Right?

[FabBad]

yep, it's not a bug but it's a workflow mixing tasking issue, or more an annoyance.
take your time, no pressure at all. just expossing some (imo as a user) issues.
Thanks.

[MuTools]

Why is it a workflow issue? You can't really "accidentally" drop it outside the rack slots as while dragging it's made clear when it's snapping to a slot or not, right?

[FabBad]

The old behaviour was just right, drag an element from slot to anywhere but that another slot or workspace, and if it was on any where else it simply wasn't possible, the cursor showed with an "X" icon (for eg. in M8).
[I don't know if i was clear.]

Also, this action isn't undoable.

[MuTools]

The old behaviour was just right, drag an element from slot to anywhere but that another slot or workspace, and if it was on any where else it simply wasn't possible, the cursor showed with an "X" icon (for eg. in M8).

That's because in M8 you could only drop racks on the rack desk, in M9 you can also drop any module/plugin on the rack desk and M9 will make a rack of it

Also, this action isn't undoable.

If you delete the new rack the action is undone.

And a "normal" undo might come in a future version, it's certainly the intention to make increase the amount of actions that can be undone.

[FabBad]

yeah i know the advantage of trow a module/plugin there,is good but having a lot of racks working with this pitfall can be a nightmare, Hypothetical example, lets say we have a project that has more than 30 racks and on the firsts racks i'm making common adjustments, changing eq by comp on rack slots, and accidentally one can release the mouse while dragging onto another slot before the cursor point the other slot, so the comp/eq it just gone... to another new rack to the last position, well, this was a user error so the user gonna undo this... nope, it's only undo the past action.
I understand that this can be a little thing for someone, but not for me, is just annoying...
just like the module "plugin-slot" in which when i click near the process on/off it drop down the menu.

Regards.

[simmo75]

Hello, I’m interested in MuLab.

Does it support MPE and VST3?

I use a lot of hardware synths/samplers, does anyone who uses MuLab have any thoughts on MuLab with external hardware?

Thanks in advance.

[MuTools]

Hypothetical example, lets say we have a project that has more than 30 racks and on the firsts racks i'm making common adjustments, changing eq by comp on rack slots, and accidentally one can release the mouse while dragging onto another slot before the cursor point the other slot, so the comp/eq it just gone...

I'm sorry but i don't understand what you mean.
Pls make a screen video of this hypothetical example.

just like the module "plugin-slot" in which when i click near the process on/off it drop down the menu.

That will be polished in the next update.

[FabBad]

I'm sorry but i don't understand what you mean.
Pls make a screen video of this hypothetical example.

i will, but on the run, i stumbled upon with this

FLAC files doesn't take into account.gif

The browser doesn't see FLAC files on "Audio Files"

That will be polished in the next update.

[simmo75]

Hello, I’m interested in MuLab.

Does it support MPE and VST3?

I use a lot of hardware synths/samplers, does anyone who uses MuLab have any thoughts on MuLab with external hardware?

Thanks in advance.

Hi again, can anyone give me an answer please?

[MuTools]

Does it support MPE and VST3?

Not yet, but VST3 support is being researched.

I use a lot of hardware synths/samplers, does anyone who uses MuLab have any thoughts on MuLab with external hardware?

Works fine, but best to check it out yourself using the demo version.

[simmo75]

Many thanks

[syntonica]

I was doing some VST demoing for sound, speed, CPU usage, etc., so I was swapping VSTs in and out repeatedly. When I quit my session, MuLab sighed and stated "Logged 409 errors." I looked at the last error log and it's littered with these:

Code: Select all

0x000070000978B000 20:51:10:453 Error MsPj[555] UTID mismatch 0x000070000978B000 <> 0x00007FFFAA605380
0x000070000980E000 20:51:10:787 Error MsPj[555] SUTC time-out

Are these just from CPU overloads? They appear to mostly be from one rather misbehaved plugin.

(I really just wanted to know if MsPj[555] was the system dominatrix and I should've given her the safe word. Needless to say, I won't be using that VST again. )

[MuTools]

I was doing some VST demoing for sound, speed, CPU usage, etc., so I was swapping VSTs in and out repeatedly. When I quit my session, MuLab sighed and stated "Logged 409 errors." I looked at the last error log and it's littered with these...

Please email the complete log file to

[MuTools]

MuLab App 9.0.58 is available in https://www.mutools.com/mulab/app/latest-binary

MuLab Plugin 9.0.58 is available in https://www.mutools.com/mulab/plugin/latest-binary

What's changed:

• Project window now has explicit Move Window button.
• When trying to plug in a 32 bit VST into MuLab 64 bit or vice versa the error alert was not specific enough anymore (due to further works on the new plugin system). Fixed.
• Clicking near the on/off button of a plugin slot does not popup the module list anymore.
• Other small improvements.