Yeah, it's been there for a while....   I think it was an X series thing, but it could have been pre-8.5 or earlier as Karl suggested.
 

Funkybot

bitflipper

John
Those controls are rather advanced and would be used very rarely if at all. Putting them on a Simple Instrument track would defeat the purpose of a Simple Instrument track. 
 

Agreed 100%. If SI tracks are too limiting, don't use them. I don't, ever.
 
But I'm still trying to figure out the logic of removing those controls from audio tracks, where they're actually pretty important. 
 

The problem with non-simple instrument tracks is they eat up two console channels and two track view channels. Sure, you can hide them, but then you loose access to some of the features. The solution to this is "Advanced Instrument Tracks" or something of the like that allow for all the audio features/options of an audio track, and have all the MIDI features of a MIDI track (including supporting MIDI plugins, arps, etc.). There are other DAWs that already do a good job at this type of thing. 

Another solution is to make use of your screensets.
 
I have all of my Midi tracks in their own screenset which makes it a breeze to switch to & from showing the midi.
 
Also, your idea if an Advanced Instrument Track is great in theory, but just think about how much screen real estate would be needed for so many controls? You'd be back in split midi/audio land before you knew it.
 
In my humble opinion.

Mod Bod

bitflipper

John
Those controls are rather advanced and would be used very rarely if at all. Putting them on a Simple Instrument track would defeat the purpose of a Simple Instrument track. 
 

Agreed 100%. If SI tracks are too limiting, don't use them. I don't, ever.
 
But I'm still trying to figure out the logic of removing those controls from audio tracks, where they're actually pretty important. 
 

I think it was because too many non-Sonar users complained about the cluttered GUI.  I only wish we had some of the clutter back.

me too!!
 
I did report a GOOD thing that X3c did. It was able to determine the interleave based on the track input mode. If you used a mono input, it changed the ionterleave to mono. If you used a stereo input, it changed the interleave to stereo. I was pleasantly surprised. I ran this up the flagpole in X2...

bitflipper
I keep waiting for a user-definable track header, like the main toolbar. I'd like to be able to hide some of the parameters I rarely use, but have the option of displaying those that are important to me (the track interleave switch being topmost on that list). This should have been the approach going into X1, IMO. It's very dangerous to change UI elements based on assumptions about what constitutes "normal" usage (how I wish Microsoft realized this!). Whenever I implement such changes in my own software, I try to offer users the option of retaining the previous behavior if they want. 

Hi bit flipper...

You can create your own set of widgets... Where the option to select All/mix/I/o etc... There is one called custom and there is a screen that let's you see and adjust which widgets you want on which tab... I believe this has been there since long before the X release.... I'm not remembering how to get to that page but I'm sure someone here can chime in with that info...

Sorry...

As to the thread? I never use simple instrument tracks and wouldn't want to even if it contained all widgets... I prefer to think of my MIDI as a track feeding a gadget that has outputs which are separate tracks just as they would be when feeding external gear... It makes sense to me that they are separate...

BTW...I only use the ALL tab myself as I prefer to always have everything visible and available...

Keni

Mod Bod

bitflipper

JohnThose controls are rather advanced and would be used very rarely if at all. Putting them on a Simple Instrument track would defeat the purpose of a Simple Instrument track.  

Agreed 100%. If SI tracks are too limiting, don't use them. I don't, ever. But I'm still trying to figure out the logic of removing those controls from audio tracks, where they're actually pretty important.  

I think it was because too many non-Sonar users complained about the cluttered GUI.  I only wish we had some of the clutter back.

You and me too!

Everything was fine until somebody needed to sell touch screens!

Keni

FastBikerBoy
It's always been there although I believe there was a bug in X1 that could stop it working or perhaps it never worked, I can't remember but it def worked in X2, and 8.5 and earlier.

Ha! Knowing that would have saved me some things... ;-)

I mistakenly thought someone would make a loud noise thanking the Bakers for fixing this...

I us the alt-drag to move my widget order but didn't think to try that on moving tracks! ;-)

Thanks Big Time!

Keni

FastBikerBoy
It's always been there although I believe there was a bug in X1 that could stop it working or perhaps it never worked, I can't remember but it def worked in X2, and 8.5 and earlier.

Thanks for the wake up call FastBikerBoy...

Keni

Keni

bitflipper
I keep waiting for a user-definable track header, like the main toolbar. I'd like to be able to hide some of the parameters I rarely use, but have the option of displaying those that are important to me (the track interleave switch being topmost on that list). This should have been the approach going into X1, IMO. It's very dangerous to change UI elements based on assumptions about what constitutes "normal" usage (how I wish Microsoft realized this!). Whenever I implement such changes in my own software, I try to offer users the option of retaining the previous behavior if they want. 

Hi bit flipper...

You can create your own set of widgets... Where the option to select All/mix/I/o etc... There is one called custom and there is a screen that let's you see and adjust which widgets you want on which tab... I believe this has been there since long before the X release.... I'm not remembering how to get to that page but I'm sure someone here can chime in with that info...

Sorry...

As to the thread? I never use simple instrument tracks and wouldn't want to even if it contained all widgets... I prefer to think of my MIDI as a track feeding a gadget that has outputs which are separate tracks just as they would be when feeding external gear... It makes sense to me that they are separate...

BTW...I only use the ALL tab myself as I prefer to always have everything visible and available...

Keni

Aside from the obvious reservations about Sonar's inbuilt limitations and oddities with instrument tracks, I've never been able to understand what people have against the concept of instrument tracks in the case of a single synth output. They just seem so logical to me.

Just like a mixing desk, you have one track per instrument. Only because this is software, we have the added convenience of being able to incorporate MIDI into the track. To me, having separate tracks for the audio and MIDI just seems like a waste of space in the clips pane. The audio track is empty - no clips, no waveforms. What is the point of it? It makes perfect sense to use that empty space to show the MIDI notes that are driving the synth.

If you've got one MIDI track driving an instrument which is being routed to multiple audio outs (like drums) then of course separating them makes more sense. I'm sure there could be a tidier way of doing it without having to have all of those empty audio lanes in the clips pane, but for now that's all we have. For me, the clips pane is where you visualize the arrangement of the song, and empty lanes detract from this.

I think what we'd find is that the people who prefer spilt MIDI/audio tracks even for single track instruments are probably those who are just used to it from pre-instrument track days. But if you're just starting out with DAW's (or coming from something like Pro Tools where they're commonplace) then they seem perfectly natural.

This goes to show how different we all can be... are...
 
I find combining the two (midi and audio) to be a bit confusing or misleading. We all see things in our own way.
 
Comparing it to a mixing desk is exactly my point... Mixing Desks mix audio, not MIDI... I don't display any MIDI tracks when I open Console View... Same reasoning.  In hardware, I would only have the output(s) of the synth... Not the MIDI...
 
So Cakewalk does it's best to give us each/both what we want... and continue to improve it tho individually we don't all agree as to which improvements are good... Only time shows that and The Bakers are fast to change things if time shows them to need it...
 
So, though I'll never use it, I hope Cakewalk finds a way to give you the Instrument track you want while not using too many programmer hours as I think there are more serious ( ;-)) areas that need work too!
 
They are commonplace and Sonar does have them and each company;s versions have/don't have various features.... Nobody yet does everything and in every way....
 
;-)
 
Keni
 

sharke
Can someone please explain to me, the logic behind removing the phase and interleave buttons from simple instrument tracks? 

 
I had a phase problem recently and was scratching my head as to where the buttons went.
Ended up using the Cakewalk Channel Tool plug-in to fix it.