Disturbing Focus Stacking
-
#1. "RE: Disturbing Focus Stacking" | In response to Reply # 0
Sun 08-May-22 11:47 AM | edited Sun 08-May-22 12:07 PM by aolanderI'm not seeing what you're calling "harsh". More detail in the foreground rocks in the stacked image. Since the front to back distance isn't that great, you probably would have enough DOF to shoot one shot at f/11, focusing on the first flowers. Although I see you shot it at 200mm, so maybe not.Alan
-
#2. "RE: Disturbing Focus Stacking" | In response to Reply # 0
Sun 08-May-22 09:37 PM | edited Sun 08-May-22 09:37 PM by elec164I agree with Alan in that I'm not sure what you are referring to as harsh that disturbs you.
For me having the two images at different sizes makes it a bit difficult to evaluate and compare.Pete
Visit my Nikonians gallery.-
#4. "RE: Disturbing Focus Stacking" | In response to Reply # 2
Mon 09-May-22 04:14 AMI'm not sure why they are different sizes.-
#6. "RE: Disturbing Focus Stacking" | In response to Reply # 4
Mon 09-May-22 05:28 AM>I'm not sure why they are different sizes.
Well looking at the EXIF, one is 1193x794 and the other is 904x601.
So clearly they are different pixel dimensions, question is when and why that happened.Pete
Visit my Nikonians gallery.
-
-
#3. "RE: Disturbing Focus Stacking" | In response to Reply # 0
"Great things are not done by impulse but by a series of small things brought together." Vincent Van Gogh
See my portfolio.
#5. "RE: Disturbing Focus Stacking" | In response to Reply # 0
It appears that there is an exposure vignette to the upper corners which creates a bright arch on the exposed rocks. This draws the eye to scan in an arch that does not feel natural.
If I take the first image and overlay/re-scale the second to match, the upper corners are darker in the merged image, exacerbating this effect. The merge itself looks great.
The exposure between frames may have been caused by a change in ambient light from cloud movement or movement of surrounding trees. I suspect that the water movement between frames may have changed the exposure of the rocks, and an average between all stacked frames results in the darker upper corners.
The software may have averaged the exposures during stacking and emphasized the lights and dark areas. Depending upon what stacking software you use, you may have options on how the software deals with differences in exposure between frames.
I have had success in similar images by overlaying a single frame on a stacked image and experimenting with blend modes. Perhaps an average blend mode will help, or even a screen blend mode with a 25%opacity will lighten the darker areas to remove the effect, or some dodge and burn could also help.
-
#7. "RE: Disturbing Focus Stacking" | In response to Reply # 5
Mon 09-May-22 04:23 PMShot with a Z6 and 70-200mm S lens
All five original frames were shot manual.
ISO 160
200 mm
f/5.0
1/30 sec-
#8. "RE: Disturbing Focus Stacking" | In response to Reply # 7
Mon 09-May-22 06:12 PMApplying adjustment to the individual frames before stacking versus adjusting the stacked image.
Capturing the individual frames in manual, converting them, un-adjusted, into image files, and combining them into a stacked image, versus applying adjustments to the individual frames, converting them into an image file, and then stacking them, may not sound like a great difference, but can make a big difference in the final result.
Consider what happened when we apply a curves adjustment to an image. If we move the middle of the curve up, we increase the level of the R,G, and B channels. However, as both ends of the line remain anchored to their respective corners, we create a curved line drawing the center of the curve upwards. However, the rate of adjustment from black to mid-tone rises faster, and the rate of change from mid-tone to white rises slower than the original.
Now consider that this curves adjustment is a layer and that we can copy this layer and apply it to another image. If the new image is brighter to begin with, the result will differ from an image that was darker to begin with.
In your image, I suspect that the water was reflecting light onto the rocks and towards the camera, and due to the rippled surface, the amount of reflection between frames changed for the rocks and water but remained the same for the other areas.
Applying the same curves adjustment has the same effect on the areas without the sunlight reflected off the water, but a different result between frames on areas that have a changed amount of light reflected off the water. In other words, the brighter regions get brighter while the darker areas remain the same.
In many cases, it does not matter so much if you make adjustments before or after stacking the images, but in this case, I believe you stumbled upon one where it may be better to adjust after stacking.Visit my Nikonians gallery.
-
#9. "RE: Disturbing Focus Stacking" | In response to Reply # 8
Mon 09-May-22 06:43 PMI don't think all this has anything to do with it. I see only subtle differences between the images, and being slightly different sizes, 200 pixels, on the long side, doesn't matter much.Alan
-
#14. "RE: Disturbing Focus Stacking" | In response to Reply # 9
Tue 10-May-22 05:13 AM>different sizes, 200 pixels, on the long side, doesn't matter much.
That 200 pixels is a linear dimension but image resolution is by area.
When considered that way it's about a 43% reduction or near 2:1 pixel reduction. Personally I would consider that significant being that those pixels aren't just eliminated (as in cropping) but instead blended into surrounding pixels. That to me alters the tonal values significantly enough to matter when evaluating something like this.
Making different sized prints of the same resolution file is different than displaying equal sized images on screen from two different resolution files of the same capture. Of course YMMV always applies.Pete
Visit my Nikonians gallery.-
#21. "RE: Disturbing Focus Stacking" | In response to Reply # 14
Tue 10-May-22 05:39 AMI don't know what happened here, but the pictures that were sent are:
UNSTACKED - 3616x2406
STACKED - 3614x2403-
#26. "RE: Disturbing Focus Stacking" | In response to Reply # 21
Tue 10-May-22 08:57 AM | edited Tue 10-May-22 08:58 AM by elec164When embedding an image into a post there is a restriction on size in both pixel dimensions and file size.
If you click on the 'More info about attachments' you will see an explanation on the restrictions. Part of which says if the pixel dimensions exceed that which is allowed, the image will be resized to fit restrictions. I believe there are ways around that but don't attempt it so am unsure of how to do it.
-
-
-
-
-
#10. "RE: Disturbing Focus Stacking" | In response to Reply # 8
-
#11. "RE: Disturbing Focus Stacking" | In response to Reply # 10
Tue 10-May-22 03:57 AM | edited Tue 10-May-22 03:58 AM by Pete OI do not know what software you use for stacking images, or, what process you use for processing images.
My process is to bring raw images into the processing software and evaluate the images for use.
I personally prefer to use Affinity Photo for stacking and have had success with macro image stacks by allowing affinity to stack the raw images, however, this consumes a lot of computer time. images are faster to stack than raw files.
The Affinity stack allows you to select the individual image files within the stack after processing and you can mask areas that you don't like or select a different stack region if desired. This is especially useful with macro image stacks and can be a get out of jail free card if you discover something moved within a frame during capture, you can select the best of the rest from the images on either side within the stack to replace that area. (you can also do the same when doing manual stacks)
This is a very intense way of doing things but achieves amazing results. You can do the same with Photoshop, but I prefer the Affinity UI.
I will apply this caveat, I sometimes don't like the results with Affinity Photo developing raw images, in which case, I use Adobe Camera Raw via Adobe Bridge and stack the DNG files instead.
I apply image sharpening and adjustments as the stacked file are converted into an image file that can then be post-processed as desired.
Stacking is something you need to practice and become fluent in the software and what can be achieved. Practice doing both, stacking processed and unprocessed image files, and doing side-by-side evaluations on your equipment, because adjusting digital images on a computer is a subjective exercise that differs between systems and hardware.Visit my Nikonians gallery.
-
#12. "RE: Disturbing Focus Stacking" | In response to Reply # 11
Tue 10-May-22 04:43 AM | edited Tue 10-May-22 05:53 AM by grnzbraThank you for the tip about masking off areas. I ran into a problem with cascading water that should be able to be solved by selecting single frames for those areas.
You mention image files and raw files. What is an image file?-
#13. "RE: Disturbing Focus Stacking" | In response to Reply # 12
Tue 10-May-22 05:13 AMImage file = your photo, raw, jpeg, tiff, whatever it might be.
Raw file = a raw image fileAlan
-
#15. "RE: Disturbing Focus Stacking" | In response to Reply # 13
Tue 10-May-22 05:17 AM>Image file = your photo, raw, jpeg, tiff, whatever it might
>be.
I guess it may depend on software used, but I (as Pete O) also use Affinity Photo and find that a focus stack using JPEG's or TIFF's comes out better than when using NEF's. Personally I don't care much for Affinity Photo's raw converter.Pete
Visit my Nikonians gallery.-
#17. "RE: Disturbing Focus Stacking" | In response to Reply # 15
Tue 10-May-22 05:25 AM | edited Tue 10-May-22 05:31 AM by aolanderWhen I save these images to my computer and view them, the pixel dimensions are 800 x 532 and 799 x 532. And they look exactly the same size when viewed in this post.Alan
-
#18. "RE: Disturbing Focus Stacking" | In response to Reply # 17
Tue 10-May-22 05:33 AM>When I save these images to my computer and view them, the
>pixel dimensions are 800 x 532 and 799 x 532. And they look
>exactly the same size when view in this post.
Interesting. When I save them they are 1193x794 and 904x601, just as stated in the EXIF data.Pete
Visit my Nikonians gallery.
-
-
-
#19. "RE: Disturbing Focus Stacking" | In response to Reply # 15
Tue 10-May-22 05:36 AMOk, a raw file is an image data file.Alan
-
-
-
#16. "RE: Disturbing Focus Stacking" | In response to Reply # 12
Personally I don't consider the NEF an image file but a file containing the raw sensor data that can be converted into an image file. Image files would be files that contain data that is directly mappable into a screen image such as BMP, JPEG, TIFF,,,,, etc.
edited to add:
An NEF is a proprietary file format based upon the TIFF file format. So in essence all of them are files,,, the further distinction is from what the file contains (raw sensor data or image file data).
Pete
Visit my Nikonians gallery.
#20. "RE: Disturbing Focus Stacking" | In response to Reply # 12
Think of a raw file as the raw “ingredients” of a photo that will need to be developed to reveal a photo.
Raw files are quite a bit larger than JPEG or TIFF files. Most professional photographers shoot in raw because it gives them more information to work within the post-processing phase.
Once a file is converted into a JPEG or TIFF file, the raw data becomes a file that contains a developed image. Any adjustments or sharpening applied during development has been baked into that image. A TIFF file is the preferred filetype for people who print images because they can retain a greater dynamic range, a JPEG file is the preferred filetype of digital images because they are compressed to a smaller size, and much of the image data is lost.
A raw file is not an image file, it is a data file.
The advantage of using raw files is that you can develop that photograph over and over, without destroying the original. The filetype contains more details such as shadow detail and can be manipulated more than a processed image file.
Edited to ad,
Most DSLR camaras can record data as a raw data file or as a processed JPEG or TIFF file. The settings on the camera that can apply picture profiles such as vivid, black and white, etc, are applied in-camera prior to saving that image. The NIKON raw file type is NEF.
You can get the camera to save raw data files and JPEG image files at the same time, some people use the JPEG as a backup image, or as a small image file that can be transferred quickly via the internet or wireless transfer.
You can fit more Holliday snaps onto a memory card as JPEG files because they contain less data.
Visit my Nikonians gallery.
-
#22. "RE: Disturbing Focus Stacking" | In response to Reply # 20
Tue 10-May-22 05:59 AM>Raw files are quite a bit larger than JPEG or TIFF files.
That's rather interesting. This photo is 8.45mb as a JPG, 27.3mb as a RAW file (Nikon Z6) and 138mb as a TIFF file. (this is not a stacked image).
File size:177205 bytesFile date:Tue 10-May-22 05:55 AMCamera make:NIKON CORPORATIONCamera model:NIKON D750Date/Time:Mon 02-May-22 10:47 AMResolution:1200 x 801Flash used:NoFocal length:46.0mm (35mm equivalent: 46mm)Exposure time:30.000 sAperture:f/8.0ISO equiv.:200Exposure bias:2Whitebalance:ManualMetering Mode:otherExposure:ManualExposure Mode:ManualJPEG Quality:80Comment:Copyright 2022 C. Lind Aitken======= IPTC data:=======City:Record vers.:4 4Keywords:onal Park cabin light painting night cabinByline:C. Lind Aitken(C)Notice:COPYRIGHT 2021 C. Lind Aitken
Attachment#1 (jpg file)
-
#24. "RE: Disturbing Focus Stacking" | In response to Reply # 22
Tue 10-May-22 06:16 AMA TIFF file CAN also record adjustment records which save details about some adjustments that have been made to the file. This adds to the file size.
TIFF photos are used mostly externally. If you want to send someone a high-resolution image with all the details and give them some room for manipulation abilities, uncompressed TIFF files are preferred.
Raw files are also uncompressed, it is like the digital equivalent of a film negative. Unlike TIFF, a RAW file first needs to be processed or developed using an Image Data Converter or other compatible software. The benefit of this format is that you can adjust various attributes such as contrast, saturation, sharpness, white balance, and others without degrading the image. Afterwards, it can be saved to another image format like TIFF or JPEG. Consider a TIFF file to be a raw file that has been unpacked.
Raw files from the image sensor have only one value for each pixel (red, green OR blue) while a TIFF has all three values for each pixel. During development, like converting a raw data file for viewing them on a computer, the missing values are interpolated from neighboring pixels (called demosaicing).Visit my Nikonians gallery.
-
#25. "RE: Disturbing Focus Stacking" | In response to Reply # 24
Tue 10-May-22 07:04 AM>Raw files from the image sensor have only one value for each
>pixel (red, green OR blue) while a TIFF has all three values
>for each pixel.
Indeed and that's why TIFF files in general are larger than NEF's. Put another way the NEF has 12-bit /14-bit per pixel whereas a 16-bit/channel TIFF has 48-bits per pixel.Pete
Visit my Nikonians gallery.
-
-
#23. "RE: Disturbing Focus Stacking" | In response to Reply # 20
>uncompressed data from your camera sensor. It is sometimes
>referred to as a digital negative.
While I agree that the NEF contains raw sensor data, the level of compression and whether its lossless is another issue. It can be compressed or uncompressed as well as lossy or non-lossy.
>Raw files are quite a bit larger than JPEG or TIFF files
Compression aside, file size is directly a function of pixel dimensions and bit-depth. While in general NEF's are larger than JPEG's (depends upon the level of compression of the JPEG's) they are generally smaller than 16-bit TIFF's.
Pete
Visit my Nikonians gallery.
G
UNSTACKED
STACKED