Clicking name of track - it's selected in Inspector, but not selected
Most parts in track header do it like this - part for track number, then track is selected.
 
I don't remember having this difference in other daws.
 
I remember having real difficulties getting 10 years ago starting with Sonar 4, when exporting a mix and get all in there that I expect.
 
And still a bit confused by this approach - smart tools does not work like I want to clicking on clips they are not selected always.
 
There are options whether to arm tracks for recording by selecting them - but are there any settins to choose how this works active/selected etc?
I certainly would like a different approach than default. I put a screaming red background color on track number to really see selected tracks easily.
 
Are you happy with this way of operating selections?
Clicking on name in console view track is shown in inspector, but not selected as such - confuses me.
Most operations, deleting tracks and stuff depend on selection and often give me unexpected result.
 
I got an excellent help the other day to alter how Sonar handles Solo/Mute in Aud.ini and now works exactly like I find intuitive.
Something like that for selections, maybe?
 
Thanks.

lfm
Clicking name of track - it's selected in Inspector, but not selected
Most parts in track header do it like this - part for track number, then track is selected.

 
The way I understand it ...
I activate a track from the control surface and channel strip, ProCh, etc. get the focus for editing ...
I select tracks by mouse (for export, cloning, etc.) ... but my control surface stays focused on what i had selected ...
 
One (action) shouldn't necessarily change the other (selection) ... and selections don't need to be the same ...
 
 

lfm
I got an excellent help the other day to alter how Sonar handles Solo/Mute in Aud.ini and now works exactly like I find intuitive.

I think I missed that ... what was it about?

FreeFlyBertl
 

lfm
I got an excellent help the other day to alter how Sonar handles Solo/Mute in Aud.ini and now works exactly like I find intuitive.

I think I missed that ... what was it about?

Scook gave me the resolving solution of getting all about a track - audio and sends - to follow the mute principles - this whether pre/post fader sends.
 
Variable is visible in prefs "LinkPFSendMute"
 
On Topic: For me I would like clicking anywhere on a track header, or a clip header to select that track. This both in TV and CV. Don't remember doing such a separation in any other daw.
 
Maybe LinkTrackActivationAndSelection=1 or something.
 
Time selections are bit different - you may want a loop range to remain selected while you select partial of a clip etc.

I also don't appreciate the behavior in Sonar to be honest. The below is a quote from my own thread I posted about a year ago.
 
