Fascinating. So not only is it feeding it an 8K / 30 (60?) FPS image, it's feeding it numerous incident angle variations and displaying all of them simultaneously?
I think that is where the custom compression algorithm comes in. If you think the fact that human body and face doesn't change much, and the fact that it's a 3d model based, the compression ratio could be very high.
I only know what I saw from the IO stream, but I think it might send a compressed 3D mesh + texture across the network and render the light field locally.
I think what they are transferring is not a video but 3d model and the skin texture applied on the model (all derived from the realtime video / depth recording on the other side). The receiving and then renders it as a 3d model on the screen.
defaultname|4 years ago
Sounds like a monster data rate.
dialogbox|4 years ago
zaptrem|4 years ago
dkarras|4 years ago
ithkuil|4 years ago
> the 8K is their Input Resolution. > That resolution is then divided into the 45 viewing directions:
eps|4 years ago
unknown|4 years ago
[deleted]