A few things I'm not clear on with VEP as I'm considering it for my setup. Getting it set up can be a fairly long job depending on how complex you want your template to be, but it's well worth the effort. There's an option in the settings of VEP to select how many channels you want available. Simply click on the input/output box, and the drop down menu will give you an option of "interface", "bus" or "plug-in", under the "plug-in" menu your VEP instances show up and you can route to/from any of the channels within that instance. Once you've got a single instance loaded onto a track in Pro Tools then all of the inputs/outputs for that instance become available in your drop down routing menus on each Pro Tools channel.
There's no need to have an instance of VEP on every track in Pro Tools though as the plug-in has multiple channels available and every instrument within an instance can be routed to seperate outputs.
The MIDI output from each instrument track gets routed to a channel in VEP with an instrument section loaded, and then the audio output of that channel gets routed back into the input section of the instrument channel in PT. I wanted to keep as much control in Pro Tools as possible with VEP just hosting the library and doing any initial volume balancing, so I went for a VEP Server instance for each section of BBCSO (Strings/Brass/Winds/Percussion) with 3 channels for every instrument section (longs, shorts, legato) all feeding into corresponding instrument tracks in Pro Tools.
There are different ways to set up the instruments and route them between VEP and PT, so it's worth having a bit of a think about how you'd like to run your template. How to set up Protools.?, will I have to replace every BBC Plugin with a VEP Instance on every channel and have an instance of every BBC Plugin as an instance in VEP on the slave PC?
0 kommentar(er)
