All,
Last week I was out capturing 360 Panos of a few local dive sites with the M2P. Generally my luck with them has been a bit hit-or-miss. Usually have success with land shots without a hard line horizon, such as where the ocean meets the sky. That day though, all misses. Not a single well stitched horizon. All were stitched in-drone. I believe some were screwed up by taking the shots at low altitude near the shore line, the changing position of the surf line threw off the stitch of the horizon. Cropped shot below:
It'd be nice if the built-in software would try to stitch the horizon first and blend outwards from there, but here we are.
However, even at a higher altitude where the surf line is insignificant the horizon still got butchered:
On my Spark, I noticed that I'd usually end up with badly stitched horizons if my gimbal wasn't perfectly calibrated. I'm make a manual correction (usually just a degree or two of roll) and it would be much improved. On the M2P though that didn't seem to make a difference, at least not on this day. Set it perfectly to the horizon and the 360s still managed to screw up.
I even checked the raw images saved while capturing the 360. The shots that were primarily shot of the ocean/sky horizon were noticeably skewed. After trying to manually straighten the individual shots with a hard-line horizon and applying a camera lens correction, I didn't have any luck stitching using Microsoft ICE.
Other pictures taken that day don't appear skewed, only those 360 shots.
Any ideas why? Too much wind and the gimbal wasn't given enough time to settle down amidst the pre-programmed 360 capture? Some other gimbal calibration beyond a manual visual correction?
I'm going to try to see if I can salvage the final shots, try to manually correct the horizon and blend things a bit.
Thoughts?
Last week I was out capturing 360 Panos of a few local dive sites with the M2P. Generally my luck with them has been a bit hit-or-miss. Usually have success with land shots without a hard line horizon, such as where the ocean meets the sky. That day though, all misses. Not a single well stitched horizon. All were stitched in-drone. I believe some were screwed up by taking the shots at low altitude near the shore line, the changing position of the surf line threw off the stitch of the horizon. Cropped shot below:
It'd be nice if the built-in software would try to stitch the horizon first and blend outwards from there, but here we are.
However, even at a higher altitude where the surf line is insignificant the horizon still got butchered:
On my Spark, I noticed that I'd usually end up with badly stitched horizons if my gimbal wasn't perfectly calibrated. I'm make a manual correction (usually just a degree or two of roll) and it would be much improved. On the M2P though that didn't seem to make a difference, at least not on this day. Set it perfectly to the horizon and the 360s still managed to screw up.
I even checked the raw images saved while capturing the 360. The shots that were primarily shot of the ocean/sky horizon were noticeably skewed. After trying to manually straighten the individual shots with a hard-line horizon and applying a camera lens correction, I didn't have any luck stitching using Microsoft ICE.
Other pictures taken that day don't appear skewed, only those 360 shots.
Any ideas why? Too much wind and the gimbal wasn't given enough time to settle down amidst the pre-programmed 360 capture? Some other gimbal calibration beyond a manual visual correction?
I'm going to try to see if I can salvage the final shots, try to manually correct the horizon and blend things a bit.
Thoughts?
