• SONAR
  • Nice MIDI through discovery (killed the middle-man)
2015/06/08 11:02:11
mettelus
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:
  1. Insert VST1 (the driver), with MIDI Source/First Synth audio, Enable MIDI output.
  2. Insert VST2 (the slave), with MIDI Source/First Synth audio, No Enable MIDI output (keep "loose MIDI" out of the game).
  3. Delete the MIDI track to VST2.
  4. Route output of VST1's MIDI track to VST2.
Saving as a template:
  1. 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.
  2. Make sure the three tracks are selected again and right click on a track (not the folder) and "Save as track template..."
  3. 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.
2015/06/08 11:19:25
BobF
mettelus
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:
  1. Insert VST1 (the driver), with MIDI Source/First Synth audio, Enable MIDI output.
  2. Insert VST2 (the slave), with MIDI Source/First Synth audio, No Enable MIDI output (keep "loose MIDI" out of the game).
  3. Delete the MIDI track to VST2.
  4. Route output of VST1's MIDI track to VST2.
Saving as a template:
  1. 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.
  2. Make sure the three tracks are selected again and right click on a track (not the folder) and "Save as track template..."
  3. 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.




I wish I could mark that helpful ...
2015/06/08 11:22:45
mettelus
LOL... I saw your other post about that
2015/06/08 13:03:13
OldTimerNewComer
The World is indeed circular.
2015/06/08 14:08:14
jatoth
mettelus
... Opening via Start->SONAR->[filename].cwp or double-clicking the cwp file causes the routing to fall apart.




Have you reported this as a bug?
2015/06/08 16:12:09
mettelus
jatoth
mettelus
... Opening via Start->SONAR->[filename].cwp or double-clicking the cwp file causes the routing to fall apart.




Have you reported this as a bug?




Yes, I posted it here. I didn't delve into all of the details of what specifically is affected by that issue, but no longer open any cwp in the above manner as a result.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account