[dTal]

Practical for an algorithm implementer, maybe - deeply impractical for real-world use. Stereo cameras are rare and nontrivial (you have to synchronize shutters). Monocular algorithms can be applied to the millions of hours of existing footage, or used with the billions of cameras, smartphones, robots, drones, and fancy doorbells that already exist right now.

[derefr]

If you can calibrate the time-delay between the two cameras, can you not just interpolate one or the other signal backward or forward in time so that it aligns with the other? (By "interpolation", here, I mean the sort of thing the Oculus does on the display side, generating frames "between" frames, to smooth motion during head rotation. Take one real frame from one camera, and build an interpolated frame between two real frames from the other camera to match it.)

[RavlaAlvar]

For “slow” moving object like human body, does synchronised shutter matters that much and if so , is there any tricks to compensate it if synchronisation is not possible?

[joshvm]

You can do reasonable software sync with identical cameras and threading - it gets you to within a few milliseconds.

Even for slow objects it's a problem because being a few pixels off might make the difference between matching and not.

[maxst]

There are dozens of 360 cameras on the market, so I think shutters synchronization is not that difficult to implement.

[CyberDildonics]

360 cameras produce spherical panoramas from a single point and would not help capture of a person on a stage over a regular camera.

[mlatu]

But 360° cams try to do something entirely different than, say a kinect.

I would be surprised if all 360° cameras had synchronized shutters.