[gstreamer-bugs] [Bug 640811] New: discoverer async api does not work (as expected)

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=640811
  GStreamer | gst-plugins-base | unspecified

           Summary: discoverer async api does not work (as expected)
    Classification: Desktop
           Product: GStreamer
           Version: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: ensonic at sonicpulse.de
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: ---


I have switched from using the sync API to the async API in discoverer. I have
a file-browser in in the selection callback I start discovering the selected
file.

When I do it like this:
gst_discoverer_stop (self->priv->dc);
gst_discoverer_discover_uri_async (self->priv->dc, uri);
gst_discoverer_start (self->priv->dc);

_discover_uri_async() starts discovering immediately, it does not emit the
::discovered() signal and _start() blocks.

Using the API like this works, but is not obvious for me:
gst_discoverer_stop (self->priv->dc);
gst_discoverer_start (self->priv->dc);
gst_discoverer_discover_uri_async (self->priv->dc, uri);

Two goals for this bug:
- clarify the docs
- ensure it does not hang.

I am not sure whats the intention of the "can_run" in _discover_uri_async(). If
I ensure that _discover_uri_async() won't call _start() everything is fine.

-- 
Configure bugmail: https://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.