How is new_streammux able to handle different fps and resolution sources?

[yeongjae1]

Please provide complete information as applicable to your setup.

• Hardware Platform (Jetson / GPU) GPU
• DeepStream Version > 6.2
• JetPack Version (valid for Jetson only)
• TensorRT Version
• 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)
• Requirement details( This is for new requirement. Including the module name-for which plugin or for which sample application, the function description)

hello. Even though I looked at the deepstream docs, it doesn’t seem to describe specifically why new_streammux can handle different Fps and resolutions. Both old_streammux and new_streammux seem to use the same round-robin algorithm, but there is no specific information on how they did it differently.

1. Therefore, I would appreciate it if you could tell me the reason.
2. If there are streams operating at different fps, one result from pgie is 10fps (source1) and the other is 15fps(source2). When parsing meta at15fps, the meta information for the 10fps source may be parsed redundantly??

[fanzh]

new_streammux can’ handle different resolution. please refer to the doc.
new_streammux is opensource. you also can add log to check.

[yeongjae1]

you mean can or cannot?
docs metioned that A batch can have buffers from different streams of different resolutions and formats

[fanzh]

There is no update from you for a period, assuming this is not an issue any more. Hence we are closing this topic. If need further support, please open a new one. Thanks.
as the doc said " So with new mux, a single resolution for this heterogeneous batched buffer is invalid.“, to be precise, new mux can’t handle different resolutions directly.
if inputting different resolutions, we suggest “it is necessary to add nvvideoconvert + capsfiler before each nvstreammux sink pad (enforcing same resolution and format of all sources connecting to new nvstreammux).” please refer to the " Work Around” part in the link above.