gmane at colin.guthr.ie
Sun Jan 24 08:26:44 PST 2010
'Twas brillig, and Tanu Kaskinen at 24/01/10 15:23 did gyre and gimble:
> su, 2010-01-24 kello 13:12 +0000, Colin Guthrie kirjoitti:
>> Someone asked recently about the Beep mixer in alsa. With a PA enabled
>> setup, controlling the Beep volume (when this is exposed via alsa)
>> becomes awkward.
>> What is the best way to handle this? Could we tie it/slave it from the
>> master volume via the alsa mixer profile stuff perhaps?
> Are you talking about the PC speaker beep? How is controlling its volume
> more awkward with PA than without?
Mainly due to the fact that mixers are moving to support PA and not alsa
so users wont be naturally exposed to a UI that helps them do this.
> We probably could tie the Beep element to the sink volume in the alsa
> mixer configuration stuff, but that alone doesn't seem like a default
> choice that always makes sense. If I use headphones, I may or may not
> want the volume to follow the sink volume: at home I might want that,
> and in a library I probably wouldn't want that.
> I think the best choice would be to control the PC speaker volume
> independently from anything else. At server side it could be implemented
> as a separate module that would provide a separate client API.
Yeah these were my two thoughts too... not sure if we really should
expose it so specifically tho'. I guess some kind of passthrough for
some elements is not a bad idea generally, but for this case if we could
have some sort of smarts that ties it to the "Event Sounds" slider
perhaps that would make for a cleaner UI?
Tribalogic Limited [http://www.tribalogic.net/]
Mandriva Linux Contributor [http://www.mandriva.com/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
More information about the pulseaudio-discuss