hi Solo, basically if we are using a 64 bit host, to USE the plugins like samplers that need more memory, we might as well keep everything 64 bit. There is no point using a 32 bit plugin in a 64 bit host if there is a 64 bit version of that plug in available, because it would be used through a middleman interface, a bridge, which can cause all sorts of issues with even the best coded plugins and best bridges.S0lo wrote:I might be missing some thing here, so correct me if I'm wrong,
I can understand that some people would prefer using a 64bit version of a plug to allow for it to use extra memory. But why would any one NOT use a 32bit plug if it doesn't need any large memory at all. Plugins like Sylenth1, Diversion, Alpha,... etc don't need more than 4Gb, they only use a few mega bytes.
So basically, speaking from my point of view, and i would say others who voted the same, i use a 64 bit host because i love using lots of sampled sounds so i need the memory. therefore i will only use other plugins that are 64 bit, to avoid using a bridge. In fact, most of my songs will not load in 32 bit logic at all, i get an out of memory error. I am using 5 or 6 gb real memory on average per song. And i only just bought an orchestral library the other day which i haven't even used yet, so that will use even more, in fact i am about to buy some more ram.
Ram is cheap, 64 bit versions of our hosts, if available, are free of charge to any user who owns a license, there is actually no *downside*in coding native 64 bit plugins for the dev.