MuLab 10.1.25

[MuTools]

MuLab App 10.1.0 alpha for Windows 64 bit is available on https://www.mutools.com/mulab/app/lates ... /beta.html

What's changed:

• MuLab now supports multiple plugins per plugin file.
• Enhanced plugin manager with various UX improvements.
• Removing plugins in the database while such plugins were being used could lead to a crash. Fixed.
• Audio Sequences played by the Sequence Player did not properly use the audio lane output setting. Fixed.

It's an alpha version that needs testing.
If you have some spare time please test MuLab 10.1.0 by rescanning your complete plugin library and let me know any issues.
Thanks.

[pljones]

Weird. I installed, ran MuLab and got a prompt "you must rescan your plugins" and said OK. It got to some dll called "vulcan1.dll" and stopped. After changing focus off and back, I got a pop up menu of a lot of plugins... still the progress bar underneath stuck at "vulkan-1.dll" with no other information showing. So I hit escape on the menu and onwards it scanned. Now it's hit "ladspavst.x64.dll" and stopped... oh, trying to instantiate the plugin, which wants to know where I keep my Ladspa plugins. OK, so it looks like the plugins get instantiated but aren't getting to push any windows to the top of the stack. On completion of the scan, the completion pop up appeared: "Successfully scanned 229 plugins. Num errors during scan = 883. See log file for details."

As you'll see, I trust MuLab to chew through most things without complaint... Looking through the log, it would have been vsti3shell that popped up the menu and blocked the scan. I guess I can get rid if it!

[MuTools]

Weird. I installed, ran MuLab and got a prompt "you must rescan your plugins" and said OK. It got to some dll called "vulcan1.dll" and stopped. After changing focus off and back, I got a pop up menu of a lot of plugins... still the progress bar underneath stuck at "vulkan-1.dll" with no other information showing. So I hit escape on the menu and onwards it scanned. Now it's hit "ladspavst.x64.dll" and stopped... oh, trying to instantiate the plugin, which wants to know where I keep my Ladspa plugins. OK, so it looks like the plugins get instantiated but aren't getting to push any windows to the top of the stack. On completion of the scan, the completion pop up appeared: "Successfully scanned 229 plugins. Num errors during scan = 883. See log file for details."

As you'll see, I trust MuLab to chew through most things without complaint... Looking through the log, it would have been vsti3shell that popped up the menu and blocked the scan. I guess I can get rid if it!

MuLab cannot prevent plugins to popup alerts or menus upon scanning the plugin for info.
VST2 plugins must be instanciated to get the basic scan info. VST3 and CLAP are not instanciated to get the scan info. Hope that already answers part of your feedback.

I see in the log that there are many many files in your plugin database that have nothing to do with VST2, VST3 or CLAP. Could it be that you once scanned your whole C:/Program Files folder and that this is the cause for all those irrelevant files in your plugin database?
That's not recommended although it should not fail. Based on what i see in the log, MuLab indeed did not fail and completed the whole rescan with proper log info. Note that a DLL file (supposed to be a VST2) that does not contain the VST2 "main" or "VSTPluginMain" functions is regarded as an error. In short: Scanning a DLL that is not a VST2 gives an error.

So your scan log looks ok to me.
Am i missing the issue?

[MuTools]

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

[pekbro]

It took me a few tries to get through the plugin scan, along with a few specific rescans to get all the
internal plugins to show up, but they did and are now working nicely.

*It did fail to recognize uaudio_la_6176 as a plugin in the end, but I can't say I'd recommend trying to look into anything coming from UA.

[RichardSemper]

First couple of rescan attempts caused crashes (mulab simply disappears)
This was when it reached the vst2 files for Whispair by Full Bucket, and after I removed that it did the same with Vital vst2. These both can be scanned individually with no problem. The same thing happened with each of the following plugins in the database.
-Turns out the problem was with the VST "VASTvaporizer 2" which appeared to scan correctly, but caused the next plugin in the list to fail, and mulab to crash out, even ultimately it wiped the plugin database! With this vst removed the scan runs great!

Following the scan I notice the improved info for each plugin.

Confirming that vst files with multiple plugins (container files) now show the additional plugins:
- Zebralette now shows up when zebra2 is installed, along with the fx plugins which are also embedded in the one file.
- Six Sines now also shows the Seven Outs version.
- BaconPaul's Sapphire suite now shows all four plugins.

Probably because it's still Alpha version the drag and drop from the browser to create new tracks etc no longer works as before. Drag and drop plugins from windows explorer still works though.

[pljones]

Am i missing the issue?

Just reporting what I've seen. The only "issue" is the way any pop up from the scanned VST fails to be visible and the scan seems to just hang. You need to go looking for where the pop up has appeared and close it to continue. Of course, most VSTs don't do this.

I scan the whole of Program Files because, annoyingly, different developers seem to put plugins in different places and, as MuLab has a very reliable scanner, I just let it try everything.

[MuTools]

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

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

What's changed:

• Scanning plugins now is noticeably faster.
• Improved crash protection during scanning of plugins.
• Improved handling of a plugin/file that caused a crash during a previous scan.
• Plugin Manager has extra option: Remove Unrecognizeds.
• Drag-drop a plugin from MuLab's browser to the composer did not work as before anymore. Fixed.
• Other small improvements.

[MuTools]

First couple of rescan attempts caused crashes (mulab simply disappears)
This was when it reached the vst2 files for Whispair by Full Bucket, and after I removed that it did the same with Vital vst2. These both can be scanned individually with no problem. The same thing happened with each of the following plugins in the database.
-Turns out the problem was with the VST "VASTvaporizer 2" which appeared to scan correctly, but caused the next plugin in the list to fail, and mulab to crash out, even ultimately it wiped the plugin database! With this vst removed the scan runs great!

