Mike McQ loves 'em. It's the main reason he upgraded to X2

 
:-)
 
:-)
 

Tom Riggs


I know that if it happened to me I would be frustrated as well. Again I encourage you to contact Cake with a problem report here http://www.cakewalk.com/Support/ProblemReporter/ The more people that do the higher the problem will get in the development queue.

Already done long ago.

Well, I am usually Mr Positive but I have to say I don't like the take lanes either-I really liked working with the layers.
So much so that I avoid the take lanes- Just don't like them and it's not a matter of gettingh use to them- Layers just always worked great for me-especially for guitars.

Take Lanes.... Yes Take them out of the program!

I agree that it's easier to maintain a program with only a single method to do "anything", but often multiple methods are important to suite situations and the variety of users...

I for one wish Lanes would simply go away and have Layers back... but as I know there are some who like Lanes, the best solution to me is to have both.... Users can then decide which works better for them....

I found layers a unique approach that did a far better job than any other program I've tried... Yes, they had a few bugs and could have used some additional improvements, but replacing them with Lanes has been a nightmare for me...

The Bakers chose to make envelope lanes additional to our earlier automation editing instead of replacing it and Lanes should have been handled the same way...

I cannot stress just how much I don't like Lanes... Even if the bugs they currently have were fixed (zoom issues and clip movement) they would still be very problematic for me by their' nature. there is no way to get large counts of Lanes on screen at any one time...

...and please. I hope people can stop telling me that I shouldn't need that many takes... We don't all have rehearsed bands performing for a simple recording. Many of us use these tools in the writing process itself and the use of many takes is very common for me when I'm doing such...

Please! Everyone post feature requests for Layers... Maybe we can get Cakewalk to feel our need!

Keni

+1

Cian, an evolved-super-singer here, iirc, stated he'd oft have to do 40+ takes.
While *pro-rehearsing* sounds great.  The true art hits my studio via hearty takes and sifting the best samples.

OTOH:
When Brandon performs take lanes for his guitar (in the video) ... it seems pretty deft.  I hope I can adapt to these awkward take lanes.  IIRC, Brandon makes his take-lanes increment sweetly in this live video demo.  http://www.youtube.com/watch?v=xw5z9BKWD-I 

But as a noob to X2, I'm discovering some work-flow issues with both takes and lanes.  Time will tell I guess.

I wonder how much it would cost to comission Cakewalk to build a custom version of Sonar?

Maybe an alteration of the install routine to allow/disallow selected features to be updated/changed?

<sigh>... I've got to do a bunch of comping today... I may try working in X1 if these songs allow me with reasonable ease...

Keni


I wonder how much it would cost to comission Cakewalk to build a custom version of Sonar?

Maybe an alteration of the install routine to allow/disallow selected features to be updated/changed?

<sigh>... I've got to do a bunch of comping today... I may try working in X1 if these songs allow me with reasonable ease...

My sentiments exactly. This is what I'd hoped the Extended or "better" version of X1 was to be. For example, I would pay $700-$800 for a DAW that is:

- Tested for extra stability by at least two outside paid resources, and among beta-testers, who get a little commission for the number of legitimate bugs found, and based on how critical the bug. (Even include a scoring system and a winner! Make it fun!)
- Has the ability to disable/enable specific major functions for efficiency and further reliability.
- Has the ability to "test" your machine for other potential performance issues and report those.
- Has a good syslogging function with levels of debugging, but also has a reporter that can give the user some readable understanding of specific common messages. It could also provide a quickly emailed support dump file in case you need Cakewalk support.
- Allows Cakewalk to be welcomed to your session through a secure SSL channel, that allows support to (with your permission per session) gain access to your DAW, and view a visual copy of your setup, Preferences, and other aspects of what you're doing that causes you grief. 
- Has a better metering for building a master. 
- Has a more flexible GUI, so that you can expand the faders to 100mm, for example. 

I'm sure I could come up with more, but I'd pay more for an Enterprise version, top priority being better stability and bug-squashing. 

Okay... this is getting silly. I'd like to say to any Bakers reading this and possibly considering reverting back to layers I for one found layers to be completely useless after a certain point and a pain in the arse in general. Aside from the quirks and bugs Lanes currently have I don't see how they are causing such confusion and frustration. The comments about layers being easier for dealing with a large amount of takes is completely contradictory to my experience. With every take past a certain point they continued to get smaller and smaller because you could not expand the track beyond the height of the screen which eventually made try to edit them impossible. You also couldn't see ANY of the other tracks because if you scrolled the track with the open layers disappeared. The rebuild function was ridiculous in its randomness. There was no way to make detailed notes making it so every take had to be listened to or you had to make hand written notes. For those notes you would have had to write down the specific clip numbers and couldn't just visually see what was what. The mute and solo buttons were buggy and again would become useless after too many takes. It was just a very bad system.

That is not meant to be offensive to anyone but I think the voices of those who are MUCH happier with the new system should be heard as well. Takes do need some work and I get that it's a major adjustment for some folks but this talk of eliminating them completely would totally screw guys like me who view them as a godsend. Having the option to choose one or the other is a nice idea however I see that causing code conflicts and introducing new bugs which we already have far too many of. I gotta wonder... how hard have you guys looked into how they work? There are specific new procedures needed to working with Lanes. Is it a pain to learn when you already have a workflow based on layers going? Sure but man... as someone who has spent equal time using both (as a relative newcomer) Lanes SMOKE layers as far as ease of use and organization.

Again I do not mean any offense but if I lose the functionality of Lanes because of all of this I'm gonna be a very angry Beepster. My workflow has sped up ten fold with Lanes... that is the god's honest truth. I do not want to go back to the way things were.

Cheers.

Genghis


.... everything I do with take lanes takes longer than doing it with the track layers did.

^^^^^^^^^^^
This, in a nutshell.

If anyone is having workflow problems with Lanes let me know. Maybe I can help provide some workarounds. I can't do anything about the bugs obviously but maybe I can help make certain things a little easier. I do TONS of takes so I mess with lanes pretty extensively.

Cheers.