Depends on how it's implemented.pljones wrote: ↑Sun Jan 13, 2019 7:08 pm Cheers. What about bridging between a 64bit host and 32bit VSTs? Presumably the 64bit bridge VST itself would only use one set of resources. But in this case, each bridged 32bit VST would be in a separate memory space, right, and not shared? Would each 32bit VST then use its own slots?
If they do the bridging through a separate process (the most likely solution) and they load all 32 bit plugins in that process, then you get another 128 slots. If they host *each* 32 bit plugin in a separate process, then you get 128 slots for each plugin.
Some DAWs let you host even 64 bit plugins in separate processes.
Now, there's memory and processor overhead to an additional process, and also additional latency with inter-process communication. But seems to work for many people.
But really, as a musician, you shouldn't have to micro-manage your plugins. We think you just want to be able to make music, and not worry about OS implementation details. Hence the >4000 limit upgrade.
Pete