@DavidPackouz, @BrennanSingularSound
Thank you for acknowledging my analysis. It’s always nice to see that if you voice valid and argued concerns there are people to take them in account.
Nevertheless, I don’t think the trip stops there… (I see you scared 
).
You are expressing a very valid concern David, which is:
So I agree with you. If I would be a user of the quantized-mode, I would definitily not like this (necessary) decision.
But is there a way we could go even further, keep a consistency between the quantized and freeform mode in terms of features while not removing features from the quantized mode and of course addressing the issue we are discussing there ?
Good news, I believe we can.
Everything I layed out in this topic is true for the first track of a song part. Then things are a bit different. And would say that after the recording of that initial track, freeform and quantized modes have much more in common, and especially if in the freeform mode you activate the “Sync tracks start & length” setting (which is by far my preferred mode as it has a little flavour of the hybrid mode I had requested prior to this last release).
So my proposal is to, instead of thinking the problem we are discussing in terms of quantized vs freeform, why don’t we think it in terms of immediacy vs deferment 
?
If the settings (“Sync tracks start & length”, and possibly some others), the mode (quantized vs freeform) and the context (first track vs others) define what we would call an “immediate-action mode”, then everything we said here has to be applied in this mode (master rule applies and secondary actions have to be removed from re-record start and stop button, leading here to the “redo” relegated to the touchscreen…). And if we are not in such a mode (like in quantized mode or for subsequent tracks if synced to start and length in freeform mode), we do not need to apply this master rule at all and can keep the current behavior as it is… That would sound a lot like the best of both worlds.
I don’t really think it complexifies the usage, as the user feels this sense of immediacy depending on the settings/mode/context… I mean, he knows what he defined and the impact it has on when he has to click on this or this…
Now, I’m not saying, this is as priority as what I emphasized earlier in this topic, but I think it definitely worth for you to think about it now, and run an in-depth analysis. And even if at first sight, it may look like a complexification of your code, it is maybe not and actually maybe even a clarification… That could potentially lead eventually to a simplification of settings to be exposed to the end-user…