Ok but what’s the purpose of having 2x differents methods for overriding data ? I don’t understand, it’s cumbersome to me. If it’s there, there must be a pratical reason i have not understood yet.
Also, having to press a pad to commit changes is weird, i don’t have enough fingers to press pads when i want to record 8x pitch faders automation at the same time. It’s breaking the flow of interpretation, that use the creative part of the brain instead of the other part you use to do cold technical stuff.
I think that for everybody, when you press record, you expect the machine to record everything (pot and faders) instantly, without having to press multiple pads. When you are recording automation, you should not have to think, the less move you have to make, the better. It must be straight forward.
So for me, the natural way would be this :
In playback mode, override is on everytime, no need to press A or B. Like this you don’t have to think, you press pitch, you tweak a fader, and boom, the pitch is changing. But nothing is stored, and at any time you can recall the initial kit state.
In record mode, every move made to filters and faders are instantly recorded. Without having to press A or B or a pad, because if you press record, it’s to record. No need to have an extra step "are you sure you want to record ?’.
But again, maybe i miss something.