Your pipeline will probably consume buffers as fast as possible by remuxing
the 120 second segment to 15 second segments as quickly as possible. Since
playlist-length=5, your playlist will start dropping older segments, leaving
the client loosing track of what it is supposed to be playing.
When using rtmpsink, you are using tsdemux and flvmux to remux the stream.
This will give the pipeline a clue on what the actual rate of the video
stream is. Since rtmpsink's sync properly is true by default your stream
will play at real-time.
Note that there is little need to "keep the hlssink" running. It's done when
it's done and it is up to your WWW server to keep serving the files. You do
need, however, make sure that the playlist (.m3u8) contains all the segments
that you want to play (e.g. by setting playlist-length=0 and max-files=0 on
hlssink).
If you want to remux the 120 second segments to 15 second segments, you
should probably demux and mux the transport stream (e.g. - tsdemux - queue -
h264parse - queue - mpegtsmux and fiddle the audio branch in there as well
if applicable).
--
Sent from:
http://gstreamer-devel.966125.n4.nabble.com/_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Locked
