Vienna Suite is certainly a very nice addition to VSL, but I believe it is missing some basic functionality when it comes to using it inside Vienna Ensemble. I'm referring to the fact that you can't automation a VS plug-in's parameters from your master computer's sequencer when it is placed inside a VE instance.
This isn't a problem unless you need to adjust a plug-in's parameters dynamically during the course of the sequence in order to suit the needs of the music. I do this quite often and I bet I'm not the only one.
Now I can use VS plug-ins in this way (i.e. dynamically), but I have to place them on the tracks of my master computer's sequencer in order to get that kind of functionality. This uses my master computer's resources when I would much rather have them in a VE instance on my more powerful slave computer. This means that unless you intend to use VS in a static fashion you can't use VS inside VE.
Now I realize that this kind of functionality is probably not easy to implement, but I'd like to point out that this type of automation already exists for VI. Using VI in Performance Control I can assign MIDI CC numbers to Velocity X-Fade, Cell X-Fade, Release Time, Expression, etc. I can control the CC data values from my master computer's sequencer and they automate the various parameters of the VI's that are inside the VE instances on my slave computer.
I'd like to see the same kind of functionality for the VS plug-ins. I would imagine it to work very much the same way it works for VI. (Example: I open the VS Power Panning plug-in and right-click on the "Width" parameter. The "Width" slider would blink red and I could assign a MIDI CC number by sliding a controller or by selecting the CC from a "Map Control" interface like the one with the VI's.)
Now am I the only one that would use this kind of automation for VS with VE? If so, then promptly ignore this. If not, then......?
Thanks, Brian [:)]