I double-checked all these 3 plugins, all scanned fine here.

Following the scan I notice the improved info for each plugin.

Confirming that vst files with multiple plugins (container files) now show the additional plugins:
- Zebralette now shows up when zebra2 is installed, along with the fx plugins which are also embedded in the one file.
- Six Sines now also shows the Seven Outs version.
- BaconPaul's Sapphire suite now shows all four plugins.

Probably because it's still Alpha version the drag and drop from the browser to create new tracks etc no longer works as before. Drag and drop plugins from windows explorer still works though.

Fixed in M10.1.1.
Thanks for spotting this!

[MuTools]

Just reporting what I've seen. The only "issue" is the way any pop up from the scanned VST fails to be visible and the scan seems to just hang. You need to go looking for where the pop up has appeared and close it to continue.

Thanks for explaining me.
I don't see a way how MuLab can control this.

I scan the whole of Program Files because, annoyingly, different developers seem to put plugins in different places and, as MuLab has a very reliable scanner, I just let it try everything.

There only are a handful of typical folders.
Anyway, as a test i also (partially) scanned the entire Program Files folder.
This lead to some optimizations in MuLab 10.1.1.

[RichardSemper]

I double-checked all these 3 plugins, all scanned fine here.

The issue was definitely with VASTvaporizer2

I tried the same tests with the latest version and had the same results i.e. mulab crashes after successfully scanning VASTvaporozer2.
I also tried a full scan of my vst folder with and without that plugin present. Everything scans perfectly when it is not present, but crash occurs when it is.

I also tried drag and drop of the VASTvaporizer2.dll file onto mulab (without it in the database):
- mulab 10.0.85 : the plugin is added, and the synth interface opens properly. No problem at all.
- mulab 10.1.1 : mulab disappears altogether. Restarting the program, the synth has been added to the database and works properly. Subsequent rescan all plugins causes the same crash again (unless VASTvaporizer2 is removed first)

I don't know what is special about this plugin - but it seems to be the only one causing any problems at all (so far )

I have attached some logfiles which show at what point in the process the mulab session ends.

[pljones]

I don't see a way how MuLab can control this.

It would depend on how the "scanning" bar is popped up on Windows. If it's a normal main app window, anything popped up by child processes during the scan should pop up over it. If it's something else, it might be that Windows can't resolve the layering. (Once MuLab is open, it would need to open as a normal floating child window, not as a pop up/notification/modal dialog/etc that gets pinned to the "front" of the stack.) If that's already the case then it's down to the plugins -- and I've seen plenty that have problems just getting their main dialog to appear properly when running standalone, for those that support it.

[pljones]

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

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

What's changed:

• Scanning plugins now is noticeably faster.
• Improved crash protection during scanning of plugins.
• Improved handling of a plugin/file that caused a crash during a previous scan.
• Plugin Manager has extra option: Remove Unrecognizeds.
• Drag-drop a plugin from MuLab's browser to the composer did not work as before anymore. Fixed.
• Other small improvements.

Forced a rescan in 10.1.1 and it dropped out without an error and left no log file. It just hung on "jsound.dll" (although that could be the last one it got the bar updated for before crashing). On rerunning, I got a MuLab popup:

Screenshot 2025-09-14 101454.png

...and yes, something to do with java:

Code: Select all

C:\Program Files\Android\jdk\jdk-8.0.302.8-hotspot\jdk8u302-b08\jre\bin\jsoundds.dll
C:\Program Files\Eclipse Adoptium\jdk-8.0.372.7-hotspot\jre\bin\jsoundds.dll

There doesn't appear to be a way to continue a "Rescan All" from the point of the crash, unfortunately.

This time when it hit instantiating a plugin that did a pop up, the pop up appeared correctly. (I'm guessing that the initial "First time scan" isn't correctly set as the main application window at the time, so Windows gets confused when a "child" window tries to attach itself.)

[pljones]

Just a question here -- so "Name" is just the "File" with the suffix removed? And "Product Name" is used as the display name for the plugin? (Same in VST3 and CLAP)

Screenshot 2025-09-14 102804.png

Screenshot 2025-09-14 102730.png

Screenshot 2025-09-14 102850.png

(Fortunately, my MuLab Plugin install doesn't have the same hungry scan path as MuLab App, so it didn't try to eat Java and fall over.)

[MuTools]

Forced a rescan in 10.1.1 and it dropped out without an error and left no log file.

When it "drops out" aka crashes there still should be a log file, at least containing all log info until the previous scan. I double-check that case and it works as expected here.

It just hung on "jsound.dll" (although that could be the last one it got the bar updated for before crashing). On rerunning, I got a MuLab popup:Screenshot 2025-09-14 101454.png
...and yes, something to do with java:

Code: Select all

C:\Program Files\Android\jdk\jdk-8.0.302.8-hotspot\jdk8u302-b08\jre\bin\jsoundds.dll
C:\Program Files\Eclipse Adoptium\jdk-8.0.372.7-hotspot\jre\bin\jsoundds.dll

Yes MuLab now has improved handling of a crash during scanning.
On restart MuLab indeed tells wich file caused the crash and it stores that fact in the database so to avoid the same crash on a next scan.

This time when it hit instantiating a plugin that did a pop up, the pop up appeared correctly. (I'm guessing that the initial "First time scan" isn't correctly set as the main application window at the time, so Windows gets confused when a "child" window tries to attach itself.)

Good thinking. I'll check that.

Thanks pljones.