Yup thread has come to it's natural end, I think points have been made. Hopefully Cake can chirp in somehow (I suspect they may avoid discussion until X3D however which would be understandable).

CakeAlexS
> I will reserve further ranting until after X3d is released... Exactly, it will be quite refreshing to have something new to b*tch about next week, fingers crossed...

Wouldn't it be nice...

A version with only minor bugs and issues?

That would truly be a Happy Holiday for all!

;-)

Keni

lawp
summarising these kind of threads is a great idea

1. midi take lanes are royally screwed up
2. audio take lanes are really good, but can be better
3. some of this should be fixed next week
 
hows that? :)
 
To all, (other than Cakealex who i know has filled out his bug report).. i do sincerely trust that each and every issue that you discussed here has been reported as a bug through the CWBRN system, or requested as a feature request... after all, CW cannot fix a bug that they don't know about.
 
..and no, saying that you posted in the forum doesnt count. :)

Anderton
Question...I'm having a hard time digesting all the information here. Is the following summary of the opinions here correct: 1. Take Lanes are most problematic with MIDI tracks, less so with audio.2. Some people have issues with Take Lane cosmetics (e.g., not sufficient variation in track heights)3. For those using Take Lanes to do traditional-style comping (e.g., lead vocal, guitar part, etc.) it works fine.4. For those using Take Lanes to do comping of multi-tracked sources (e.g., acoustic drum part with multiple mics, there are issues. Is this correct? I've been using Take Lanes in the context of (3) and find the speed comping to be incredibly useful, but I haven't really worked with MIDI comping yet.

Hi Craig...

Well... That's a bit simplified, but close...

MIDI tracks has bugs more than feature issues I'm told. I am very happy with sound on sound for MIDI tracks the way I work...

Zooming? A major issue for the kind of editing I often do... Big problem for me there...

Take Lanes are NOT good for my traditioan comping as you mention above... I see how the system wants me to work, but it just don't cut it for my needs... If it was simply a different way to do the same job that would be one thing, but it's not... The end result may be the same but what an engineer/producer needs to do is very situational as well as personal...

Little issues which bug me and entice me are a different matter too as I find many of these tools can be good for a particular time and place but not for a standard/default... Even something as simple as an on/off button for the set of comping tools would quickly solve that... But I run into extra work because my needs don't always allow me to evenly splice areas and the ability to select/solo a take/clip is sometimes handy and sometimes unsatisfactory as it starts to play from where I click to select and can't start playback before the material I want to listen to as it's the beginning of a clip... So I clumsily select the clip than I must relocatee using the mouse at screen top to hear from the clip's beginning....

<dmn> I didn't want to go thru this stuff again... Sorry... I'm gonna stop here tho the issues are far deeper... Suffice it to say that so far lanes don't even come up to layers for me let alone improve on them...

Keni

Mystic38

lawp
summarising these kind of threads is a great idea

1. midi take lanes are royally screwed up2. audio take lanes are really good, but can be better3. some of this should be fixed next week hows that? :) To all, (other than Cakealex who i know has filled out his bug report).. i do sincerely trust that each and every issue that you discussed here has been reported as a bug through the CWBRN system, or requested as a feature request... after all, CW cannot fix a bug that they don't know about. ..and no, saying that you posted in the forum doesnt count. :)

I have many bug reports filed as well as feature requests and the wide array of topics here spans a broad range...

I do and have always tried to make responsible reports whether I did well at it or not...

The Cakewalk team has always been good at giving solutions and a little more as they've been trying to do with their' software since the beginning. Even tho I don't like all their decisions I know they work very hard to give us the best they can... I hope they know that I believe that even with all my issues... ;-)

I was never at such odds with them until X and with some massaging, I can now live with most of that very comfortably... Then they threw lanes at us which for some it's a total pleasure and others a total nightmare... I get my work done anyway, but it takes 3 times a long as I must work around even the work arounds sometimes... ;-)

I must say that there have been many wonderful things in X and these to continue to increase as well...

So, all kidding and complaining aside, I hope X3d is a great step forward and brings us all a Happy Holiday plus!

Keni

i asked for these things back in x2 and still nothing...
 
being able to choose which take is the 'priority' take when you collapse... i mean, how could they not have seen that in a beta test... 

There were a lot of issues with X2. Please remember X2 was under Roland, now X3 is under Gibson.  There seems to be a big change in management structure (in a good way) and it appears there is no going back. X2 is the distant past now.

elijahlucian
i asked for these things back in x2 and still nothing... being able to choose which take is the 'priority' take when you collapse... i mean, how could they not have seen that in a beta test... 

Unless I'm mistaken, that's one of the useful things I found in X3c... If you've "promoted" the clips/takes you want, they do correctly appear on the closed track... ( well, most of the time as I just stubled on a situation where this wasn't happening quite right... I have to research it more before I decide on reporting as well as waiting for X3d to discover what we now have! ;-)

Keni

I'm pretty sure roland didn't take all the tech support tickets with them when they left, meaning, these issues should be resolved BEFORE making a new version... that's how it's supposed to be done... at least, when paying customers are in the equation.... 

Let me point you to your own thread:
what about making sonar x2 stable?
 
Let's carry on with topic of takelanes here...