[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 #14 from Viktor Peters  2006-05-08 12:51 UTC -------
(In reply to comment #13)
> (In reply to comment #12)
> > Special treatment of such tracks, so the switch controls the 'record' and not
> > the 'mute' flag?
> 
> I have hacked gnome-volume-control to set the 'record' flag if the track name
> ends in 'Capture'. This is a bit nasty but I guess it will do until/unless
> GstMixerTrack is modified to allow an app to find out whether a track has a
> playback/capture (mute/record) switch. I'll add this stuff to my patch for bug
> #313495.

I think, I should undo my decision swapping the meaning of gstreamer 'record'
and 'mute' for capture tracks. 'GST_MIXER_TRACK_RECORD' is just a confusing
appellation. Should be 'GST_MIXER_TRACK_RECORD_AUDIBLE' or something like that.
But I'm not the only one, who got confused. The gnome-volume-control author
bound the record toggle button with the gstreamer record flag instead with the
mute flag...

> Speaking from an HIG perspective I think the way that alsamixer (and now
> gnome-volume-control) present exclusive capture groups is unintuitive. I have a
> couple of ideas about how to fix this, what do you think about them?

Uff, Ahhh, HIG! Sorry, but I'm definitly the last person who you should talking
about HIG stuff... :)


-- 
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.