ERROR from depay_elem4: The stream is in the wrong format

Please provide complete information as applicable to your setup.

• Hardware Platform (Jetson / GPU) - Jetson Xavier
• DeepStream Version - 4.0.1
• JetPack Version (valid for Jetson only) - 4.2.2
• TensorRT Version -
• NVIDIA GPU Driver Version (valid for GPU only)

I am running the deepstream-app for 10 cameras connected to a NVR through RTSP(h264). It runs properly for a few hours and then randomly it stops with the following error.

PosixMemMap:71 [12] mmap failed
ERROR from depay_elem4: The stream is in the wrong format
Debug info: gstrtph264depay.c(1270):gst_rtp_h264_depay_process():/GstPipeline:pipeline/GstBin:multi_src_bin/GstBin:src_sub_bin4/GstRtpH264Depay:depay_elem4:
NAL unit type 27 not supported yet

Surprisingly, it automatically starts working after sometime again randomnly. Is there any way to properly debug this issue?

According to the spec of “RTP Payload Format for H.264 Video”, "NAL unit type 27 " is MTAP24 aggregation packet. Seems current rtph264depay does not support it yet.

Only the following types are supported, please confirm with who generate the RTSP stream to make sure the RTSP server provides the following NAL unit types rtp payload :
Single NAL unit packet

How do we check if the RTSP stream is generated properly? We have connected it to IP cameras and so the NVR is the RTSP Server for us. So, all that we can manipulate are the Camera Configuration Settings.

If the rtsp stream is in the wrong format, how does deep stream run properly for a couple of hours and stops. If the stream format is inherently wrong, deep stream should not run it from the get go. What could be the explanation for this unexpected behaviour?

Hi sivaishere96 ,

Please help to open a new topic for your issue. Thanks