131–140 of 184 posts
The videos don't load for me (due to mixed content, I believe), so here they are: https://www.youtube.com/watch?v=SOpwHaQnRSY https://www.youtube.com/watch?v=sA4Za3Hv6ng The hyperlapse of the climbing video looks like an FPS game from a decade ago with texture refreshing as you get closer.
Earlier quoted context omitted.
Take a look at an older paper 'Content-Preserving Warps for 3D Video Stabilization'. That seems to do an ok job http://createdigitalmotion.com/2009/06/magical-3d-warping-te...
EDIT: After clicking through to their website, I found this updated technique which shares one principal author that seems to work even better: http://people.cs.nctu.edu.tw/~yushuen/VideoStabilization/ Wow. Actually, if they that add that technique to the mix it might solve the deformed "pop"-effect you see in some videos, like the deformed building you see around 16 seconds into this videos: http://research.microsof…
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
The videos don't load for me (due to mixed content, I believe), so here they are: https://www.youtube.com/watch?v=SOpwHaQnRSY https://www.youtube.com/watch?v=sA4Za3Hv6ng The hyperlapse of the climbing video looks like an FPS game from a decade ago with texture refreshing as you get closer.
Hmm... Did I not embed these correctly? The project page as well as the embed links are plain http:// this is what it should be, no?
Earlier quoted context omitted.
EDIT: After clicking through to their website, I found this updated technique which shares one principal author that seems to work even better: http://people.cs.nctu.edu.tw/~yushuen/VideoStabilization/ Wow. Actually, if they that add that technique to the mix it might solve the deformed "pop"-effect you see in some videos, like the deformed building you see around 16 seconds into this videos: http://research.microsof…
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 schem…
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.
Bloody amazing! Fantastic work! Release it. Release it soon. This is something that everyone would want. I see they have listed a Windows app coming. Is that Windows desktop app?
If I were them I would offer this as a web service: upload your video and have it converted for $1.
Bloody amazing! Fantastic work! Release it. Release it soon. This is something that everyone would want. I see they have listed a Windows app coming. Is that Windows desktop app?
If I were them I would offer this as a web service: upload your video and have it converted for $1.
I'm curious to see what happens if they insert more action-packed footage. An MTB course with trees, switchbacks, and jumps would be an interesting stress test of this technique.
left side video was shot here: https://www.google.com/maps/place/Altona+Town+Hall/@53.54767...
Earlier quoted context omitted.
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 schem…
> 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 i…