FFS
 lvl.3
Flight distance : 50003 ft
Japan
Offline
|
There is some wierd stuff going on with the 1080p codec or at least the way the Osmo encodes it’s 1080p footage. Specifically aliasing in hard lines and bad artifacting in complicated scenes like forests. It’s almost like the downsampling from 4K is using “nearest neighbor” when converting the sensor’s output to 1080p insead of some other anti-aliasing method.
At first I thought it was a binning issue because the only time I was using 1080p was in 4x slow mo. I accepted the degradation as a trade off for slow motion. However, since I was getting tired of 4K60fps not working with my iPad properly I found myself shooting in 1080p for non-quality critical stuff. It didn’t take long before I noticed there was a way bigger step down in quality in 1080p mode than I am normally used to in my cameras.
In my experience, with cameras like the GH5, another 4K60fps camera, when you choose to shoot in 1080p is does not result in any noticable reduction in quality when viewing the content back on a 1080p monitor; the footage essentially looks the same. I assume this is because cameras like the GH5 are oversampling the footage and just downrezzing it. However the Osmo pocket looks far worse when the footage was shot in 1080p. I am not sure why this is, considering that the 1080p codec has a bitrate of only about 60% that of 4K on the Osmo, which should actually mean BETTER quality per pixel if the end project is watched in 1080p!
I hope this improves with an update down the road because the 1080p workflow is something to be desired when shooting and editing on a mobile platform.
|
|
lvl.4
