This is just a rant, nothing so see here!
Since everyone seems to "accept" that Sonar does NOT handle "loop and punch" properly I'm on to a new (old) issue.
Thankfully the "Loop & Punch" issue was fixed in X3 (d was it?).  Score 1 for the bakers!
Now, lets get some sanity in the "inputs"; please?
<rant>
WHY CAN I NOT CREATE MONO & STEREO INPUTS!
I'm sure its some kind of OS driver thingy, but COME ON!
Input 1 is INPUT 1, for cris sake.
A REAL console has 4, 8, 16, 32 101; whatever inputs.
Channel 1 is Channel 1, not 1-2 left, 1-2 right, 1-2 stereo.
I know the crap has been beaten out of this dead mule, but GD it.
FIX the GD thing!
</rant>
Thanks for listening, I feel much, much better now...
 
TTFN,
 
T

This bugs me too. But only because I'm old and easily confused. ;-)
 
I'm sure it is designed to be more powerful along with the ability to have 3,842 tracks.
 
Regards,

I seem to "accept" your rant. :)

Thank you, thank you for mentioning one of my desires for SONAR X series. 
 
Of the four DAW hosts that I have bought, SONAR is the only host that does not allow me to format my mono inputs in a clean, concise manner.  Depending on the selection of stereo or mono for any given track, you will see inputs formatted as stereo (R&L) or mono tracks.  When you have soundcards that have 24 - 26 inputs like I have, it makes it easier to select the input you want.
 
In my case, I use Outputs the same way to route to special headphone mixes.
I may have a Avalon 737 coming into input input 15 and a Universal  M610 coming into input 16 as a permanent set up.  It would be better to see them as "Avalon 737" and "UA 610M" instead of "Avalon 737-UA610M Left", "Avalon 737-UA610 Right" and "Avalon 737-UA610 Mono" all in one confusing drop down list.

Sure, I've developed a "workaround" by using Track templates but I get projects in (bundle files) where I have to change inputs or outputs as I do further tracking to live musicians where I am routing things on the fly.

I guess we're all on the same page here.
It sucks getting old, AND being RIGHT all the time.
Come on Cake, fix it for CRIS SAKE!
 
T

Totally one of my gripes as well, particularly because of the implications for External Inserts. One of the end results of Sonar's "stereo only" handling of I/O is that if I specify one mono channel in an External Insert, Sonar will assume that I've used both channels in the stereo pair. So if I have a pair of Distressors on I/O 1 and 2 and I use the Distressor on channel 1 in an External Insert, the Distressor on channel 2 cannot be used anywhere else in the project.
 
It makes my face go like this:
 
Dean

Can you please explain what the issue is with the inputs?  I am just not quite getting what you were explaining (I need more coffee).
 
Thanks, 
 
Bob Bone
 

robert_e_bone
Can you please explain what the issue is with the inputs?  I am just not quite getting what you were explaining (I need more coffee).
 
Thanks, 
 
Bob Bone
 

Here is a shot I took a while back. 
 
Sonar's friendly input list compared to another product's friendly input list.  At this time, I was using my friendly names to also indicate the signal path.  I've simplified my friendly names a bit.  I've pretty much given up on SONAR friendly names and only use that feature in competing products where it makes my input selection easier.

Well there you go!
Its not a OS driver issue.
Come on Cake!
How 'bout some REAL friendly input/output routing???
 
T
Thanks for that Dave.
My labeling looks as backasswards as yours on screen; what a mess!

+1 from me. would have been nice.
but since we have dealt with this for a long time. I take it as it is.
would love to see happen though.
 
dingle