Nvinfer not processing frames from second stream

• Hardware Platform Jetson
• DeepStream Version 6.3
• JetPack Version 5.1
• TensorRT Version 5.1

I want to restart pipeline once FPS reaches 0, here’s my previous question about this.
I’m restarting pipeline by changing states:

pipeline.set_state(Gst.State.NULL)
pipeline.set_state(Gst.State.READY)
pipeline.set_state(Gst.State.PLAYING)

The problem I have now is that when application starts the FPS of one stream will be 0, for example:

2024-07-23 06:19:02.420 | INFO     | utils.FPS:perf_print_callback:106 - ***PERF: {'stream0': 35.05, 'stream1': 0.0}***
2024-07-23 06:19:07.425 | INFO     | utils.FPS:perf_print_callback:106 - ***PERF: {'stream0': 28.37, 'stream1': 0.0}***
2024-07-23 06:19:12.427 | INFO     | utils.FPS:perf_print_callback:106 - ***PERF: {'stream0': 28.19, 'stream1': 0.0}***

After restart I also get this warning message:

nvinfer gstnvinfer.cpp:1728:gst_nvinfer_process_objects:<secondary1-nvinference-engine> Source info not found for source 1. Maybe the GST_NVEVENT_PAD_ADDED event was never generated for the source.
nvinfer gstnvinfer.cpp:1728:gst_nvinfer_process_objects:<secondary1-nvinference-engine> Source info not found for source 1. Maybe the GST_NVEVENT_PAD_ADDED event was never generated for the source.
nvinfer gstnvinfer.cpp:1728:gst_nvinfer_process_objects:<secondary1-nvinference-engine> Source info not found for source 1. Maybe the GST_NVEVENT_PAD_ADDED event was never generated for the source.

The pipeline looks like this now:

streammux → pgie → tracker → sgie → tiler → nvvidconv → nvosd → sink

I had to switch from nvurisrcbin to uridecodebin since nvurisrcbin will fail when I try to restart pipeline.

How can I make the nvinfer process multiple streams and how do I remove the GST_NVEVENT_PAD_ADDED warning?

It means there are no video source from source 1. There maybe still a problem with your rtsp source 1 even if you do that.

Hi, I removed tiler from the pipeline and now both of the streams work when I start the application. However, once I restart the application sometimes the FPS for both streams would be 0, while for others it would be normal:

2024-07-24 06:38:10.593 | INFO     | utils.FPS:perf_print_callback:106 - ***PERF: {'stream0': 0.0, 'stream1': 0.0}***
2024-07-24 06:38:15.599 | INFO     | utils.FPS:perf_print_callback:106 - ***PERF: {'stream0': 0.0, 'stream1': 0.0}***
2024-07-24 06:38:20.604 | INFO     | utils.FPS:perf_print_callback:106 - ***PERF: {'stream0': 0.0, 'stream1': 0.0}***
2024-07-24 06:28:15.105 | INFO     | utils.FPS:perf_print_callback:106 - ***PERF: {'stream0': 28.78, 'stream1': 28.78}***
2024-07-24 06:28:20.106 | INFO     | utils.FPS:perf_print_callback:106 - ***PERF: {'stream0': 28.79, 'stream1': 28.79}***
2024-07-24 06:28:25.107 | INFO     | utils.FPS:perf_print_callback:106 - ***PERF: {'stream0': 28.59, 'stream1': 28.59}***

There are no errors displayed. Is there anything I can do to restart correctly?

But there is no problem with video source. Even when pipeline restarts correctly, and frames are processed I still get this warning.

Are you saying that sometimes all streams are good and sometimes they’re not?
Could you attach your simplified code so that we can try on our side?

Hi, it seems it was a hardware failure (cameras stopped working the other day, now they fixed it). I solved the issue with pipeline restart by creating a new one, more details here.

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