We have come across an issue of Automation lane display mismatch with parameter actual value on Cubase.
Step to reproduce:
- Write automation (with some fluctuations).
- When transport is stopped, place the cursor on a steep curve.
- Value presented in the automation lane doesn’t match the value in the plugin.
What we found is inconsistent values sent by the host in getParamStringByValue() and processParameterChanges().
So it presents the string asked as it should, but actual value in the plugin is set to another value (hence, the mismatch).
We saw this reproduces on various vendors and hosts but wasn’t reproduce for Steinberg plugins under Cubase.
Is this bug coming from the host or did we mishandle something around the automation flows?