Take Lanes suck. End of story.

do you need a hug?

I like take lanes a lot.  A great improvement over layers, for me.
 
I think they need some tweaking, which I hope we will see over the next few updates, but I like where they're going.
 
Sorry you're not having the same experience.

Then don't use thenm

BlixYZ


 
using the mute and isolate tool to comp different takes is amazing!

I'm with you, there, BlixYZ.
 
 

dubdisciple

Then don't use thenm

If everyone took that attitude toward things that didn't work in Sonar, nobody would use it.

Snap To Grid is buggy, ok ... don't use it.


Selection Is buggy, ok ... don't use it.


Take Lanes are buggy, ok ... don't use it.


Pro Channel is buggy, ok ... don't use it.


Track Meters are buggy, ok ... don't use it.


Inserting Synth is buggy, ok ... don't use them.


LOL

dubdisciple, i gotta change my avatar 8/

Blix..even more odd than us having the same avatar, i grew up 10 minutes from your location. I'm blue devil!

JERSEY!!!!!!!!!!!!!!!!!!!!!!!!!!!!
or were you PA dub?

BlixYZ


also, is it possible to use take lanes to record multiple takes of GROUPS like say 7 tracks of recorded drums?  where you can edit and comp them all as one track?

Go to Preferences--->Project----->Record and turn on "Group clips across tracks". Now when you record all the clips will be "clip grouped" and editing one will edit them all (including in take lanes).

Takes can be removed from clip groups by right clicking on the clip and selecting that option. Clip groups can also be created after the event using the same right click method with all the clips selected.

Believe it or not, my BIGGEST problem with Lanes isn't that cut/paste is unforgiving, Mutes are relatively unpredictable, you can't see JUST the Lane you want (solo'd) when the Lanes are collapsed as Jlien asks about, but I seriously get lost in them! It's so incredibly messy how they're laid out, even if logical. They just add more clutter, rather than make it easier on your eyes and your project orientation. It's VERY easy to confuse a Lane for a track on a larger monitor. Worse, if you leave Lanes expanded, then shrink the track to minimal height, the track prior to the one with Lanes showing might be mistaken for the track your Lanes are actually on. 

They're just "Greasy" to me. I still feel they were "slapped" on to X2 rather than really worked during Beta. 
Let me add something here about Beta testing that I'll bet even Beta testers aren't always trying: "Stress" testing. Double-meaning. How many Beta testers routinely try out new features or new releases with a stop-watch? For example, Create 5 tracks with 3 Lanes each, label them, take Track 5 and move it to Track 2 and re-label it to Snare Drum, arm all tracks to record. Record three takes of each. Then take three snare hits and move them from one Lane to another.

This is the kind of Professional Beta testing I was trained years for. This is where you discover what features REALLY work well and which ones simply get in the way. I doubt many developer-type companies do these types of trials. 

Lanes have advantages over Layers, but I personally found Layers easier to deal with when navigating through a Project. Maybe during tracking Lanes are great, but I'd prefer Layers to Lanes for mixing/editing for sure. I used a lot less profanity with Layers.

brconflict


Lanes have advantages over Layers, but I personally found Layers easier to deal with when navigating through a Project. Maybe during tracking Lanes are great, but I'd prefer Layers to Lanes for mixing/editing for sure. I used a lot less profanity with Layers.

The few "advantages" Lanes have over Layers are far less important to me than the "advantages" Layers had over Lanes....

I used to use Layers all the time and got miffed occasionally due to bugs.... Now with Lanes, I'm always miffed due to design limitations/issues as well as bugs!

The zoom and screen space issues are by far the most discouraging for me... The other little bugs I am uncomfortable with but could tolerate.... if..................

Keni

Beepster, the only thing that makes me think Cakewalk intended Layers to be relatively complete is the absence of an option to use either Layers or Lanes. I don't see that the cose for Layers couldn't have been left in, and just add the Lanes code. If you choose (either in the install or Preferences) to use Lanes or Layers, then that code can either be shelved for your installation, especially if the code is modular. 

I can only speculate the architecture, but judging by the track record of Cakewalk with Sonar, one would say that Lanes are new, and not refined yet. 

As I stated in another thread, I don't want X1b until it's really ready, but I sincerely hope that all of the gripes on this board and in the field are at least evaluated, not just an internal agenda from a closed off team from the outside user community, coupled with a handful of obscure bugs most users are likely never to see as was the nominal case with X1 iterations, IMO.

brconflict

As I stated in another thread, I don't want X1b until it's really ready, but I sincerely hope that all of the gripes on this board and in the field are at least evaluated ...

I've been using Cakewalk software for 2 decades and what you are wishing for has never been the case. I've never seen a version of Sonar where an initial release or a 'patch' was "really ready".


You need to lower your expectations if you are going to stick with Sonar. It's always been the Modus Operandi to 'Release new version', 'Kind of patch', 'Drop', 'Release new version', 'Kind of patch', 'Drop' .... and loop.


I think they are getting closer to the core of it being as stable as it can be for the age of the code ... but the new stuff seems to be taking a step back in the ol' stability department. But that's the way it's always been ... so ...


I don't want to see you ditch Sonar. I think it's as functional, if not more, than it's ever been. What I would suggest you take in to consideration is, do you want to stick with these new workflow changes like Take Lanes and wait for them to get fixed ... or go back to 8.5.3? Keep in mind, Layers didn't work bug free either ... so ... we can't really complain all that much about Take Lanes being buggy, we just have to make a decision of which one we like better and which one we can tolerate more, I guess.

Beepster


This might be a long shot but it's possible they left them kind of half finished on purpose to see how us end users reacted. Like what worked and what direction the bulk of users want to see them head to. Yanno, instead of putting all the extra work of programming in a bunch of stuff that just ends up flopping then having to start from scratch. The Bakers certainly aren't dumb guys and it does seem they pay attention to what gets said here and submitted as feature requests. Maybe they couldn't reach a consensus on certain things and decided to leave it up to us. We'll probably see these things get a lot better in the future. It'd be nice if those improvements came by way of a patch instead of a full upgrade though but that doesn't seem likely. 

But as I said many times and I'm sure folks are getting tired of hearing it I really do like them. They've made my production life a whole lot easier.

Alright... I'll leave now. ;-)

Hear, Hear! ;-)

I would love this to be the case as I'm reasonably certain they would then find some way to appease both or our mindsets as there seem to be as many voices on each side of this line... (Or so I hope? ;-))

Keni