🔥 Lifetime deal! Get Control Surface Studio for Just £67 👉 Click Here To Get It
Time left... mailtimers.com
⚠️ Lifetime licenses are ending soon, get yours before they're gone ⚠️
Your shopping cart is empty.

Encoder Acceleration Help

Submitted by bbedar on Sat, 03/18/2023 - 11:21
bbedar
Control Surface Studio User

I am having what appears to be a common problem. I bought this software to edit a control surface for my x-touch mini, which as everybody now knows has firmware based built in acceleration in the rotary encoders. The device comes with an editor that allows you to change from Absolute to Relative 1 (Right 1-7, Left 121-127), Relative 2 (Right 1-5, Left 123-127) and Relative 3 (Right 1-3, Left 125-127). When these encoders are used with the base interpretation of the software, set at L 127, R 1, Steps 127, the encoder only works when turned very slowly. If you turn it quickly at all, it sends a different signal that isn't picked up by the software.

I see solutions with this in reactions, which I am digging into now. However, these reactions require me to reprogram my entire control surface through script that I am very unfamiliar with. I currently have all 8 encoders set to do different things in 4 different modes. It seems like it would be extremely difficult and time consuming to write all of these out as reactions, just so the knob turns correctly.

Thus, I guess my question is two-fold. Has anybody found a viable solution to this problem? I don't care how it's fixed; we can translate all of the messages to just be L127 R1, or we can try to get the acceleration to work. Whichever will get me to my end result faster and cleaner.

The second question is, can CSS try to implement an acceleration feature? It could be built into the GUI; when you select a Relative encoder, you could have the option to put in a range of L and R values, instead of just 1.

upload files: 
Topic Category: 

2 Responses

Comments

bbedar
Control Surface Studio User
#1

Template attached.

upload files: 
bbedar
Control Surface Studio User
#2

nevermind, problem solved.