Nvstreammux dropping late buffer

[907331598]

I’m using the nvcr.io/nvidia/deepstream:7.1-gc-triton-devel base image with the following nvstreammux configuration:

“nvstreammux”, {
“batch-size”: 1,
“width”: src.width,
“height”: src.height,
“sync-inputs”: True,
“attach-sys-ts”: True,
“live-source”: True,
“batched-push-timeout”: 200000,
“buffer-pool-size”: 60,
“nvbuf-memory-type”: 0,
“max-latency”: 200000,
“enable-padding”: False,
“drop-pipeline-eos”: False
}

However, I’m seeing warnings like the following:

gstnvstreammux.cpp:2200:gst_nvstreammux_src_collect_buffers:<telephoto_ai_mux> dropping late buffer pad id = 0
window_start = 0:00:05.799942000
src_buffer pts= 0:00:05.800000000

This indicates the buffer is only ~60 microseconds late, yet it’s being dropped. Similar logs show consistent behavior for subsequent frames.

Questions:

1. Why is nvstreammux dropping frames with such minimal delay?
2. Shouldn’t max-latency=200000 (200ms) allow some buffer?
3. Are there other parameters (e.g., frame-duration, sync-inputs, attach-sys-ts) that might be misconfigured or interacting in an unexpected way?

Any insights on how to prevent these unnecessary drops would be appreciated.

[fanzh]

Please provide complete information as applicable to your setup.

• Hardware Platform (Jetson / GPU)

• DeepStream Version

• JetPack Version (valid for Jetson only)

• TensorRT Version

• NVIDIA GPU Driver Version (valid for GPU only)

• Issue Type( questions, new requirements, bugs)

• 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)

[fanzh]

Sorry for the late reply, Is this still an DeepStream issue to support? Thanks!

1. ‘max-latency’ means “Additional latency in live mode to allow upstream to take longer to produce buffers for the current position”. which is not related to the printing above.
2. what is the fps of RTSP source? “batched-push-timeout” setting is based on fps. please refer to this faqHow to set parameters reasonably to improve the efficiency of nvstreammux in live mode.

[yingliu]

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.