SIPL capture TSC timestamp vs NvMedia captureTimeStamp

Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other

Target Operating System
Linux
QNX
other

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
1.6.0.8170
other

Host Machine Version
native Ubuntu 18.04
other

I would like to understand the difference between NvMediaImage’s captureTimeStamp and nvsipl::INvSIPLClient::ImageMetaData::frameCaptureTSC and clarify which one is more accurate.

https://docs.nvidia.com/drive/drive-os-5.2.0.0L/drive-os/DRIVE_OS_Linux_SDK_Development_Guide/baggage/structnvsipl_1_1INvSIPLClient_1_1ImageMetaData.html#a9861f0d1fea318036aaaaf77451dbdb3

https://docs.nvidia.com/drive/drive-os-5.2.0.0L/drive-os/DRIVE_OS_Linux_SDK_Development_Guide/baggage/structNvMediaImageRec.html#a36ea8d6bf3bfa5dd238b7811c09be1a1

Is TSC timestamp the instance that the image handle arrives at the consumer running on the processor, and captureTimeStamp the instance that the ICP or ISP produces the data?

Thanks

Dear @goksani,
We are checking internally for confirmation about your ask and update you as soon as possible

Dear @goksani ,
NvMediaImage ’s captureTimeStamp (NVIDIA DRIVE OS Linux SDK API Reference: NvMediaImageRec Struct Reference | NVIDIA Docs) is either a monotonic timestamp or PTP timestamp (if system in configured to use PTP clock)

nvsipl::INvSIPLClient::ImageMetaData::frameCaptureTSC ( https://docs.nvidia.com/drive/drive-os-5.2.0.0L/drive-os/DRIVE_OS_Linux_SDK_Development_Guide/baggage/structNvMediaImageRec.html#a36ea8d6bf3bfa5dd238b7811c09be1a1) is TSC timestamp and it is same as NvMediaImageGroup::captureTimeStamp (NVIDIA DRIVE OS Linux SDK API Reference: NvMediaImageGroup Struct Reference | NVIDIA Docs).