Using Message broker to add bounding box in real time to a different UI

Please provide complete information as applicable to your setup.

• Hardware Platform (Jetson / GPU)
Jetson
• DeepStream Version
7.1
• JetPack Version (valid for Jetson only)
6.1
• TensorRT Version
10.3.0.30-1
• NVIDIA GPU Driver Version (valid for GPU only)
540.4.0
• 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)
running test4 on python bindings with a rtsp input and amqp message broker
• Requirement details( This is for new requirement. Including the module name-for which plugin or for which sample application, the function description)

Hello, I’m trying to use deepstream to run inference and publish bounding box and confidence to the message broker to that it’s integrated to a different UI in real time.
However, the payload I get is single detection for each message, for instance, using minimal schema I get:
id, | class id | bounding boxes | class | confidence score |
but I would like to get all the detections into one message, I thought test-4 was meant for this, I’ll look more closely into the genereate_event_msg_meta() function to figure it out.

But before that I want to confirm that what I’m trying to do is feasible with how deepstream works: get all the information (bounding boxes and scores) at each detection frame and display it on a separate screen (no rtsp output possible of course).

Regards

please start the cmd with appending --schema-type=1. " 1=minimal" means one message including all objects in one frame. please refer to generate_event_message_minimal of \opt\nvidia\deepstream\deepstream-7.1\sources\libs\nvmsgconv\deepstream_schema\eventmsg_payload.cpp.

Thank you for the answer, I’m actually already using the minimal schema type. But the issue is that test4 is using object level meta and I can’t seem to send direct frame level meta. Is there any example that treats frame meta directly?
Do I need to create custom payload?

To be more precise, I’m refering to this documentation : MetaData in the DeepStream SDK — DeepStream documentation

As in ds4, I’m trying to extend the user_event_meta with a custom msg_meta (msg_meta.extMsg) that contains the following:
frame_number, timestamp, object_list (object list being a python dictionnary that contains all the elements from obj_meta_list.

Unfortunately, the python dictionnary type does not work for msg_meta.extMsg so I’m stuck.
I do feel like I’m trying to implement something that already exists (obj_meta_list) but I don’t know how to pass it to the message broker as a default nvds payload (as seen in eventmsg_payload.cpp)

Okay it seems to work now,
Perhaps I had been doing something wrong the whole time, but test4 seems to provide all detections in each message.
Thank you for your time

Thanks for the update! Is there still an DeepStream issue to support? Thanks!

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