Understood Noel (not sure who is was directed to but doesn't matter). Related or not related those links I supplied, there are subtle points around them. I think in some ways functionality may need to be taken away to stop people using them away from the intended design, or maybe some functionality needs to be introduced to babyspoon the user, anyway I digress it's in all in those threads.... I would say there is a lot of traffic about this...
 
Thanks..

Noel Borthwick [Cakewalk]
I suspect there is a misunderstanding of how the clips view displays data in X3 and the clips view editing paradigm rather than a bug.
 
X2 and earlier had a very simplistic representation of overlapping clips. Overlapping clips were drawing in order of creation or something like that *not* respecting whether they were audible or not. This made editing very non-intuitive.
In X3 we changed the drawing and editing tools to respect a WYSIWYH paradigm (what you see is what you hear). If you have a ton of overlapping clips but only one clip is audible, SONAR will favor displaying the audible clip. By far this is a far superior representation of the clips view because you are editing what is audible. Any non audible clips will NOT be drawing if they overlap with audible clips. i.e. there is a notion of "audible depth".
If you want to edit a muted clip that is obscured by an audible clip, the proper workflow is to open take lanes and edit them there. There is no other efficient way to edit overlapping data on a single track - its a paradigm that most other DAW's don't even allow.
You could move the clip that obscures the muted clip but that defeats the whole purpose IMO.
 
Hope this clarifies this somewhat...

Thanks Noel, if that was for me, my issue started in X3 and the behavior on my referenced bundle file changed after X3D. The root of this issue was working with Melodyne and how SONAR processed muted clips and in what order they were present in the take lanes. TS confirmed it was a bug, but I never got an SBM ticket number.
 
I PM'd Keith with the location of my project file and what I am seeing. This was not the workflow behavior I seen in X3C. I understand that we are supposed to be working on clips in the lanes now, but still, we should be able to select the clips in the audio track view and I am not able to with my posted project that DID work as expected in X3C.

I havent seen your project but are the clips you are trying to select in the clips view actually visible? If there is an audible clip on top of it you will *not* be able to select it because of the reasons specified above. 
Anyway Keith will look at your project when he gets a chance. Many people are out for the holidays so there could be a delayed response.

Thanks for the reply Noel, there are no clips on top of one another that I see. I am reporting that I was able to select these same clips from the audio track view in X3C and am NOT able to in X3D.
 
Again, a new project in X3D does not exhibit this behavior and this project file was created and saved in X3.
 
 No problem. I appreciate the look see.