Hello All!
 
The subject line says it all! Does a single instance of a 32 bit VST adversely impact performance on a 64 bit system? Does it limit my RAM size, slow down processor speed, suck up system resources? I know there are many forum members out there much smarter than me who know the answer to this question so I apologize for my ignorance and thank you in advance for enlightening me!

The only potential issue is stability. Bridged plugins can be temperamental. In my experience problems are most likely to occur with VSTi's that load samples or really old, often free plug ins. Most plug work without issues. I you get "teleport server" error messages you may have found one thats problematic.
 
 

Well, that's the downside.
 
I guess you could say that, 32-bit VSTs that are well behaved in a 32 bit host are likely to work fine under a 64-bit host. However, 32-bit VSTs that are cranky under a 32-bit host are likely to be a disaster under a 64-bit host.

it's just the extra layer (bridge) that is the main thing..most synths etc won't use the extra memory 64 bit affords them.
 
there are obvious things where it's an advantage .e.g. samplers with large sample libraries can use over 4gb memory.
 
even in 32 bit mode, it can use a maximum of 4gb PER vst instance, assuming the memory is available. (If I'm remembering that correctly)
 
 

to me the main drawback or annoyance is the spacebar not working when focus is on a 32 bit wrapped plug-in.

It probably depends on the particular 32 bit VST. Most work fine for me, but I sometimes have glitches when using SampleTank, which is only 32 bit at the moment.

dlesaux
Does a single instance of a 32 bit VST adversely impact performance on a 64 bit system? 

For all practical purposes, no.
 

dlesaux
Does it limit my RAM size, slow down processor speed, suck up system resources? 

 
Each 32-bit plugin will be limited to <2GB RAM, but that won't affect the overall project or other plugins. Only sample players need more than that. Software synthesizers and bread 'n butter DSP effects (compressors, reverbs, equalizers, etc.) don't.
 
It will not cause a measurable increase in CPU or other resources. Sometimes, 32-bit versions can be slightly more CPU-efficient. Occasionally, the 64-bit version performs slightly better. The operative word being "slight".
 
Most important, 32-bit plugins sound exactly the same as their 64-bit equivalents, contrary to some uninformed opinions previously expressed on this forum.
 

If you are using X2 Producer 64-bit, see "BitBridge Server Configuration" here regarding RAM usage:
 
http://www.cakewalk.com/D...;Req=Dialogs2.064.html

Spencer
to me the main drawback or annoyance is the spacebar not working when focus is on a 32 bit wrapped plug-in.

this is the biggest issue for me too. it's because the 32bit plug-ins runs as separate processes and aren't as "integrated" with sonar as the 64bit plug-ins are. (you need to be "in" sonar to tell Sonar to play). because of this you also cannot dock a 32bit plug-in in the multi dock or use x-ray on it

melmyers
It probably depends on the particular 32 bit VST. Most work fine for me, but I sometimes have glitches when using SampleTank, which is only 32 bit at the moment.

LMFAO.... "at the moment".
 
IKObi has been promising ST3 for over two years now (well, saying it's in the works).
 
In the software forum just the other day he said he just saw the "instrument list" and claims that's how close it is.
(like an instrument list is indicative of far along the software development is????!!!????)