Debounce for Loupedeck Dials?

[hepto]

Hi, asking this here rather than as an issue as I may just not know how to do this but it is possible.

I'm using Companion with a Loupedeck Live S and it does not appear to have any kind of debounce on the dials.

I've checked some older issues and it seems that the buttons of the Stream Deck have debounce baked into firmware, so maybe this is why there appears to be no support for this in Companion?

At the moment I am trying to configure a dial to control the brightness of a screen, but if I spin it too fast it floods the monitor with commands and then can error. So I need a way such that the later commands are not sent until the ones before are complete, or actually it drops the ones in the middle and just does the latest one.

Is this sort of thing possible?

[dnmeid]

What you describe is not a problem of the dials or debounce. It seems more related with flow control of the connection that you use to control your monitor or maybe even the monitor API. I have seen a lot of APIs that are not resistant to flooding.

What you can do is to set up some locking mechanism. My recommendation is to not control the value directly from the dial but to increase/decrease a value in a custom variable. Then you can use a trigger that is triggered when the variable changes. With the start of the trigger you can set another variable to indicate a locking state and either at the end or after some time you reset that variable. Now you can use the locking variable as a condition of the trigger, so the trigger only runs when the value variable changes and when the locking variable allows.
With that mechanism you'll have your debounce and at the same time you don't miss any clicks of the turn.

[hepto]

Yes I was thinking of doing something like this but hoped that there might be a simpler way baked in. Will give it a shot and report back, thanks.