3 ms·
Cool, I'd not seen the updated work. I wonder how much can be done in realtime. I have no idea what the compute split is between between the different processes
by z303 12y ago
Cool, I'd not seen the updated work. I wonder how much can be done in realtime. I have no idea what the compute split is between between the different processes.
With sensors (gyros etc) the camera path would be trivial, instead of recovering that from the video. Rendering the results would be possible on a mobile GPU. Just leaving the frame conversion to a point cloud in terms of compute and memory.
Maybe some scheme where you down sample the input frames to create the deformation mesh, then apply that to the full size frame would be the way to go
- vanderZwan 12y ago> With sensors (gyros etc) the camera path would be trivial, instead of recovering that from the video. Well... not quite trivial. They're calibrated differently per model, and it's actually quite tricky to reconstruct the path based on accelerometers and gyroscope alone. There's also the likely issue of synchronising the data from these sensors with the video input. If you solve that second issue however, it could in theory at least help with recovering the path from the video, creating better predictions where the point cloud has moved to for example.
- z303 12y agoI was being a little cheeky with that. I know position and orientation data can be quite noisy and getting clean good quality data is not simple