Not blaming anyone for blaming the user, except Cakewalk that has a tendency to mark usability defects as "as intended". Given the PITA that is the external defect reporting system, it makes the hassle of reporting bugs in general really not worth it.
 
I'll try to repro the CTRL+A thing again this weekend. Maybe I missed something.

Yevster, I'm curious...  in the video you posted it looks like a region going back along the timeline is being selected when you dragged up to the top of that first clip, but the clips on the left (in that earlier region) still have their non-selected color.   Are you saying that if you were to move at that exact moment, those clips on the left would move as well?
 

Yep. I should have added it to the video. I'll take another one when I get a chance.

OK, then that is really weird!    I can't say I've come across non-selected clips (at least based on selection color) moving or otherwise being modified.
 

I often lasso select clips, and some of them don't looks selected, but when I move them, the ones that don't look selected do indeed still move.
 
This is definitely annoying and buggy.
 
Lance

I wonder what's different that causes some systems to have this symptom and others to not.   Odd.
 

FastBikerBoy

ston
For the second issue, very often if you lasso-select a bunch of clips, or clips and folders, which include one or more on the very top 'row' (i.e. the uppermost track) then the selection marker in the time ruler will extend all the way back to measure 1:0:0
 
It's a really annoying 'feature' of the application that it does this.  Makes selection a PITA.  Cakewalk need to fix this issue IMO.
 
I bet you 50p that it you only lasso select clips up to 'row 2' then CTRL-select the final 'row 1' clips, this won't happen. 
 

 
I can see the time range being selected beyond the lasso range, I can think of several reasons for that but the clips within that range aren't being selected which was the OP's complaint (I think)
 

 
hey karl, 
i'm not sure i can think of any of the reasons that would happen.  can you give me an example or two?

When I say several I probably mean two.
 
MIDI notes included of any great length, previously selected material elsewhere. Point is though the earlier clips aren't being selected (as far as I can see). It's very difficult to see exactly what is happening in what I'm assuming is a GIF.
 
TBH I think I'm more concerned by the fact that the very top clip doesn't appear to be selected despite being touched by the lasso.

> I'll have to give it a try this evening... :-)
 
Well, I did do that.  I created 3x MIDI tracks each with some clips containing MIDI notes and some with automation data.  I set one to 'Clips', one to 'Notes' and the third to 'Automation'.  Using CTRL-A I was able to select and move everything.
 

I've had the CTRL A thing yevster describes (in X3 too). I agree that it makes no sense. "Select All" really should mean "everything", clips and automation. It obeying the filter for lasso select makes sense, I think, but an ambiguous "Select Some" keystroke is a pretty odd thing.