Repository navigation
Replies: 2 comments 2 replies
|
Afaik we support the encoders the same os the official Elgato Software. Please check their official SDK Docs for the Infos. |
2 replies
|
Those mentions of sliders will be from when OpenDeck was built for my custom hardware project, which had sliders (you can see this in the app icon). There's no real way for plugins to be able to differentiate because the Stream Deck SDK has no notion of sliders. That's why the sliders on my hardware just impersonated dials, with the slider's length split into 192 as the same number of ticks in one dial rotation. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
The OpenAction docs describe dialRotate as both an encoder dial rotate and an encoder slider move. For a dial, ticks is a signed step count (positive clockwise, negative anticlockwise). For a slider, ticks is an absolute position, with 0 as the lowest and 192 as the highest.
Looking at the host, encoderChange only carries device, position, and ticks, and that value is forwarded unchanged as dialRotate.ticks. I cannot find a way for a device plugin to declare that an encoder is a slider, or for an action plugin to tell a position apart from a delta.
Does OpenDeck support sliders today? If it does, how should a device plugin report the position, and how should an action plugin know to treat ticks as a 0–192 position instead of a step count?
All reactions