Sync timestamp of RealSense to different camera
This question has been asked before, but I haven't seen a definitive or clear answer: how can I sync the timestamp of a RS to a non-Intel camera? I'm not referring to actual board-level sync or genlock, but simply getting the clocks to be in lockstep.
-
Hi Bschwartz If you do not wish to use hardware-sync genlock then another possibility is to use camera metadata to sync between streams from a RealSense and non-RealSense camera. This method is discussed at the link below.
https://github.com/IntelRealSense/librealsense/issues/2186
-
Thanks Marty! It's not that I don't wish to use hardware genlock, it's just I can't find anything useful about it. Where is the whitepaper about hardware-sync genlock? It's taken down. I just need to achieve some kind of sync between a synced array of RS and one or more non-RS RGB cameras.
-
Also, the Github link you shared doesn't seem to present a complete answer either, just the first part of an answer:
You can see the available frame metadata for D400 using
rs-save-to-disk(look for generated .csv files in the output directory). We offer system time, frame # and hardware timestamp (for now only after applying the Kernel patch). You can certainly use this information to synchronise between the two devices.But how does one actually achieve sync? In the case of a ZED from this particular post, he doesn't go into any detail.
-
The genlock sync paper has been withdrawn by Intel as it was an unvalidated and experimental proof of concept, and the mode 1 and 2 paper in the link below is considered to be the validated and mature method of performing hardware sync.
https://dev.intelrealsense.com/docs/multiple-depth-cameras-configuration
The removed genlock paper can though be downloaded to your computer as an archived PDF document from the link below though
https://github.com/IntelRealSense/realsense-ros/files/10359354/External.Synchronization.pdf
There is not any further information available about the metadata-based sync method, unfortunately.
Please sign in to leave a comment.
Comments
4 comments