[gstreamer-bugs] [Bug 440574] New: gstreamer-properties needs to allow custom ALSA devices

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=440574

  GStreamer | gst-plugins-base | Ver: 0.10.x
           Summary: gstreamer-properties needs to allow custom ALSA devices
           Product: GStreamer
           Version: 0.10.x
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Keywords: usability
          Severity: minor
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: jordan.crouse at amd.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: 2.15/2.16
   GNOME milestone: Unspecified


There are a few audio projects that do all their work through userland ALSA
plugins.  The example I'm most interested is bluetooth-alsa, which uses a
plugin to redirect the incoming alsa output to a bluetooth device.  The audio
device is defined as a custom device in my .asoundrc, but it is not registered
with the kernel, and thus not in the list from /proc/asound/cards.

Gstreamer properties only lets me select from the list of cards in
/proc/asound/cards, and there isn't any option for me to specify a custom
device.  I can change the custom device by hacking the gconf directly (i.e
'audiosink device="plug:cpm.headphone"'), but that gets overwritten again when
start gstreamer-properties again.  Please provide an option for a user to
easily specify a custom device.



Other information:


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=440574.