Cant open RTSP stream with GStreamer on Jetson

Accelerated Computing Intelligent Video Analytics DeepStream SDK
,
1

• Hardware Platform (Jetson / GPU) Jetson Orin Nano
• DeepStream Version 7.0
• JetPack Version (valid for Jetson only) 6.0
• TensorRT Version 8.6.2

There is one RTSP stream in particular that is bugging me.

I am running this command on my computer and it opens that rtsp stream just fine. VLC can also open it.


GST_DEBUG=3 gst-launch-1.0 rtspsrc location=<my_rtsp_url> protocols=tcp ! rtph265depay ! h265parse ! avdec_h265 ! autovideosink

The Jetson can also open this rtsp stream using VLC but not with GStreamer. I get this

image
image951×250 25 KB

I don’t know why I am getting this and have no idea on how to fix it. Strangely enough, it finds the stream
image

I get these warnings when using the command on my computer

image
image1810×452 108 KB

3

from the error, it is because the client can’t get the response from the camera. can you try other protocol? for example, gst-launch-1.0 rtspsrc location=<my_rtsp_url> protocols=udp ! fakesink. if it still can’t work. I suggest using network capture tool to analyze the network interaction when playing using VLC.

4

It didn’t work with protocol udp either. What network capture tool do you recommend?Also, what should I look for when analyzing differences between the streams I can read and the one I can’t?

5

RTSP protocol is public. you can use wireshark to capture network packets. then analyze the RTSP interaction. for example, what the client send, when the client receive. why using VLC is fine.

1 Like
6

In this RTSP stream I can’t read, I am acessing the cameras through a DVR. In the ones I can read, I am accessing them directly. Is there any difference to a GStreamer pipeline or additional steps I have to take when acessing the camera through DVR?

7

About “In the ones I can read, I am accessing them directly”, How did you access? is it a different rtsp address?

8

yes, a different rtsp address.

9

I found out what the problem was.
This is the result I was getting

image
image1850×385 81.3 KB

After I removed gstreamer1.0-plugins-ugly. I got this

image
image1829×595 167 KB

Any ideas on why this happens?

10

Sorry for the late reply, Is this still an DeepStream issue to support? Thanks! why did you remove gstreamer1.0-plugins-ugly? could you share the two RTSP addresses? wondering if there is any difference.

11

Not sure if I can share the rtsp streams, I did remove the lib because I saw someone doing it here Dahua ip camera with jetson nano - #3 by junshengy . It might be an issue with the camera but I found it really strange. It worked on my notebook with that lib but I had to remove it for it to work on jetson. I just wanted more details of what might be causing this.

12

from the error, it is RTSP protocol interaction issue, not a DeepStream issue. I suggest using network capture tool to analyze the network interaction when playing using VLC and gstreamer. why is play by VLC fine？

13

Ok, I will try that. Maybe VLC can open it because it uses another library or method to do it.

14

Sorry for the late reply, Is this still an DeepStream issue to support? Thanks!

15

I found a workaround. It doesn’t seem to be a Deepstream issue, it probably is related to camera vendor. I hope I don’t have any more problems with these cameras. What cameras do Deepstream devs use to test rtsp features?Just in case I need to switch my cameras, I want to find cameras that are guaranteed to work with Deepstream.

16

Thanks for the updare! any camera supporting the standard RTSP protocol.