I am one of the many who have expressed frustration with take lanes, specifically with editing audio.  In the spirit of "a picture (or video) is worth a thousand words" I decided to post some clips that demonstrate some of the issues I am having.  This is done in the spirit of trying to improve what is a generally good product.  I hope that for each issue either 1) someone can point out a user error on my part, 2) others can jump in with "the same thing happens to me!", and 3) if a true bug or poor design is confirmed, CW will be able to use the video to help identify and fix the problem.  
 
So for #1.  Earlier versions of X3 had major problems when dragging clips around within take lanes.  X3c and now d are better, but problems still pop up.  These appear to happen when either there are lots of takes or I delete some take lanes as part of my editing (perhaps both, hard to tell as for my workflow the two situations typically go together).  See the linked video below.  As I drag a clip from one take lane to another, the other takes in the same time period disappear, or are slip edited down to  a tiny sliver.  This is repeatable in the sense that if it happens once, I can repeat it for the same clip over and over.  But, it does not happen for every clip.
 
http://nomadrecordingstudio.com/Sonar/Lanes%20drag%20error.MOV
 
Anyone else seeing this?
 
Cheers,
 
David
 
PS more to follow this weekend.

Take lanes are confusing to me. I think the idea is that audio remains on own lane, and you use the smart tool to cut the takes up so you can slip edit them, and activate the parts you want in your final track, but they on their own lane.
For me, the take lanes do not expand tall enough. But it could be that I don't fully understand them yet.
 
All the best with it all,
 
Lee.

leebut
Take lanes are confusing to me. I think the idea is that audio remains on own lane, and you use the smart tool to cut the takes up so you can slip edit them, and activate the parts you want in your final track, but they on their own lane.
For me, the take lanes do not expand tall enough. But it could be that I don't fully understand them yet.
 
All the best with it all,
 
Lee.

Yup we are in the same boat...

Best way to understand take lanes in X3: buy Groove3's Sonar X3 Explained. It's $15 right now and it explains the new concepts very well.
 
But as a prerequisite, I highly recommend this: forget everything you know about editing using layers. That knowledge won't help you when it comes to take lanes.

> Best way to understand take lanes in X3: buy Groove3's Sonar X3 Explained. It's $15 right now and it explains the new concepts very well.
 
Agreed, I only just recently went through them again...

No argument with anything written, but regarding the specific issue I noted in my OP can anyone confirm or show me how this is user error. This is seemingly a simple drag and drop move to clean up takes that appears to be buggy.

By dragging and dropping clips from lane to lane, you are treating lanes as tracks. In your mind, you are thinking of lanes as being tracks. Lanes are not tracks. A track is the sum of several lanes. I see this mode of thinking that is causing confusion.

I can totally understand why people would get the idea to think of lanes as tracks. Perhaps Cakewalk could make a point to bring thus to light in an upcoming blog or new training video.

Sylvan
By dragging and dropping clips from lane to lane, you are treating lanes as tracks. In your mind, you are thinking of lanes as being tracks. Lanes are not tracks. A track is the sum of several lanes. I see this mode of thinking that is causing confusion.

So what is the function of dragging and dropping clips from lane to lane? Should it be prevented?

Things like right-clicking on the Track and choosing "Remove Muted Takes" and/or "Flatten Comp" take the need to drag and drop clips from lane to lane.

The purpose of choosing certain takes is to build a track, a final track from the sum of several takes. Dragging clips from track to track makes sense, but from lane to lane seems odd since the "Track" is still the track. I hope I am making sense to someone other than myself. But I totally see it this way and in so doing I see the reasoning in the way Take Lanes are implemented.