Solved a Hideous VSTi Problem

[braincell]

Don't put your plugins in the root of your VST folder, instead make sure they have their own subfolder. This was in Cubase 5 64 bit, Windows 7 64 bit Home Premium.

[Zer]

Well, do you store your socks at home above the Jackets or the trousers?

[braincell]

That is the problem. I dump everything on the floor. This is a bad idea in VST, at least for my plugin.

[Zer]

just like me But I learned from some hd crashes, that it is a good choice to align vst in several directories for further managing

[braincell]

In this case it caused a 32 bit plugin to load instead of 64 and the blue screen of death!

[kylie]

In this case it caused a 32 bit plugin to load instead of 64 and the blue screen of death!

have you heard of jBridge? it might be a worth a try.

"Using inter-process communication mechanisms, it aims to make it possible to run 32bit plugins in 64bit hosts, 64bit plugins in 32bit hosts, or even bridging 32bit plugins to 32bit hosts, allowing to overcome the memory limitations of a single 32bit process, in this last case."

http://jstuff.wordpress.com/jbridge/

[braincell]

I read about it when I had the problem but creating the folder solved the problem. I have the 64 bit plugin available and working now. I would like to know why that fixed it.

[kylie]

did you have both versions (32bit and 64bit, if available) on that machine, in the same (root) folder?
and have you already used the plugin? afair sometimes the plugin database needs a rescan, but, then, I'm no cubase xpert like you

[braincell]

I tried all that. Discovered the plug-ins information window which is pretty cool. You can deactivate and activate plugins in there. The only solution was to create it's own folder. Evey other possible solution was explored.

[siriusbliss]

90% of my plugins are in root VST folder, with some having sub-directories along with their presets, etc.

Usually rescanning the VST folder clears things up.

But then, I'm not using Cubase

I DID have some similar stability issues with Ableton, but that's since stabilized.

Greg

[braincell]

Not only did I rescan but I went so far as to install Cubase again. I guess it's a bug in Cubase. I was fortunate to have the tenacity to figure it out. There is almost always a workaround to every computer glitch.

[kylie]

I tried all that. Discovered the plug-ins information window which is pretty cool. You can deactivate and activate plugins in there.

yeah, that's what I wanted you to point to. didn't remember exactly, since it's been a long time since I opened cubase. I remember having to reenable the one or the other plugin after a crash. I use subfolders most of the time, just for being able to tell them apart. ah and I have SL3 over here. no 64bit

The only solution was to create it's own folder. Evey other possible solution was explored.

well, then it's like that. it's a great find for anybody having trouble with odd behaving plugins
did you look up the release notes to see if it's an already known bug?

[braincell]

Just checked. Nothing in there about that. It might only affect my plug-in and software/os combo. I posted it to the VSL forum and contacted their support so hopefully this will help someone else.