Device parameter display text lag, bug?

[bassc]

Hi, wondered if anyone has come across this issue.

Devices/CursorRemotePage, adding a parameter.addValueObserver works fine and as expected.

But adding a addValueDisplayObserver, the display text received for the value lags 1 or 2 values behind the actual value. It is also the same doing it the new way using parameter.value().displayedValue().markInterested() and reading the display text in addValueObserver.

I found this in my script and then checked the shipped Mackie MCU script, and it's the same there. On the MCU going into device mode ("plug-in" button) and rotating a rotary slowly to the very top (on a plugin that has device pages), then bring it down one notch, is where it is most noticeable. The rotatory display will max out at 126 then go to 127 after the rotary is turned back the other way, updating to the previous value rather than current.The min/max out values have a greater discrepancy when the rotary is turned faster (because of the greater step jump).

I am on the slightly older Api v5, Bitwig 2.3.5.