Funkybot

I think you should entirely do away with differentiating between audio and MIDI tracks and just have tracks that recognize the content on them, and act appropriately. . 

And that would take away one of the reasons I choose Sonar, over some other DAWs I have tried out. By all means improve instrument tracks, but please, please, do not take away the wonderfully versatile current system.
 
Track folders help a lot if you are concerned about screen clutter.

@Mystic38

Erm ... you might want to read the OP again. It's not primarily about outputs. Just as the thread title says, it's about simple instrument tracks.

As a conclusion he says:
"So please improve your instrument track !!! we should be able to create instrument track, assigning audio outputs and channels without adding a new vst in the rack"

And that's exactly what we're talking about. ;)

I don't know, what's so hard to understand. I guess, most (although constructive, still kind of negative) thread contributors just don't work that way, so they see no sense in the feature request.

And the VS700c does not care about Folders. And don't you see: If I had to put each and every MIDI-AUDIO-pair into a folder ... I had, let's say, 10 folders. Or on the other hand, if the requested feature was implemented, I had 10 simple instrument tracks, which is, what the SIT is all about... So it's a totally valid request.

At least the Bakers totally got what it is about and responded accordingly.
(No offence to others!)

Hey guys

I have read the rest of the comments and :

1) I AM TALKING ABOUT INSTRUMENTS TRACK and not the couple audio/midi for VSTS
I have never said to change the  couple audi/midi tracks , 
Most of composers  use these both tracks to compose with a vst, I Know !
but the instrument track does exist  right? ... so why not requesting to improve it ?
It's just a different workflow...
if u never use instrument tracks, i don't see the point to say that my request is useless coz of course it is if u don't use instrument track.

2) Adding (example)  20 times the same vst  in the rack for  20 patches, no thank u :) ( my computer will cry) 
example : kontakt with 8 instruments (using audio midi tracks)  = sonar : 344 mb 
                kontakt with 8 instruments (using 8 instruments tracks) = sonar :655mb
knowing that i don't compose with only 8 instruments,  sometimes 30, and I have only  4gb ram by theory

3) I can't wait sonar x3 then lol 

I never use simple instrument tracks. They are too limiting. But that was their reason for being, simplicity.

The flexibility offered by using MIDI tracks and separate audio tracks should not be altered. 

My point, exactly.

JoseC.

I never use simple instrument tracks. They are too limiting. But that was their reason for being, simplicity.

The flexibility offered by using MIDI tracks and separate audio tracks should not be altered. 

My point, exactly.

this is how I work too.

I like to keep all my midi tracks in one folder so I don't have to look around in the whole project to find the
instrument i want to edit.. and then I put the different audio tracks/synth outputs in different folders that give 
clues of what they sound like... ex. "drums", "strings", "aco.guitar", "el.guitar" ect..

it's nice just having to open one folder to find all MIDI-tracks in there.

...
anyway.. just because I don't work with instrument tracks myself doesn't mean I'm agains a feature like this.
flexibility is one of the things that makes sonar stand out compared to other DAWs and I don't understand why
this would be a bad thing.


edit:_______________
i also hide MIDI tracks in the console view so I can use this to mix without messing around with the midi tracks.

stevec

Multiple instances of the same synth that is multi voice seems more clutter than one being fed by multiple MIDI tracks and outputting to multiple audio tracks.

 
Almost...   Picture those multiple pairs of MIDI and audio tracks as multiple SITs instead.  Half the physical tracks feeding the same multi-out synth.  Assuming that one wants/needs pairs of MIDI and audio tracks, of course.
 

It depends on how you arrange tracks in the TV. I do not have "pairs" of tracks. In the Track View I use to have all midi tracks at the top and all audio at the bottom. Console is only audio. I don't actually need having the synth's audio track visible in track view until it is bounced, and then what I don't need anymore is the MIDI track.

Right, I get that.   I was just using "pairs" as a way of saying that there are two physical tracks instead of one SIT, regardless of how they're arrranged. 
 
I do understand why some prefer to use the traditional MIDI+Audio track set, particuarly for accessing certain controls (audio trim, anyone?).  But I personally use SITs more often that not these days, so I really like the idea being presented in this thread - multiple SITs all pointing to the same synth instance.