DeepStream basics


We started using DeepStream5, and facing issues to understand basics on how to develop or run the application.

  1. We are not able to run samples mentioned in earlier version of DeepStream. In fact, we are not able to locate Jupiter in Jetsonnano as per DLI online courses instructions.
  2. The instructions say that we need to run only txt file and config file. What exactly are these files?
  3. Where does C program/Python program fits in DeepStream application

Please provide complete information as applicable to your setup.

• Hardware Platform (Jetson / GPU) Jetson Nano
• DeepStream Version 5.1
• JetPack Version (valid for Jetson only) 4.5
• TensorRT Version7.1
• NVIDIA GPU Driver Version (valid for GPU only)
**• Issue Type( questions, new requirements, bugs)**Questions
**• 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)**Basics
**• Requirement details( This is for new requirement. Including the module name-for which plugin or for which sample application, the function description)**NA

We need more details to debug this bug, it’s better you can create a new topic for it.

Which instruction, I think you need to refer NVIDIA DeepStream SDK Developer Guide — DeepStream 5.1 Release documentation

generally c will have better perf however python will be more simple to implement your own logic

Thanks @bcao . I can see in documentation that we need to run sample using below mentioned command

$ deepstream-app -c <path_to_config_file>

Where <path_to_config_file> is the pathname of one of the reference application’s configuration files, found in configs/deepstream-app .

If only configuration file is the one which we may required to build simple recording application, why do we require language specific code. What I mean, in case, if I just want to record the video, and send the frames to Kafka, do I required to write any custom code in C. I am asking this question as recording of video and sending frames to Kafka, we already have components available Deepstream.

Hey, just like what you said if current deepstream-app can meet your requirement, then you don’t need to write any c code. However there may be many requirements in different use cases, so only changing the config may not be enough.