-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Global time domain for RS2_FRAME_METADATA_SENSOR_TIMESTAMP #8521
Comments
Not the exact same question but lots of answers in this thread. Does this help? |
Thanks very much @rafaelspring for your assistance to @MBSadeghzadeh :) |
@MartyG-RealSense Always happy to help :) |
I hoped to understand this part of document. It was not pointed out in the other issue too. |
@MBSadeghzadeh Advanced mechanics of metadata is not one of my specialist knowledge areas, so I would refer you to an excellent source of information about timestamps in the link below. In this discussion, frame_timestamp is described as generated in firmware and designating the beginning of UVC frame transmission (the first USB chunk sent towards host). |
You were right @MartyG-RealSense. I have done some tests and saw the same results. Global Time only applies to |
Do you need advice about anything else please? Thanks! |
|
Could you explain more about what you mean about considering the global time domain for Frame Metadata timestamps such as RS2_FRAME_METADATA_SENSOR_TIMESTAMP as well, please? In regard to global time, there is further information at the links below that may help to answer your questions about it (bearing in mind that my knowledge of advanced-level metadata concepts is limited). |
I mean we can only see the frame timestamp in global time domain and other timestamps are in hardware clock domain. Is there any possibility to convert them to global time domain? |
Thanks very much @MBSadeghzadeh for the clarification. @ev-mp Would it be possible to provide advice about this question please: We can only see the frame timestamp in global time domain and other timestamps are in hardware clock domain. Is there any possibility to convert them to global time domain? |
I have two D435i, if I made use of Hardware Synchronization and Global Time, would I have a zero time difference between two cameras' frame_timestamps ? |
@MBSadeghzadeh If hardware sync is enabled then timestamps will drift apart over time. If hardware sync is not enabled then the timestamps appear to be perfectly aligned. The section of Intel's multiple camera hardware sync white paper linked to below describes this, in the paragraph that begins with the bolded text Now to the somewhat counter intuitive aspect of time stamps. |
How can I check timestamps drift? do I have to subtract consecutive timestamps of a single camera or subtract the timestamps of both cameras? |
You can observe them manually (for example, taking screenshots of both cameras' timestamps and comparing the images). A hardware sync discussion in the link below includes a C++ script where drift is checked with code. Another way of validating sync that is suggested by the hardware sync white-paper is the use of high-speed LED panels. https://support.intelrealsense.com/hc/en-us/community/posts/360049401673/comments/360012819533 |
Thanks @MartyG-RealSense. Reaching a zero time difference between two cameras is also possible but only with a bit coding. |
Realsense provides different kinds of timestamps. The most important one to me is
RS2_FRAME_METADATA_SENSOR_TIMESTAMP
which is the timestamp of the middle of sensor's exposure calculated by device. I have enabledFrame Metadata
so I am able to read all kinds of timestamps that each frame includes.As it has been written here, I wonder if
rs2_timestamp_domain
only specifies the clock in relation to whichRS2_FRAME_METADATA_FRAME_TIMESTAMP
was measured or it also specifies the clock domain ofRS2_FRAME_METADATA_SENSOR_TIMESTAMP
?The text was updated successfully, but these errors were encountered: