brian brock 
Another problem with the implementation of Take Lanes is that the button to open/close the lanes is hidden if the track is minimized.

 
Shift+T toggles lanes, and if you enable Auto-zoom and leave lanes open on a track, they'll open along with the zoom whenever that track has focus.
 

brundlefly

brian brock 
Another problem with the implementation of Take Lanes is that the button to open/close the lanes is hidden if the track is minimized.

 
Shift+T toggles lanes, and if you enable Auto-zoom and leave lanes open on a track, they'll open along with the zoom whenever that track has focus.
 

Thanks brundlefly...
 
I have not enjoyed using the Auto Zoom, but I will try this and see if it makes working with Lanes a little easier...
 
the Shift-T you gave me a while back and I use it constantly...
 
Now if there's a way to open/close multiple tracks' Lanes simultaneously it would help too...
 
I still don't know why... Maybe something I do un-knowing, but every once in a while my screen will suddenly jump and open Lanes on every track forcing a one-by-one closing of each... <sigh>...
 
Hearing a few comments from the Bakers about how happy they are with X3, I'm hopeful that many of these issues have been improved as well as other topics... (This one is just so in-my-face all the time)
 
Keni
 

Keni, don't multiple track lanes open when quick grouped?
 

brian brock
I just can't understand why Cakewalk would throw out a fully developed unique solution.  It was a part of the software which differentiated them from the all-too-homogenous pack of DAW software.  It's not like anyone is going to switch to Sonar from Cubase because Cakewalk tried to imitate Cubase - on the contrary, I believe people are likely to move in the opposite direction.  Cubase's implementation of this is very similar to what Cakewalk tried to do, but it works.  Further, Cubase benefits from having developed their method over time, and that integrity shows when you discover all the interesting things you can do with it.  The old Sonar implementation, layers, offered a similar sense of well-traveled experience and possibility.
 
Another problem with the implementation of Take Lanes is that the button to open/close the lanes is hidden if the track is minimized.  With the old implementation (I'm familiar with 8.3), the button was in the track "header" area, next to the minimize button.  This becomes a bigger problem, because often the track is minimized, but the lanes are not collapsed.  In order to get rid of the lanes taking up space, you have to enlarge the track enough to see the open/close button.  The track header area often has a lot of wasted space in the new Sonar.
 
Clip automation seems really hard to use and having to go to the track area to manipulate clip properties seems counter to good sense.
 

 
I feel I pretty much agree with the basics of what you're saying here... and I'm guessing that the reason they changed from Layers to Lanes had to do with potential... I'm thinking there were things they wanted/needed to add to this function-type and couldn't find a way to solve it with the Layers concept... so they changed to Lanes to accommodate these and are now actively (I hope) cleaning up the issues and making the new paradigm to work better... Even for the Layers-approach die-hards such as I am! ;-)
 
My gut feeling right now...? Hang Tight! (Hang Tuf...?) I (want to) believe a solution is on it's way!
 
Keni
 

stevec
Keni, don't multiple track lanes open when quick grouped?
 

Unless I'm doing something wrong...? No, it doesn't appear to work...
 
 

Every now and then, I get a display anomaly when using Take Lanes.
Usually, this can be resolved by saving the project... and closing/reopening X2.
Not a show stopper... but annoying
 
I'd like to see crossfades implemented with Take Lanes.
Don't like comping without them...
 

Keni

stevec
Keni, don't multiple track lanes open when quick grouped?
 

Unless I'm doing something wrong...? No, it doesn't appear to work...
  

Huh, I could have sworn that worked - ctrl+clicking on the Lanes button of course, not the keyboard shortcut.  
 
Well, here's hoping this will also work in the next big thing.
 

I agree Jim. I like manually managing the cross fade too.
 
The work around I use is to use the mute tool to determine which part of which lane are used. Then Manually split the clips and delete the silence. Then I zoom out and disable the lanes view and use the mute tool on the whole track to un-mute all of the remaining clips and slip edit and fade to taste. Then finally bounce all this to a clip or a track.
 
Of course the more edits there are the longer this takes. Admittedly sometimes I just use the mute tool and then bounce to track if I'm feelin' lazy.
 

I just don't see the point in 'take lanes'. - The previous system worked. - This take lane malarkey has just created problems and hasn't solved any. - If one expands a track all content goes to the associated take lane leaving the track itself completely barren, you then have to reduce the track height manually to gain some screen real estate. Doesn't exactly add to a workflow. 

JenksTer
If one expands a track all content goes to the associated take lane leaving the track itself completely barren, you then have to reduce the track height manually to gain some screen real estate.

Exactly.  This is where efficiency went out the window in the move from layers to lanes.  The biggest area you have to edit in (the track) is empty and the lanes are height restricted - ridiculous!  This one makes me grind my teeth every time.