4 ms·
Could you synchronize two Kinect devices on one clock and then toggle the display/capture of that grid every odd or even 10ms span? So, only one grid is displa
by charleso 16y ago
Could you synchronize two Kinect devices on one clock and then toggle the display/capture of that grid every odd or even 10ms span? So, only one grid is displayed and processed during its 'slice' of time, with the grids strobing rather than continuously projected.
Software-only, or would that result in too jerky of a motion capture?
- ramidarigaz 16y ago10ms seems like a reasonably small period of time. I believe it is considered to be effectively instantaneous in UI. Edit: Although, I suppose the "refresh rate" of the entire system would then be 20ms, which might be noticeable. Chop that down to 5ms per Kinect, and it might be viable.
- derefr 16y agoOnly one "eye" [Kinect] has to notice/process the movement; the other can infer, during the integration step, that the "rest" of a moving object comes with it, rather than stretching out.
- ra 16y agoAbsolutely you can. That's exactly how LED matrix displays work (look up charlieplexing). Unless the 3d environment is rapidly changing, you don't need that many frames per second from each device to capture a good image. 25 fps is one frame every 40ms.
- bradgessler 16y agoHow about slightly different wavelengths of infrared?
- levesque 16y agoHow about projecting different patterns?
- JabavuAdams 16y agoCouple this with shutter-glasses and time-multiplexed display. Now you can make a "3d" display that works for multiple viewers. Of course, the frame-rate would suffer.