Overlay image corruption with red band when scaled down - DS 5.1, Jetson NX

When using sink0 with overlay size much reduced (like 640x360, to mimic P-in-P like effect), the overlay gets corrupted and I see red pixel band as following.


(the red band actually changes in size as mouse cursor goes over it)

The following, with original config, of course works.

$ cd /opt/nvidia/deepstream/deepstream-5.1/samples/configs/deepstream-app
$ deepstream-app -c ./source1_csi_dec_infer_resnet_int8.txt

However when width and height of the sink0 is changed to something like 1/9 the size, this isssue starts happening

[sink0]
enable=1
#Type - 1=FakeSink 2=EglSink 3=File 4=RTSPStreaming 5=Overlay
type=5
sync=0
display-id=0
offset-x=0
offset-y=0
width=640
height=360
overlay-id=1
source-id=0

When 960 x 540 (1/4 the size) is specified, it works fine.
When 480 x 270 (1/16) is specified, it does not show the overlay at all.

Also, not sure if this is relevant, when the issue occurs, you see “System throttled due to Over-current” warning message on the desktop.

image

Please let me know if there is a way to circumbent this issue to show the reduced image overlay using DeepStream on Jetson.

I’m testing this on Jetso Xavier NX Developer Kit with JetPack 4.5.1 image, with RaspberryPi Camera Module v2.

Just for a reference, I uploaded the screen capture.

I believe this is easily reproduced.
Any feedback is appreciated.

Hi,
Looks like you hit hardware limitation in downscaling output frames. If you need small resolution, please adjust resolution setting in nvmultistreamtiler or nvstreammux, to smaller value.

Hi DaneLLL,
Thank you so much for the reply.

I modified the [streammux] config as well as the [sink0] config as following, and got the P-in-P effect right.

[sink0]
enable=1
type=5
sync=0
display-id=0
offset-x=1180
offset-y=620
width=640
height=360
overlay-id=1
source-id=0

[streammux]
live-source=1
batch-size=1
batched-push-timeout=40000
width=640
height=360