Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Solved: Debugging/debouncing GPIO buttons... (false triggers)
#6
(11-15-2022, 07:12 PM)challenge Wrote: yes the script is in moode, nothing custom.
I guess this is the source code for it? :
https://github.com/moode-player/moode/bl...buttons.py

there's a section in moode settings UI that enables the GPIO handler, called "GPIO config" or something like that.
You enable it, and then there's another screen where it allows to associate commands to gpio pins.

Not at home, but have a screen here:

yes, I found it.

nothing fancy, it sets up a bunch of callbacks on the button (bit). I thought we could check if many (if not all) buttons were active at one time (the spike should affect all of them), we could simply ignore them all...
See what you have set-up as the first button... it should be TOGGLE PLAY PAUSE, in my opinion... if it's possible, set it as NEXT, and then you might confirm that, from now on, instead of toggling play-pause, switching the amps on/off should have moOde skip tracks...
If that's the case, we might think of a all-buttons-on-at-the-same-time ignore thing.

Cheers, Al.
Reply


Messages In This Thread
RE: Debugging/debouncing GPIO buttons... (false triggers) - by Nutul - 11-15-2022, 08:04 PM

Forum Jump: