MuTools

markuc · Post by **markuc** » Sat Feb 16, 2013 4:49 pm

Hello,

what it means ? And way writes this report for all my VSTs ?
(SPL Vitalizer, Tone Boosters all plugins ... )

Thank for answer

MuTools · Post by **MuTools** » Sat Feb 16, 2013 5:04 pm

Maybe it's this: OSX and Windows do not allow loading 32 bit plug-ins into 64 bit hosts and vice versa. So make sure the VST plug-ins you want to use have the same bit-depth as the host (MuLab/MUX) you're using. If such version does not exist for a specific VST plug-in then you could try jBridge.

markuc · Post by **markuc** » Sat Feb 16, 2013 5:43 pm

Thanks for answer, but all this plugins are 64bit. And i am running 64bit MuLab.

MuTools · Post by **MuTools** » Sat Feb 16, 2013 6:00 pm

Then can you please elaborate on what exact steps you take and also list a couple of small/easy-to-install (freeware) vst plugins that fail.

markuc · Post by **markuc** » Sat Feb 16, 2013 7:41 pm

Simply all my vst effect plugins does the same. Not important how i wont open it.

I click into rack windows - vst - effects - XY - Couldn't create instance for XY.

I wont add new module to polysynth editor - right click - add module - vst - effects - XY - Couldn't create instance for XY

ALL my plugins does the same.

(ToneBoosters plugins, SPL, SSL ... )

MuTools · Post by **MuTools** » Sat Feb 16, 2013 8:10 pm

Please email me your VstPlugins.Xml file. It's in your MuLab/User/Settings sub-folder.

Crackbaby · Post by **Crackbaby** » Sat Feb 16, 2013 8:13 pm

markuc, it's "want" not "wont" (short for "will not")... it's very confusing to read

markuc · Post by **markuc** » Sat Feb 16, 2013 9:00 pm

I am very very sorry, my English is simply terrible ...

markuc · Post by **markuc** » Sat Feb 16, 2013 9:14 pm

now i see it ... MuLab scans my (386)VstPlugins folder, i don't know why ...
How to set my 64bit VstPlugins folder ?

markuc · Post by **markuc** » Sat Feb 16, 2013 9:20 pm

fixed ... thank you !

MuTools

KVR Audio

Couldn't create instance for ... (any VST)