xvimagesink: Received buffer without a new-segment. Assuming timestamps start from 0.

[Uday Verma]

Hello All,

I am writing a test program where I run a simple pipeline like this:

videotestsrc (is-live = true) -> capsfilter -> colorspace -> queue ->
tee -> fakesink (just to run the pipeline without a not-linked error).

Now to test my gstreamer-fu, I am randomly adding/removing new
xvimagesinks to the tee on a running pipeline.  My goal is to add and
remove xvimagesink on a running pipeline without ever causing the
pipeline to hault (or the video in the xvimagesink to pause).  I am at
the adding phase right now.

Whenever i add an xvimagesink to the tee I get the warning:

** (test:14748): WARNING **: Internal data flow problem. :
gstbasesink.c(2877): gst_base_sink_chain_unlocked ():
/GstPipeline:pipeline0/GstBin:bin12/GstXvImageSink:xvimagesink12:
Received buffer without a new-segment. Assuming timestamps start from 0.

The video keeps running sometimes, and sometimes it pauses.  Any
ideas/pointers on how I can get rid of this warning?

Here's the code for your reference:

Pastebin: http://pastie.org/660161
Permanent: http://www.soundc.de/code/tmp/test.c

Thanks in Advance,
Uday

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

[Uday Verma]

Alright, so setting sync=true on the xvimagesink stopped giving out
those warning.  But still after adding around 18-20 xvimagesinks the
pipeline just stops (the video in all sinks pauses).

I watched the logs with GST_DEBUG=4 and got this.   Let me know if you
need more info.

Thanks,
Uday

Log:
-----------------------------------------------
0:00:24.901936787 16677      0x2033010 DEBUG     GST_ELEMENT_PADS
gstelement.c:2575:gst_element_pads_activate:<bin1> pads_activate with
active 1
0:00:24.901945030 16677      0x2033010 DEBUG             GST_PADS
gstpad.c:639:gst_pad_set_active:<bin1:sink> activating pad from push
0:00:24.901952125 16677      0x2033010 DEBUG     GST_ELEMENT_PADS
gstelement.c:2605:gst_element_pads_activate:<bin1> pads_activate
successful
0:00:24.901958563 16677      0x2033010 DEBUG                  bin
gstbin.c:1900:gst_bin_sort_iterator_free:<bin1> free
0:00:24.901965379 16677      0x2033010 DEBUG                  bin
gstbin.c:2403:gst_bin_change_state_func:<bin1> check async elements
0:00:24.901993290 16677      0x2033010 DEBUG                  bin
gstbin.c:798:find_message:<bin1> we found a message 0x2253cf0 from
xvimagesink1 matching types 00100000
0:00:24.902002063 16677      0x2033010 DEBUG           GST_STATES
gstbin.c:2425:gst_bin_change_state_func:<bin1> done changing bin's
state from READY to PAUSED, now in READY, ret ASYNC
0:00:24.902008791 16677      0x2033010 DEBUG           GST_STATES
gstelement.c:2442:gst_element_change_state:<bin1> element will change
state ASYNC
0:00:24.902014795 16677      0x2033010 DEBUG           GST_STATES
gstelement.c:2387:gst_element_set_state_func:<bin1> returned ASYNC
** (test:16677): DEBUG: Total 2 sinks.
0:00:24.902034024 16677      0x2033010 INFO            GST_STATES
gstbin.c:1632:gst_bin_get_state_func:<pipeline0> getting state
0:00:24.902040439 16677      0x2033010 DEBUG           GST_STATES
gstelement.c:1859:gst_element_get_state_func:<pipeline0> getting
state, timeout 99:99:99.999999999
0:00:24.902046899 16677      0x2033010 DEBUG           GST_STATES
gstelement.c:1864:gst_element_get_state_func:<pipeline0> RETURN is
ASYNC
0:00:24.902052705 16677      0x2033010 INFO            GST_STATES
gstelement.c:1900:gst_element_get_state_func:<pipeline0> waiting for
element to commit state


On Sun, Oct 18, 2009 at 11:29 PM, Uday Verma <[hidden email]> wrote:

> Hello All,
>
> I am writing a test program where I run a simple pipeline like this:
>
> videotestsrc (is-live = true) -> capsfilter -> colorspace -> queue ->
> tee -> fakesink (just to run the pipeline without a not-linked error).
>
> Now to test my gstreamer-fu, I am randomly adding/removing new
> xvimagesinks to the tee on a running pipeline.  My goal is to add and
> remove xvimagesink on a running pipeline without ever causing the
> pipeline to hault (or the video in the xvimagesink to pause).  I am at
> the adding phase right now.
>
> Whenever i add an xvimagesink to the tee I get the warning:
>
> ** (test:14748): WARNING **: Internal data flow problem. :
> gstbasesink.c(2877): gst_base_sink_chain_unlocked ():
> /GstPipeline:pipeline0/GstBin:bin12/GstXvImageSink:xvimagesink12:
> Received buffer without a new-segment. Assuming timestamps start from 0.
>
> The video keeps running sometimes, and sometimes it pauses.  Any
> ideas/pointers on how I can get rid of this warning?
>
> Here's the code for your reference:
>
> Pastebin: http://pastie.org/660161
> Permanent: http://www.soundc.de/code/tmp/test.c
>
> Thanks in Advance,
> Uday
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel