Bug 386181
Summary: | Difficult finding the *real* hardware mixer | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Linus Torvalds <torvalds> |
Component: | pulseaudio | Assignee: | Lennart Poettering <lpoetter> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 8 | CC: | covex, knutjbj, pierre-bugzilla |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-09-09 22:55:20 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Linus Torvalds
2007-11-16 03:07:17 UTC
You can always fiddle with the raw mixer settings with "alsamixer -c0", regardless of PA is installed or not. It is a big mess that currently we have three volume controls in a series on machines like the Thinkpads: the "PCM" slider, the "Master" slider, and the real hardware volume up/down buttons. The plan is to initialize them all to "sane" defaults" and expose only a single of them in the UI. This has partially been implemented in F8. However what is lacking is the initialization to "sane" defaults in ALSA. In short: I am working on this, but I do not believe that the fix should be exposing all HW controls, but instead just make the ALSA utils to find better defaults for the redundant volume controls. I believe the hardware mixer is being still exposed in the Gnome volume control. This is going to be fixed though :) In PulseAudio 0.9.12 from rawhide we will now "extend" the hardware volume range in software. On one hand this means that we now can offer the same volume changing capabilities to all users regardless of what the hw supports, and otoh (which is more relevant here) we will always expose the hardware volume -- we won't hide it anymore under any circumstances. Which means that it is much more unlikely that a misconfigured alsa mixer will cause too silent audio, and much more likely that just using the pa mixer will fix the volume for you. Also, in related news Jaroslav will upload alsa 1.0.18 to rawhide shortly which will initialize the alsa mixer by default more sensibly, so that PCM audio will always be hearable by default on the output device. In summary this should mean that it is now much more likely that the audio device's volume will be correctly configured by default. And if it isn't pavucontrol will suffice to fix it. And if this doesn't work, it's a bug in alsa-util's default mixer setting database. |