MuLab 10.1.25

[sl23]

No, that would require deleting it from the rack wouldn't it? But I never touched that.
In, fact, thinking about it, I recall seeing it be deleted as I loaded the new project as it drew my attention to it.
But hey, I don't want to make a big deal as it is clearly one of those random things.

EDIT: I just had a crash during further testing of reloading this project. But as i say, I don't want to hassle you, just letting you know what's happening. Would the Log file help? Or is it not worth looking into yet?

[sl23]

Ok, further testing has made the same VST disappear from the rack, all I did was to reload the project, no changes, no deleting of anything manually, just simple clicking the PROJECT button and selecting OPEN and then double clicking the project file. A subsequent reload, brings it back.

Perhaps this may be specific to the plugin though as It is not an official plugin. I mean, it's a paid for plugin, but for the Roland S1 Aira Compact, so not an official Roland plugin. But it seems to only affect this plugin. I'll gather some details about the plugin and pass them on to you asap...

EDIT: Repeated a third time. Here's the link to the website: https://roland-s-1-editor-soundbank.jimdofree.com/

[MuTools]

When that specific plugin has unexpectedly disappeared again then pls do MuLab menu -> Tools -> Keep Log and email me the most recent log file in your MuLab/User/LogFiles folder.

[sl23]

Will do!

[jd88]

It happens repeatedly that a / the pad activity indicator remains in the "ON" state.
-

Bildschirmfoto 2025-10-04 um 16.42.19.png

-
This is especially true when duplicate notes or the same notes are played in quick succession.

Unfortunately, the indicator status cannot be changed manually (e.g., by clicking with the mouse) or by playing the note. It remains until the plug is reloaded.

Deleting and undoing the pad also does not change the status.

[jd88]

It seems completely unnecessary to me that, according to MuLab, you can route audio data via an "event output" (Patchpoint) which Audio-connections are empty, only Event uses.

(e.g., here: last entry in the photo = MIDI event output)

---

Bildschirmfoto 2025-10-04 um 16.57.07.png

---

Sometimes, according to MuLab, you can even route something into a plug-in, e.g., to an event mapper? Or like here Foto "PP-Audio OP") Patchpoints back within the same Plug??????

---

It would actually be desirable if you could determine which outputs or types of outputs can be routed to, but by the way, you can't.

The list of routing options is sometimes unnecessarily long. I think it's to much for User (often he cannot see, what the target maybe). In some cases there are more then 100 Targets ... (if Plug complex). Many does'nt make sense to route into.

[MuTools]

It seems completely unnecessary to me that, according to MuLab, you can route audio data via an "event output" (Patchpoint) which Audio-connections are empty, only Event uses.

Where do you see this list?
The screenshot you included does not show the context.

[MuTools]

PS: Maybe also relevant to share the project.

[heks]

Hi, not sure why but, I have an issue this beta version. When I get M10.1.10 to scan my vst's it crashes instantly when scanning Halogen vst3. I can open an older project with Halogen in ( made in a previous version) and it loads/plays without issue. ?

[MuTools]

Hi, not sure why but, I have an issue this beta version. When I get M10.1.10 to scan my vst's it crashes instantly when scanning Halogen vst3. I can open an older project with Halogen in ( made in a previous version) and it loads/plays without issue. ?

It's an issue with Halogen, imho.
It seems to access its DLL even after exitDLL has been called!
Workaround for this plug:
Goto Plugin Manager, select GForce Halogen, and enable "Keep DLL Open Until End".
Then Rescan it.

[heks]

Hi, not sure why but, I have an issue this beta version. When I get M10.1.10 to scan my vst's it crashes instantly when scanning Halogen vst3. I can open an older project with Halogen in ( made in a previous version) and it loads/plays without issue. ?

It's an issue with Halogen, imho.
It seems to access its DLL even after exitDLL has been called!
Workaround for this plug:
Goto Plugin Manager, select GForce Halogen, and enable "Keep DLL Open Until End".
Then Rescan it.

That seems to have worked, I know what to do now if I come across it again, many thanks.

[pekbro]

Hi, not sure why but, I have an issue this beta version. When I get M10.1.10 to scan my vst's it crashes instantly when scanning Halogen vst3. I can open an older project with Halogen in ( made in a previous version) and it loads/plays without issue. ?

It's an issue with Halogen, imho.
It seems to access its DLL even after exitDLL has been called!
Workaround for this plug:
Goto Plugin Manager, select GForce Halogen, and enable "Keep DLL Open Until End".
Then Rescan it.

I did report this, their intention was to look into it, according to their support staff.
They were surprised to hear it was the vst3 version, I had to correct them about that even.

[jd88]

In different DAW's I geterror-messages while scanning MuLab Plugs (Plug: Latest official BETA). Example: Reaper:

-

IMG_3506.jpg

IMG_3505.jpg

--

--

And while loading the synth-plug:

- - - -

Bildschirmfoto 2025-10-07 um 14.13.15.png

[MuTools]

Choose "Use Default".

It's a M10.1 beta bug and only happens when you use MuLab 10.1 for the very first time in a new folder, ie. when no PluginDatabase.xml is found.

Next update won't show such alert anymore.
Thanks for reporting this.

[pljones]

Does the plugin scan check the plugin database file is writable and report if it gets a write failure cleanly and clearly, so the user knows they've installed in a bad place?