Vienna Symphonic Library Forum
Forum Statistics

182,058 users have contributed to 42,201 threads and 254,657 posts.

In the past 24 hours, we have 2 new thread(s), 8 new post(s) and 42 new user(s).

  • HELP! Maximizing Efficiency using Pro Tools, Vienna Ensemble, and Plogue Bidule

    Hey Guys, I'm relatively new to the virtual instrument world and am looking for some input on how to manage my VSL instruments as efficiently as possible. I am running Pro Tools v.8.0 on Mac OSX 10.5.7. In Pro Tools, I create multiple instrument tracks and insert 1 Vienna Ensemble (v2.0 build 4017) plug-in on the first instrument track in Pro Tools. I then re-route each Vienna Ensemble instrument track to individual Instrument tracks in Pro Tools. So basically, the first track in VE routes to my first instrument track in Pro Tools, the 2nd VE track is sent to my 2nd instrument track in PT, and so on... The track limit for each VE plug-in routed to pro tools is 16tracks; therefore, for each VE plug-in I insert in Pro Tools, I can manage 16 instruments. First off, does this bog down my RAM and is there a more efficient way of doing this? What are the anvantages of using the Plogue Bidule vs my current set up? If so what are they? My goal is to create a template in Pro Tools with almost every VSL instrument already loaded so I don't have to create a new setup every single time I start a new song/project. I realize using a slave CPU in conjunction w/Ensemble PRO would probably be my best solution, but Bidule is a hell of a lot cheaper, so I'm trying to weigh my options and save green at the same time. I would truly appreciate anyone's help or insight. Thanks for your time! Cheers, - Pierre

  • I'll give you my setup maybe that will help you with some ideas... My standard template where I'm using PT 8 HD3 on my mac pro where I only run as a host, and 3 servers running VE Pro. What I'm doing is each section will have its own stereo channel in PT, so all french horn intruments (solo, vienna, triple, ensemble, epic) will route through one stereo channel, the same goes for all the other sections respectively. Then each ensemble will route to there respective channel destinations (brass, strings, woodwinds, etc.). And finally, all is routed to one stereo channel channel which is the entire orchestra. This allows me to simulate the location of each ensemble in any giving space via multiple reverbs. Also I can eq or compress, if at all, each and every part of the orchestra for detailed control of the mix. I'm sure this is pretty common, but in PT thus far this has worked great for me.

  • Hi there, I am having exactly the same problem in VSL - How to organize my projects. Becasue VSL so meticulsouly breaks down articulations, I have sometimes 16 sample patches and more loaded for a single instrument. That ends up being 16 MIDI tracks to score one line. I use Pro Tools, and i was hoping for some way to change MIDI channel dynamically (so one MIDI track can keep switching between Kontakt channels, and thus each instrument only will take up one track). But my reading so far suggests this is impossible. Does anyone have any input? Is the only solution to have a session in my DAW with many MIDI tracks per instrument? all thoughts welcome! -m

  • last edited
    last edited

    @Maxxer said:

    I have sometimes 16 sample patches and more loaded for a single instrument. That ends up being 16 MIDI tracks to score one line. I use Pro Tools, and i was hoping for some way to change MIDI channel dynamically (so one MIDI track can keep switching between Kontakt channels, and thus each instrument only will take up one track). But my reading so far suggests this is impossible. Does anyone have any input? Is the only solution to have a session in my DAW with many MIDI tracks per instrument? all thoughts welcome! -m

    I'm a newbie to the VIs, but I think you're missing the point of using the matrix. With speed parameter, key switching and controllers, you don't need 16 midi tracks for one line! That's the whole point of the matrix. May I suggest, RTFM? Try pages 20-21 of the docs.