Hi @Anil_Rao, thanks for asking. Now to be fair to PS, I’ll be the first to admit that I’m not a genius when it comes to the technical aspects, and I try to take the simple, easy route. There’s operator error too, and I’m not even sure I’m doing the best job in the field when capturing, which could make it harder for PS to do stuff.
Here is a close up example of a simple 4-image stack. It’s a grouping of aspen trunks separated by maybe 15-20ft front to back. I’m zoomed out at 170mm and shooting at f/8. There’s a visible difference in focus between front and back trunks, plus 2 other focus points in between. Anyway, PS often can’t figure out which area is best, or the in-focus areas are “too close” for PS to distinguish, and it attempts to do some content aware filling, or other things I don’t understand. The end result are areas that are not well defined and clearly not fit for printing or often even web display. This particular intimate scene worked better at f/16 than the attempt at stacking.
A little hard to tell in this image, but hopefully you can see. Keep in mind too, this image contains only aspen trunks - no moving in the wind and not many fine details or difficult edge transitions. Imagine what the difficulty is in hundreds, thousands of tiny leaves. In most of the grass images I do, the details are so small that the imperfections in the stacks are not even close to being visible in a 1500px web view.
Anyway, thanks for asking. And again, it’s highly likely that I lack some process flow to improve what PS can do.
EDIT: Same image after using Helicon. Significant improvement! But also now giving me insights in to what causes these transition areas. Still experimenting… Here’s the Helicon version using Method A