MuLab 10.0.85

[MuTools]

Or at least allow multiple selection of a range (rather than one by one addition with shift) and delete the selection.

You can Shift+lasso multiple plugin items.

Oh... I just noticed that, whilst no "Unrecognised" entries add to Instruments, it looks like they happily get added as Effects.
Name = 7-zip
Folder = /C:/Program Files/7-Zip
File = 7-zip.dll
Bit Size = 64
Plugin Type = VST2 Effect
Type = Not recognized as a valid VST2 Plugin

So "Plugin Type = VST2 Effect" and "Type = Not recognized as a valid VST2 Plugin"?

An imperfection indeed which comes from this method to quickly define the plug type without opening a file:
Extension DLL is assumed to be VST2.
Extension VST3 is assumed to be VST3.
Extension CLAP is assumed to be CLAP.

Taken note about the imperfection but not sure atm if i can find a quick fix.

[sl23]

Wrt to VST2 to VST3 conversion:
I'll have to set up a project as I've converted everything now. But you could do it yourself if you have time, if not I'll create a project when I have time.
Just create a project with VST2 plugins that have a VST3 counterpart, save the project, move or delete the VST2 versions and reopen.
But make sure to use several different plugins, not just one or two. You'll be asked if you want to convert to VST3, click that and after you've done that for all of them, you are then asked to locate each without knowing which one you are supposed to be looking for.

Junctions are symlinks for folders. I am not having issues in any way at all with using Junctions. That isn't what this is about. It is the fact that a VST2 crashes MuLab when it can't locate it's resource folder in C:/ProgramData/Novation/Resources. The VST2 itself causes MuLab to crash and freeze. The plugin is Novation's V-Station v2.0.

The plugin works fine, unless you open a project and it can't find the resource folder.

I repeat, this has nothing to do with Junctions, I only mentioned that as it happened to be my situation.

[MuTools]

Wrt to VST2 to VST3 conversion:
I'll have to set up a project as I've converted everything now. But you could do it yourself if you have time, if not I'll create a project when I have time.
Just create a project with VST2 plugins that have a VST3 counterpart, save the project, move or delete the VST2 versions and reopen.
But make sure to use several different plugins, not just one or two. You'll be asked if you want to convert to VST3, click that and after you've done that for all of them, you are then asked to locate each without knowing which one you are supposed to be looking for.

I already did that yesterday and the name of the plug is in the title bar.

Junctions are symlinks for folders. I am not having issues in any way at all with using Junctions. That isn't what this is about. It is the fact that a VST2 crashes MuLab when it can't locate it's resource folder in C:/ProgramData/Novation/Resources. The VST2 itself causes MuLab to crash and freeze. The plugin is Novation's V-Station v2.0.

Best to report this to the plug dev.

[sl23]

It should be on the title of the Choose VST3 Plugin popup window, which it isn't.

For example, in this project, I get asked 6 times if I want to migrate to VST3 as the VST2 dll can't be found. Each time I'm asked, I get this window:

Sa22.png

Which is all well and good if there's only a single VST plugin involved, as is the case here. But when there's several different plugins, I'm then confronted with a window like this that gives me no idea what I am supposed to be selecting:

Sa22.2.png

Again, this project is a simple easy example of six missing instances of only a single plugin, W1 Limiter, as I upgraded it to VST3 from VST2. So all projects containing it need upgrading. But if I have many different plugins upgraded in this way, I have no idea what I should be selecting when asked to in that second window. There is no information anywhere in the current view of the entire MuLab window that gives me any clue as to which VST I should be selecting in order to upgrade it from it's VST2 version to VST3 version. The picture shows that and there is no way around it, it is nothing more than a pure guess!

Let's say you have 10 different plugins requiring upgrading to VST3. You are asked this for each of the 10 plugins, then you are asked to choose a VST3 version for each. How do you know which is which when selecting a plugin? I mean you could write it down, but then if you had many instances of each plugin, that makes those 10 plugins bloat into maybe 20, or even 30 selections needing to be made, all depending on how many instances you used of each plugin! That's way too much to remember and write down, making sure the order is correct, and you don't accidentally miss one!

So my request is to please have this name shown in the Choose VST3 Plugin window, so we know what it is we should be selecting for that specific upgrade. Thanks.

