The extreme wide-angle lens of GoPros helps with that immersive look, putting you in amongst the action. But it also comes at the cost of a kind of bulging fisheye look, where horizons and straight lines get curved and subjects in the middle of the frame look artificially big compared with the things around them. And that might not be the look you’re going for. You might be wanting a more “normal” perspective.
It has always been possible to correct for it, whether you’re shooting still photos or video. But until now it has involved extra work in post-processing. I’ve written about how to do that with still photos as well as with video.
But with the GoPro HERO5, it’s now possible to shoot in modes that correct the distortion in the camera, eliminating the need to do it later. It’s a new Field of View setting available in photo modes and some video modes and called Linear FOV mode. It applies software correction to the lens distortion before it saves the image file to the memory card.
GoPro recommends it particularly for aerial footage, but it’s a good option to have anytime you’re after a more traditional perspective.
Here are a few examples of what it does. These first ones are still photos shot with a GoPro HERO5 Black:
With the horizon already pretty much centered and the detail in the frame in the distance, the effect is less obvious in this one:
These are screen grabs from video shot side-by-side with a GoPro HERO4 in its standard Wide FOV mode and the GoPro HERO5 Black in its Linear FOV mode.
Limitations and Drawbacks
Linear FOV isn’t available in all video sizes and framerates, in part because the software processing has to cannibalize information around the edges of the frame. These are the video modes it’s available in:
- 1080p (60fps and below)
Linear FOV is available in the Timelapse Photo mode but isn’t in the Timelapse Video mode.
As you can see, lines get straightened and the whole look is much less distorted. But there is a price to pay, and that’s principally in terms of losing image real estate from around the edges of the frame and the parts near the edges can get a stretched look. It’s pretty obvious is all of these examples, but especially so in the shot of the bridge above where it looks as though it was shot from a different spot. But in all of these examples they were either shot using the same camera in the same spot or two cameras mounted exactly side-by-side.
There is also something to be aware of even if it’s not a drawback, as such, and that is that shooting in Linear FOV mode is non-reversible. That is, once you shoot in Linear mode you can’t revert the image or video footage back to the wide view as you can with the old post-processing method. So you’ll want to be certain as you shoot that Linear mode is what you want.
You can, of course, continue doing it the old way of shooting in the regular Wide FOV mode and correcting in post.
Here’s a quick example where I corrected an image shot from the GoPro HERO5 Black in Lightroom using the method I’ve outlined here. At the time I originally processed this example and wrote this post, Lightroom didn’t have a built-in lens profile specifically for the GoPro HERO5 Black yet. Used the one for the HERO4 Black and found that it worked well on HERO5 Black images. Since then, a new version of Lightroom (2015.8) has come out that adds HERO5 Black support. Here’s a screenshot of the options available:
First, an image taken at the Wide FOV and then processed with the default level of distortion correction in Lightroom (there’s a slider so you can adjust the level):
And then a version comparing the in-camera Linear FOV shot from the same spot (taken on a tripod) with the Lightroom version with distortion correction. As you can see, the Lightroom-corrected version retains a much wider perspective while still straightening lines.
With Lightroom there’s a slider that gives you control over the amount of correction applied. Here’s an example of what I mean:
For video, you should be able to use GoPro Studio to remove the fisheye, but for now Studio v.220.127.116.1172 needs an update–it’s not registering HERO5 footage and giving the option for fisheye correction of video.