I have spent many hours trying to resolve this, but I am not sure if it is me or MuLab. Likely it is my project at fault. I found a repeatable crash, but although it is repeatable, I can't seem to resolve it.
I load my plugin, PolyHostInterface.vst3, it runs fine no issues. But I've been trying to test plugin load and missing plugin failures. PHI works ok in this regard, but if a plugin is not found for some reason, on closing ML, there is nearly always a crash. Is this likely my plugin or MuLab?
Ok, so a bit more detail... PHI loads other VST2x64 and VST3x64 plugins as preset chains. It provides several other features, but the main issue is that if a PHI preset is loaded with a plugin not found or failed to load it, then ML crashes only on exit. I'm guessing it has something to do with how ML saves the project maybe and it is getting confused by the missing plugin in PHI, just a guess, as I said.
I can post the plugin and link to source if required. But just wanted a quick response before doing that.
Thanks Jo.
ML crash on exit with my plugin
-
- KVRAF
- 3165 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- KVRAF
- 13873 posts since 24 Jun, 2008 from Europe
First of all:
Are you loading plugins inside your host-plugin that are also plugged into MuLab directly?
For example:
Plug X is inserted into a MuLab rack slot.
PHI is inserted in another MuLab rack slot.
That same Plug X is also plugged into PHI.
Because that's a case not supported by VST3 due to the initDll and exitDll design issue.
A plugin could be generating/processing audio, it could be making a salad, it could be navigating starships... anything. There are only a restricted amount of interface functions between host and plug as defined in the VST3 API.
Are you loading plugins inside your host-plugin that are also plugged into MuLab directly?
For example:
Plug X is inserted into a MuLab rack slot.
PHI is inserted in another MuLab rack slot.
That same Plug X is also plugged into PHI.
Because that's a case not supported by VST3 due to the initDll and exitDll design issue.
MuLab/any plugin host does not know what happens inside a plugin.sl23 wrote: Thu Jul 09, 2026 2:33 pm but the main issue is that if a PHI preset is loaded with a plugin not found or failed to load it, then ML crashes only on exit. I'm guessing it has something to do with how ML saves the project maybe and it is getting confused by the missing plugin in PHI.
A plugin could be generating/processing audio, it could be making a salad, it could be navigating starships... anything. There are only a restricted amount of interface functions between host and plug as defined in the VST3 API.
-
- KVRAF
- Topic Starter
- 3165 posts since 28 Mar, 2008 from a Galaxy S7 far far away
No its simpler than that. PHI is a plugin host itself, it loads and contains those plugins, not in a sidechain type way you stated. Phi loads plugins directly into it, I suppose like MuLab does? Not sure.
Here's a pic of ML and PHI: effectively, it is a host within a host.
Here's a pic of ML and PHI: effectively, it is a host within a host.
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- 13873 posts since 24 Jun, 2008 from Europe
It sounds like you misunderstood what i wrote. Maybe i wasn't clear. It has nothing to do with side-chaining. It has to do with DLL loading. Anyway, if you encounter an issue with the plugin you're developing make sure to test it in various hosts using the exact same circumstances. Ask help in plug dev fora on the web. I'm sorry but i can't help with developing plugins, I already have a huge shortage of dev time myself.
Oh by the way: What's missing in MUX Modular that you want to implement in your host-plug?
Oh by the way: What's missing in MUX Modular that you want to implement in your host-plug?