AW: the humble videotestsrc element is magical !!!

[Bernhard Graaf]

Hi Andreas,

May you give us the total server and client pipelines for the not working
scenario?

Bernhard

-----Ursprüngliche Nachricht-----
Von: gstreamer-devel [mailto:gstreamer-devel-bounces at lists.freedesktop.org]
Im Auftrag von Andres Gonzalez
Gesendet: Donnerstag, 4. August 2016 18:35
An: gstreamer-devel at lists.freedesktop.org
Betreff: the humble videotestsrc element is magical !!!

Hi,

I am trying to stream using tcpserversink and the various muxers.  For a
server example:

gst-launch-1.0 -vv videotestsrc is-live=true ! queue ! videoconvert !
x264enc byte-stream=true ! h264parse config-interval=1 ! queue ! matroskamux
! queue leaky=2 ! tcpserversink port=50010 host=0.0.0.0
recover-policy=keyframe sync-method=latest-keyframe sync=false

For the client on a different local box: 

gst-launch-1.0 -vv tcpclientsrc host=192.168.1.80 port=50010 typefind=true
do-timestamp=false ! matroskademux ! typefind ! avdec_h264 ! autovideosink

this works perfect. However, if I use *any* other source element in the
server pipeline, source elements that are known to work on the server box,
the *client* errors out with:

ERROR: from element /GstPipeline:pipeline0/GstTCPClientSrc:tcpclientsrc0:
Internal data flow error.
Additional debug info:
gstbasesrc.c(2943): gst_base_src_loop ():
/GstPipeline:pipeline0/GstTCPClientSrc:tcpclientsrc0:
streaming task paused, reason not-negotiated (-4)
ERROR: pipeline doesn't want to preroll.

I have looked at the dot files created by the server gst-launch for both
cases, that is, the exact same pipeline but using different src elements. In
other words, the pipeline is exactly the same from the first queue element
to the end of the pipeline.   The only difference I find is that the
pipeline using videotestsrc inserts an additional capsfilter element
immediately after it. The linking and state transitions on the server also
appear to be the same for both cases.

So it appears that these other server sources are doing something different
than what the videotestsrc is doing, and that difference is effecting the
negotiation on the client. 

Any ideas on how I should configure the server sources so the client will
negotiate correctly?   

Thanks,

-Andres



--
View this message in context:
http://gstreamer-devel.966125.n4.nabble.com/the-humble-videotestsrc-element-
is-magical-tp4678965.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.
_______________________________________________
gstreamer-devel mailing list
gstreamer-devel at lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel