And MIDI, doods... help out kylo if you can. I'm out of ideas.
 

I can see that the small clips have dotted outlines indicating they are linked, but the one you're locking does not. I am able to replicate this by unlinking a clip from the linked copies, and then locking data on the unlinked clip. Bounce to clip(s) on the unlinked clip fixed it, but it does appear there's a problem with unlinking. I have a vague memory that this has come up before. As far as I can tell, it's only data-locking linkage that's not being broken. Position locking and edits to the unlinked clip are not affecting the others.
 
 

It's a good theory, but in some cases the 2 clips have never been linked together at all. They were produced by dragging from the same plugin but that's as far as it goes.

I've had trouble with clip management ever since comping was introduced. I've seen the issues the OP has with locks toggling in clips and the weirdness of clips acting locked when they are not. I also don't use comping or take lanes but according to Beepster's post, we are all using take lanes even if we don't want to. It bothers me enough that I've given up using midi patterns or step sequencer to assemble midi drum tracks. Clips have developed a mind of their own.

ampfixer
I've had trouble with clip management ever since comping was introduced. I've seen the issues the OP has with locks toggling in clips and the weirdness of clips acting locked when they are not. I also don't use comping or take lanes but according to Beepster's post, we are all using take lanes even if we don't want to. It bothers me enough that I've given up using midi patterns or step sequencer to assemble midi drum tracks. Clips have developed a mind of their own.

Kind of yes and kind of no.
 
To me it's a culmination of...
 
a) the Smart Tool... which is ultra crammed and insanely context/area sensitive with seemingly endless and ever changing tools. So much so it itself seems to get confused as to which form it should be taking on at any given point in time. Without knowing exactly what the tooltip should look like, what it should be doing and where it should be doing it it's almost impossible to use. I've kind of got the hang of it all but still often times I revert to the older, more dedicated single purpose tools just to cut through the logistical nightmare (and sometimes outright refusal of the ST to switch to what I what).
 
b) the way comping has drastically altered the old school way of doing things. Comping is the new way and although the old workflows CAN be acheived you still have to really know comping through and through to completely revert back to those old school methods.
 
All in all, to me, after learning how it all works I do think it's a great workflow but once X3 came out (the first with the fully implemented comping features) it seriously disrupted my editing until I did actually sit down for a half hour to specifically figure out WTF was going on.
 
Now I fly with it but I also have to keep all this stuff in mind from the time I hit record until I flatten my comps (and in many cases drag the comps into a clean track).
 
The absolute BEST thing to do for those not used to it is crack open lanes right from the start of tracking to watch them get inserted into the lanes and keep them open (or crack them open again) for editing... and edit in the lanes.
 
There are some extremely helpful vids in the CakeTV area that explain (mostly) what's going on with comping.
 
Aside from that... yeah, we're kind of fuxxored for just straight old school track editing. All that is a massive conceptual nightmare in all DAWs since layered style tracking has been introduced anyway though. Always something weird is gonna happen or have to be forced. Seems Cake have just said "f*ck it... it's gotta be done in lanes".
 
I am (mostly) okay with that and have my little workflows to enable old school track editing.
 
I DO most definitely want to be able to archive and hide lanes though. That would make things an arseload easier.
 
Cheers.

The thing is... layers worked just fine. You could comp with them, and you could use them as, well, layers. They also work okay in the few other DAWs I've used. But, with Sonar, there seems to have been some sort of change of focus a couple of years back that assumed that the only reason you'd have overlapping clips is if you were comping a bunch of takes, and now things no longer work well if you're not comping.
 
However, much of that is arguably beside the point - some of the functionality is clearly broken for reasons that don't seem to relate to workflow.

Kylotan
It's a good theory, but in some cases the 2 clips have never been linked together at all. They were produced by dragging from the same plugin but that's as far as it goes.

No offense, but frankly it makes more sense to conclude that you're mistaken about how the project got to this state than that a bug managed to do something as complex as linking the properties of two instances of an object imported from outside SONAR's project space as separate actions.
 
There's a bug alright, but I think it's your typical "dumb bug of omission", not some super-smart bug intent on locking all your data against your will. Bwahahahahaha! Your base are belong to us.

Subjective really. Layers looked cool when I first got my hands on them in X1 (after switching from another DAW) but immediately turned into a massive liability once I actually started doing serious tracking. Take Lanes were a huge improvement (to my workflow).
 
In my old DAW there were no layers or lanes. The clips just stacked up in the background and you had to right click the track to bring up the clip you want to be heard. You could overlap and X-Fade two clips in the list but you could not see anything except the main track.
 
I did like that right click/list system but not being able to see all the clips at once was a "problem". Of course I had no idea it was a "problem" until I had access to a layering/lane system.
 
So as I said... subjective.
 
Based on the forum comments most people, once they get used to the new system, seem to like it (not all) but it certainly does cause a lot of shock and confusion in the interim. Especially for those who've been using the program for a long time.
 
I like it in general but I learned starting with X1 and only did basic DAW stuff before that (so I'm an infant in the grand scheme). I had very few old habits to break.
 
It is more flexible and allows for more speed in general AFAICT but it's most definitely different and an acquired taste/skill. It's still getting some of the kinks worked out too so that's an extra monkey wrench for those used to the old ways/just learning it.
 
Flattening/Bouncing then getting rid of everything else in the lanes seriously is the best way to go once you have a good set of final takes going IME. I do a save as labelled Clean Up or even import everything into a new project to work unhindered.
 
Meh... you just gotta learn it to see if you like/hate it or somewhere in between. Not learning it though is going to guarantee a bad experience... which is what I went through until I gave myself a crash course.
 
Cheers.

The video in post #27 clearly shows that it's a bug (I can only reproduce Dave's case just after the clip is unlinked from the group, with the clip still being highlighted). I suggest you contact tech support attaching the project file. That's the only way CW can fix the bug (except for redesigning of the feature).
 
As for the selection issue in post #1, I can't tell until you post a video in which you zoom in horizontally (by keeping hitting Ctrl + right arrow, for example, until you can no longer zoom) at the start of measure 331. Clip Properties Inspector doesn't always show correct information.

brundlefly

Kylotan
It's a good theory, but in some cases the 2 clips have never been linked together at all. They were produced by dragging from the same plugin but that's as far as it goes.

No offense, but frankly it makes more sense to conclude that you're mistaken about how the project got to this state than that a bug managed to do something as complex as linking the properties of two instances of an object imported from outside SONAR's project space as separate actions.
 
There's a bug alright, but I think it's your typical "dumb bug of omission", not some super-smart bug intent on locking all your data against your will. Bwahahahahaha! Your base are belong to us.

No offense taken, but you're wrong. Those clips were never linked.
 
In my 3rd gif on this thread it is toggling the locked status on literally every linked clip in the song (as far as I can see). The first 4, on the left, are ones I edited myself, which may have started from a copy of another clip. The next 2 are dragged in from EZPlayer, from a commercial MIDI library. And the last 6 on the right are ones I created myself from a blank slate. There is no way that the 2 commercial MIDI library clips and the 6 I wrote myself were ever part of the same clip, unless Sonar is magically doing that in the background, invisibly.
 
The way I see it, if it is plausible that 'linkedness' can somehow persist beyond a simple yes/no value that is used to decide whether to render that padlock or not, then it is plausible that linkedness can somehow end up on 2 clips that were never manually linked in the first place.
 
Either way, it's an annoying bug and it's wasted a lot of my time lately.