New nvstreammux automatically scaling 4K stream to 1080p despite USE_NEW_NVSTREAMMUX=yes

[sagar0]

DeepStream Version: 7.1
Issue Type: Bug

Problem Description

I’m experiencing unexpected automatic scaling behavior with the new nvstreammux despite having USE_NEW_NVSTREAMMUX=yes set. My pipeline has 4 sources: 3 at 1080p resolution and 1 at 4K resolution. The new nvstreammux is scaling the 4K stream down to 1080p, even though the documentation states that the new nvstreammux should preserve mixed resolutions.

Pipeline Structure

source1_1080p ─┐
source2_1080p ─┤
source3_1080p ─┼─→ nvstreammux ─→ queue ─→ nvstreamdemux ─→ individual sources ─→ nvinfer
source4_4K ────┘

and between the source bins and nvstreammux I have below elements:

[RTSP Sources] → [Source Bins: rtspsrc→capsfilter→depay→parse→nvv4l2decoder] → nvstreammux → queue → nvstreamdemux → nvinfer

I’m not setting any explicit resolution properties on the streammux, and my configuration only includes adaptive-batching and max-same-source-frames settings.

Any guidance on the correct configuration or pipeline structure for preserving mixed resolutions with the new nvstreammux would be greatly appreciated.

[miguel.taylor]

Hi,

Can you add a capsfilter caps=video/x-raw(memory:NVMM), width=<width>, height=<height> with the correct resolution in <width> and <height> just before each sink pad of the nvstreammux? This is to ensure that the caps are being negotiated correctly and that the streammux is the one scaling the buffers.

[Fiona.Chen]

The new nvstreammux does not support different resolution multiple inputs. All input videos should be scaled to the same resolution before being input into new nvstreammux. Your case is not supported.

[Fiona.Chen]

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