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
Hi Robert,
With CSS we dropped using the Web App / framework style of encoder/relative control as there were a number of issues with it. One of the main ones being that it wasn’t possible to add multiple mappings to a single controller input using that method. So we went for our own custom solution which also allowed for more editable options (as you mentioned).
I thought it would be possible to use the web app control via a Reaction but after having a dig around it can’t quite do it at the moment. But! we are working on a huge update to the Reactions ecosystem and I’m pretty sure you’ll be able to add web app/framework controls using it.
One thing I need to ask is, what functionality/mappings are you looking to control with your relative controls?
Sign up
User registration is currently not allowed.