When you say 12 photos, are you taking 3 360 degree shots, each with 3 exposures? Merging each shot to get 3 HDR images, and then feeding all 12 into EasyHDR? Thu 3:12 you post an example of your results? I would like to see what you are getting with your method. Or, if you're happy to just add a large blur at the nadir: not a problem. Then, if that upsets any other stitching areas: overlay two final versions and use an eraser tool on the top layer to expose patches of the other version below. Sometimes need to turn it off for those images. One minor issue to watch out for is the Dynamic Stitching option can sometimes get too enthusiasic with wooden flooring planks near the Nadir and merges them weirdly.
Needs to be a medium/large room with lots of details for it to latch onto for the calibration. If you calibrate it in a small bathroom you'll get different results when you then take images outside, or in a larger room also vice versa. Takes a little experimentation to find the sweet spot. If you're getting blurred margins in the Insta360 tool then the camera is calibrate incorrectly.
#Easyhdr wrong image dimensions software
The manufacturers know more about their sensor than anyone else, so they made it export JPGs that have already done all the work better than most external software (that I've tried, anyway). gave me a perfectly correct, but very noisy and CA filled result. I found having to calibrate the lenses, etc. I defer to your better experience with DNGs. EasyHDR notes that there are several images with the same exposure (all the +/-0 and merged images) but uses them to get rid of the noise.
#Easyhdr wrong image dimensions plus
I don't use PTGui, I stack 12 images in EasyHDR, which is 3 different exposure settings, plus their merged HDR image, and use Smart Merge, rather than 'True HDR'. Just change the Default FoV to 70 and back to FoV Mode: Vertical and hope for the best. If you're not going to use this on mobile, maybe don't switch to Diagonal just now, because: although it's more correct, using it exposes a lot of mathematical bugs you'll end up fighting until they're fixed. That and the stitching in the studio appears to be geared for outside work were blurring the margins works. That made the noise go from terrible to simply bad.ĮasyHDR doesn't appear to do any better or worse than PTgui for creating HDR images.Īs for using the jpg files generated via the Inst360 studio vs the DNG files, the DNG file won hands down. I also tried 9 exposures covering a range of +/- 4. Reducing the field of view, switching to diagonal mode appears to help. I did some playing around with the suggestions. Using a tripod and having no features less than 3 metres from the camera is required. Stitching is OK if you calibrate the camera correctly, which is a bit of an art.
insp files can be merged and batch exported from the software easily enough, then recombined in EasyHDR.
The internal processing libraries from the manufacturer that are used to generate the JPGs do a better job than any software I've tried to improve them. Alternatively, using Neat Image software will do a very good job of getting some of that noise out of your images.ĭNGs from the camera are a waste of time. You've also got a fair bit of noise, which you can avoid in the future by taking more exposure ranges, +/-4 and +/-2 and stacking them with some HDR software that is 360 image aware like EasyHDR. It would be 90/95 in FoV Mode: Diagonal, but the maths is currently fighting against you by stretching your Portrait view over a Landscape monitor. If you set up the FoV mode correctly to Diagonal, or ever do a panorama that is intended to also work on a mobile: you can't do much more than a crossfade with Transitions because they're currently FUBAR'd.įor FoV Mode: Vertical viewed on a 16:9 monitor, your Default FoV should be 70/75 degrees to look "normal". See my recent post about it here: viewtopic.php?f=6&t=14932 (I'm going to get back to the quality/colour issues thread later, when I can work out what the heck is going on.)Īs I replied in a previous thread: as your navigation method can't really work on mobile, you might be OK if you fudge the FoV, but it will look different on 16:9 Monitors, 4:3 monitors and superwide monitors. You can tell because when you change the width of the browser it simple reduces the 'window' on your panorama, instead of adjusting to the new size and zooming in/out to fit correctly. The obvious problem is you're using FoV mode: Vertical, which is intended for Portrait/Mobiles.
I think there are a lot of areas that I can improve.
0 kommentar(er)
