I'm with Beepster on this one. Looking at that project, I can't for the life of me figure out what the OP was going for there.

1. Why are there so many takes? 27? What is this project that you have so many takes of a single track?
2. Where are the rest of the takes? The beginnings and endings? Were these deleted? Why not use the Ctrl+Mute tool to promote only the sections you need?
3. In this scenario wouldn't auto-punching as needed have worked better?
4. Another option might be to use separate tracks if you know you're going to need this many
5. If I were working with an artist, including myself, that needed that many takes, I'd advise them to spend a week or two practicing, then come back when they were ready

I really think lanes are designed to work in scenarios where you have a few takes (lets say vocals/guitars) and you're trying to comp together the best bits of each. I honestly don't think the Cakewalk folks were thinking of 27 takes, and I don't blame them. 

You have to code to most common scenarios, not the oddball ones. At work we call it the 99 to 1 rule. If 99 people need something done a certain way, but 1 needs something done differently, you code to the 99.

Seems simple to me .... he started out with one take, kept doing takes and deleting or resizing the parts in the take lanes that he didn't want, and ended up with the original part of the take being at the end.

I don't like Take Lanes at all ... so for me ... my workflow has been made a 1,000 times harder because I have to use individual tracks now for every take and piece it together that way without the benefit of rebuilding layers.

Not to mention the bugs. It's one of those features where, when you have a bug, there's no way to turn it off or uninstall it. Like the Pro Channel.

But I'm a hater ... don't listen to me.

Maybe I'm a dolt, but if that OP situation was mine and I wanted all those takes combined into a concise single track I'd just bounce that 'laned' track to another track. And delete the 'laned' track.

Actually that's how I do it.

/POST

But he could accomplish exactly what he wanted to do before with Remove Empty Layers/Rebuild Layers.

And now he can't. Same for me

REBUILD feature also missing here!!!!!!!!

SteveStrummerUK


But he could accomplish exactly what he wanted to do before with Remove Empty Layers/Rebuild Layers.

And now he can't. Same for me

Exactly & in one click.

I'm with Beepster.
 
I far prefer lanes.  Once I took the time to learn how to use them they improved my workflow considerably.

But I'm a hater ... don't listen to me.

Please don't do that, bro. Not with me. 

If they could code layers back in as an alternate option they should but really... lanes are working FAR better here so I'm gonna be selfish and say keep the friggen' lanes. They make sense to me. They work better. I can edit them no matter how many I create. Etc...

That's what I don't get about this thread post. At the amount of layers the OP is talking about I couldn't even get the cursor the select them anymore to do ANYTHING. I make tons of takes so I have a huge pool to select from for the final product. They just did not work for me. Rebuild layers is a great idea but the way it threw stuff all over the place ruined it. It was totally random. I can't work like that. I need order.

SteveStrummerUK


But he could accomplish exactly what he wanted to do before with Remove Empty Layers/Rebuild Layers.

And now he can't. Same for me

BluerecordingStudios


REBUILD feature also missing here!!!!!!!!

carl

SteveStrummerUK


But he could accomplish exactly what he wanted to do before with Remove Empty Layers/Rebuild Layers.

And now he can't. Same for me

Exactly & in one click.

Understood gents.

And everyone who has used layers will have X1 or another earlier version of Sonar at their disposal. If they bothered me THAT much I would just use X1 for my tracking then open the project in X2 for mixing. I just don't get it. 

Ugh... if digging lanes makes me an arsehole then so be it. I like them. Lanes rule. LONG LIVE LANES!!!