MuLab 10.1.25

[MuTools]

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.pngScreenshot 2025-09-14 102850.png

In MuLab 10.1 there are plugin files and plugin items.
A single plugin file can contain many plugin items.
So at least there is a plugin file name and a plugin item name.

By default the plugin file name equals the real file name itself, without extension.
But it could be, for reasons, that you have multiple versions of the same plugin in different folders. These would end up with the same name in the database making it difficult to differentiate between them. That's why MuLab allows renaming the plugin file within the database. The real file on disk keeps the same name (changing that could be problematic to some plugins) but you can give it a custom file name in MuLab's plugin database.

A plugin item ( = a real plugin inside a plugin file) only have a single non-editable name and that's the name given by the plugin developer.

Does that clarify it?

[pljones]

Yes, thanks -- so multiple plugin files could have the same plugin name (i.e. in separate folders but same file name).

So where multiple instances of the same Name exist without a differentiating Product Name or anything else (e.g. plugin type, etc), that would cause a conflict - is there a conflict resolution method or does one just get "(nn)" appended (for "nn" depending on how many there are)"?

[pekbro]

I still wish for an option to sort plugins by company name...

*My effects list is 5 1/2 x the length of the browser window and manually arranged by company name, it takes me a couple of hours to make that.

[Michael L]

I still wish for an option to sort plugins by company name...

In the browser, I group some plugins by company name and some by type.
Is that what you want?

[pekbro]

I still wish for an option to sort plugins by company name...

In the browser, I group some plugins by company name and some by type.
Is that what you want?

Yea pretty much, a lot of DAW's will do that automatically for you, if you like. Even the categories,
since there is facility in the plugin formats to list such things, though not every developer bothers
to categorize their stuff for you, sadly.

Anyway, I expect it should not be too difficult. That said, probably not a high priority, which is
understandable. I can't imagine any arguments against it though. As it is, the browser is pretty
flexible and all, but a bit tedious if you're dealing with high plugin counts. imo

[sl23]

As it is, the browser is pretty
flexible and all, but a bit tedious if you're dealing with high plugin counts. imo

Agreed. With a lot of plugins, it gets tedious. If categories were listed permanently in the plugin manager would help alleviate this a bit.

But I still think the browser should be expanded to handle many of the options from the plugin manager too.

[MuTools]

Yes, thanks -- so multiple plugin files could have the same plugin name (i.e. in separate folders but same file name).

So where multiple instances of the same Name exist without a differentiating Product Name or anything else (e.g. plugin type, etc), that would cause a conflict - is there a conflict resolution method or does one just get "(nn)" appended (for "nn" depending on how many there are)"?

When they're in the same context then yes they get an automatic appendix, eg. when you have equally named plugins in a modular area. In any case there would be confusion in your musical project you can rename plugin instances yourself to clear things up where necessary.

[masterjoe]

Checked the new 10.1.1 but after Mulab told me that the plugin database needs an update it crashes repeatedly when it tries to scan Visco.vst3 (Visco 2.0).

[MuTools]

Even the categories,since there is facility in the plugin formats to list such things

MuLab automatically adds any category reported by a plugin to the category editor.
So i'm not sure what's missing here.

PS: I'm looking into adding a "Developers" group option for the browser.

[MuTools]

Checked the new 10.1.1 but after Mulab told me that the plugin database needs an update it crashes repeatedly when it tries to scan Visco.vst3 (Visco 2.0).

Double-checked it and no problem here, scans and opens fine.

[MuTools]

I still think the browser should be expanded to handle many of the options from the plugin manager too.

Agreed. At least things like Make Favorite and Edit Categories should be doable from the browser too without having to open the Plugin Manager. Will do.

[pekbro]

Even the categories,since there is facility in the plugin formats to list such things

MuLab automatically adds any category reported by a plugin to the category editor.
So i'm not sure what's missing here.

PS: I'm looking into adding a "Developers" group option for the browser.

Great! That's exactly what I'm after. I just want to organize plugins by developer.

[masterjoe]

Checked the new 10.1.1 but after Mulab told me that the plugin database needs an update it crashes repeatedly when it tries to scan Visco.vst3 (Visco 2.0).

Double-checked it and no problem here, scans and opens fine.

It only seems to happen in the MuLab app, not in the plugin version. Can I provide you with any info for further investigation?

[MuTools]

It only seems to happen in the MuLab app, not in the plugin version.

I tried it in MuLab App, works ok here.

Can I provide you with any info for further investigation?

Sure, i'll give it a quick look.

[masterjoe]

It only seems to happen in the MuLab app, not in the plugin version.

I tried it in MuLab App, works ok here.

Can I provide you with any info for further investigation?

Sure, i'll give it a quick look.

Maybe it's quickest if I delete the old DB and add everything from start? What do I have to delete where for that?

Ah and BTW it would be wonderful if MuLab app and MuLab plugin would actually SHARE the plugin database. Because scanning in both entities does not make that much sense IMO. And if more options for catagorizing plugins and stuff are added you would have to do that in both as well. Thats pretty annoying.

So maybe you could move the database for both to a common place where they can share the data?