elijahlucian
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.... 

If those "paying customers in the equation" are using X2 Producer, they're being offered an upgrade price for X3 Producer (which is a better program) for the price of Addictive Drums all by itself. And they get the $99 version of Melodyne, all the Nomad Factory Blue Tubes plug-ins, VST3 support, ARA integration, Skylight improvements, Gobbler integration, Pro Channel EQ improvements, a tape emulation module, speed comping, and bunch of other features. Oh, and four free updates (so far) with additional video capabilities coming next. If they stick with X3 for a year, it costs them $12.50 a month.
 
I think few people would consider that kind of deal as showing anything but gratitude for existing customers.
 
Can you imagine if musicians were subject to this kind of thinking? "I think your first album has a bunch of mistakes in it, especially some of the mixes but also some parts are out of time, so I think you should redo the parts and remix the tracks so the album is up to today's standards before releasing another album. Oh, and you should replace my first copy for free."
 
For better or for worse, that's just not the way the world works. Well, on second thought maybe Trent Reznor would remix stuff and give it away for free...but he's an exception

In my experience, the problem with take lanes and comping mode is not as much whether they work or not, but that they seem to be designed for very specific (and yes, quite common and useful) usage scenarios.  Since I often want to do things which are outside of common scenarios, the changes are often frustrating for me - the previous implementation was much more versatile, and involved less guessing at the way I am being expected to work.

Only issue I see resolved in X3D is:
> Resolved an issue where the order of Take Lanes would behave abnormally when switching Screensets


But the proof of the pudding is in the eating, please report your findings here.

my fav feature was deleate unused lanes. beat that thing to death, since i play 10 takes like a noob, just cus i can

blacksheep
my fav feature was deleate unused lanes. beat that thing to death, since i play 10 takes like a noob, just cus i can

I also record my rehearsals...! 'Cause I can.

> Resolved an issue where the order of Take Lanes would behave abnormally when switching Screensets
 
Please let me know of any specific changes in X3D that you think may be fixed.
I would love Cake to come in and chirp in at this point after looking at this thread. Right onto other things...

Jlien X
 
Anyway, what I'd really like to know is if there's a way to record all takes (including overlapped clips) in just one lane WITHOUT enabling the Expand/Collapse Take Lanes button. Can X3 do this?
 
When I record MIDI, I want to use lanes as a place to keep alternative ideas (that's why I don't want muted clips in additional lanes to appear in the main track when the lanes are collapsed).
 

 
Just responding to this one point. The answer is no. A lane as it name implies cannot have overlapping data on it. It is like a lane on a highway - you can't have two cars at the same place in the lane without causing a crash :)
The whole point of lanes is to provide a way to "explode" a view of overlapping clips on a single track to multiple lanes, and provide a way of editing and managing this data through the comping tools and workflow.
You cannot use a single lane as a repository for multiple clips that overlap - its not designed for that.
 
If you haven't already watched the comping video's I highly recommend checking them out so you can understand some use cases for the comping workflow and tools.

Where you guys lost me a bit on this was why you REPLACED layers with lanes instead of just offering the Lanes as a way to do the comping stuff and leaving the layers in place for people to be able to have their multiple takes in overlapping stacks (like I like to do with vocals). 
 
Seems like it would have been just as easy to leave the layers there in the code and just ADD the lanes to the options.
 
I'm sure there was some reason for this direction, but from a feature-set and usability point of view, it seems like you would inevitably alienate a notable percentage of your client base by doing this, especially for as many complaints as you got with the implementation in X2.
 
It seems like the marketing and development teams would have gotten together for X3 and said something like "why don't we bring the layers back for layering purpose and fix the lanes function for take comping and that way we can satisfy everyone."  Instead, what's happened is those who liked the layers feel like they've been taken away (X1 and previous users) and those who liked the idea of the take lanes feel like it is still somewhat half-baked, specifically that it's still somewhat buggy for all but the circumstances it was specifically developed for.
 
Just a few thoughts.  Is there some technical reason why layers didn't get left in/brought back?

Blades
Where you guys lost me a bit on this was why you REPLACED layers with lanes instead of just offering the Lanes as a way to do the comping stuff and leaving the layers in place for people to be able to have their multiple takes in overlapping stacks (like I like to do with vocals)...[snip]...what's happened is those who liked the layers feel like they've been taken away (X1 and previous users) and those who liked the idea of the take lanes feel like it is still somewhat half-baked, specifically that it's still somewhat buggy for all but the circumstances it was specifically developed for.
 
Just a few thoughts.  Is there some technical reason why layers didn't get left in/brought back?

To summarize something I've said in other threads:
 
For me, speed comping is a fantastic feature. I think the problem people have is that with Layers, you could sorta comp, and sorta edit. With Take Layers, you can comp really, really well...edit, not so much. These are Take Lanes and not Edit Lanes.
 
I don't know why people don't just use tracks for how they used to use Layers. My understanding is that Layers were supposed to do what they're doing now, but didn't. So people didn't get a chance to use layers as intended, and instead used them as "auxiliary tracks." But I really don't see anything layers offered that tracks in track envelopes don't offer, except for the ability to delete unused layers and collapse the remaining ones into a single track. Yet with tracks in a track folder, you can still bounce into a single track and any tracks that weren't muted will be in the bounced track, so I'm just not sure what you lose by using tracks instead of layers. From my subjective standpoint, take Lanes enable wicked fast comping for the kind of comping most, if not the vast majority, of people do while tracks are ideal for editing.
 
As to whether there could be an option for both, I don't do coding. However, my gut tells me that lanes and layers are very fundamental areas of the program, so messing with them could be opening a Pandora's box.
 

a few reasons why editing in layers is often preferable to editing in tracks have been posted here and there.  Here are some things I have noted...
 
It can be useful if you want to have many clips with different audio all feeding the same effects, for example, without using extra CPU on multiple tracks.  Yes, you can use a bus, but layers made this kind of routing simpler, not more complicated.
 
Background harmonies can be placed on one track, given one effect treatment, and then collapsed.  It's convenient.
 
Track Folders don't show a waveform when collapsed.
 
Track folders are not nestable, but tracks with layers can be put in a folder.
 
By implementing layers as a part of the edit filter, you avoid the pandora's box.
 
 
 
 
It might be possible to make track folders more like the layers function.  You could theoretically have a special track folder which acts like a bus, with it's own effect bin and all contained tracks routed through it.  That could be cool.