Should NPRN repeat address (CC 98/99) and NPRN Reset (if enabled) with each value?

Bug reports
1

When moving a knob (in a 4 mixer) multiple value changes are sent in quick succession. It’s possible to send less bytes by skipping the NRPN address as the value is changing … and to only send the reset once at the end once the value is no longer changing.

This assumes there is a buffer or other state that knows the controller has queued up value messages.

The current behavior is the safest, but the least efficient.

2

yes, that is the main reason behind that. At this moment each message is self-contained and does not need to know the context/state other message stream. I wish to add support for running status at some point (on the outbound side), this is basically the same thing.

1 Like