Vab
What would have been wrong with keeping layers when they added take lanes?
To much overlapping functionality, and too much development effort to keep supprting both if they were optional. Lanes are an evolution of layers. As far as I'm concerned, they
appear more different than they are functionally. And layers were certainly not without issues. In fact some of the complaints about lanes were true of layers as well.
I think part of the problem is that users are conflating new comp recording and editing functionality with lanes. Certainly there are tie-ins, but it seems to me that many issues with the comping workflow are being unfairly laid at the doorstep of lanes. And many of the complaints simply don't pan out on closer examination; ultimately a lot of the issues boil down to garden-variety resistance to change and/or unfamiliarity with the new tools.
I spent a goodly amount of time yesterday trying to get to the bottom of a user's complaint that he couldn't follow Seth Perlstein's Drum Production workflow from SONAR 8.5 using lanes in X3. As hard as I tried, I could not pin him down on what the issue was. He ended with "its just nowhere near as smooth or desirable"... oh wait, that was you.
But, seriously, I wish you'd go back to that that thread, and clearly explain what's not "smooth and desirable" about lanes vs. layers with respect to that particular workflow. No offense intended, but based on some of your other threads I've posted in, it's hard to imagine that you would have had enough experience with lanes to really know what the differences are or be troubled by them.