Ive never interfaced an encoder with jivelite. (Or sbpd) for that
matter. The encoder code in sbpd, is the same as originally done by
pippen. It should be easy enough to limit volume change rate in
sbpd. jivelite is a better question for Ralphy
We have programs that use wiring pi libs
hi schiff1108,
Can you detail your issue?
The Squeezelite Settings page is years old, if it was misbehaving I'd
expect lots of feed back over the years.
piCorePlayer is running in RAM. The config files are in RAM. The [Save]
button writes to the config file in RAM and does a backup to the SD
@LivewareProblem
Good glad you got it working !
I may have a try myself and also possilbly try the Digispark Pro (more
I/O's)
@Paul-
Can you clarify something for me please ?
The documents for sbpd seem (or rather do) to say that its output is
sent by http to the server and this gives rise to
Thanks for the replies guys!
I decided to re-write the trinket code, as I already had the knob /
encoder / trinket / housing built and configured. I have a spare encoder
so may look at the SqueezeButtonPi-Daemon in the future for control if I
add a screen.
That being said, I didn't realise
Thanks Paul.
Yes. I tried to make a joke w/ refernce to another thread.
You are right. I do see some unexpected behaviour when I make changes to
Squeezelite settings.
Actually, I am doing further analysis looking at various scenarios:
* just pressing the save button
* Restarting Squeeelite on
