Mavic 1 lens is FOV 78.8° 26 mm (35 mm format equivalent) which is actually a wider angle of view than the M2P. Any more than 26 images is a poorly designed shooting algorithm, with way too much overlap. DJI must have realized that, but not backfilled the MP with the better algorithm , to shoot it faster with the fewest number of needed images. At it's core, the sphere only needs three rows (30° up, horizontal, and 30° down) of 8 images shot at increments of 45° around the clock, plus two straight down shots at 90° to each other. Hence 26 images.
It certainly does, which is why there are 26 photos instead of only 18! However, 30° above the horizontal still can't shoot the sky ceiling, so you either need clone one in from the sky that is captured, or add it from stock photos of skies, or cut off the pano at the top edge of the top row. The default created jpeg output file on the card uses the first method in a "good enough" automated method, which can look a little strange at the top seam, when you pan up in the image.The M2 doesnt do a series of +30 degree gimbal shots either which is why the 360s are worse in that you have to photoshop in a load more sky than before.
In hindsight, I think you may be correct about that. Good to know, because that would explain some issues I had, trying to include the top of a building in the top edge of a spherical panorama, and I made sure it was visible in the frame when I elevated manually to 120°, before shooting the pano, but when I got home, it was cut off in the actual pano, and cloned in! Unfortunately, I haven't paid close enough attention to the exact degree of the top row angle. I will on my next Spherical Panorama, though! I know it does a top row above horizontal. My guess is that a top row that is a full 120° might not contain any horizon, and might ruin the whole stitch, with no common areas to stitch from.ITs significantly less after it done its thing than mavic 1. Last time i looked at gimbal angle it showed 15 or 20 degrees not 30.
The in-built sky fill is hideous for an image you want anywhere that isnt facebook and exposures often need to be balanced.
Hence photoshop needed to do it properly - and the extra missing sky is more work.
I'll definitely check, too! I'm still on FW 1.00.00. Pity that GO 4 won't let us save both jpg and DNG on the panoramas as originals. It's one or the other, but not both, unlike single images where you can save both, if we shot them completely manually. Unfortunately, PanoramaStudio 3Pro can't read the DNG metadata for GPS, for the mapping feature, so I use jpg's instead of DNG, which are plenty good enough because of the 1” sensor and 20MB still image size, and the 100MB size of the resulting 100% jpg stitch.I'll check it next time (i must admit i havent checked since last firmware upgrade, maybe its changed) but from memory i used to see +15 on gimbal only, not +30 (M1 did +30).
My workflow is basically convert the DNGs to TIFFs (with exposure corrections here in ACR). Then import the TIFFs into Microsoft ICE which does a good job of stitching (and free).
Then into Photoshop to correct the sky, canvas and aspect and the 3D workspace in Photoshop to make the seamless joins and create the final panorama.
And i agree a 360 looks far better if your main point of interest breaks the horizon line and as you said, that involves an upward angle.