sniklaus

That means that there were 175574 HTTP GET requests, but my guess is that if someone fast-forwards that that might trigger another request. So the actual number of views may be a little lower.

That looks awesome, thank you for sharing!

Thank you for sharing your thoughts! We designed the automatic camera path estimation to minimize the amount of disocclusion which indeed simplifies the problem. As you correctly pointed out, inpainting the background is an additional challenge and while we address it, the inpainted results sometimes lack texture.

Good suggestion, thank you!

It is the result of a lot of work (a lot) and I truly believe everyone in my situation with the right mindset would have been able to achieve it. Being a Ph.D. student and having a chance to do internships at companies like Adobe or Google does sometimes feel like a privilege though, so I understand that not many are in the same situation.

I just got the daily email from my server with some metrics. It has experienced over 500 gigabytes of traffic in the last few hours and the video is only 3 megabytes in size. I definitely did not expect such a HN-effect.

It seems like he is using them extensively but not too extreme. Looks great, thank you for sharing!

It's complicated but the gist of it is that they are trying to commercialize it, yes. For what it is worth, you might be able to find it in commercial software once they were successful with their business endeavors.

2. Yes and there are two mechanism for handling seams. First, the inpainting which extends the point cloud and can provide a higher sample rate. Second, a postprocessing step that heuristically fills in any seams that may still be present despite inpainting.

4. The downside of it is that one needs a lot of resources in order to try all of these variants, which not everyone is lucky enough to have access to.

Those masks look great, thank you for the pointer!