This is a problem. If I am running a sequence on my DAW accessing VE3 server on another Mac, and when I change to another sequence which only needs the EXACT same setup, VE Service on the Slave re-loads all over again.
One of the main points (for me at least) of running VE as a slave is that we AVOID this reload.
Now, I can understand why this has been done in this way, as VE Server must behave like a real plugin in the DAW (which would of course reload in the same manner).
Could it PLEASE be made an option for the Service on the Slave to ask (via the plugin): "do you wish to reload". If I KNOW that my sequences are setup to address the same sounds sets (as they are currently, by running VE as a standalone on a separate machine, via MIDI and ADATs) then I would KNOW that my sounds will link up.
Waiting for Vienna Service to reload is, frankly, a complete showstopper for this networking solution, brilliant though it is. My thinking is this: I must switch constantly, all day long, between different sequences on my DAW, as I work my way through numerous music cues for my projects, which DELIBERATELY SHARE the same setups (not just on VE, but other standalone VSTi's too accross my studio).
For now, I am back to a rack of 2408's. Obviously, a 64 bit version of VE will still vastly improve this (non-networked) workflow. But jut think: if I load up 25GB worth of samples or more on a slave, networked, and have to wait for this to reload everytime I switch sequences, I will be wasting a lot of time.
In the real world of music production, sadly, we must sometimes work at great speed, swapping around sequences often with clients present in the studio.
So, my "feature request", if you will, is can VE3 be tweaked to allow an option that avoids a re-load somehow?
Thanks,
Ben