Mulab Plugin housed in Studio One Pro 7 - I get: 'CFBundleLoadExecutable failed for plugin 'x'. Couldn't Create VST instance for 'x'. This happens on a vast array of plugins.
Hm! Some open, some don't? NI Kontakt 7 opens, but NI Raum and NI FM8 won't. Jam Origin Midi Guitar 2 will not. It ranges from small VST's like EQ's etc. to more major products. They all scan successfully in Mulab Plug, but....
These all used to open in Mulab Plug in my previous DAW... Studio One opens them, but Mulab inside Studio One fails. Blue Cat Patchwork opens them in Studio One, but Patchwork inside Mulab inside Studio One will not.
MAC M2 Pro Ventura 13.5.2.
What on earth? There seems to be no relationship between those that open and those that won't... as above, even by the same developer (eg. Native Instruments).
Mulab Plugin in Studio One Pro 7 Fails to Open Numerous VST's
-
- KVRist
- 311 posts since 11 Nov, 2012
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
Just a quick thought: Are there any special characters in the path towards these plugins?
Feel free to email me the log file of such MuLab Plugin session where you encountered the errors.
You can preserve a log file via MuLab menu -> Tools -> Keep Log.
Logs are in your MuLab/User/LogFiles folder.
Feel free to email me the log file of such MuLab Plugin session where you encountered the errors.
You can preserve a log file via MuLab menu -> Tools -> Keep Log.
Logs are in your MuLab/User/LogFiles folder.
-
- KVRist
- Topic Starter
- 311 posts since 11 Nov, 2012
Thank you! 
. No, the path is and has always been the standard path - all plugs are stored in the regular VST / VST3 folders. I have emailed a log to you at your infodesk address.
. No, the path is and has always been the standard path - all plugs are stored in the regular VST / VST3 folders. I have emailed a log to you at your infodesk address.