[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


Ronald Bultje changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rbultje at ronald.bitfreak.net




------- Comment #22 from Ronald Bultje  2006-05-29 14:51 UTC -------
Hi,

this patch should really be sent to the gstreamer people, I think it has some
great additions that we'd love to see in a next GNOME release.

About mute&record: both your interpretations are correct, those were the
intended meanings.

About grouping: placing capture things in the playback tab was a bug, this
patch fortunately fixes that. A radiobutton/combobox has the disadvantage that
you cannot select 'none'. In addition (more technically), API for deciding
whether capture is exclusive or >1 is currently missing in GStreamer, although
OSS/ALSA both expose this as a property. A patch for this would be appreciated,
but I'd still recommend to leave the checkbox as-is for now. I'll get flamed by
the HIG people, but again, there's nothing better right now. Maybe I'll write a
new widget: a unselectable radiobox (round, like radiobutton, to indicate
exclusiveness, but with a checkbox instead of a circle to indicate
unselectability).

About mute/0% volume: this is a system bug that we cannot fix. You can do ugly
hacks around, but I can always think of situations that will break it and
provide a worse user experience. Let's please leave it as is, at least it
doesn't break too badly in common use cases.

Anything else I should comment on?


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