[gstreamer-bugs] [Bug 336075] ALSA emu10k1 mixer tracks are wrongly classified as playback tracks

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=336075
 GStreamer | gst-plugins-base | Ver: 0.10.x





------- Comment #11 from Sam Morris  2006-05-07 15:38 UTC -------
I think I agree with what you are describing, it's just that toggling (what
gnome-volume-control presents as) the 'Microphone Capture' switch does not
affect the capture switch of ALSA's 'Microphone' control. Instead, it affects
the control's playback switch. I will describe what happens in more detail:

        I now have a series of Switches in gnome-volume-control labelled
'Microphone Capture', 'Phone Capture' and so on.

        I expected enabling one of them to disable the rest (as their ALSA
controls are all in the same capture group). But instead, they toggle on and
off individually.

        From watching the changes to the tracks in the Playback tab, I can see
that toggling the 'Microphone Capture' switch also toggles the mute icon
underneath the 'Microphone' track in the Playback tab. The same is true for CD,
Phone, Line-in and so on.

        (This association does not hold in reverse; if I mute the 'Microphone'
track in the Playback tab then the 'Microphone Capture' switch does not get
toggled.)

        These tracks all have the same capabilities: pvolume pvolume-joined
pswitch pswitch-joined cswitch cswitch-exclusive

        It has just occurred to me that gnome-volume-control is toggling the
'mute' flag of the GstMixerControls. gnome-volume-control needs a way to know
whether to toggle a GstMixerTrack's 'mute' or 'record' flags when the user
toggles the track's switch.

        I should mention here that if a GstMixerTrack has no channels then
gnome-volume-control presents it as a 'switch' which is basically a checkbox
that toggles on/off. Currently the switch only controls a GstMixerTrack's
'mute' flag.

Another strange thing is now happening:

        I now have both 'Bass' and 'Bass Capture' tracks (the 'Bass' ALSA
control is described by amixer as having only the 'volume' capability).

        Toggling the mute flag of either track affects the mute flag of the
other as expected; changing the volume of the 'Bass' track only changes the
volume of 'Bass Capture' if the tracks are not muted. 

        Changing the volume or record flags of 'Bass Capture' doesn't affect
'Bass' at all.

        From watching alsamixer, I can see that the 'Bass' track is the one
that actually controls ALSA's 'Bass' control.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.