ISSUE with Soft synth templates input (changes to previous synth's output)

My issue is there in my own synth templates and also sonars factory templates. What I have noticed is that something happens when I insert a soft synth template that all inputs to the audio tracks in the template goes a -1 . I know it's hard to understand so let me illustrate.

Let's say I open a new empty project with no audio or midi track. And I insert sonars factory soft synth template True Pianos 》Piano Dub style. Everything gets inserted as it should be. No problem. Everything gets routed as it should and I can start playing the piano or record it. There is no issue when there is no other synth present in the project. Now I try to add one more synth the problem comes up. I go on and insert factory template Studio Instruments Bass 》Chorus Rock. And try to play it I hear no sound. So I split the instrument track and check the routing. No problem with the midi track, it's routed ok. Then I check the audio track is input is routed to True Pianos Primary Output: Stereo. Same thing happens for what ever synth template I insert. Only when there is no other soft synth in the project everything gets routed properly or else the input gets routed to the previous synth output.

Now if I insert a soft synth with multiple outputs. Eg now if I insert Session Drummer 3 》TR-909 Produced Multi-Out. SD3 Kick track's input gets routed to SI-Bass Guitar 1 Primary Output: Stereo. SD3 Snare track's input gets routed to SessionDrummer 1/2 stereo (SD Kick output). And SD3 HiHat gets routed to SessionDrummer 3/4 stereo (SD Snare output) and so on. That's y I said everything gets routed to a -1. Is there any solution. Is it a bug?

It happens only with templates. No problem if I try inserting the synth from the synth rack. But I always use the templates coz I have a large number of custom templates which I always use.

That's pretty weird; I don't recall ever hearing of that, and can't reproduce it now. This is in Platinum - Manchester? If so, try installing the Newburyport update just released. Otherwise you might need to uninstall/reinstall - sounds like something's corrupted. Or there's a more general issue with the way your PC is enumerating audio ports that's confusing SONAR.
 
What happens if you re-save a track template with the correct synth output assigned, and re-load it?
 
EDIT: You might also try re-naming AUD.INI, and letting SONAR build a new one.

Found out configuration file in Preferences. Can I just try clicking the 'Reset Config to Defaults' button there.

I tried the 'Reset Config to Defaults' option. No use. Its still the same. If someone has an option to solve this without uninstalling it will be help full. The problem happens only when loading the soft synth templates. It has some thing to do with an error while the soft synth templates gets inserted.

To make sure I also tried renaming it manually. Still the problem exists. Now I am wondering what settings does my old AUD.INI would have preserved. Should I retrieve it back. I guess I can ignore it.

EdiT

Cool. I'll try that and get back to you :)

I don't think resetting your config will change anything; this just looks like a Sonar bug, plain and simple.
 
I have seen soft synth inputs get screwed up from time to time and I didn't know what caused it - this seems like a candidate as I often use track templates.
 
I've also seen track templates mess up drum maps quite significantly too.

Kylotan
this just looks like a Sonar bug, plain and simple.

If that were true, I would expect to have seen dozens of threads like it by now, and I've seen none. It may be a bug, but hardly 'plain and simple'; clearly the OP's particular environment is a factor.
 

I've also seen track templates mess up drum maps quite significantly too.

 
Drum Maps are a whole different issue. Soft synth MIDI ports are assigned and numbered in the order they're inserted. If the new synth is on a different virtual port than when the template was originally saved, the map is going to be wrong - unavoidable, but easily corrected.

Alright guys I will have to fresh install and see. I can't do it right now, I will have to wait a few days. Till then if anyone got any idea to solve this u are welcome.

Wow! msorrels you are simply awesome. I changed my driver mode to ASIO and the problem solved. Hurrah! I was using MME 32 bit driver which for some reason doesn't seem to have input drivers.

It should work without any input drivers.  Be sure and submit bug report or a support ticket or something.  The only thing that has worked for me is posting here and hoping someone from Cakewalk development sees it.  The wall between support and development at Cakewalk appears to be nearly unbreachable.  But spring is coming, perhaps they will do something to sort out the input/output/routing issues that have plagued Cakewalk for so many years.