E-M1 III Focus Stacking II, IQ bad Compared to PS

Bassam Guy

Veteran Member
Messages
7,887
Solutions
15
Reaction score
7,575
The SOOC composite JPEG for a photo stack doesn't look very good. Others came out better but there are sharper parts that did not show in the composite. I fed Photoshop the same ORF files used in-camera and results are much better.



Screen cap of zoomed 1:1 comparison (PS on the left, SOOC on the right)
Screen cap of zoomed 1:1 comparison (PS on the left, SOOC on the right)

Photoshop's Composite
Photoshop's Composite

SOOC Composite
SOOC Composite

Is this expected? I'll go back to focus bracketing if I can't expect better than this.
 
Solution
Thanks but my question is about SOOC vs PS, not about camera movement, number of shots, aperture, etc. PS does a much better job than the camera using the very same images.
The answer to that is trivial.

A PC simply has way more processing power and fast memory available than a camera. The stacking software can use much more complex algorithms to stack.

Whereas the camera has to do the best it can with very limited resources, and provide a (any) result in short time.

In camera stacking is grossly overrated by marketing. It almost only serves the purpose of convincing consumers to buy the few Olympus/OM lenses that are "compatible" with focus stacking. The results are sub-par and only useful for two things: to assess if the...
Last edited:
By the majority of us, that is!

Photo Stack is not miraculous. It is a marvellous, but difficult technique, full of pitfalls. First of all, the parameters can be wrong: the number of shots, combined with the f value and the difference in between can easily result in areas, or strips of unfocused subject, which are a total killer of the shot. But this is more or less apparent.

But worse is the non-apparent difficulty. If the camera and lens is not held very steadily, things can go wrong. They can, of course, go totally wrong - but that is a blessing, because you are notified that there was a failure, a stacked image is not produced, but the individual frames are still available, as JPEGs or ORFs, to be processed afterwards, preferably in Helicon Focus or Zerene.

But they can also be apparently ok, no failure reported but the stacked image sucks. That happens when there was excessive wiggle of the photographer-camera-lens, and one or more frame just is not in the right place, and the stacking process includes some oof areas that totally ruin the image! It was, I suspect, the OP case. Fortunately, the individual frames are still available, in this case, and everything can be made good.

But to me that is not correct: if the shot is not 100% successful, a failure should be reported immediately, not by observing the image later. Perhaps a firmware update will improve this...

Note that camera motion in-between frames is much easier than it is thought. A special note to the fact the IBIS, however excellent it is, does not stop that. To my understanding, IBIS (and OIS, and synchronous function) correct camera motion while the frame is taken, not to my knowledge efficiently afterwards, not even when pressing half-way the shutter apparently freezes the image.

So, I think that Focus Stacking can be wonderful, but if we are not sure of total immobility we should brace ourselves, or find a support to steady the camera-lens during the process. Even a tree trunk, a fence, a door knob, a camera case, a boot...
Thanks but my question is about SOOC vs PS, not about camera movement, number of shots, aperture, etc. PS does a much better job than the camera using the very same images.
 
Last edited:
My E-M5 II can do in camera focus stacking but I don't have any of the Pro lenses need for that feature to work.
Install the hacked firmware. It will let you use any arbitrary lens with AF to do focus stacking on the EM5.2.

It will not always be as good as if you used the few lenses supported by the original firmware (which btw include the non-pro Oly macro lenses). Likely because of focus breathing that some lenses have. But it will work, and let's you decide if the results are acceptable to you.

It is unlikely OM will release any new firmware for the old EM5.2. So there is a good chance the hacked firmware is the last firmware you will ever install on that camera. Btw, in case you do video, it also removes the video duration limit.

https://www.mu-43.com/threads/modified-firmware-looking-for-users.99804/
However, I do a lot of focus bracketing and then stack the images in PS. I've never noticed any problem with sharpness. I agree that PS is slow particularly on my old computers.

****
 
Last edited:
Thanks but my question is about SOOC vs PS, not about camera movement, number of shots, aperture, etc. PS does a much better job than the camera using the very same images.
The answer to that is trivial.

A PC simply has way more processing power and fast memory available than a camera. The stacking software can use much more complex algorithms to stack.

Whereas the camera has to do the best it can with very limited resources, and provide a (any) result in short time.

In camera stacking is grossly overrated by marketing. It almost only serves the purpose of convincing consumers to buy the few Olympus/OM lenses that are "compatible" with focus stacking. The results are sub-par and only useful for two things: to assess if the bracketing worked or needs to be repeated, or for those that for some reason or another need to immediately upload the stacked results to show someone on the web.
 
Last edited:
Solution
I am afraid I didn't make myself clear. The technique is not "sub-par". If the images are perfectly aligned, it works like a treat - provided that 15 images are enough, which is not always the case. I have on several occasions used dozens of frames for stacking to my liking (afterwards). But if 15 frames or less are enough, and the camera is very steady, the result is excellent.

