We have a button that takes a specific action when pressed. Some users are apparently asking for that to be automatable. But that seems totally wrong to me. We’ve never automated push buttons before, only buttons that toggle state.
Part of the reason is that a push button can issue a 1 and then a 0 state change, and BOTH those state changes could be seen in a single process buffer, leaving only the latest value as being seen by the plugin (since we don’t have sample-accurate parameter automation). To me, even making it a parameter seems wrong. It’s not a state, it’s an action. So what does its value even matter? It’s the user action they want to somehow automate, but to me it seems that parameter automation is not the right way to do that, just a convenience method that might lead to problems of one or the other of the button states getting lost.
Even if the changes are seen in different buffers, since our action involves writing to a file, we can’t do that while processing, so the Editor needs to know the change happened. Will a push button attached to a bool parameter ever call buttonClicked() in the Editor code when reading back the automation?
Is automating push buttons even a thing? Does it automat properly in all hosts/conditions?
