Bug: OSC volume change not reflected in Faderport 16
Hi,
it seems that something's wrong with OSC message propagation to control surfaces. I have a Faderport 16 (FP16) properly configured and working perfectly well with Reaper (using native support, note that alternatively using CSI does not change in anyway what I'm describing below). If I move a fader on the FP16, the corresponding Reaper track fader will move accordingly (thus affecting the volume) and vice versa: changing volume on a Reaper track causes the corresponding FP16 fader to move, that's perfect.
Now, if a change the volume of a Reaper track through OSC (independently from the FP16), unfortunately that change is not reflected on the FP16: the corresponding fader does not move, and that creates a mismatch between the real track volume on Reaper and corresponding FP16 fader position, as if the OSC message was not properly propagated. This seems to be specific to OSC processing since changing the volume with Reascript does cause the FP16 fader to move. That does not seem like a normal behaviour. I suspect it's merely a bug? Please help.
|