gst-launch-1.0 rtspsrc location=rtsp://192.168.3.199/h264/ch1/main/av_stream ! rtph264depay ! nvv4l2decoder ! m.sink_0 nvstreammux name=m batch-size=1 width=1920 height=1080 ! nvinfer config-file-path=pgie_config.txt !
nvstreamdemux name=nvdemux nvdemux.src_0 ! queue ! nvvideoconvert ! nvdsosd ! nvvideoconvert ! nvv4l2h264enc ! h264parse ! flvmux ! rtmpsink location=rtmp://192.168.3.200:1935/live/99 sync=false
It works good.
but Move the nvdsosd plugin to the front of the nvstreamdemux plugin It will crash.
gst-launch-1.0 rtspsrc location=rtsp://192.168.3.199/h264/ch1/main/av_stream ! rtph264depay ! nvv4l2decoder ! m.sink_0 nvstreammux name=m batch-size=1 width=1920 height=1080 ! nvinfer config-file-path=pgie_config.txt ! nvvideoconvert ! nvdsosd ! nvvideoconvert ! nvstreamdemux name=nvdemux nvdemux.src_0 ! queue ! nvvideoconvert ! nvv4l2h264enc ! h264parse ! flvmux ! rtmpsink location=rtmp://192.168.3.200:1935/live/99 sync=false
Log:
Setting pipeline to PLAYING …
New clock: GstSystemClock
Progress: (request) Sending PLAY request
Progress: (request) Sending PLAY request
Progress: (request) Sent PLAY request
NvMMLiteOpen : Block : BlockType = 261
NVMEDIA: Reading vendor.tegra.display-size : status: 6
NvMMLiteBlockCreate : Block : BlockType = 261
NvMMLiteOpen : Block : BlockType = 4
Redistribute latency…
===== NVMEDIA: NVENC =====
NvMMLiteBlockCreate : Block : BlockType = 4
Caught SIGSEGV
#0 0x0000007faa57b048 in __GI___poll (fds=0x55d8a36110, nfds=548319822392, timeout=) at …/sysdeps/unix/sysv/linux/poll.c:41
#1 0x0000007faa687e08 in () at /usr/lib/aarch64-linux-gnu/libglib-2.0.so.0
#2 0x00000055a8504b90 in ()
Spinning. Please run ‘gdb gst-launch-1.0 6150’ to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core.
Why?
How to modify this command line to work properly?
**• Hardware Platform (Jetson / GPU)**Xaveir
• DeepStream Version5.0
• JetPack Version (valid for Jetson only)
• TensorRT Version
• NVIDIA GPU Driver Version (valid for GPU only)
• Issue Type( questions, new requirements, bugs)
• How to reproduce the issue ? (This is for bugs. Including which sample app is using, the configuration files content, the command line used and other details for reproducing)
• Requirement details( This is for new requirement. Including the module name-for which plugin or for which sample application, the function description)