[Bug 702046] New: rtspsrc doesn't produce buffers

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=702046
  GStreamer | gst-plugins-good | git

           Summary: rtspsrc doesn't produce buffers
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: blocker
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: youness.alaoui at collabora.co.uk
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Created an attachment (id=246567)
 --> (https://bugzilla.gnome.org/attachment.cgi?id=246567)
Test code to reproduce rtspsrc bug

After I updated gst-plugins-good to the latest git, my custom pipeline using
rtspsrc stopped working. It seemed like udpsrc was not receiving any packets.

I tracked down the issue to this commit from Wim Taymans : 
http://cgit.freedesktop.org/gstreamer/gst-plugins-good/commit/?id=4fc1f3088b470a89c7e40e5b6e333f9537f12ee9

I am now forced to have a workaround in the code where I wait a certain amount
of time and call gst_element_set_state PLAYING on rtspsrc again in order to
make it work. Without that second set_state, the pipeline simply does not work.

Why was the code there in the first place and why was it removed? and why do I
need to set the state of the element to PLAYING twice in order for it to work ?
Shouldn't rtspsrc sync_state_with_parent on the udpsrc it creates internally?

Note that for some reason, it still works with playbin though, or with a simple
gst-launch pipeline.
Either way, this is a regression that should be fixed.. or someone explains to
me why the custom pipeline does not work!

I have attached a sample test application which can reproduce the bug. It takes
the rtsp url as first argument, then will output something and quit once
rtspsrc signals 'pad-added'. As you will notice, we never receive the
'pad-added' signal, but if you uncomment the g_timeout that sets the element to
playing again, it will work,

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