Splitmuxsink cannot create multiple files when using with tee and omxh264dec

Andrew Max drodevilosun at gmail.com
Wed Sep 25 16:34:22 UTC 2019


Splitmuxsink cannot create multiple files when using it with rtspsrc and
omxh264dec.

Pipeline 1: (Create only 1 file with 46KB)

gst-launch-1.0 rtspsrc
location=rtsp://192.168.1.127:8000/Streaming/Channels/102 protocols=4
latency=0 name=myrtsp drop-on-latency=true  user-id=admin user-pw=admin
myrtsp. ! capsfilter caps=application/x-rtp,media=video ! rtph264depay ! 
tee name=t ! h264parse ! omxh264dec ! appsink sync=true  t. ! queue !
h264parse ! splitmuxsink location=./%d.h264 async-handling=true
name=filesink max-size-byte=2000000 max-size-time=2000000000

It cannot create multiple file.

But when I remove "/Streaming/Channels/102", it can create multiple file:

Pipeline 2: (Can create multiple file)

gst-launch-1.0 rtspsrc location=rtsp://192.168.1.127:8000/ protocols=4
latency=0 name=myrtsp drop-on-latency=true  user-id=admin user-pw=admin
myrtsp. ! capsfilter caps=application/x-rtp,media=video ! rtph264depay ! 
tee name=t ! h264parse ! omxh264dec ! appsink sync=true  t. ! queue !
h264parse ! splitmuxsink location=./%d.h264 async-handling=true
name=filesink max-size-byte=2000000 max-size-time=2000000000


I also tried with avdec_h264: It can create multiple file:

Pipeline 3: (Can create multiple file)
gst-launch-1.0 rtspsrc
location=rtsp://192.168.1.127:8000/Streaming/Channels/102 protocols=4
latency=0 name=myrtsp drop-on-latency=true  user-id=admin user-pw=admin
myrtsp. ! capsfilter caps=application/x-rtp,media=video ! rtph264depay ! 
tee name=t ! h264parse ! avdec_h264 ! appsink sync=true  t. ! queue !
h264parse ! splitmuxsink location=./%d.h264 async-handling=true
name=filesink max-size-byte=2000000 max-size-time=2000000000

Is there any wrong with tee when connect with splitmuxsink? 
I found that buffer which was sent to downstream is invalid PTS (function
handle_mq_input() in gstmiltifilesink.c). So, it will assign timestamp to
DTS. I am still investigating this problem.




--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/


More information about the gstreamer-devel mailing list