I’ve got an issue related to parameter automation which seems a bit weird. Maybe someone with better knowledge of the AudioPatameter classes can give me a hint here.
I’m using the AudioParameterFloat class as well as on-screen sliders and a graphic GUI that needs updating when parameters change. To adapt to parameter changes I’m implementing a timer callback that updates sliders and GUI in function of the parameters, as described in various tutorials.
What I’m observing is the following: if in the timer callback I only adjust the sliders (with dontSendNotification, so I don’t trigger things I might not want), automation works flawlessly.
However if I also redraw the GUI in the timer callback, the host (Beatmaker 3 in this case) seems to loose automation steps from time to time while recording is on. It is as if a previous value of the parameter gets written back to the host after a while, even though I have no clue whatsoever how this can happen, as I’m not changing any parameters in my GUI drawing routines. So the only difference with the case where it works is that I spend more time in the timer callback.
Any ideas what could be happening behind the scenes here? What would be a good way to debug in this case? It might help to monitor the communication between host and plugin (reading/writing parameters), but since that is all handled by the AudioParameterFloat class, I don’t see how I could do that from my own code.
Thanks a lot in advance for any hints that could solve this problem.