Interpreting Relative Encoders
I have an issue whereby the definition of an encoder in the surface script is quite simple
Type = Relative
Left = 1
Right = 127
Steps = 127
That was fine while I was prototyping and you move an encoder slowly. When using encoders with acceleration, the Left value can range between eg 1,2,3,4 and the right 127, 126, 125, 124
What is the correct way to manage this as the actions seem to be ignored when I turn the encoder quickly? What is the controller filter actually doing when it comes to relative encoders?
Cheers
Maybe you could try doing feedback via Reactions?
here’s a blog post on sending led feedback to your controller using reactions: https://remotify.io/tutorials/sending-custom-led-feedback-your-midi-cont…
Sign up
User registration is currently not allowed.