[Bug 773110] autoaudiosink appears completely non-configurable

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=773110

Tim-Philipp Müller <t.i.m at zen.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
                 CC|                            |t.i.m at zen.co.uk
          Component|gst-plugins-base            |gst-plugins-good

--- Comment #1 from Tim-Philipp Müller <t.i.m at zen.co.uk> ---
> autoaudiosink appears to be completely non-configurable.

Well, its entire purpose is to try to do its best without configuration :)


> I can find no documentation on "rank" for plugins, let alone how a
> user would adjust them.

Google seems to throw up plenty of results, including our API docs. In case
this was your way of asking how to do this, one would use
gst_plugin_feature_set_rank() after looking up the plugin feature (element
factory) from the GStreamer registry in one's application after calling
gst_init() and before starting the pipeline.


> It certainly doesn't appear to try jacksink.

Ah no? It certainly does here. It might also depend on the pipeline, it will
only try jackaudiosink if it looks like the caps might be compatible. Since
jackaudiosink only accepts F32LE here that may not always be the case.

It may also try alsasink or other sinks before trying jackaudiosink.


> If the user has > 1 audio  interface, autoaudiosink appears to offer
> no way to be configured to use 1

As mentioned above, it's not the purpose of this element to provide a great
deal of configuration options. There are other ways for applications such as
the GstDeviceProvider API to find available audio output elements (although the
jack plugin does not appear to support this yet).


> possibly relying on ALSA's "default" PCM name.

ALSA developers have told me this is not an unreasonable thing to rely on (if I
have understood them correctly at least). What is it you would suggest here?
Not use the "default" at all? Try more/other devices?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.