Bug 520884
Summary: | gnome-volume-control has no way to select which device it controls | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John Brier <jbrier> | ||||||||||
Component: | pulseaudio | Assignee: | Lennart Poettering <lpoetter> | ||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | medium | Docs Contact: | |||||||||||
Priority: | low | ||||||||||||
Version: | rawhide | CC: | awilliam, bnocera, emcnabb, lkundrak, lpoetter, mclasen, wtogami | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | All | ||||||||||||
OS: | Linux | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | 0.9.21-1.fc12 | Doc Type: | Bug Fix | ||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2009-10-31 02:45:19 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: | |||||||||||||
Attachments: |
|
Description
John Brier
2009-09-02 18:54:15 UTC
If you go to the output tab in gnome-volume-control, do you see a "Connector" choice ? Does it offer you to switch between various outputs ? Yes, from connector my choices are Analog Output and Analog Headphones. If I select Analog Headphones and plug my headphones into the front headphone jack the audio is very low. If I select Analog Output and plug my headphones into line out in the back like I prefer the internal speaker plays. If I leave the connector on Analog Output and plug into the front headphone jack the internal speaker cuts off (probably by some hardware switch?) and I get proper level audio but there is a lack of bass compared to the line out. Another option i have is in the BIOS I can turn off this internal speaker altogether.. but then I can't use it when I want to share a video with someone or something. Passing to PulseAudio, as this isn't something gnome-volume-control can do anything about. Please provide the output of "amixer -c0" and "pacmd ls" Created attachment 359804 [details]
amixer -c0
Created attachment 359805 [details]
pacmd ls
Ok, I must admit that this confuses me quite a bit. You have three outputs? Line_out, Headphones, Speakers, is that correct? Could you please use the low-level alsa mixer (alsamixer -c0) to figure out which controls of 'Speaker', 'Headphone', 'Master', 'PCM', 'Front' actually influence which set of outputs for you? What I am looking for is a table that tells me which control influences which output. It might be possible (and likely) that some controls influence multiple outputs. This is probably relatively easy to fix by adjusting the files in /usr/share/pulseaudio/alsa-mixer/paths/ a bit. Currently we only have two paths there because we do not distuingish between Line-Out and Speakers. We probably need to add a third profile there. analog-output.conf currently enables Speaker and Headphone, but sets the volume of Headphone to 0dB (if this is possible) analog-output-headphones.conf currently disables Speaker fully and uses Headphone for proper volume control. Also, make sure to upgrade to test7 before doing any testing. Line_out Headphones Speakers
'Speaker' *
'Headphone' M M M
'Master' * * *
'PCM' * * *
'Front' * *
The Headphone control in alsamixer can only be muted or unmuted and when you mute it it mutes Master Front and Speaker which then have to be manually unmuted to hear anything again. You can see this in my table as "M"
The Speakers output you refer to is actually an *internal* speaker inside the workstation, in fact it is just *one* speaker. The Headphones input is on the front of the workstation as well and when you plug a 3.5mm heaphone plug in there it turns off the internal speaker, as if it was a hardware based switch.
I found it odd that Front affected Headphones, but not Speakers, I guess I thought headphone/speakers were connected in some way.
I'm attaching a text file with the alsamixer output in various states so you can see how hitting 'm' on Headphone affects the other outputs by muting them.
The other thing to mention is that sometimes when adjusting PCM and Front in alsamixer the Master would be be affected. Sometimes it would *jump* down to the lowest level and I thought I saw it progressively adjust Master at one point too.
>Also, make sure to upgrade to test7 before doing any testing.
How do I get this? what package is this? Can I just yum update? or do I need to reinstall?
I just did this after testing and it looks like I'm at the latest:
[root@cam ~]# yum update
Loaded plugins: refresh-packagekit
Setting up Update Process
No Packages marked for Update
[root@cam ~]# yum repolist
Loaded plugins: refresh-packagekit
repo id repo name status
adobe-linux-i386 Adobe Systems Incorporated enabled: 17
rawhide Fedora - Rawhide - Developmental packages for the next Fedora release enabled: 14,882
rpmfusion-free-rawhide RPM Fusion for Fedora Rawhide - Free enabled: 462
rpmfusion-nonfree-rawhide RPM Fusion for Fedora Rawhide - Nonfree enabled: 118
tools.gss tools.gss enabled: 12
repolist: 15,491
John
Created attachment 360121 [details]
alsamixer_-c0 output in three states
Created attachment 360122 [details]
table of how alsamixer settings affect the real audio outs.
Lennart, any update on this ? Fixed upstream now, will prepare a new upload soon. pulseaudio-0.9.20-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/pulseaudio-0.9.20-1.fc12 pulseaudio-0.9.21-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/pulseaudio-0.9.21-1.fc12 pulseaudio-0.9.21-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. pulseaudio-0.9.21-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. |