[MuTools]

It should be on the title of the Choose VST3 Plugin popup window, which it isn't.

Ok i see the issue now:
When the project has been saved quite recently while the VST2 was still active, the formal VST2 plug name as messaged by the plug dev is saved into the project. My recent test was with M10 and the plug name was properly shown in that popup, hence my reply yesterday. But M9 and older projects don't yet have that plug name embedded in the project file and so no plug name was visible in that popup title. In the next M10.0.45 for older projects the raw VST2 DLL name will be used in that case.

[sl23]

That's ok, I know it must be difficult keeping track of all that dev stuff!
Thanks for the fix

[EvilDragon]

Best to report this to the plug dev.

Except that plugin has been discontinued, no fixes are going to ever happen.


BTW, did you investigate IPluginCompatibility - if yes, what do you think? I'd say it's well worth supporting. More and more plugins (and hosts) are implementing this feature.

[MuTools]

No i did not yet investigate that. Can't do it all. One man company, you know. The last main updates i invested a lot of time in MuLab's plugin engines. Now it feels that also other feature ideas deserve R&D attention. After the M10 release i'll have a fresh reflection about MuLab's next steps.

[sl23]

Thanks for your hard work. It is appreciated by everyone here, I'm sure!

[EvilDragon]

All good, was just asking! No rush or anything

[MuTools]

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

MuLab Plugin M10.0.45 beta is available on https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed:

• MuLab App + Plugin for Windows 32 bit now are available again.
  Note however that these 32 bit versions are deprecated and sometimes an alert remembers you that it's best to migrate to the 64 bit version. So the MuLab 32 bit to 64 bit migration period is prolonged but not forever.
• Migrate VST2 To VST3: If the VST3 cannot be defined automatically and a popup list appears it now always includes a plugin name in the title bar.
• Some small improvements in the Plugin Manager.
• Rack Desk options menu now also includes "New Rack" which does the same as Shift+click on the + rack button: It pops up a list with the various new rack templates.
• EQ/Filterbank: When switched off a frozen spectrum was drawn. Fixed.
• Insert User Key: Dialog can also accept a zip file with a text file with the user key.
  Useful to ensure the user key text file is inserted in its original form and not modified (eg. by auto-translation) by a web browser or email client.

[4u610h346]

MuLab App + Plugin for Windows 32 bit now are available again.
Note however that these 32 bit versions are deprecated and sometimes an alert remembers you that it's best to migrate to the 64 bit version. So the MuLab 32 bit to 64 bit migration period is prolonged but not forever.

It is quite impressive that you've done it this long. It can be a bit of work, maintaining separate branches like that. Even though it will one day end, thanks for the work you put in.

It made my day, as I almost considered it a forgone conclusion that v9 was the last 32bit version.

I'm a fan of MuLab 64bit. But there are a couple of 32bit machines "in this studio" that will be glad to have v10.

FYI, not that I'm encouraging this, MuLab works on WinXP (with One-Core-API x86/x86_64).
But don't you dare bother Joe with support requests, if something doesn't work!

But if you've got a "POWERFUL" old box (you can't let go of) put MuLab on it, and everywhere else.

[sl23]

[*]Not sure if this is a bug or not?
When I have a project with many racks, around 8-10 or more, if those racks are expanded and I go to a rack on the left, say rack 2 or 3, then open a mux by clicking the little diagonal arrow to the right of a Rack Slot, the rack section auto scrolls to the end, I would rather it didn't do this as I am working on a specific rack that then loses focus.

GIF 28-03-2025 17-11-53.gif

It may be due to an older Mux preset. I am in the process of replacing it anyway, but it may be relevant?
Here's the preset in case it is the cause:

MaxBug.zip

It also scrolls the rack desk to the far right if I click the mux window too!

[sl23]

Did you move/delete my rack FR?

Just a little update to the bug above... It seems to also do this on other projects and when I click on a rack with a single used slot with a VST. So it seems it isn't the specific mux preset. Could it be a setting in MuLab causing this?

[sl23]

I've just been testing some more. I couldn't reproduce it after switching projects back and forth a few times, until I tried again with a project containing that mux preset, then it is repeatable whether you click that preset or a VST. Maybe a project bug? Should I email you the project?