If the answer to any of these conditions is "no" - i.e., 15 frames are not enough or the camera moved during the take - then, as you say the little computer in the camera is not enough. No problem, the frames are there, go to a "big computer"!

However, on many, many circumstances, stacking works, and looks like a miracle! It just is not an universal miracle, but when it works it is as good as any stacking done some other way.

And I have seen faults in stacking done in many other ways, with different software, with halos and ghosting, and oof areas! In fact, I know photographers who swear they will never use it. But photography is full of pitfalls - noise, lack of dynamic range, lens aberrations, diffraction, metamerism, ... And we go on doing it, fighting one problem at a time - and enjoying it, and being proud of our resources and skills!
 
Thanks but my question is about SOOC vs PS, not about camera movement, number of shots, aperture, etc. PS does a much better job than the camera using the very same images.
The answer to that is trivial.

A PC simply has way more processing power and fast memory available than a camera. The stacking software can use much more complex algorithms to stack.

Whereas the camera has to do the best it can with very limited resources, and provide a (any) result in short time.

In camera stacking is grossly overrated by marketing. It almost only serves the purpose of convincing consumers to buy the few Olympus/OM lenses that are "compatible" with focus stacking. The results are sub-par and only useful for two things: to assess if the bracketing worked or needs to be repeated, or for those that for some reason or another need to immediately upload the stacked results to show someone on the web.
Lesson learned but nothing lost. I can use PS or other whether I have done in-camera stacking or regular focus bracketing.
 
I am afraid I didn't make myself clear. The technique is not "sub-par". If the images are perfectly aligned, it works like a treat - provided that 15 images are enough, which is not always the case. I have on several occasions used dozens of frames for stacking to my liking (afterwards). But if 15 frames or less are enough, and the camera is very steady, the result is excellent.

If the answer to any of these conditions is "no" - i.e., 15 frames are not enough or the camera moved during the take - then, as you say the little computer in the camera is not enough. No problem, the frames are there, go to a "big computer"!

However, on many, many circumstances, stacking works, and looks like a miracle! It just is not an universal miracle, but when it works it is as good as any stacking done some other way.

And I have seen faults in stacking done in many other ways, with different software, with halos and ghosting, and oof areas! In fact, I know photographers who swear they will never use it. But photography is full of pitfalls - noise, lack of dynamic range, lens aberrations, diffraction, metamerism, ... And we go on doing it, fighting one problem at a time - and enjoying it, and being proud of our resources and skills!
My answer remains the same. A PC based stacking software can not only use more elaborate algorithms. It can do additional steps to the stacking itself, like are necessary for merging imagines of slightly different size, or perspective as the camera ever so slightly moves between the shots. Especially if handheld bracketing. There are lots of things that can be done, that the in-camera firmware just cannot do for lack of processing power and storage space and the resulting time to execute.

Another way to explain would be: there is a reason a PC workstation cannot run on a tiny 10 Watt/hour camera battery.
 
I am afraid I didn't make myself clear. The technique is not "sub-par". If the images are perfectly aligned, it works like a treat - provided that 15 images are enough, which is not always the case. I have on several occasions used dozens of frames for stacking to my liking (afterwards). But if 15 frames or less are enough, and the camera is very steady, the result is excellent.

If the answer to any of these conditions is "no" - i.e., 15 frames are not enough or the camera moved during the take - then, as you say the little computer in the camera is not enough. No problem, the frames are there, go to a "big computer"!

However, on many, many circumstances, stacking works, and looks like a miracle! It just is not an universal miracle, but when it works it is as good as any stacking done some other way.

And I have seen faults in stacking done in many other ways, with different software, with halos and ghosting, and oof areas! In fact, I know photographers who swear they will never use it. But photography is full of pitfalls - noise, lack of dynamic range, lens aberrations, diffraction, metamerism, ... And we go on doing it, fighting one problem at a time - and enjoying it, and being proud of our resources and skills!
My answer remains the same. A PC based stacking software can not only use more elaborate algorithms. It can do additional steps to the stacking itself, like are necessary for merging imagines of slightly different size, or perspective as the camera ever so slightly moves between the shots. Especially if handheld bracketing. There are lots of things that can be done, that the in-camera firmware just cannot do for lack of processing power and storage space and the resulting time to execute.

Another way to explain would be: there is a reason a PC workstation cannot run on a tiny 10 Watt/hour camera battery.
And my answer remains the same! :-) Photo Stack is a wonderful process, with limitations (lots of them!), excellent and convenient when it works, with work arounds when it does not, and there is always going back to our beloved workstation, with the same data!
 
You left out some details. Did you shoot with a tripod or handheld? And what was the stacking setup (number and differential) you used?

. . . Steven
Handheld. Just eight shots.
That could lead to a problem because the focal depth of the flower is significant.
Thanks, but that doesn't explain the disparity between PS and SOOC - and the ORFs have all areas of interest well focused.
But something is goofy here. The ICFS of the flower last image does not show any focus at all on the most distant lobe of the flower. That is not something I see when using ICFS. Instead short comings lie in some ghosting (likely motion or change of lens perspective on largely OOF elements of an individual image), or largely failed stacks where something moved during the shooting of the individual images.
 
