Bug 520884 - gnome-volume-control has no way to select which device it controls
Summary: gnome-volume-control has no way to select which device it controls
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pulseaudio
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-02 18:54 UTC by John Brier
Modified: 2013-08-14 23:05 UTC (History)
7 users (show)

Fixed In Version: 0.9.21-1.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-31 02:45:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
amixer -c0 (3.83 KB, text/plain)
2009-09-04 13:15 UTC, John Brier
no flags Details
pacmd ls (15.35 KB, text/plain)
2009-09-04 13:16 UTC, John Brier
no flags Details
alsamixer_-c0 output in three states (15.72 KB, text/plain)
2009-09-08 19:35 UTC, John Brier
no flags Details
table of how alsamixer settings affect the real audio outs. (234 bytes, text/plain)
2009-09-08 19:42 UTC, John Brier
no flags Details

Description John Brier 2009-09-02 18:54:15 UTC
Description of problem:

gnome-volume-control controls all outputs on my HP xw4400 workstation (line out and speaker, maybe headphone too)

Version-Release number of selected component (if applicable):

gnome-media-2.27.90.fix-1.fc12.i686

How reproducible:

100% 

Steps to Reproduce:
1. turn sound up with gnome-volume-control
2. 
3. 
  
Actual results:

Notice sound is coming out of line out and speaker in front of system

Expected results:
cannot disable speaker and enable line out

Additional info:
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
05:04.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)


If I use 'alsamixer -c 0' I can control "HDA Intel" "Speaker" output and decrease it but as soon as I adjust audio again with gnome-volume-control it goes back up.

Comment 1 Matthias Clasen 2009-09-03 02:26:33 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 ?

Comment 2 John Brier 2009-09-03 13:35:13 UTC
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.

Comment 3 Bastien Nocera 2009-09-03 15:20:30 UTC
Passing to PulseAudio, as this isn't something gnome-volume-control can do anything about.

Comment 4 Lennart Poettering 2009-09-04 02:35:40 UTC
Please provide the output of "amixer -c0" and "pacmd ls"

Comment 5 John Brier 2009-09-04 13:15:55 UTC
Created attachment 359804 [details]
amixer -c0

Comment 6 John Brier 2009-09-04 13:16:38 UTC
Created attachment 359805 [details]
pacmd ls

Comment 7 Lennart Poettering 2009-09-07 21:58:57 UTC
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.

Comment 8 John Brier 2009-09-08 19:35:09 UTC
		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

Comment 9 John Brier 2009-09-08 19:35:57 UTC
Created attachment 360121 [details]
alsamixer_-c0 output in three states

Comment 10 John Brier 2009-09-08 19:42:02 UTC
Created attachment 360122 [details]
table of how alsamixer settings affect the real audio outs.

Comment 11 Matthias Clasen 2009-10-07 03:37:23 UTC
Lennart, any update on this ?

Comment 12 Lennart Poettering 2009-10-31 02:45:19 UTC
Fixed upstream now, will prepare a new upload soon.

Comment 13 Fedora Update System 2009-11-11 05:07:37 UTC
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

Comment 14 Fedora Update System 2009-11-23 05:23:57 UTC
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

Comment 15 Fedora Update System 2009-11-27 22:00:04 UTC
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.

Comment 16 Fedora Update System 2009-12-01 04:27:35 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.