Change rtsp from H264 to H265 during runtime time

wei.zhang12 · May 6, 2024, 7:10am

Please provide complete information as applicable to your setup.

• Hardware Platform (Jetson / GPU)
• DeepStream Version
• JetPack Version (valid for Jetson only)
• TensorRT Version
• NVIDIA GPU Driver Version (valid for GPU only)
• Issue Type( questions, new requirements, bugs)
• 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)

When the deepstream pipeline is running, I change my camera output format from H264 to H265.

And then I will get below connection issue and it can’t be recovered from reconnection.
I need fully understand this rtsp-reconnect-interval. How many times reconnection will it try? If I set rtsp-reconnect-interval =0, does it mean, it will never reconnect even if there is no data, or the camera dies. After camera is back, what will happen?

WARNING from element uri-decode-bin: No data from source rtsp://admin:1qaz2wsx@192.168.211.108/cam/realmonitor?channel=1&subtype=1 since last 60 sec. Trying reconnection
Warning: No data from source rtsp://admin:1qaz2wsx@192.168.211.108/cam/realmonitor?channel=1&subtype=1 since last 60 sec. Trying reconnection
WARNING from element src: Unhandled error
Warning: Unhandled error
WARNING from element src: Could not write to resource.
Warning: Could not write to resource.

ERROR from element uri-decode-bin: Failed to populate and link video elements
Error details: /dvs/git/dirty/git-master_linux/deepstream/sdk/src/gst-plugins/gst-nvdsbins/gstdsnvurisrcbin.cpp(1706): cb_newpad_rtspsrc (): /GstPipeline:v2x-pipeline/GstBin:source-bin-00/GstDsNvUriSrcBin:uri-decode-bin
Resetting source rtsp://admin:1qaz2wsx@192.168.211.108/cam/realmonitor?channel=1&subtype=1
Returned, stopping playback
[NvMultiObjectTracker] De-initialized
mqtt disconnected
Deleting pipeline

junshengy · May 6, 2024, 8:01am

In this case, the pipeline needs to be restarted. Reconnecting cannot solve this case.

This sample is close to your usage scenario

github.com

NVIDIA-AI-IOT/deepstream_reference_apps/blob/master/runtime_source_add_delete/deepstream_test_rt_src_add_del.c

/*
 * Copyright (c) 2020-2021, NVIDIA CORPORATION.  All rights reserved.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

#include <stdlib.h>
#include <stdio.h>
#include <gst/gst.h>
#include <glib.h>

This file has been truncated. show original

rtsp-reconnect-interval means that if no data arrives within the specified time, the connection will be reconnected. If it is set to 0, nothing will be reconnected.

yingliu · May 28, 2024, 7:47am

There is no update from you for a period, assuming this is not an issue anymore. Hence we are closing this topic. If need further support, please open a new one. Thanks

system · June 11, 2024, 7:47am

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