Maybe I just didn’t develop muscle memory for A and B buttons in the context of the live looper but it happened to me a couple of times already that I accidentally discarded a buffer instead of committing it.
So I thought, maybe the machine could communicate more actively that there is uncommitted audio in the record buffer. Blinking light seems to be a proper indicator for such kind of things.
At first, I was not sure about where such indicator would make more sense, on button A (= “there is something to commit”) or button B (= “there is something to undo”). But the more I think about it, the more I’m inclined to the blinking A button as it seems to be more logical and have a more positive attitude.
Something’s blinking! What’s that?Uncommitted changes! Do you want the blinking to go away? Then press the blinking button!
This would also prioritize the A button in user’s eyes and make the Undo button (B) perceptionally less important (as it never blinks).
Does it make sense?