NTP Timestamp is always 0

[wei.zhang12]

Please provide complete information as applicable to your setup.

• Hardware Platform Jetson
• DeepStream Version 6.4
• JetPack Version 5.1.2
• 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)

I follow below guide to configure the NTP timestamp for RTSP/RTCP
https://docs.nvidia.com/metropolis/deepstream/dev-guide/text/DS_NTP_Timestamp.html?highlight=configure_source_for_ntp_sync#ntp-timestamp-in-deepstream

But I always get zero.

Below is my test step:
I verified my camera can send RTCP Sender Reports

I test with
python3 deepstream_test1_rtsp_in_rtsp_out.py -i “rtsp://admin:1qaz2wsx@192.168.211.108/cam/realmonitor?channel=1&subtype=1” -g nvinfer --rtsp-ts

And I also configure (after I refer to this link NTP timestamp value always 0 - #17 by dailiupup)
streammux.set_property(‘live-source’, 1)
streammux.set_property(‘attach-sys-ts’, 0)
streammux.set_property(‘frame-duration’, 0)

But I always get 0 for NTP timestamp

And I also capture a log file by below steps

set env variable.
export GST_DEBUG=6
export GST_DEBUG_FILE=/tmp/gst.log
after running in a while, execute /tmp/gst.log |grep nvstreammux >1.log.
zip and share 1.log.

1.log (86.7 KB)

[yuweiw]

@wei.zhang12

streammux.set_property(‘frame-duration’, 0)

Please do not set this value if you don’t use it. Could you try to comment this out and try?

[wei.zhang12]

If I comment frame-duration, I still get 0 for NTP timestamp

And I also attach the log files

1.log (94.5 KB)

[yuweiw]

Could you attach the log with the command below?

1.set env variable.
    export GST_DEBUG=6
    export GST_DEBUG_FILE=/tmp/gst.log

2.zip and share gst.log.

[wei.zhang12]

@yuweiw log has been provided in previous reply

[yuweiw]

Can you send a full log message without filtering it by /tmp/gst.log |grep nvstreammux >1.log?

[wei.zhang12]

Here is the log file without filtering
gst.log.gz (2.4 MB)

And I also capture the payload by wireshark. I can get the NTP Timestamp from RTCP

[yuweiw]

Just from your log, the SR message was only received once and that it was invalid.

	line 31021: 0:00:07.896942724 e[332m10459e[00m 0xfffee0017000 e[37mDEBUG  e[00m e[00m     rtpjitterbuffer gstrtpjitterbuffer.c:4290:do_handle_sync:<rtpjitterbuffer0>e[00m ext SR 588302799, base 18446744073709551615, clock-rate 0, clock-base 18446744073709551615, last-rtptime 18446744073709551615
	line  31022: 0:00:07.897109636 e[332m10459e[00m 0xfffee0017000 e[37mDEBUG  e[00m e[00m     rtpjitterbuffer gstrtpjitterbuffer.c:4298:do_handle_sync:<rtpjitterbuffer0>e[00m keeping for later, no RTP values
	line 31024: 0:00:07.897158629 e[332m10459e[00m 0xfffee0017000 e[37mDEBUG  e[00m e[00m     rtpjitterbuffer gstrtpjitterbuffer.c:4330:do_handle_sync:<rtpjitterbuffer0>e[00m keeping RTCP packet for later

You can see that Rtspsrc strictly follows RFC 2326 and therefore does not (yet) support RealMedia/Quicktime/Microsoft extensions. Maybe there’s something special about the rtsp source you’re using. You can file a topic to the Gstreamer Forum to ask why the SR message was only received once and that it was invalid in Gstreamer.

[wei.zhang12]

Thanks yuweiw. We can close this topic. I have to give up this SR message solution.