Hi, guys. Just a note that I've created https://bugzilla.redhat.com/show_bug.cgi?id=497966 - alias AlsaVolume - as a tracker bug for reports of cases where the PulseAudio volume control can't usefully control the volume because another mixer channel needs to be adjusted (e.g. no matter what you set the gnome-volume-control slider to, you have to open alsamixer and set PCM to 100% before you hear any sound). Please set any bugs of this kind to block AlsaVolume. Thanks.
On Tue, Apr 28, 2009 at 7:53 AM, Adam Williamson awilliam@redhat.com wrote:
Hi, guys. Just a note that I've created https://bugzilla.redhat.com/show_bug.cgi?id=497966 - alias AlsaVolume - as a tracker bug for reports of cases where the PulseAudio volume control can't usefully control the volume because another mixer channel needs to be adjusted (e.g. no matter what you set the gnome-volume-control slider to, you have to open alsamixer and set PCM to 100% before you hear any sound).
Is this the kind of bugs that are fixed by creating an entry in the ALSA db? if so, it would be nice to add there a reference to the procedure required to create the required data on the affected machine.
On Tue, 2009-04-28 at 08:51 +0200, Gianluca Sforna wrote:
On Tue, Apr 28, 2009 at 7:53 AM, Adam Williamson awilliam@redhat.com wrote:
Hi, guys. Just a note that I've created https://bugzilla.redhat.com/show_bug.cgi?id=497966 - alias AlsaVolume - as a tracker bug for reports of cases where the PulseAudio volume control can't usefully control the volume because another mixer channel needs to be adjusted (e.g. no matter what you set the gnome-volume-control slider to, you have to open alsamixer and set PCM to 100% before you hear any sound).
Is this the kind of bugs that are fixed by creating an entry in the ALSA db? if so, it would be nice to add there a reference to the procedure required to create the required data on the affected machine.
In some cases that's the fix, in others it needs to be fixed in PulseAudio (it depends if we only need to change the *initial default level* for a second mixer element - in which case we add an entry to the ALSA db - or if a second mixer element *needs to be varied dynamically* when you adjust the single volume slider - in which case Pulse has to be adjusted to handle this).
I'll add a comment to the bug with a note on what information people need to report for bugs of this type, thanks for the suggestion.