Possible bug in MIDI events construction for VST3
REAPER: 5.981 x64, Windows (but also with version from 10.2018)
Environment: Ubuntu 18.04/Wine Staging 4.11
MIDI input: virtual keyboard, played by mouse, "dragged" along the keyboard with left button pressed
Reproducibility: always.
The observation:
Events in VST3 have sample shift and musical time (in QNs). When the transport is stopped and current time is zero, both numbers are normally zero. But under specified conditions I periodically (not every event) get:
sample shift = 1 (have not seen other values)
musical time = <seems like continuously growing musical time, unclear when the counter is reset>
That musical time is not expected (the musical time of currently processed buffer is still reported as zero).
I was unable to reproduce the effect with the same version of REAPER/plug-in under real Windows 10 nor native Linux version. But I have not tried hard.
My own code is non standard and experimental, it can happened I somehow influencing that result. But all other data fields looks reasonable and I "print out" the information immediately after receiving it from REAPER, it seems like these numbers are really generated inside REAPER.
|