So, rebuild function on take lanes missing - makes them almost unusable {the purpose of rebuild is to separate doubled clips in one take lane and TO DELETE EMPTY TAKE LANE, it takes enormous time in big projects to search for empty take lanes and consolide graphical view}, it seems that CW doesnt listen to customers needs anymore.
 
Another fail is that you forgot to implement multiple MIDI input ports for VST3 based instruments - one of the most important features {must have for Vienna Instruments for example}
 
So for now, I dont know for what I really paid, some unusable NOMAD and XLN stuff? Thank you, I dont want this and please fix at least this important workflow issues.

BluerecordingStudios
So, rebuild function on take lanes missing - makes them almost unusable {the purpose of rebuild is to separate doubled clips in one take lane and TO DELETE EMPTY TAKE LANE, it takes enormous time in big projects to search for empty take lanes and consolide graphical view}, it seems that CW doesnt listen to customers needs anymore.
 

The comp video showed a "remove empty lanes" feature, so there should be no need to search for them.   Have you tried it?
 

Is there a vst3 version of those Plugins? We can certainly look at it but it hardly qualifies for you to call it crippled support. Our first priority was to support the the main base of vst3 which we have done.

yes but this doesnt solve rebuild doubled clips...

stevec

BluerecordingStudios
So, rebuild function on take lanes missing - makes them almost unusable {the purpose of rebuild is to separate doubled clips in one take lane and TO DELETE EMPTY TAKE LANE, it takes enormous time in big projects to search for empty take lanes and consolide graphical view}, it seems that CW doesnt listen to customers needs anymore.
 

The comp video showed a "remove empty lanes" feature, so there should be no need to search for them.   Have you tried it?
 

If I'm reading the OP correctly I think what he (she?) expected was a Rebuild where clips that did not overlap end up in a single lane (like layers in X1) and what is happening is it is only removing empty lanes. Not sure I'd want to revisit the chaotic way Rebuild used to work but I could see his point. A proper rebuild function should probably work like this:
 
Hit rebuild.
 
Top lane is loaded with all the clips that do not overlap closest to the beginning of the timeline.
 
Once an overlap occurs they appear in the second lane and then any overlapping clips from that point forward (until another overlap occurs) get moved to this second lane.
 
Then it follows that throughout the project and any empty lanes produced by the process are removed.
 
Edited to remove derp... I think.

Noel Borthwick [Cakewalk]
Is there a vst3 version of those Plugins? We can certainly look at it but it hardly qualifies for you to call it crippled support. Our first priority was to support the the main base of vst3 which we have done.

I am waiting more than year for this update Noel, thank you for your fast reply. Of course it is VST3 plugins, right under VST3 folder in CW. Thank you again

Beepster

stevec

BluerecordingStudios
So, rebuild function on take lanes missing - makes them almost unusable {the purpose of rebuild is to separate doubled clips in one take lane and TO DELETE EMPTY TAKE LANE, it takes enormous time in big projects to search for empty take lanes and consolide graphical view}, it seems that CW doesnt listen to customers needs anymore.
 

The comp video showed a "remove empty lanes" feature, so there should be no need to search for them.   Have you tried it?
 

If I'm reading the OP correctly I think what he (she?) expected was a Rebuild where clips that did not overlap end up in a single lane (like layers in X1) and what is happening is it is only removing empty lanes. Not sure I'd want to revisit the chaotic way Rebuild used to work but I could see his point. A proper rebuild function should probably work like this:
 
Hit rebuild.
 
Top lane is loaded all the clips that do not overlap closest to the beginning of the timeline.
 
Once an overlap occurs they appear in the second lane and then any none overlapping clips from that point forward (until another overlap occurs) get moved to this second lane.
 
Then it follows that throughout the project and any empty lanes produced by the process are removed.

Sonar X1 has this implemented as you remember and it was one of the best function in whole soft...
 

Have you dug into comping yet in a recording scenario? There is definitely an intended workflow here. When you're in comping mode the Take Lanes are actually very intelligent with breaking the takes into individual Take Lanes and promoting the most recent take.
 
Before claiming it's crippled I might spend some time with the documentation and the new workflow: http://www.cakewalk.com/Documentation/default.aspx?Doc=SONAR%20X3&Lang=EN&Req=NewFeatures.08.html#2474993
 
There's a bit of a learning curve but as you start to record new projects you'll find that the take lane integration with comping is actually incredibly nice. The comping tool is a very nice addition.
 
Anyhow I'm interested to hear your feedback when you've had some more time with it. I think it's probably a good idea to be as descriptive as possible with your workflow on this so we can understand. Even internally we found that take lanes mean different things to different people depending on their workflow and so explaining things to one another required a lot of show and tell with real use scenarios.

BluerecordingStudios
 
Sonar X1 has this implemented as you remember and it was one of the best function in whole soft...
 

 
Except it didn't work in an organized way like I described. It tossed non overlapping clips all over the place randomly and without maintaining the sequence in which the takes were recorded making it very difficult to figure out what take was what (no notes so you had to audition it all which was very time consuming).
 
And layers themselves were a bear simply because once you got to a certain number of them they took up the whole screen and got so small you could not edit them properly or even use the Solo/Mute buttons. At first I liked Layers until I started really using them then they drove me nuts. Lanes have thier problems (in X2) but I just find them much easier to work with despite the lack of a rebuild option.
 
I would however like to see a rebuild similar to what I described. The only drawback would be organizing the notes on Lanes that contained multiple takes but that could be fixed with some kind of Notes menu that allowed you to choose the note of specific clips within the lane.
 
There are other issues I'm starting to visualize with my method but they could be resolved as well with a little thought into implementation which I'm not going to theorize about today.
 
Either way thank you for letting us know about how the Lanes are working. Cheers.

BluerecordingStudios
yes but this doesnt solve rebuild doubled clips...

 
I'm not sure what you mean here, but you can't have two clips in the same space in the same lane. As soon as you try that the new one overwrites the old. If you use the comping tool just clicking on a clip automatically promotes it and then muted clips can be deleted using that option from the right click menu.
 
Personally for me it has made my comping workflow method almost completely automatic. It really is fantastically quick and smooth. IMHO of course.