Hello,
We've developped a PushSrc based element (with gst 0.10) and it works well except when we want to show the frames on autovideosink, it seems to be stuck to the first image. The element creates a frame from an rtp/udp flow. The pipeline is the simplest : gst-launch oursrc ! ffmepgcolorspace ! autovideosink We get a warning saying that : ... 0:00:00.173991047 22569 0x8052050 WARN bin gstbin.c:2399:gst_bin_do_latency_func:<pipeline0> failed to query latency ... 0:00:00.681874400 22569 0xb2a07910 WARN bin gstbin.c:2395:gst_bin_do_latency_func:<pipeline0> did not really configure latency of 0:00:00.200000000 (the fps is 5) When using fakesink, we see the buffers passing. Can the latency problem be the cause ? Can it be with these lines ? gst_base_src_set_live(GST_BASE_SRC (filter), TRUE); gst_base_src_set_format (GST_BASE_SRC (filter), GST_FORMAT_TIME); gst_base_src_set_do_timestamp (GST_BASE_SRC (filter), TRUE); Thanks for your help, Jonathan _______________________________________________ gstreamer-devel mailing list [hidden email] http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
I'm a little bit further in the comprehension but this need help !
The problem seems to be that a segment event is not sent. If I put a "gst_base_src_new_seamless_segment" in the _create function, thinks are better, it is not realtime and it crash regularly but at least, it gives refresh in autovideosink. Compared to videotestsrc, it lacks : /GstPipeline:pipeline0/GstFakeSink:fakesink0: last-message = "event ******* (fakesink0:sink) E (type: 102, GstEventNewsegment, update=(boolean)false, rate=(double)1, applied-rate=(double)1, format=(GstFormat)GST_FORMAT_TIME, start=(gint64)0, stop=(gint64)-1, position=(gint64)0;) 0x80608c0" between the PLAYING and the clock setting but I don't know where to look for. If someone have a hint, it will be highly appreciated ! Thanks, Jonathan On 11/20/2012 10:25 AM, Jonathan Demeyer wrote: > Hello, > > We've developped a PushSrc based element (with gst 0.10) and it works > well except when we want to show the frames on autovideosink, it seems > to be stuck to the first image. The element creates a frame from an > rtp/udp flow. > > The pipeline is the simplest : > gst-launch oursrc ! ffmepgcolorspace ! autovideosink > We get a warning saying that : > ... > 0:00:00.173991047 22569 0x8052050 WARN bin > gstbin.c:2399:gst_bin_do_latency_func:<pipeline0> failed to query latency > ... > 0:00:00.681874400 22569 0xb2a07910 WARN bin > gstbin.c:2395:gst_bin_do_latency_func:<pipeline0> did not really > configure latency of 0:00:00.200000000 > > (the fps is 5) > > When using fakesink, we see the buffers passing. > > Can the latency problem be the cause ? > Can it be with these lines ? > gst_base_src_set_live(GST_BASE_SRC (filter), TRUE); > gst_base_src_set_format (GST_BASE_SRC (filter), GST_FORMAT_TIME); > gst_base_src_set_do_timestamp (GST_BASE_SRC (filter), TRUE); > > Thanks for your help, > > Jonathan > > _______________________________________________ > gstreamer-devel mailing list > [hidden email] > http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel > _______________________________________________ gstreamer-devel mailing list [hidden email] http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
Free forum by Nabble | Edit this page |