In the process of creating track templates this weekend I made a nice discovery when using "Enable MIDI Output" on one VSTi to drive another. I typically insert them MIDI/audio tracks, but then moved them to a folder. Basically, VST1 (MIDI) drives VST2. When putting them in a folder I realized the VST2's MIDI track was superfluous so winced in anticipation and deleted it... and all was fine!
Routing for this:
- Insert VST1 (the driver), with MIDI Source/First Synth audio, Enable MIDI output.
- Insert VST2 (the slave), with MIDI Source/First Synth audio, No Enable MIDI output (keep "loose MIDI" out of the game).
- Delete the MIDI track to VST2.
- Route output of VST1's MIDI track to VST2.
Saving as a template:
- I like using folder, so selected the 3 tracks and moved to a new folder first (select and right click "Move to Folder"->New Track Folder"). Rename the folder.
- Make sure the three tracks are selected again and right click on a track (not the folder) and "Save as track template..."
- To use, simply right-click the left pane of the Track View and "Insert from Track Template..."
Very important caveat to this: Any cwp's with these types of routings embedded can only be opened by opening X3/Splat
first, and then opening the cwp file (via either the File or Quick Start menus). Opening via Start->SONAR->[filename].cwp or double-clicking the cwp file causes the routing to fall apart.