beautiful work, jerry!

Thanks Jonesey! I'll take a look when I get some time!

jac


I'd like to ask the folks who weighed in on this for a little more info.

I like the idea of a separate midi KS track (shoulda thought of that one myself - duh!). I'm curious about the drum map references though. I haven't looked into setting up drum maps myself, they usually just work when I use a drum synth like SD3. Do those of you who use them in this context have some maps set up with articulation names? If so, do you set them up yourselves or are there templates available for that (could be a lot of work, if not) - or possible some secret for creating them quickly.

I use EW Symphonic Orchestra (gold) and Symphonic Choirs as well as Garritan libraries (GPO, JABB, and IO).

Any additional info would be appreciated!

Using a separate keyswitch track is the only way to go when doing studio work because otherwise your KS "notes" will show up in the staff view and the event list which you definitely don't want, as it will create confusion.  Just be sure to label your KS track in such a way that you know at a glance what track it is linked to.   
 
Check out my above post for the actual template I used for this piece:
www.jerrygerber.com/symph8.htm
 
JG

dlion16


beautiful work, jerry!

Thanks!

Do you mean that each instrument samples, such as 1st Violin would have an audio track, a normal midi track and a drum map for keystrokes? jjim1  

Do you mean that each instrument samples, such as 1st Violin would have an audio track, a normal midi track and a drum map for keystrokes? jjim1  

  Do you mean that each instrument samples, such as 1st Violin would have an audio track, a normal midi track and a drum map for keystrokes? jjim1

I use Vienna Symphonic SE and SE+, VSL Dimension Strings, Hollywood Strings, and some external synths. I typically have a strings folder with separate instances for each section (1st, 2nd, Violas, Celli, Basses), and Woodwind folder, a Brass folder, etc. For piano, I go to Ivory II Grands. Although it is complicated, with Hollywood/EastWest they tell me an 8-core CPU runs more efficiently with separate instances. I have had no memory or CPU issues with standard VSL. Dimension strings requires a little more horsepower, and Hollywood is very taxing on the system.

For myself there's better performance overall with less dropouts keeping my Orch.outside of X2.

I'll use one large instance of VEP5Pro x64 & as my project template or metaframe. 
I typically use 8 VEP midi event input instances per project ( 8 folders/ 16 midi channels per) using the default 32 ins + 32 outs in X2 bussed to my main orch out. I'll eq instruments per channel using VEP's mixer & run MIR or orch verb outside of X2.

I use other VSTi's inside X2 (asst. Kontakt synth.- drums libs, gtr sims) or I'll add another instance of VEP5 to the server that are project specific. 
There's some drawbacks to the workflow but I prefer using VEP5 this way rather than  re-starting X2's transport over & over because of dropouts.

Speaking of gapless.....