[gstreamer-bugs] [Bug 434260] New: PulseAudio plugin takes long to determine whether PulseAudio server is running.
bugzilla-daemon at bugzilla.gnome.org
Sat Apr 28 20:10:08 PDT 2007
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:
GStreamer | gst-plugins | Ver: 0.10.12
Summary: PulseAudio plugin takes long to determine whether
PulseAudio server is running.
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: gattahernan at hotmail.com
QAContact: gstreamer-bugs at lists.sourceforge.net
GNOME version: 2.17/2.18
GNOME milestone: Unspecified
Whenever I launch a GStreamer-based application and the Audio output settings
are set to Autodetect, GStreamer first tries to see if pulseaudiosink is a good
output and it takes around ten seconds to figure out that the PulseAudio server
is not running to then fall into a plugin that works. Setting the output plugin
to ALSA for example, works instantly. The PulseAudio plugin has a Rank of 256
while alsasink has 253, so the first is chosen probed first.
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=434260.
More information about the Gstreamer-bugs