Wrong track state sent to control surface for action or API-based track selection
I have a Faderport control surface setup, and when I click tracks with the mouse, the control surface receives the newly selected track's current volume and all is well.
But if I jump to a track using an action or API call, such as Go to next track (40285) or Go to previous track (40286), it continues to send the volume of the last mouse-selected track.
Perhaps the intended behavior is such that only the last touched track will get sent to the Faderport? But if that's the case, shouldn't the Set first selected track as last touched track (40914) cause the Faderport to receive the newly selected track's volume?
I thought perhaps I could hack my way around this with Reascript but I confess the csurf APIs are completely impenetrable to me.
If this isn't a bug, I'd very much appreciate some cluebatting. (Edit: I'm now quite sure this is a bug.)
Thanks!
Last edited by tack; 12-30-2018 at 06:39 PM.
|