Workflow Question: Importing Midi

Use File > Open to open the MIDI. If there are no predefined MIDI output devices selected in Preferences > MIDI > Devices the file will open with TTS-1 setup to play the file.
 
Tutorial #4 in Help > Getting Started is a good way to learn how to work with MIDI and soft synths.

Only if I assign the output of the midi to the softwarsynthtrack (2-Pianissimo), it will produce sound.
So, do I have to add to every midi, a corresponding softsynthtrack?
 

O.K. I got one step further.
I was able to route all midi to TTS-1.
And I understand, that the TTS-1 is like a universal midi-catch-all-device.
Thank you so far, guys.
What would be now the most elegant solution, to assign high-quality software synth to the different tracks? The TTS-1 is nice for a preview, but not really HD-Sound ;-)

I would suggest using your original workflow to get everything set up how you like it, including the soft synths, routing etc. and then save this as a TEMPLATE

Then when you want to do it again you just open the template and throw the MIDI tracks where you want them

Alternatively, if you often have different types of instruments then I would set up TRACK TEMPLATES for each instrument - this will load up the tracks, soft synths, routing and busses with just one click

It is worth pointing out that EVERYTHING can be saved in a template - eg for your drums you can save the actual MIDI setup, the routing of each kit piece to a separate track, effects on each track (ie compression, eq) any routing such as busses or FX sends etc. etc.

The first option would work best if all of your projects use the same/similar instruments

The second would work best if things change often (you can save lots of TRACK TEMPLATES - so each time you add one that isn't already there you can save it for next time)

The most powerful workflow is to use a combination of both options to best suit your needs

Time spent setting up TEMPLATES is an excellent investment of time IMHO as you will save loads of time (and hassle) in the long run

I have track templates set up for all kinds of common situations, with the most often used ones being track templates set up for different custom drum kits I put together in Native Instruments's Battery 3 drum synth.  In each custom kit, each cell actually used is assigned to its own stereo output channel, and rough levels for each cell's volume are set as well.  Along with that, in the Sonar track template, Battery 3 and the custom kit is loaded into the synth rack, and a track folder is created, with a whole bunch of audio tracks all inserted and assigned to pick up the output of each separate drum kit piece from Battery 3.
 
Further, these audio tracks are routed to separate buses, such as for toms and cymbals, etc, and those get routed to a Drums Bus, which is itself routed to the Master Bus.
 
So, with only a couple of mouse clicks to do the insert of one of these track templates, I get a GIANT bunch work done for me, Battery 3 loaded with a custom kit, each kit piece sending its output to separate stereo outputs, a bunch of audio tracks all set to the different audio output from Battery 3, and then bus grouping of things like cymbals and toms and such going to sub-buses, then to a common drums bus, and finally to the master bus.
 
The above is INSANELY powerful, and one of the things I absolutely LOVE about Sonar.
 
I have such track templates set up for a whole range of different kits I enjoy using, and have additional track templates set up for other synths I use, such as Kontakt, where a similar process is used for having a string section built from individual instruments, same for a brass section, etc.
 
So, go through the tutorials, watch some videos, consider picking up one of the Sonar books out there (they are quite good), and have a blast.
 
Bob Bone