Does nvdspreprocess element supports adding and removing camera dynamically

[dilip.patel]

Please provide complete information as applicable to your setup.

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

Hello,

Is there any way to use nvdspreprocess element in case addition/deletion of camera source is dynamically done when pipeline is running.

Currently ROI information is being passed to nvdspreprocess element through config file. is there a way to reload config file while pipeline is running.

is there other way we can pass ROI information & network-input-shape?

can we set network-input-shape to <max_supported_camera>;3;16;224;224? e.g. 32;3;16;224;224

[yuweiw]

Could you provide a detailed description of your user case and attach your whole pipeline?

[dilip.patel]

Hi @yuweiw ,

I am working on fall detection (action recognition) use case. my pipeline is similar to DeepStream 3D Action Recognition App — DeepStream 6.2 Release documentation.

in my case, user can add/remove camera dynamically same as nvidia sample for add/remove runtime pipeline.

let’s say I start my pipeline with one camera with specific ROI information and then user wants to add more cameras to same pipeline with different ROI configuration.

I can manage by

1. Stopping pipeline
2. updated nvdspreprocess config file with new settings
3. Run pipeline

I am wondering if we have any other option to update nvdspreprocess configuration runtime without restarting pipeline.

[yuweiw]

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

We currently do not have support for this scenario. Could you try to set the config-file para again after you run the pipeline？

  g_object_set(G_OBJECT(preprocess), "config-file", your_new_config_file, NULL);

Also, our preprocess is open source sources\gst-plugins\gst-nvdspreprocess\gstnvdspreprocess.cpp. You can modify anything you want on it.