Bounding box overlay not displaying in VST Web UI

Accelerated Computing Intelligent Video Analytics Metropolis Microservices for Jetson
1

Hello,

I’m currently testing a YOLOv8-based object detection model within a Jetson + DeepStream JPS pipeline. While the model inference seems to be working correctly, I am experiencing an issue where no bounding box or label overlays appear in the VST Web UI, despite valid metadata being published to Redis.

Verified Behavior

Model inference is successful
Metadata is correctly pushed to Redis Stream

Example output:
127.0.0.1:6379> xinfo STREAM test

“entries-added”: (integer) 74997,
“last-entry”:
{
“version”: “4.0”,
“sensorId”: “FW7502-PEF”,
“objects”: [
“334|689.491|852.487|1535.85|1063.38|chair|#|||||||0”,
“2|663.804|72.7719|1569.66|1065.77|person|#|||||||0”,
…
]
}

→ As you can see, object metadata follows the expected format (object_id|x1|y1|x2|y2|class|...).

Confusion

My Questions

  1. Does JPS 2.0.1 truly disable or drop support for the VST overlay feature?
    If so, could you please point me to the official documentation or release notes confirming this?

  2. What are the current supported methods to display bounding boxes and labels in JPS with VST?

    • Is any additional configuration or package required?
    • Would downgrading to a previous JPS version be the only viable workaround?

Environment Info
JPS version: Suspected to be 2.0.1 (JetPack 6 / L4T 36.4)
Redis metadata: Verified and correct
Inference engine: YOLOv8

2 
"overlay":
{
        "video_metadata_server": "",
        "video_metadata_query_batch_size_num_frames": 300,
        "use_video_metadata_protobuf": false,
        "enable_gem_drawing": true,
        "analytic_server_address": "http://192.168.0.178:30080/emdx",
        "overlay_text_font_type": "DejaVuSansMono.ttf"
},

I found the video_metadata_server entry in vst_config.json . I didn’t find any definition in the documentation, but could this have something to do with overlay behavior?

3

One option is DeepStream output RTSP with BBoxes. Is it fine for your project?

4

It’s not okay. We have fully confirmed that it is osd through Ds-test.

What we need is a graphic that is overlayed separately on the video.

6

Why you need a graphic that is overlayed separately on the video? VST already saved the original videos which without the BBoxes.

7

It’s based on our business logic, but that’s beside the point.

What I’m wondering is that VST seems to support bounding box overlays, but they don’t actually work.

Am I missing something? Is this still a work in progress? If there are any plans, I’d be curious.

Also, the Metropolitan microservices type seems to offer something like a developer preview version. If so, please check if our organization is eligible for the preview version.

8

VST don’t support a graphic overlay on the video. Regarding Metropolitan microservices developer preview, you need to register with your company mail to try it.

9

However, VST has a UI for the bbox overlay.

Does this mean it’s only supported in the preview version?

I have my company email ready. Please provide more detailed instructions.

10

Metropolitan microservices developer preview is for dGPU, are you working on Jetson or dGPU?

11

We are both ready

12

You can check the introduction here and after register, you can access it: Metropolis Microservices | NVIDIA Developer