- For sink elements,
sync=1is necessary, otherwise the pipeline will run as quickly as possible, thus ignoring synchronization.
2.I tested the following pipeline and it works fine. I setmax-batch-size=10andlive-source=1(run about 13 hours)
gst-launch-1.0 nvmultiurisrcbin port=9000 ip-address=localhost batched-push-timeout=33333 max-batch-size=10 drop-pipeline-eos=1 live-source=1 uri-list=xxxxxx.m3u8 width=720 height=480 ! nvmultistreamtiler width=720 height=480 ! nveglglessink
3.Set batch-size to 1 and let add/remove APIs update this logic cause pipeline slowdown and hence the maxBatchSize usage.This is a known issue,Use new streammux to avoid this issue
USE_NEW_NVSTREAMMUX=yes gst-launch-1.0 nvmultiurisrcbin port=9000 ip-address=localhost batched-push-timeout=33333 max-batch-size=1 drop-pipeline-eos=1 live-source=1 uri-list=http://10.19.226.168:8080/live/livestream.m3u8 width=720 height=480 ! nvmultistreamtiler width=720 height=480 ! nveglglessink