RTSP re-connects to downstream RTMP

[rory.hughes1]

Please provide complete information as applicable to your setup.

**• Hardware Platform (Jetson / GPU) - GPU
**• DeepStream Version - 6.3
**• TensorRT Version - not with machine currently to check
**• NVIDIA GPU Driver Version (valid for GPU only) - not with machine currently to check, fairly recent
**• Issue Type( questions, new requirements, bugs) - questions
**• 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)

Hi all,

I have an issue that I’m hoping has a simple solution. I don’t think that this has been addressed elsewhere on the forum. I have a deepstream pipeline that ingest rtsp streams, does the usual mux, inference, track, demux and then outputs rtmp streams. I am using an nvurisrcbin components on the input and using the rtsp-reconnect-interval argument to facilitate re-connection if the input stream drops. This seems to work as intended on the input stream, but the pipeline still fails on the output stream. How should I properly configure post-demux components to ensure that the pipeline stays resilient even when the rtsp input stream drops? Note I am using the python bindings for deepstream.

For completeness here is roughly my pipeline:

nvurisrcbin -> muxer -> pgie -> tracker -> analytics -> nvstreamdemux -> nvvideoconvert -> nvdsosd -> nvvideoconvert -> h264parse -> flvmux -> rtmpsink

Any help is much appreciated!

[fanzh]

@rory.hughes1

but the pipeline still fails on the output stream.

seems rtmpsink can’t send data again after resuming receiving data. flvmux and rtmpsink are Gstreamer opensource plugin, please refer to the reference to check if there are some resilient parameters.

[rory.hughes1]

Is there an Nvidia-suggested set of components for resilient live streaming of RTMP? For additional info, my specific error is
ERROR - (pipeline0.rtmp_sink_0) gst-resource-error-quark: Could not write to resource. (10): gstrtmpsink.c(283): gst_rtmp_sink_render (): /GstPipeline:pipeline0/GstRTMPSink:rtmp_sink_0:

[rory.hughes1]

I solved this issue!

For future readers, the error
ERROR - (pipeline0.rtmp_sink_0) gst-resource-error-quark: Could not write to resource. (10): gstrtmpsink.c(283): gst_rtmp_sink_render (): /GstPipeline:pipeline0/GstRTMPSink:rtmp_sink_0

Is not because components are unable to write to the rtmpsink it’s that the rtmpsink is unable to write to the rtmp server (outwith the deepstream application). It was an external configuration change that was needed.