Multiple VST Protection

[CleverConQueso]

I was having stability issues when I loaded multiple instances of the same VSTi. The issues are all but gone now that I got in the habit of making multiple copies of the VSTi dll and keeping track of which copy I have loaded.

How about automating this with a feature called 'Duplicate VST Protection" where dll's are copied to a unique temp file and that temp is loaded?

Thanks,
- CCQ -

[woodslanding]

really??? This might explain some of my stability issues.....

can you actually rename the dll's? I have 5 instances of Kontakt, 3 instances of Reaktor, and 2 instances of Zen in my wkp, and I almost never finish an editing session by closing Usine. In fact, I'm lucky if Q-U-I-T still works, or I can still see the gui.....

I'll try this, thanks for the tip!!!!!!!

[Floego]

I remember that this problem with duplicated vst started about the time multicore and multithreaded processors got common into systems. The vst's couldn't properly work into that enviroment, in some cases it was the fault of a certain synthedit version used to create the vst, in other it was the fault of winxp and it's multithreaded architecture, etc.

Renaming vst is very useful in general but take notice it may confuse some particular software , vst samplers could take the worst part on this. So , just try and tell!

Oh! and a duplicated vst protection could be great...in any software, I just don't know why it is not to be seen in any host

[CleverConQueso]

In my experience, yes to both of you. I sent a workspace to Nay-Seven and he said some things that got me thinking. I haven't had a crash since.

Yes, I just copy and paste the DLL. x, x copy1, x copy2, etc. Some dll's have subfolders and although I copied them as well, I can't think of any reason why that's helping or even being used. It's a pain to keep track of which one's you've loaded, particularly if you're mixing patches from different songs. But what's nice is in Usine, the full name of the dll file shows up patch and in the browser list. I haven't used a lot of other VST hosts but my memory is that display the correct name of the VST, not the file name. I had the same experience with crashes rather than quits. Very frustrating.

And yes, different versions of SynthEdit and multi-core both came up when I Googled around looking for a solution. I'm on Win7 32, 4GB, quad core.

- CCQ -