Originally Posted by Busdriver
Maybe not a tutorial but something explaining the general concept.
Traditionally, we hosted our VSTi's in our DAW. This was/is bad for those with huge orchestral (or other) templates who only had 32 bit DAW's. 32 Bit DAW's can only use 4GB or so of ram no matter how much your computer has.
Additionally, for many, having a 64 Bit DAW is great as you can basically use as much ram as your computer has. That's a GOOD thing. The BAD thing is everytime you open up a session, you have to wait for your template to load again. Depending on your computer, drives, OS, DAW and VSTI's, this can range from 5 minutes to a half hour. Imagine working on a film with the director sitting there waiting 20 minutes for EACH cue to load up. Imagine making last minutes tweaks on 30 cues. Not fun. Not acceptable. At least not for me.
Enter VEP. VEP can run both 32bit and 64 bit simultaneously. Best to run 64 bit, but you also have 32 bit for those VSTI's that are not updated to 64 yet. It will host your VSTI plug ins OUTSIDE your DAW so there are no long load times going between cues, no bogging down in your DAW. That's a GOOD thing. Setting it up can be a bit daunting, and that's potentially a BAD thing, but overcomable and in the long run - worth it.
So, you build a little virtual synth / sampler house inside VEP and outside your DAW. Load up all your favorite sample libraries, save it as a template. Then, you instantiate INSTRUMENT TRACKS inside your DAW and put the VEP plugin on the instrument track. This virtual instrument opens up a internal network between VEP and your DAW. How many you use and how you organize is personal and beyond this brief description. These VEP "Instruments" allow communication between your DAW and VEP. Inside your DAW, you add midi tracks which corespond to each of the individual instruments hosted inside VEP. These midi tracks are delivered to your specific VSTi's via VEP's internal network. They can number in the hundreds.
If you set VEP up right, you can have an individual iinstrument track play a specific sample in Kontakt for instance, have that Kontakt instrument come out a separate output into the VEP mixer, and have the VEP mixer assigned via the internal network to your DAW to an individual Audio Track for JUST THAT INSTRUMENT!!! A DISCRETE individual pathway from midi to final audio for potentially HUNDREDS of voices. (Depending on how many "voices" your DAW can host.) My "midi" orchestra comes back in on about 60-80 stereo audio tracks. This is fantastic.
To make it even more powerful, you can run VEP on the host computer, or host and slave computers, or just slave computers, in any combination and bring them ALL back into your DAW.
It's a fantastic setup IMO. This is the basics, and maybe someone else can add more. My fingers are tired.....