MuLab 10.1.25

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

masterjoe wrote: Mon Sep 15, 2025 1:03 pm Maybe it's quickest if I delete the old DB and add everything from start? What do I have to delete where for that?
The Plugin Manager now has an Option "Remove All".

Post

MuTools wrote: Mon Sep 15, 2025 2:42 pm
masterjoe wrote: Mon Sep 15, 2025 1:03 pm Maybe it's quickest if I delete the old DB and add everything from start? What do I have to delete where for that?
The Plugin Manager now has an Option "Remove All".
Well MuLab.exe does not even start as it currently is in an endless loop of trying to update the database (because Visco.vst3 crashes it seemingly). So I can't use any functions in Mulab app ATM. Would have to delete the database manually. But I don't know where it is located?

Post

What do you mean by "crashing"?
Do you mean MuLab "hangs"?

"Crash" = sudden abortion. Not listed by Task Manager anymore.

"Hang" = freezes, no more interaction, but still listed in Task Manager.

Post

I also don't understand why you would not be able to launch MuLab as MuLab does not scan plugins on startup.
The only thing it does related to plugins is to check if a previous plugin scan caused a crash and if yes it identifies the plugin and stores that nasty fact in the database to avoid such scan crash again.

Post

Hmm, it does in fact crash without the main UI appearing.
The first thing that happens when I start MuLab.exe is that MuLab wants to convert the plugin database. The main UI of MuLab is not visible at this point. I confirm the conversion dialog and then MuLab starts scanning the plugins automatically. I only see the scanner window but nothing else. This works for a while and when it reaches Visco.vst3 the scanner window hangs for a second and then disappears (=crash). When I try to launch MuLab.exe again the same procedure begins (conversion dialog - scanning - crash at Visco). I never reach the main UI. It always starts over scanning from the beginning and then crashes at Visco.vst3. This is what happens when I start MuLab.exe 10.1.1.
The plugin (in Studio One) behaved differently. There the main UI (of the plugin) appeared and then the question to convert the database came up on top of it. I confirmed the dialog and then it started scanning and after a while succeeded. Here even Visco.vst3 did no cause any troubles and everything finished fine.
Strange as it sounds - this is what happens here...

Post

Thanks for the detailed description!
I'm gonna check some things...

Post

I too had this kind of problem, havent noticed which file is causing it yet, will try again but it doesnt get to the ui, it just disappears. Restarting just goes through the same procedure of scanning some plugins then disappearing.
Beauty is only skin deep,
Ugliness, however, goes right the way through

Post

Just tried again 3 times and its falling over Full Buckets Sixtraq. I will remove it and see if it helps.
Beauty is only skin deep,
Ugliness, however, goes right the way through

Post

Ok, once I removed my Full Buckets folder, not just sixtraq, and also Ujam Fin-Micro.dll it managed to successfully complete the scan. Next I will re introduce those plugins and see if anything happens.
Beauty is only skin deep,
Ugliness, however, goes right the way through

Post

masterjoe wrote: Mon Sep 15, 2025 5:11 pm The first thing that happens when I start MuLab.exe is that MuLab wants to convert the plugin database. This works for a while and when it reaches Visco.vst3 the scanner window hangs for a second and then disappears (=crash). When I try to launch MuLab.exe again the same procedure begins (conversion dialog - scanning - crash at Visco). I never reach the main UI.
bibz1st wrote: Mon Sep 15, 2025 6:22 pm I too had this kind of problem, havent noticed which file is causing it yet, will try again but it doesnt get to the ui, it just disappears. Restarting just goes through the same procedure of scanning some plugins then disappearing.
Found the cause.
Will be fixed in the next update.
Thanks for reporting this!

Post

No problem, glad you found it.
Beauty is only skin deep,
Ugliness, however, goes right the way through

Post

MuTools wrote: Mon Sep 15, 2025 7:31 pm
masterjoe wrote: Mon Sep 15, 2025 5:11 pm The first thing that happens when I start MuLab.exe is that MuLab wants to convert the plugin database. This works for a while and when it reaches Visco.vst3 the scanner window hangs for a second and then disappears (=crash). When I try to launch MuLab.exe again the same procedure begins (conversion dialog - scanning - crash at Visco). I never reach the main UI.
bibz1st wrote: Mon Sep 15, 2025 6:22 pm I too had this kind of problem, havent noticed which file is causing it yet, will try again but it doesnt get to the ui, it just disappears. Restarting just goes through the same procedure of scanning some plugins then disappearing.
Found the cause.
Will be fixed in the next update.
Thanks for reporting this!
Wonderful :tu: :tu: :tu:

Post

For me there are two things that I would like to see in 10.1 regarding the plugin manager:

(1) Only use ONE plugin database for both MuLab app and plugin, they shall share it.

(2) The favorite plugin folders shall always be visible and editable in a separarate, dedictated text list in the main UI of the plugin manager (the current menu for switching between them is rather clumsy). There you can add, remove and scan them. You should be able to scan them all at once (batch) with the click of a button. This saves time!

Post

MuLab's updater not picking up the new beta?

Btw, no plurals for these:
Remove Unrecognizeds
Remove Unfounds

Uhbik, not showing all plugins, only one displayed.

If a category is empty, ie no CLAP plugins, or CLAP Synths but no effects then do not show that category. Great that these are there but it means clickign on empties just to see if there is anything there.

Great job though :tu:
Last edited by sl23 on Tue Sep 16, 2025 2:16 pm, edited 1 time in total.

Post

masterjoe wrote: Tue Sep 16, 2025 9:29 am For me there are two things that I would like to see in 10.1 regarding the plugin manager:

(1) Only use ONE plugin database for both MuLab app and plugin, they shall share it.

(2) The favorite plugin folders shall always be visible and editable in a separarate, dedictated text list in the main UI of the plugin manager (the current menu for switching between them is rather clumsy). There you can add, remove and scan them. You should be able to scan them all at once (batch) with the click of a button. This saves time!
Wouldn't it be better if all the databases, colour settings, mux patches, etc, were central?

Post Reply

Return to “MuTools”