Martin G. wrote in post #12883413
John,
I am glad you found your own answer and even better for you, it is the program you already have!
I admit, it was a pleasant surprise 
Martin G. wrote in post #12883413
John,
I am not surprised that Rik took time to properly answer. Too bad you did not have the link to the forum, will send it to you in private, I am not sure if it is allowed to post links to another forum here. It would have been the best place to get feed backs as members there do massive stacks all the time.
Once again, I thank you for your time, Martin. I am registering on that forum right now and will try to see if I can find a satisfactory answer. By "satisfactory," I mean an answer that makes sense, because (although Rick did answer), none of what he said actually proved true in my own experiments.
For example, Rik said Photoshop routinely makes "incorrect assessments" as to what should be in focus, yet it was the Zerene program that made FAR more "incorrect assessments" in my complex test.
Rick also said Photoshop also worked from a "layers" model (which Rik disfavors), but he didn't really say why, other than it makes it "awful" for re-touching. However, Photoshop was so accurate, there was nothing to re-touch, so what really proved to be "awful" for me was dealing with the need to retouch almost everything that the Zerene program left me with!
Martin G. wrote in post #12883413
John,
I believe I use Zerene in a non conventional way, I never take what it produces as an image. So whatever the output is, I do not really care as I redo everything manually. I therefore have no artifacts and no bokeh problems. But it takes a lot of time and patience. So it is excellent if you can get the result you want in an instant in Photoshop.
Well, we most definitely are not in agreement here!
The way I look at it is, Time is Money, and the more time anyone has to spend "correcting" what the software should have done right to begin with, the less that person really needs the product. (Taken to the extreme, if you had to do everthing by hand, then you wouldn't need the product at all.)
By contrast, the more you are able to "push a button" and get everything you want to get done, done right, the more that product becomes a useful tool that helps you leverage your time, not waste your time cleaning-up the product's botch-job.
This basic goal of a stacking program is exactly why I felt Adobe CS5 was the superior product ... because it did the job that the other products should have done ... so I don't have to waste my time doing the clean-up work for them. I mean, just look at my images on the blog post and imagine the time it would have taken to correct the botch-jobs of the other products ... no thanks!
It would have been impossible to correct the botch-job that Helicon-Focus did to my image, and would have taken hours to correct the Zerene job too. And, while I realize different results would obtain for simpler stacks, the idea of any tool is to make my life easier ... not hours-and-hours "harder" ... and that is exactly what the Adobe product did do for me and what the other products failed to do.
Martin G. wrote in post #12883413
John,
I would be curious to hear what Rik has to say about this. It seems that very few very experienced "stacker" use Photoshop for stacking, but it could simply be the pricetag of that program, 1000$ versus 100$ for Zerene + let's say Photoshop Element for 120$ in my case. So 220$ (once more, you do not need the pro-version to do stacks) versus 1000$, it is a huge difference for many of us.
Well, I touched on what Rik said above, but again it just didn't obtain when I actually compared the products. (And I still haven't heard back from him, since I sent him the full-sized comparison of the results ...)
As for the cost of each product, I am sure price does have a lot to do with more people stacking with a cheaper download than a more expensive one. More people who are "having fun stacking" are going to be willing to spend $100 on Zerene than are going to want to spend $1000 (10x that amount) on the Adobe CS5. (Plus, I don't think Adobe has even had the stacking capability until recently with CS5 Extended--I may be wrong on that, I don't know).
Yet, here again, Time is Money, so if you're spending an extra :45 to an hour per image, "touching up" all the mistakes of a cheap program ... factor that by dozens/hundreds of images a week ... and again multiplied over months/years of time ... and you are losing in a major way in the long run.
Martin G. wrote in post #12883413
I really never had good results with Helicon, I am "happy" to see that you came to the same conclusion. Not that I want to "bash" on a program, I simply do not get what's the big deal with Helicon.
All the best
Martin
I am with you Martin, I honestly don't want to bash anyone either, but my experience mirrored yours and the Helicon-Focus was the worst of the bunch. Destroying the bokeh in a macro shot is like taking the grapes out of the wine ...
Where stacking is concerned, it isn't just the ability to "align" multiple images correctly, it is also the ability to retain the colors accurately and pleasingly, not to mention how critical it is not to botch-up the smooth & creamy aspect to the bokeh, that comprises the whole image.
Maybe I did something wrong in my tests, but I doubt that very much. I used the exact same files for all 3 programs, and I rendered all 3 of them into one stacked 16-bit ProPhoto .tiff image ... that was then re-sized to a 2000 x 1333 8-bit sRGB .jpg image for internet viewing. These flaws did not just happen in the conversion to sRGB .jpg, either, they were all immediately viewable in the final 16-bit ProPhoto .tiff "stack."
Except in the Adobe CS5 stack. That was the only one which transferred seamlessly to a 16-bit ProPhoto .tiff, and again seamlessly to an 8-bit sRGB .jpg.
I am sure there are many instances where these other programs can stack "simpler" images with straighter lines just fine, but I purposely chose a complex image with dozens of curvy ends, and processed it with the maximum-potential color space, precisely to see which program/s would rise to the occasion ... and which program/s would have their limitations exposed. And, for me, the Adobe CS5 stack was the one that came through.
Cheers!
Jack
.