mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #516] Check for external volume change #330
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#330
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DementevAlex on GitHub (Aug 3, 2020).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/516
Hello!
Just got librespot to control volume through the ALSA mixer with no problems.
I also have IR receiver attached to my Raspberry PI to do some stuff including volume control. It also works with ALSA mixer.
And as I understand it seems like librespot doesn't check the volume value. For example I set volume on my phone to 60% then changed it to 30% via IR. After that I still see 60% on my phone.
Is it possible to add the volume value reading?
@ashthespy commented on GitHub (Aug 4, 2020):
This is on my #todo list. The bits and bobs are there, I hacked up a solution some time ago, but it's a waste of resources, as it spins up a thread just to poll for volume changes..
@DementevAlex commented on GitHub (Aug 4, 2020):
Well that's good news, thanks.
After some googling I found the spotcontrol. If I can set up lirc to control volume through it (not through ALSA directly) and volume level will be shown on my phone or desktop app then it would fit me as a tmp solution.
But it's going to be even more waste of resources :)
@celismax commented on GitHub (Feb 20, 2021):
Hi @AlexanderShevelev !
Did you find a workaround unsing ALSA ?