Many thanks to Tallisman for posting this reply on another thread. I've edited it slightly to put the information into context.
Quote:
Originally Posted by Tallisman
Several of us spent a long time making this work as good as possible, but there was always a price to pay. The costliest was the demise of PDC!
For this routing scheme to work you need the following for best results:
- Folder Track (to hold the whole thing)
- - VSTi Container track (multi channel = number of outs desired)
- - hybrid tracks (Midi & Audio tracks) - one per output
The hybrids must be routed to send midi to the VSTi container only (the portion of the send referring to audio is disabled! These tracks will automatically route their audio to the folder track which serves as a submix for all of the instruments outputs. The VST container track must send audio, and only audio (NO MIDI) to each of the Hybrid tracks.
Folder
| - VSTi (receives Midi but no audio from hybrids) (sends audio but no midi) (does not send audio to folder)
| - - hybrid 1: Send:Midi(to VSTi) all==>01 Audio None ==> none
| - - hybrid 2: Send:Midi(to VSTi) all==>02 Audio None ==> none
| - - hybrid x: Send:Midi(to VSTi) all==>x Audio None ==> none
and of course enable "allow feedback routing"
But why?
The reason I used to do it was so that my Stylus RMX or Kontakt 3 templates would not consume 38 tracks worth of GUI space. And for that I paid the price - I was not able to use some plugins on the audio returns of those instruments as some plugins would make everything fall out of sync by introducing delay.
- - - - -
Then, about a year ago, Cockos introduce a new feature. They allowed us to hide a track from either the TCP or the MCP - this was a happy day and a long time coming. With it I could now reclaim Mixer space and TCP space.
Very shortly after Cockos gave us that candy, Tim ("SWS") decided he would blow it off the hinges. The SWS extension introduced a full featured Track management feature-set.
This SWS blowout enables me to make my 38 track K3 template begin life in my projects as 4 tracks in the TCP and 4 tracks in the mixer. All 38 (or so) tracks are present in the project but most are hidden until they are needed (then deleted if not needed near mixdown). You see, the settings tweaked using the SWS extension are saved with the track templates. So, when I add the Kontakt3 template this is what happens:
-- TCP gets the Folder (submix / overall volume control) and 4 visible MIDI tracks,
-- MCP gets The Folder track and 4 visible audio tracks.
The rest are hidden from both the TCP and MCP, but can be made visible when they are needed.
Thanks to SWS I gained control over my projects and unruly VSTis without sacrificing plugin delay compensation.
greetings
.t
|
Also, please read this, from Justin:
http://forum.cockos.com/showpost.php...1&postcount=51