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)
We currently have a gstreamer application and we are using the “drop-frame-interval” to skip frames. Our gstreamer pipeline looks like this
“filesrc location=pathToVideo.mp4 ! parsebin ! nvv4l2decoder drop-frame-interval=5 ! nvvideoconvert ! video/x-raw(memory:NVMM),format=RGB ! appsink emit-signals=True name=sink sync=False”.
We have a callback that fires whenever a frame is put onto the queue in appsink. In this callback we increment a frame_number variable to keep track of the frame number. I.e.
my_callback_function() {
frame_num += drop-frame-interval
}
However we have noticed that the frames aren’t matching up with opencv. I.e. frame number 1000 as read in by gstreamer is different that frame number 1000 as read in by opencv.
So we wanted to confirm our understanding of how gstreamer skips frames. So if we have say 30 frames and we “drop-frame-interval=5”, then frames 0,5,10,15,20,25,30 should be decoded. Is this correct? Apologies for the dumb question, but we’re a little confused.
An yes we’ve read the documentation here: Gst-nvvideo4linux2 — DeepStream 6.1.1 Release documentation. We wanted to confirm our understanding of the documentation is in fact correct.