Honestly..... I don't.    This is the first template I've set up.   My recording experience has been in the rock genre so orchestral is something new for me.   I have three string libraries (HS, Albion, Cinestrings), HWBrass, Komplete, EWQLSO, and others.   I've been struggling conceptually on what to include in my first template.  I know from experience that I'll build and rebuild this many times as my experience, tastes, and needs evolve.  But as a starting point, I guess I'm thinking I need to include every instrument and articulation that I have at my disposal.    Probably not the best move, huh?
 

Many of the articulations are different version of the same thing. In HW for example, 1st Violin NV NV VB MV RR and 1st Violin NV NV VB VB RR are the same except for the way CC1 controls vibrato and volume. You would not normally use both. To top it off 1st Violin Sus 6 RR 4th Pos is another way to control 1st Violin - this time CC1 controls vibrato and CC1 control volume.  1st Violin Sus 9 RR 4th Pos is the exact same patch but uses 9 simultaneous voices instead of 6. You would only use one of the 4 options.
 
For HW, use the templates as a guide. Here's the thing - set up templates that include what you NEED. If you have a huge template it may not even load because even 32 GB RAM would not be enough. If it does load, it will take a long time. If you are using 10% of the tracks, that is an awful waste of time and resources.

Just one question. Are elements of the mixer in vepro automatable using envelopes?

I think the reason for better performance is as DRanck said...
Sonar only sees ONE VST, VE Pro, and handles it as ONE, so 
the load on Sonar is less then have "Multiple" VST's on multiple 
Tracks...making the processes handled by Sonar far less...and 
therefore, providing better overall performance.

DRanck
I just added a tutorial video on using VE Pro with Sonar. If you are interested in using VE Pro with Sonar it might be helpful.
http://www.daveranck.com/#!tutorials/c1ajd
 

Great video - thanks!
...Steven

BTW VEP is on sale through May 31st for 20% off, less at JRR shop.

Nice price on VE Pro Steven!
 
Elfin - 
 
From the manual:
Parameter Automation
All parameters in Vienna Ensemble Pro 5 and its hosted plug-ins are automatable from the master host (512
mappable parameters available), including touch automation. MIDI CC Contol is also possible.
 
So I would say yes, it supports automation although I have never used it. I do automate plugins that are hosted in VE Pro though and that works just fine.
 
Dave
 

I am using VE Pro Server and VI Pro on a second computer (using it on the same one as Sonar was too much of a load for a full orchestra), and it works great. The only issue I am running into is that I cannot use all of the Continuous Controllers (CC) that are  used in VI Pro. It uses quite a few controllers between 14 and 30, and those are not available from the picklist in Sonar. Does anyone know how to overcome this problem and add more controllers to the list? I tried entering the number (14) and it did nothing.
 
TIA.
 
-- Martin

Ok...
 
Finally got VE Pro..... 
 
I've installed VE PRO... and you get two programs ... VE PRO Server and VE PRO a (32bit and 64bit)
 
I've installed the Vienna Instruments and that works lovely.
 
So what is the additional Vienna Ensemble and  Vienna Ensemble service? (32bit and 64bit versiosn)
 
 
 

actually, you get three programs<G>...
 
the server runs in the background and hosts all of your plug-ins. It can run on you main machine  or on a separate machine dedicated to hosting plugins.
 
There is a VST plugin (VST2 & VST3 I think, I use the VST3) that drops into Sonar as a VST Instrument. This provides access to the server.
 
And there is a stand-alone client, which used to be separate, but now appears to be rolled into the server. I hadn't even noticed that till you posted.
 
VEPro is  Vienna Ensemble Pro - Vienna Ensemble is  a cut down version that comes with their libraries. You don't need that.
 
Hope this  helps!
 
I'm in the midst of (finally?) building my templates. I've spent a fair amount of time over the last several months tinkering with VE Pro and VI Pro - they required a bit more cockpit time than I imagined (hoped?). But I think I get it  now, and I'm having a blast building the template!