Please provide complete information as applicable to your setup.
• Hardware Platform (Jetson / GPU) Tesla T4
• DeepStream Version 5.0.0
• JetPack Version (valid for Jetson only)
• TensorRT Version
• NVIDIA GPU Driver Version (valid for GPU only) 10.2
• 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)
I want to know what did deepstream do to the “gstrtspsrc” element in function “configure_source_for_ntp_sync”.
I have another gstreamer pipeline reading the same RTSP stream with DeepStream (RTCP SR already enabled). I want this two pipeline to have same ntp-timestamp so that I can syncronize the meta information like bounding boxes. FYI, my own pipeline looks like this:
gst-launch-1.0 rtspsrc location="rtsp://rtsp_stream:554/lab1" protocols=GST_RTSP_LOWER_TRANS_TCP ! rtph264depay ! h264parse ! queue ! splitmuxsink location="lab1-splitmuxsink_%05d.ts" muxer=mpegtsmux max-size-time=10000000000
However, I found that my pipeline’s gstreamer timestamp is drifting, i.e., the difference between multifilesink’s message’s timestamp value & gstjitterbuffer’s gstreamer time (gstreamer_time += ((sr_ext_rtptime - base_rtptime) * GST_SECOND / clock_rate)) upon “handle_sync” signal is steadily growing (from seconds to tens of seconeds).
My implementation of time syncronization between gsteamer & RTCP SR is obtained from DeepStream 4.0.1 SDK since this is the only open source version.
So I want to know how DeepSteram application deal with this time drifting internally between gstreamer buffer timestamp & RTCP SR’s gstreamer timestamp.
Please give me some instruction.