New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 11 users
Status: Archived
Owner: ----
Closed: Nov 7
NextAction: ----
OS: ----
Pri: 2
Type: Enhancement

Sign in to add a comment
Control the ALSA volume control even when using PulseAudio
Project Member Reported by, Oct 30 2012 Back to list
On some devices (maybe all?) there will be both a PulseAudio and ALSA volume control. The AGC manages the PulseAudio volume, but if the ALSA volume isn't set to a halfway reasonable range, there's not much it can do.

To fix manually open a terminal and run "alsamixer". Hit F4 to move to capture devices and F6 to select the device in question. Move the slider appropriately. You can tune this in real-time in a loopback call if you want; ideally it would be at a high enough level such that the PulseAudio volume (visible through the "Sound Preferences" Gnome control panel) isn't maxed out.

Ideally, we would be able to control the ALSA volume control as well to avoid cases like this.

We shouldn't see this problem on ChromeOS (which uses ALSA, not PulseAudio) or GVC (which has some kind of volume tuning procedure).
Project Member Comment 1 by, May 31 2014
Labels: -Restrict-View-Talk Restrict-View-Google
Comment 2 by, Oct 15 2014
Labels: Area-Audio
Comment 3 by, Dec 11 2014
Project Member Comment 4 by, Dec 11 2014
Labels: EngTriaged IceBox
Project Member Comment 5 by, Nov 3 2015
Project Member Comment 6 by, Nov 26 2015
Labels: -Restrict-View-Google
Comment 7 Deleted
Comment 8 Deleted
Project Member Comment 9 by, Jan 11 2017
Owner: ----
Status: Untriaged
Moving back to triage since no status updates took place for more than a year.
Project Member Comment 10 by, Feb 3 2017
Status: Available
Comment 11 Deleted
Project Member Comment 12 by, Nov 7
Status: Archived
[Bulk edit] This issue hasn't been modified the last twelve months -> archiving.

If this is still a valid issue that should be open, please reopen again.
Sign in to add a comment