-----
 

 
As the screenshot indicates, a "focused track" and a "selected track" are two different things in Sonar. This is quite inconvenient because, for example, if you hit Alt+3 wanting to display only the "selected" tracks in the PRV, it also displays the "focused" track, which you don’t want displayed. Similarly, when you want to solo the "focused" track by hitting Alt+S (this is "Solo All Selected Tracks" and I have to use this because there's no shortcut key to solo the "focused" track), it solos the "selected" track(s) as well. You could easily edit/delete clips on another track accidentally/unintentionally because of the current behavior. I hope there’ll be an option to change it.
 

The first post in this thread also explains what I'm trying to say...
http://forum.cakewalk.com/Is-this-behavior-changeable-m2937905.aspx
 

As I understand it. Prior to X2a, There was a workflow issue where you could be working say on the bass in the prochannel and you desired to mute the kick, so you mouse over to the track view or the console view and click the kick track's mute. BOOM!, your prochannel now is the kick track's prochannel just because you clicked a control on the kick track. No longer does Sonar select or focus a track upon control change for that reason.
 
Onward and upward............
 
 
 
 
 
 

I agree with those who find the separation of focus and selection confusing, but I also agree with those who recognize why this is useful.

Thanks to Icontakt for always good illustrations as well as good input.
 

bitman
As I understand it. Prior to X2a, There was a workflow issue where you could be working say on the bass in the prochannel and you desired to mute the kick, so you mouse over to the track view or the console view and click the kick track's mute. BOOM!, your prochannel now is the kick track's prochannel just because you clicked a control on the kick track. No longer does Sonar select or focus a track upon control change for that reason.
 
Onward and upward............

What you mentioned are probably things that influenced this behavior.
 
But making this by choice in preferences would not hurt.
Buttons like mute/solo are not always what you want to select a track as well.
 
So thinking of like an integer in settings used as flags for parts that you want linked.
Bit0=0/1 ; track header panel linked or not
Bit1=0/1 ; mute button
Bit2=0/1 ; solo button
Bit3=0/1 ; track name field
Beit4=0/1 ; Track header(what is seen as minimized state)
 
or similar approach.
 
If bit is set, Sonar also see to that track becomes selected.
 
Using a global variable in software for such operations handling mouse events is really easy to do.
So if setting is a bit hacker level, as a first step, does not matter.
In time one can make preference dialog extended etc.
 
We have some now for mouse, whether to move now time by clicking here and there etc.
Rightclick do this, double click do that....
 
Maybe separate option bit for right click, left click, etc...
 
In general in AUD.ini or for mouse operations what quite often got it's own preferences page.
Example 1
You want everything as it is today.
LinkActivationAndSelectionFlags=0;
 
Example 2
You want clicking everything mentioned above but mute/solo to also select Track.
LinkTrackActivationAndSelectionFlags=0x19 ; binary 11001
 
You have a separate bit for track fader, pan etc.
 
Selection are probably among the most common things you do while working a project. And the more you can customize that - is a huge thing making you feel good about the workflow of your daw.

lfm
Thanks to Icontakt for always good illustrations as well as good input.
 

bitman
As I understand it. Prior to X2a, There was a workflow issue where you could be working say on the bass in the prochannel and you desired to mute the kick, so you mouse over to the track view or the console view and click the kick track's mute. BOOM!, your prochannel now is the kick track's prochannel just because you clicked a control on the kick track. No longer does Sonar select or focus a track upon control change for that reason.
 
Onward and upward............

What you mentioned are probably things that influenced this behavior.
 
But making this by choice in preferences would not hurt.
Buttons like mute/solo are not always what you want to select a track as well.
 
So thinking of like an integer in settings used as flags for parts that you want linked.
Bit0=0/1 ; track header panel linked or not
Bit1=0/1 ; mute button
Bit2=0/1 ; solo button
Bit3=0/1 ; track name field
Beit4=0/1 ; Track header(what is seen as minimized state)
 
or similar approach.
 
If bit is set, Sonar also see to that track becomes selected.
 
Using a global variable in software for such operations handling mouse events is really easy to do.
So if setting is a bit hacker level, as a first step, does not matter.
In time one can make preference dialog extended etc.
 
We have some now for mouse, whether to move now time by clicking here and there etc.
Rightclick do this, double click do that....
 
Maybe separate option bit for right click, left click, etc...
 
In general in AUD.ini or for mouse operations what quite often got it's own preferences page.
Example 1
You want everything as it is today.
LinkActivationAndSelectionFlags=0;
 
Example 2
You want clicking everything mentioned above but mute/solo to also select Track.
LinkTrackActivationAndSelectionFlags=0x19 ; binary 11001
 
You have a separate bit for track fader, pan etc.
 
Selection are probably among the most common things you do while working a project. And the more you can customize that - is a huge thing making you feel good about the workflow of your daw.

Perhaps, but I have no control (thankfully) over these things.
When X2a came out I thought "It's Broke!" because my control surface code was following the old way of doing things where changing a strip widget selected the widget's track inside sonar.
 
With every option in any software's preferences will be a blessing to some, and cause tech support calls and Baker clarification of those things on this board for others.
 
It's a teeter totter balancing act for sure!
 
Happy Friday and Rock On.
 
 

I often click on a track in the track view, but the track in the Inpsector/ProChannel is different.  This has caused me to alter EQ or Sends for the wrong track many times.