differences between windows and ubuntu- simple pipeline

Dudi.r dudi017 at gmail.com
Mon Mar 10 06:08:33 PDT 2014


Hi,

Im sorry but this is the log on the server side:


Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
/GstPipeline:pipeline0/GstCapsFilter:capsfilter0.GstPad:src: caps =
application/
x-rtp, payload=(int)96, media=(string)video, clock-rate=(int)90000,
encoding-nam
e=(string)H264
/GstPipeline:pipeline0/GstUDPSink:udpsink0.GstPad:sink: caps =
application/x-rtp
, payload=(int)96, media=(string)video, clock-rate=(int)90000,
encoding-name=(st
ring)H264
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Got EOS from element "pipeline0".
Execution ended after 4181823860 ns.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
/GstPipeline:pipeline0/GstUDPSink:udpsink0.GstPad:sink: caps = NULL
/GstPipeline:pipeline0/GstCapsFilter:capsfilter0.GstPad:src: caps = NULL
Setting pipeline to NULL ...



server:
gst-launch-0.10 -v filesrc location=file.pcap ! pcapparse src-port=58694  !
application/x-rtp, payload=(int)96, media=(string)video, 
clock-rate=(int)90000, encoding-name=(string)H264  !  udpsink  port=5000 

client:
gst-launch-0.10 udpsrc port=5000 caps="application/x-rtp,
media=(string)video, clock-rate=(int)90000, encoding-name=(string)H264,
payload=(int)96" ! gstrtpjitterbuffer latency=1000 , do-lost=true !
rtph264depay ! queue ! ffdec_h264 ! autovideosink 

I'm familiar with the sprop parameter, but the server doesn't show it.. :/
thank you.




--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/differences-between-windows-and-ubuntu-simple-pipeline-tp4665864p4665871.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.


More information about the gstreamer-devel mailing list