Question on Multi-camera sync video shooting
I've read through the multi-camera-setup and being confused about one thing. In the External Trigger part, it said:
Pulse width = 60ms(setup) + #of frames33ms
For example: for capturing 3 consecutive frames Ton needs to be high for 160ms
Does this mean there is a 60ms setup time in EVERY lidar-on period, and only after that capturing can happen? If so, it'll be a big problem for shooting video, because it hurts the FPS too much.
-
Official comment
Hello Liuxin,
You are right, this would be a big problem for shooting video. That is why this process is not meant for shooting video. This is used to capture static scenes with multiple cameras, with each camera obtaining only a few frames at a time and fps is not as much of a concern.
You cannot have multiple L515 cameras streaming video continuously while the cameras are facing each other because their laser projections will interfere with each other.
Sincerely,
Jesus G.
Intel Customer SupportComment actions -
hi, Jesus, thanks for the quick response.
I don't know much about the photoelectricity that makes L515 works. But does it really need the whole 33ms for laser scanning? Some other ToF system, like Azure Kinect, uses several 100+us laser scans with 1300+us interval between, thus allowing user to set an offset of 160us between 2 synced cameras to avoid interference, while still making the 2 frames' exposure almost at the same time.
Is it possible for L515 to support similar feature in the future? Shooting multi-cam outside-in video is in hot demand. Please consider it. Thanks. -
Hello Liuxin,
The 33ms corresponds to the fixed 30 fps of the depth sensor of the L515. 1second/30fps = 33ms/frame. The Azure Kinect uses a much different LiDAR technology than the L515 so it cannot be directly compared in terms of exposure times.
This feature cannot be changed in the current L515 but it may be different in future products, which we don't have visibility into.
Thank you for your feedback.
Sincerely,
Jesus G.
Intel Customer Support
Please sign in to leave a comment.
Comments
3 comments