sure.. but you had no clue of what this feature exactly did before
you posted it as a rant..
I had the absolute clue that it is useless bullshit,
Your problem is, you dont had a clue.. "found it in the manual so it has to make some sense"..
what a smart attitude towards the world
its an redundant menu entry and with a program that dont even allows usefull entrys to keep things compact thats one useless detail taht just can go..
when they have an autowarp fuction please a ready developed one that contains some own arteficial intelligence..
Everything else looks really stupid. And we dont like the feel to work with a stupid program that has many retard menu entrys..
Thats not ableton style.
minimal feature set but smart implemeted and therfore even more powerfull..
nice doctrin.. maybe not allways possible to hold to that.. but defently a reminder to dont go into the opposite direction..
I wonder how ableton is doing design decissions.. theier developers are all programmers, but do programmers know what a daw needs? so ther must be an experianced front end design team for the main agenda.. the henke/behlens duo?
Or are the having some kind of nerd democarcy there? Would explain the tendency away from stage work towards office management software...
However they do it..there is not too much place to discuss detail problems... so there wont be detail fixes..
but lets keep on listining them.. the more little the itch as more important to put some light on it...
all the selection in arrange is probably realy a bit quirky.. at least it´s surprising that the moves dont sit tight after so many years.. there is probably something litlle hidden thats against human logic.. just hard to analyze why one has lost the selection now again.. and again.. and again..
fixing such litlle handling things can improove the workflow a lot..
Just hard to nail or describe them..
I still often have to redo tha alt/drag clip copy... became better in recent versions of life..
but still it seems that removing the alt key before the copy has been executed leads to an canceld operation..so you have to do it again..
probably dont matters on faster machines..
But.. in general..the program should register wished user operations and just holding on executing them even when the command gets interupted by other heavy tasks or the user is too quick of the keys ...
maybe not endless. but keeping the last 3 commands in memory and just executing them could speed up things here a bit on bigger arrangement chunks?