I noticed that when I load my track templates the sends aren't saved.  Is this by design or something that isn't working in the current version?
 
Thanks!

Don't know what version you have, but in the latest, Sends are not only saved with Track Templates but if you load the Track Template into a project that doesn't have the referenced sends, those sends will be created.
 
Make sure the Edit Filter is set to "All." You might have the sends in the track, but aren't seeing them.

Thanks Craig,
 
I'm using the latest version of Platinum and it's good to hear that it can save the sends within the track templates. I'm having a hard time finding the edit filter settings that you mentioned however.  Would you mind letting me know where I can find those settings?
 
Thanks Again!

 
I don't know why that alluded me..  So after some testing it appears that track templates don't save sends to hardware outputs.  It's almost as if they get ignored.  I was able to get outputs sent to buses and sends that are pointing to buses to save in the template.  However, if the output or send is pointing to a hardware out it isn't saved and either the send doesn't appear when a track template is loaded or it is routed to the Main Outputs instead.  
 
If the sends or outputs saved in a track template are pointing to a bus that is pointing to a hardware output, the bus is created if it doesn't exist in the project but the buses again default to the main Outputs and not their intended hardware output.  This renders the routing rather useless as I have to reroute the outputs each time I import the template.  Can anyone confirm this?  Is it a possible bug?

Hardware outputs aren't buses, so I don't think they can be treated as destinations in the same way that buses existing within the SONAR ecosystem can be treated. 

Hi.
I tried:
 
I found that a track with a send to a hardware output saved as track template seems not to work as expected, since I am getting back only the track without any send upon loading the specific track template.
 
But, I also tried to save as track template a different track, with a send to a bus that it's routed to a hardware output and it worked better but with a short notice:
 
- if the bus is already in the project it will not change its output as saved into the track template but the bus will maintain its original output.
 
- if the bus is not in the project everything seems fine: I am getting the bus with the hardware output saved into the track template as expected.
 
Regards,
Giorgio

Thanks for trying it out Giorgio, it appears that you have had the same results as I.  Now it's a matter of hearing if others see the same limitations.  I wonder if someone from Cakewalk can let us now if this limitation is by design or simply a bug.
 
If anyone one else is willing, would you try to save a track template with a send to a hardware output?  When you load the template, is the send still in the track?  Also, if you could try saving a track with a send to a bus that is pointing to a hardware output other than your DAW main outs.  In my testing the track template would load the send and create the bus (if it didn't exist) however the bus output wouldn't reflect the hardware output.  Instead it would default to the main output.
 
Thanks guys!
 
Adam