Similar as udpsrc but to pass RTP packets directly to gstreamer

bojan74 bojan.flander at gmail.com
Sun Jan 22 14:04:52 UTC 2017


I must add additional info and corrections for what I wrote before.

Now I was testing will full h264 video that is input for my pipeline and I
saw:
- both mp4 files (with udpsrc and with appsrc) contain full video, so
nothing is lost
- udpsrc video length is 3:27 and it normally plays till end (time marker
slider is going from start till end and also seeking is possible anywhere)
- appsrc video length is 2:15 but full video ends at 1:30. It is played 2-3
times faster then with udpsrc and so ends at 1:30. And I don't know from
where gets 2:15 for length info. If I click between 1:30 and 2:15 in player
marker jump to start.

To repeat again my whole pipeline is like this:
udpsrc/appsrc -> rtpjitterbuffer -> rtph264depay -> h264parse -> mp4mux ->
filesink

appsrc caps are in both versions: 
application/x-rtp, media=(string)video, clock-rate = (int)90000,
encoding-name = (string)H264

and also other settings are mostly same.

But it looks that there are some problem with time. Currently I don't set
anything with 
	  GST_BUFFER_PTS (buffer) = 
	  GST_BUFFER_DURATION (buffer) = 

Is it necessary to use this in case of my pipeline?
If yes, what do I need to set here if I am feeding appsrc with RTP packets? 
To use RTP timestamp fro GST_BUFFER_PST and to calculate duration from RTP
header timestamp for GST_BUFFER_DURATION?




--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Similar-as-udpsrc-but-to-pass-RTP-packets-directly-to-gstreamer-tp4681541p4681585.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.


More information about the gstreamer-devel mailing list