@Jlien... Sadly there is no Hide Lanes feature and I personally think that is a major design oversight. As far as the copy/paste bindings I'm not sure what's up with that but it's probably a bug. They definitely need some refinement but I still like them much better than layers.

And when they first came out I said there should be a way to easily choose which lanes appear on top in the parent track. Something like when you click a lane to bring it in focus it pops into the parent track for editing and stays there when you collapse them or the old Nuendo way of right clicking and selecting from a take list which one is on the surface. What would be ideal though is having a rearrangeable take list where you can layer the takes in whatever order you want by dragging their position on the list while also being able to hide unneeded lanes in the same list. There are many times I'd rather do my editing in the parent track.

I haven't played around with it but I think by dragging take lanes up to the top of the open lanes section it will make that take be on top in the parent track but I'm not sure. That still isn't exactly ideal though because you still have all the other takes below it making editing in the parent track tricky if not outright impossible without locking the other takes.

Meh... I should type up a feature request at some point. 

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


Have I said this before?  GRRRRRRRR!!!!!!

I'm with you... I have had nothing but problems grief and frustration with them.... Yes, I know I can avoid using them but I'm so accustomed to using layers that it's the closest thing.... and I'm very "unhappy" about it...

Not going anywhere? They better "go" somewhere as they're a blight on the credibility of Sonar... I know some people will rise up and tell me how great Lanes are and how they have a wonderful future...

From my point of view they're a horror...

Maybe with some major fixes, additions, changes and re-thinking they might turn into something but as they are they're 10 steps behind Layers (which needed work)...

So.... Please don't tell me it's "time to move on" as I think it's time for The Bakers to move on fixing them! I've been a loyal user since the company started and I've seen many changes come.... and go! This would not be the first walk down a wrong or troubled path....

Keni

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

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. ;-)

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.

I think if you have features that you want added to lanes submit a feature request. You can list the features you want here too. You may get others to support the features and submit their own requests.

That way you don't have to worry about CW being "closed off". 

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.

Bub

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.

Bub, you are speaking reality. I don't disagree with any of that. The price of Sonar is quite good considering what it does right, and how much research over the years has gone into the software. It's not something just whipped up, for sure. No, I realize the truth about all this, which is why I don't just think I would jump to another DAW. I don't really feel like I should have to spend learning curve time to pick another, but I would pay more money for Sonar if it would get more attention to these faults or issues.

But why would Sonar give so much attention to something like their plug-ins vs. Lanes? Why pour so much time, money, and resources into something 3rd-parties already do very well than to spend that time and money ensuring Layers were bullet-proof and usable, which is more in Cakewalk's own territory (i.e. master the basics first)? Marketing, truly. NAMM. 

But, as a result I don't use Cakewalk plug-ins because if other issues with the DAW are any indication of how thorough Cakewalk was developing the plug-ins, then I certainly have no faith in their plugins vs. the 3rd-party plug-ins I already use. So, no win/win between me and Cakewalk. I'm only one opinion, though. Just one.

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