GNOME Bugzilla – Bug 562781
Latency issue, got told to file report
Last modified: 2008-12-03 11:53:11 UTC
gst-launch-0.10 filesrc location=Ray_Parker_Jr-Ghostbusters.mp3 ! mad ! audioconvert ! faac ! filesink location=/tmp/ghost.aacSetting pipeline to PAUSED ... Pipeline is PREROLLING ... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstSystemClock WARNING: from element /GstPipeline:pipeline0: Internal GStreamer error: clock problem. Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer. Additional debug info: gstbin.c(2196): gst_bin_do_latency_func (): /GstPipeline:pipeline0: Failed to configure latency of 0:00:00.000000000 Got EOS from element "pipeline0". Execution ended after 21157370348 ns. Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... FREEING pipeline ...
I believe this was fixed in gst-plugins-ugly 0.10.10 with this commit: * ext/mad/gstmad.c: (gst_mad_src_event), (gst_mad_chain), (gst_mad_change_state): * ext/mad/gstmad.h: track discont on incomming buffers and set discont on outgoing buffers. Pass unknown events upstreams instead of dropping them. Please recheck.
confirmed, with latest ugly the message is gone