Just a historic note on the unisex track function. Pros and cons that had to be resolved.
Fresh, new, unorthodox with definite advantages. Turned off many potential users because it did not follow established protocol.
One major advantage is the output controls on the mixer, specifically volume and pan, work for anything virtual. Pan is pan and volume is volume. You've seen how depending on the design of a synth, the volume control may or may not work in Sonar because the volume and pan may have been designed to respond to CC data, not a fader, so it is a mix and match as to what controls what.. Can still be done of course, but not in a single consistent way across virtual synths. Fault is not with Sonar or any of the other major contenders, but the lack of strictness in what constitutes a vsti.
Reaper leveled the field with everything no matter what controlled by a single mixer fader and pan.
This however created a big problem for those using ourboard hardware synths. Since Reaper was controling the unisex track with real output faders and pan, hardware synths were screwed. They needed CC commands to regulate gradients. That left folks like me with a considerable arsenal of vintage synths dead in the water. No control over anything external as far as volume or position in the stereo field.
Fortunately, the devs gave in to the whiners and set up a switch to convert the output sliders to CC data. Everything worked fine after this. Happened somewhere mid stream in ver 4. But, to get this to happen, you have to actuate the command on the channel which then changes the channel to a midi chanel, not an audio channel, not a unisex channel anymore. Does give the best of both worlds.
All this said, if you have to look for one program that has set the bar for comprehensive routing and control of keyboards, it's Studio One ver 3 and onward. Wish Sonar and Reaper could come up to this level of control.
John