However, if you feed Microsoft Hyperlapse some proper action video, it can certainly make something very watchable and even enjoyable out of it. In fact, I'd say that it even ruins the video. For the driving video, where it was mounted on a static place, it clearly doesn't really help. Would we recommend Microsoft Hyperlapse? Well, that depends on the kind of video you're making. Granted, it moves around a bit, which makes it seem like I was a drunk cyclist, but that's a sacrifice I can accept. Hyperlapse completely worked out the shakiness and erratic camera movement and created a nice, smooth timelapse. After letting Microsoft Hyperlapse have a go at it, though, it actually looks very good. Of course (take my word for it), the source video that runs at normal speed at 60 FPS is also hardly watchable due to the side-to-side movements. Below are both the videos, with the plain one up top.Ĭlearly, the original timelapse is unwatchable. Basically, I set out to make the worst source footage I could within 10 minutes. A bike ride let me mount the camera with a first-person view, and I intentionally biked around moving side-to-side excessively and found some wobbly roads to see how Hyperlapse would cope with very shaky video. However, the problem with this attempt was that the original video was actually quite good, leading me to wonder if I'd used Hyperlapse in the wrong conditions? I therefore did what any good Dutchman would do: I went for a bike ride. What is nice is that it cuts out the long still bits, meaning you don't have to watch me grab a mint and tuck a cable out of sight. That may be due to the car's interior occupying a large portion of the view. We clearly see the camera trying to follow the dominant path, although it does have a delay and doesn't always seem to know what to look at.
We'll let the results speak for themselves. Below is the video processed by Microsoft Hyperlapse:
0 kommentar(er)