[...] Instead short comings lie in some ghosting (likely motion or change of lens perspective on largely OOF elements of an individual image), or largely failed stacks where something moved during the shooting of the individual images.
Gary, when something moves during the shooting but not much, strange things can happen and some frames can be ignored from the final result, without any information. I have seen this, have even "forced" this to happen.

It is not common, though, but happens.
 
[...] Instead short comings lie in some ghosting (likely motion or change of lens perspective on largely OOF elements of an individual image), or largely failed stacks where something moved during the shooting of the individual images.
Gary, when something moves during the shooting but not much, strange things can happen and some frames can be ignored from the final result, without any information. I have seen this, have even "forced" this to happen.
Well, that may be. In shooting of mosses on 2/15, I positioned my tripod on some rather not necessarily stable vegetation. I noticed that on some stacks with the EM-1X that the camera only recorded 6 or maybe 8 images in a stack set for 15. I thought there was something wrong with my EM-1X's ICFS algorithm implementation, but perhaps the camera will throw out certain images if they are bad enough, but keep them if only they are a bit messed up. When the latter happens the stack is not all that great. I didn't know the ICFS function actually just deleted certain bad single images.
It is not common, though, but happens.
 
[...] Instead short comings lie in some ghosting (likely motion or change of lens perspective on largely OOF elements of an individual image), or largely failed stacks where something moved during the shooting of the individual images.
Gary, when something moves during the shooting but not much, strange things can happen and some frames can be ignored from the final result, without any information. I have seen this, have even "forced" this to happen.

It is not common, though, but happens.
Some frames likely were ignored. I was hunched over with nothing to lean against. Out of about three tries, only one didn't get the "Error processing..." message.
 
Does Anyone know where I can get the download file for the Latest Firmware Update for the EM1-mk3 (which would be v1.6 not 1.5) ?
EDIT: Actually, ANY Firmware file - from v1.2 to 1.5 would also be appreciated !!!!

I've searched for a download file, but all references I've pursued so far lead to the Workspace update process.
I would like to apply a 'hack' to the firmware, allowing any AF lens to be seen/usable for 'Focus Stack' on the EM1-iii...
I applied the hack to my EM5-ii, and it's wonderful and HUGELY useful not being restricted to PRO lenses only for Focus Stacking (once you get a handle on stack settings).
The hack for EM1-iii (& ii) is available for earlier versions of firmware, but not the latest 1.6, which needs MODing the actual firmware file to implement the 'hack'.
I made the mistake of updating my EM1-iii because I had purchased a 40-150 f4 PRO... which I returned after testing it alongside some of my other lenses... :-\
Can't go backwards on firmware install... so I need an EM1-iii v1.6 firmware file I can hack...
Thanks for any assistance.
EDIT: Actually if anyone knows where or has EM1-3 firmware files for v1.2 thru 1.5, would be greatly appreciated
Also, I have friend who has an EM1-2, and will prolly want old firmware file - v 3.2 or newer, before 3.7...
again getting either/both older firmware files would be VERY appreciated !!!
Thx
Yuri

--
" For the animal shall not be measured by man. In a world older and more complete than ours they move finished and complete, gifted with extensions of the senses we have lost or never attained, living by voices we shall never hear. They are not brethren, they are not underlings; they are other nations, caught with ourselves in the net of life and time, fellow prisoners of the splendour and travail of the earth.” - Henry Beston
 
Last edited:
UPDATE - Focus Stacking for EM1-3 using ANY AF lens, not confined to OLY PRO lenses !

AWESOME ! My EM1-3 now does Focus Stacking with non-PRO AF lenses - tested and confirmed w/ Oly 14-150 Focus Stack test- using v1.5 MOD firmware.
So, I can report that doing the HEX modifications shown in this post (using HxD Hex Editor for win)
https://www.mu-43.com/threads/modified-firmware-looking-for-users.99804/page-23#post-1606415
to the v1.5 firmware for the E-M1-3 worked for me.
Saved Mod File, renamed to E1399999.BIN and onto SD card into DCOLYMP folder. Suggest removing the existing ALBM folder before proceeding with firmware install.
If you need the 'Clean' version of Firmware V1.5 (EM1-3) , Michael Meissner was kind enough to post links to many different firmware for a variety of Oly bodies here:
https://www.mu-43.com/threads/firmw...meras-january-2023.118773/page-2#post-1622611
Camera works as before, many settingsnot changed, or not reset... I expect some will be... like date.
Camera reports firmware v1.5 (I had v1.6 on it before the MOD install).
... can't speak to the video 30 min. limitation removal - I haven't attempted that yet, and don;t expect to in the near future.
Thx
Yuri
 

Keyboard shortcuts

Back
Top