Charles Adams
lvl.4
Flight distance : 3821312 ft
United States
Offline
|
I do not claim to be an expert photographer, and the solution I am about to promote is not necessarily the only solution to the problem I had. I'm curious for the input of others.
This weekend I was taking a variety of 360 degree panoramic shots with the M3. I save the RAWs, but I was utilizing the resulting JPG files. I found that every one I was taking was producing a "mushy" underexposed "bottom". The results were really crud.
Without going into my diagnostic process, I was able to identify the cause, and implement a solution (with a lot of trial and error in between).
The problem was that I was shooting in "pro", and what I had done was manually select the ISO and the apperture, and I was letting the drone change the shutter speed to account for exposure. That was producing my "mushy" bottoms.
Where I finally landed was manually selecting the ISO and the shutter speed, and letting the drone change the apperture (auto). I validated before taking the photo that the dimmest part of the view and brightest part of the view were still in range for the drone's apperture capabilities.
It seems that the "program" for executing the 360 panoramic was moving too fast for the shutter speed the drone was selecting for the dimmer parts of the scene. When I was able to select a fixed/faster shutter speed (and let the drone automatically select the apperture), the JPG for the panoramic turned out really well.
When I went to full "AUTO", the picture was turning out better, but the sky was still blown out. So full AUTO was better, but still not great.
|
|