@kb420 Uh... it's a lot of words but the premise is actually pretty simple.
However specifically for MIDI loop recording there could/should be a specific featureset/workflow that is semi separate.
I'm envisioning something like a new record mode for MIDI Loop recording whereby you can do what I described except there is an option that allows the user to Accept or Deny the last pass.
That way as the parts are built up you can "Accept" the last pass and it remains audible (then you can move on to the next sound layer) or "Deny" will mute or undo the last pass so you can continue on the same part/element without stopping transport.
That's really the only major flaw I see for that workflow. However they could eke in another option that allows all this to occur in a single clip. I personally don't see the huge deal about doing a clip bounce after the fact but if that's what people want then of course they should try.
As far as "toggling" take lanes or completely removing them... that's not making a lot of sense. What do you mean? You can toggle lanes on/off (show/hide) and as noted you can make it so only one take is created (overwrite and/or create new track instead of lane). The clips have to go somewhere and Layers did the same thing anyway... just differently.
If you mean an option to revert BACK to layers... well that would make sense but I doubt that's going to happen at this point. Too many of the tools and workflows are designed around lanes so it would raise a whole host of design issues. It would have to likely be a Global setting and all those design problems taken into consideration for each setting. Mixing Layers and Lanes in the same project or toggling back and forth just wouldn't work AFAICT.
For me Layers caused a lot of ridiculous problems and seem to be designed backwards (mute instead of promote) but I can still mostly work the same way as I did with Layers in X1 if I REALLY wanted to.
I'm not trying to be a Cake apologist, "RTFM" douche or "fanbois" here. It's just most of the angst I see in regards to lanes really is about them not being understood (and Cake has not helped much conveying how they work most efficiently).
Once they are understood there are most definitely things that can be improved but Layers had it's own pile of problems.
So, Loop Recording MIDI for the "layer" technique could be improved but just allowing for simple real time mode of Accept/Deny/Mute Last on the fly would fix that.
The minimum height size of the lanes is dumb. The always on auto zoom is dumb. Some of the Take Lane MSR stuff is dumb but for MOST stuff, if used properly Lanes tend to be far more efficient and logical... especially with the Comping features. The "Notes" section alone has improved my editing experience immensely. Comping has been brilliant. Multi track grouping is very clever (but could use some improvements IMO).
Different strokes and all that but I simply do not see the massive barriers Lanes seem to cause others. I just see old workflows being disrupted after years of use, and believe me I am sympathetic, but the Bakers took a gamble to modernize the workflow in the X series and it's mostly paid off.
I manage to make them work... and rather well for most stuff and I'm bungling amateur.