mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #29] Use pulseaudio native volume management #18
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#18
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 @sashahilton00 on GitHub (Jan 29, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/29
Tuesday Apr 19, 2016 at 18:44 GMT
Originally opened as https://github.com/plietar/librespot/issues/75
Hello,
When using pulseaudio backend it would be nice to delegate volume management to pulse audio sink. Besides having a logarithmic scale natively, it would also allow to manage librespot volume in one place and avoid several volume alteration (librespot, pulseaudio sink, pulseaudio output).
However, it would be necessary to move volume management from the player to the audio_backend.
What do you think?
@sashahilton00 commented on GitHub (Jan 29, 2018):
Saturday Aug 27, 2016 at 23:58 GMT
I'd like to see this for the ALSA backend, too!
@brain0 commented on GitHub (Mar 3, 2018):
Using pulseaudio's volume control requires using the asynchronous pulseaudio API instead of the "simple" API. This is very complex, since nobody has done this in Rust yet. I have started a prototype for a pulseaudio API binding for tokio, but haven't worked on it for a while now.
@mirko commented on GitHub (Mar 14, 2018):
I'd really like to see the native volume management being used as well. I'm aware of the API change using PulseAudio and its necessary effort, though..
@roderickvd commented on GitHub (May 25, 2021):
#685 implements what you ask for (logarithmic and cubic mappings, transparently for all backends), without the need to implement the asynchronous PulseAudio API.
If you feel like you don't want bits touched by volume controls in several places, then either set
librespotor PulseAudio volume fixed to 100% and it will bypass touching any samples.