[gstreamer-bugs] [Bug 482946] New: warning in demuxer when receiving GST_EVENT_LATENCY

[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=482946

  GStreamer | gst-ffmpeg | Ver: 0.10.2
           Summary: warning in demuxer when receiving GST_EVENT_LATENCY
           Product: GStreamer
           Version: 0.10.2
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: gst-ffmpeg
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: yann.gilquin at purplelabs.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Please describe the problem:
When an event GST_EVENT_LATENCY (since 0.10.12) is received on a src pad, it's
not managed and the gst_ffmpegdemux_src_event func returns FALSE.

This leads to the following warning on gstreamer side :

Internal GStreamer error: clock problem.  Please file a bug at
http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.
build/host/gst/gstpipeline.c(487): gst_pipeline_change_state ():
/playeraudiovideo:
Failed to configure latency of 0:00:00.000000000 

Steps to reproduce:
1. create a pipeline with ffdemux element and set it to PLAYING state
2. 
3. 


Actual results:
You get the previous warning and latency cannot be set.

Expected results:
The event should be send upstream.

Does this happen every time?
Yes.

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