Result of multifilesink is executed only when an RTSP client is connected


I run RTSP and multifilesink at the same time.
However, the result of multifilesink is executed only when an RTSP client is connected.
Here is the script and flow:

test-launch --gst-debug=3 "v4l2src device=/dev/video0 \
   ! queue \
   ! tee name=w \
   ! queue \
   ! videoconvert \
   ! video/x-raw, format=(string)GRAY8 \
   ! multifilesink location=/tmp/%d.y max-files=100 -e w. \
   ! queue \
   ! nvvidconv \
   ! video/x-raw(memory:NVMM), width=1920, height=1080 \
   ! omxh264enc \
   ! h264parse \
   ! queue \
   ! rtph264pay name=pay0 pt=96 \
   " " " " "
1. Run test-launch (multifilesink using with tee)
2. client RTSP connect
3. Check client RTSP normal output
4. client RTSP stop

Sections 2 and 3 where multifilesink files are created in the above process.
Multifilesink file is created only when RTSP client is connected.
Can’t I create a multifilesink file regardless of the RTSP client connection? (created from number 1)

RTSP is on demand so the pipeline starts when the connection is requested and constructed. For running streaming continuously, please set up UDP streaming. You can refer to
Gstreamer TCPserversink 2-3 seconds latency - #5 by DaneLLL
Jetson 4k Encoding -> Decoding Pipeline and latency - #11 by DaneLLL

We have deprecated omx plugins. Please use nvv4l2h264enc or nvv4l2h265enc

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.