G80 close-up focus bracket stacks - Inside a paperweight

This was an experiment I have been meaning to do for a while. The subject is a glass paperweight that is one of my wife's favourite possessions. I have tried to photograph it before, using single shots, but was not really happy with the results. To my delight, my wife was rather pleased this time round.

I used an Olympus 60mm macro on a tripod-mounted G80 to capture sets of focus bracket images, the closest set being almost 1:1. I set the camera to capture 200 images for each bracket set at f/2.8, with an increment of +3, with the focus running from close to far. I used manual focus and set the focus to a bit nearer than anything I wanted to focus on. I let the capture run until it had obviously passed the furthest thing I wanted in focus, or for the full 200 shots. I shot JPEG as the G80 buffer only holds 45 or so raw files and exceeding that would have slowed the capture process down too much for my taste.

I loaded each bracket set into Helicon Focus and removed the images that were in front of and beyond what I was interested in. I used the stacking method and number of images shown below for each scene. I exported the stacked images as JPEG and did various global and local adjustments to them in Lightroom.

168 images, Depth Map method

42f8611fe4d244eea3109c2019764dca.jpg

54 images, Pyramid method

804c1c16018e488fbd23591e88ba1cd2.jpg

42 images, Depth Map method

86102d350a374163a52534d060a1af34.jpg

87 images, Depth Map method

a654aa4b11974734b89fea238f2312a6.jpg

99 images, Pyramid method

60ee8b00f75f4dc3a5baa60b2145e643.jpg

90 images, Pyramid method

96f9e82e984c428d915be2efb35ac297.jpg

--
Nick
http://www.flickr.com/photos/gardenersassistant/collections/
GardenersAssistant Photography Videos - https://www.youtube.com/channel/UCmBgEwRDfiQMYTPORSzDxvw
https://www.talkphotography.co.uk/t...-dslr-primes-a-journey-of-exploration.531050/
Beautiful photos! These and your other focus bracketing series make me save up for a G80 (or EM5ii)!
Thanks. But please do bear in mind you are seeing the few successes I have had. I'm actually doing hardly any bracketing and stacking because of the problems I have had getting nice (to my eye) results. And the ones that do work can need lots of time and effort to make them look ok.

I wouldn't want you to spend lots of money and be disappointed. If you have other reasons for wanting a G80 or EM5ii then fine, but I wouldn't use bracketing/stacking as the main reason for getting a new camera.

--
Nick
http://www.flickr.com/photos/gardenersassistant/collections/
GardenersAssistant Photography Videos - https://www.youtube.com/channel/UCmBgEwRDfiQMYTPORSzDxvw
https://www.talkphotography.co.uk/t...-dslr-primes-a-journey-of-exploration.531050/
Thank you for putting things into perspective.

I'm still using a 1/1.7" compact (Nikon P7800) and happy with it (and it's sharp 28-200 zoom lens), but would like to get more into macro photography in the future. Budget, size and weight wise, I'm looking at mFT.
 
Last edited:
I shot on 2, i think 3 is maybe too far. On G80 and Em1 are both on increment 2.
Thanks. Could you point out the problems you are seeing that using 2 rather than 3 might solve?
If too close, 3 might be too far away.
So no specific problems you have noticed in this case with 3?
While with 2 on Oly and Pana, actually get this number as others adopted, so never a problem.
A method brings you fine background, without dots, B is somewhere in the middle, more sharp but doted background, while C gave you much more sharp than A and B, but noisy too. So in that case i combine all three in photo stack. I choose which part will present, what need to be in focus is on B and C, back is combo of A and some B.
What surprised me about these is that I didn't feel the need to combine versions.

Another combination I use sometimes is one of the parameterised methods, A or B, using two version with different parameter values. That is for dealing with halos.
If mixing idle setting 4-8 you can get halos, especially on A and B.
It was a while ago now (I don't do much stacking), but for halos, with for example B, I seem to recall using one with a low value for Radius (with the halos) and another with a high enough radius to not have the halos, and using the first as the base version and brushing in from the other one over the halos.
When you will have a situation when just some part should be in focus, A and B are very welcome since A+B combo is making background and C+B for the object in focus.
In what way do you combine A+B and C+B. Are you layering and masking in Photoshop or similar, or do you do some/all of it in Helicon?
You should see in full size, to see nice background (no dots) :

Link1

Link2
They look very good. As regards halos, they are rather simpler than the ones I have had most problems with which had more complicated geometry. This is an example that I talked through in this video starting at 21:55.

73e64558be824698808162cc33ac5f87.jpg



--
Nick
GardenersAssistant Photography Videos - https://www.youtube.com/channel/UCmBgEwRDfiQMYTPORSzDxvw
 
I'm still using a 1/1.7" compact (Nikon P7800) and happy with it (and it's sharp 28-200 zoom lens), but would like to get more into macro photography in the future. Budget, size and weight wise, I'm looking at mFT.
I use a camera with a smaller than 1/1.7" sensor (1/2.3") much of the time for my macros of insects etc - a Panasonic FZ330 and before that an FZ200 and before that a Canon SX10 and a Canon S3, all with close-up lenses. I also use mFT - G3, G5 and now G80, with close-up lenses and also an Olympus 60mm macro. I have also used an APS-C dSLR, Canon 70D, quite a lot with both close-up lenses and Sigma 105 macro lens.

I haven't been able to convince myself that either (a) mFT or APS-C gives me overall better results for most of what I do than the bridge cameras or (b) that a macro lens gives me overall better results for most of what I do than close-up lenses on mFT or APS-C.

I know this sounds heretical, and to many people it seems obviously and self-evidently wrong. However, it is a complicated story (and I have chosen my words very carefully - please note especially the "for most of what I do" part of it). I have written up my journey of kit, technique and processing options and experiments over more than three years in the tediously long and unreadably detailed series of posts linked at the bottom of my sig below. I'm not suggesting that you wade through that. Here is something rather more straightforward you might like to consider.

Here are nine examples, one each from a Canon SX10 bridge camera, an FZ200 bridge camera, a G3, G5 and G80 mFT, and two each from an FZ330 bridge camera and a Canon 70D dSLR. You may find it instructive to work out which images came from the small sensor, mFT and dSLR cameras, and also which ones used close-up lenses and which used macro lenses. (There is, quite literally, more to this than meets the eye, so if you are interested we might later want to discuss some other considerations, for example subject matter, usability and post processing. These all play quite heavily into my considerations about what kit to use.)

#1

efe5d93e4a16417986b04946b8f58f38.jpg



#2

70a1fc3844d0413d966f7a4afe8baba4.jpg



#3

ea9b44f9a21e4122bf7e25e020352e8b.jpg



#4

1945b3e43a8f4e148775cd8ede5f10ed.jpg



#5

41c3c29fb70d4f6185710a5cb69888a4.jpg



#6

db1a451fa8b24d9798084ce9d3d98703.jpg



#7

a267e94decb3428d917589c2eb294931.jpg



#8

d96feef560124c4da19697a6ccb8da4f.jpg



#9

28664ac962784a83bae8a41ed114b877.jpg





--
Nick
GardenersAssistant Photography Videos - https://www.youtube.com/channel/UCmBgEwRDfiQMYTPORSzDxvw
 
I'm still using a 1/1.7" compact (Nikon P7800) and happy with it (and it's sharp 28-200 zoom lens), but would like to get more into macro photography in the future. Budget, size and weight wise, I'm looking at mFT.
I use a camera with a smaller than 1/1.7" sensor (1/2.3") much of the time for my macros of insects etc - a Panasonic FZ330 and before that an FZ200 and before that a Canon SX10 and a Canon S3, all with close-up lenses. I also use mFT - G3, G5 and now G80, with close-up lenses and also an Olympus 60mm macro. I have also used an APS-C dSLR, Canon 70D, quite a lot with both close-up lenses and Sigma 105 macro lens.

I haven't been able to convince myself that either (a) mFT or APS-C gives me overall better results for most of what I do than the bridge cameras or (b) that a macro lens gives me overall better results for most of what I do than close-up lenses on mFT or APS-C.

I know this sounds heretical, and to many people it seems obviously and self-evidently wrong. However, it is a complicated story (and I have chosen my words very carefully - please note especially the "for most of what I do" part of it). I have written up my journey of kit, technique and processing options and experiments over more than three years in the tediously long and unreadably detailed series of posts linked at the bottom of my sig below. I'm not suggesting that you wade through that. Here is something rather more straightforward you might like to consider.

Here are nine examples, one each from a Canon SX10 bridge camera, an FZ200 bridge camera, a G3, G5 and G80 mFT, and two each from an FZ330 bridge camera and a Canon 70D dSLR. You may find it instructive to work out which images came from the small sensor, mFT and dSLR cameras, and also which ones used close-up lenses and which used macro lenses. (There is, quite literally, more to this than meets the eye, so if you are interested we might later want to discuss some other considerations, for example subject matter, usability and post processing. These all play quite heavily into my considerations about what kit to use.)

#1

efe5d93e4a16417986b04946b8f58f38.jpg

#2

70a1fc3844d0413d966f7a4afe8baba4.jpg

#3

ea9b44f9a21e4122bf7e25e020352e8b.jpg

#4

1945b3e43a8f4e148775cd8ede5f10ed.jpg

#5

41c3c29fb70d4f6185710a5cb69888a4.jpg

#6

db1a451fa8b24d9798084ce9d3d98703.jpg

#7

a267e94decb3428d917589c2eb294931.jpg

#8

d96feef560124c4da19697a6ccb8da4f.jpg

#9

28664ac962784a83bae8a41ed114b877.jpg

--
Nick
http://www.flickr.com/photos/gardenersassistant/collections/
GardenersAssistant Photography Videos - https://www.youtube.com/channel/UCmBgEwRDfiQMYTPORSzDxvw
https://www.talkphotography.co.uk/t...-dslr-primes-a-journey-of-exploration.531050/


No idea which one is from which camera/sensor.


I like #3, #5, and #7 the most. Some (#1, #4, #9) c/would maybe be improved with focus stacking?

Before buying the P7800 I thought about the FZ200. Because I wanted the best quality allround compact for a small budget (I paid 279 euro) with sufficient zoom, I opted for the P7800 in the end. Now, after almost 2 years, I'd like to continue taking landscape/nature photos, but add macro/close-up to it, without buying multiple cameras. The P7800 has a fantastic lens, so the 1/1.7" sensor is OK-ish for my nature/landscape photos most of the time, but I wouldn't want to go any smaller for that.

I'll definitely read up on this, including the links in your signature, as I'm not in any hurry to buy something yet.
 
strawbale wrote:
No idea which one is from which camera/sensor.
Given where I'm coming from, that doesn't surprise me. :)
I like #3, #5, and #7 the most. Some (#1, #4, #9) c/would maybe be improved with focus stacking?
#4 and #9 definitely not as the subjects were in motion - not bits of them moving, like antennae moving, which you can sometimes deal with in a stack, but walking around (rushing, in the case of the ant).

#1 might have stayed still long enough for a stack, I don't remember - I do have images of it in different positions, so it obviously was moving from time to time.

The problem I find is that once I commit to a stack (at sweet spot aperture, otherwise stacking doesn't make sense), I may not be able to complete the captures in the time available, so as well as missing the stack I may miss getting a usable small aperture single shot. (All these examples are minimum aperture shots, equivalent to around f/45 on full frame, f/22 on mFT.)

I suppose the thing to do would be to take single shots first and then try a stack, changing aperture/ISO/shutter speed/flash setting as appropriate which in itself can take a little while to get right.

Another complication is that I find a different lens suitable for stacks. I find the Olympus 60mm macro on the G80 best for sweet spot aperture focus bracketing or 4K photo sets, but close-up lenses on a 45-175 zoom lens best for single shots. In practice that could mean carrying a separate camera for stacks, along with the two that I already carry, one for flash-based single shot macros and one for natural light close-ups. I find two cameras ok, but even though I carry a bag around I find three much more inconvenient to handle.
Before buying the P7800 I thought about the FZ200. Because I wanted the best quality allround compact for a small budget (I paid 279 euro) with sufficient zoom, I opted for the P7800 in the end. Now, after almost 2 years, I'd like to continue taking landscape/nature photos, but add macro/close-up to it, without buying multiple cameras. The P7800 has a fantastic lens, so the 1/1.7" sensor is OK-ish for my nature/landscape photos most of the time, but I wouldn't want to go any smaller for that.
I have found that I prefer what I can get from my G80 for botanical and landscape subjects. Before I got the G80 my preference for these was my 70D, but I've found I prefer my G80 for these subjects.
I'll definitely read up on this, including the links in your signature, as I'm not in any hurry to buy something yet.
Yes, best to read around a variety of sources and opinions and match to your own particular needs, preferences etc.
 
I shot on 2, i think 3 is maybe too far. On G80 and Em1 are both on increment 2.
Thanks. Could you point out the problems you are seeing that using 2 rather than 3 might solve?
If too close, 3 might be too far away.
So no specific problems you have noticed in this case with 3?
While with 2 on Oly and Pana, actually get this number as others adopted, so never a problem.
A method brings you fine background, without dots, B is somewhere in the middle, more sharp but doted background, while C gave you much more sharp than A and B, but noisy too. So in that case i combine all three in photo stack. I choose which part will present, what need to be in focus is on B and C, back is combo of A and some B.
What surprised me about these is that I didn't feel the need to combine versions.

Another combination I use sometimes is one of the parameterised methods, A or B, using two version with different parameter values. That is for dealing with halos.
If mixing idle setting 4-8 you can get halos, especially on A and B.
It was a while ago now (I don't do much stacking), but for halos, with for example B, I seem to recall using one with a low value for Radius (with the halos) and another with a high enough radius to not have the halos, and using the first as the base version and brushing in from the other one over the halos.
When you will have a situation when just some part should be in focus, A and B are very welcome since A+B combo is making background and C+B for the object in focus.
In what way do you combine A+B and C+B. Are you layering and masking in Photoshop or similar, or do you do some/all of it in Helicon?
You should see in full size, to see nice background (no dots) :

Link1

Link2
They look very good. As regards halos, they are rather simpler than the ones I have had most problems with which had more complicated geometry. This is an example that I talked through in this video starting at 21:55.

73e64558be824698808162cc33ac5f87.jpg

--
Nick
http://www.flickr.com/photos/gardenersassistant/collections/
GardenersAssistant Photography Videos - https://www.youtube.com/channel/UCmBgEwRDfiQMYTPORSzDxvw
https://www.talkphotography.co.uk/t...-dslr-primes-a-journey-of-exploration.531050/
I would take care using f/2.8 on 60mm and 3 seperation. I think you shouldnt do much editing of stuff when you combine all three.

I save A,B, C into Tif file. In PS i do Load files into stack. Now you combine A+B and B+C, no matter what is first. On A+B i solve background and halos, i put A bellow B and erase B part with Soft Round, Opacity some 70-80 % (so just background while subject will be solved on B+C). When A+B is done join them and open (Indicate) C layer. Now erase where subject isnt so clear, edges etc on joined (A+B) layer. So A+B layer is above and C is bellow. So on C you never erase. So its about erasing bad part and joining them.

Sometimes even C part cant solve some details, there you go manual, on PS. Helicon can do that.





--
 
No idea which one is from which camera/sensor.
Given where I'm coming from, that doesn't surprise me. :)
I like #3, #5, and #7 the most. Some (#1, #4, #9) c/would maybe be improved with focus stacking?
#4 and #9 definitely not as the subjects were in motion - not bits of them moving, like antennae moving, which you can sometimes deal with in a stack, but walking around (rushing, in the case of the ant).

#1 might have stayed still long enough for a stack, I don't remember - I do have images of it in different positions, so it obviously was moving from time to time.

The problem I find is that once I commit to a stack (at sweet spot aperture, otherwise stacking doesn't make sense), I may not be able to complete the captures in the time available, so as well as missing the stack I may miss getting a usable small aperture single shot. (All these examples are minimum aperture shots, equivalent to around f/45 on full frame, f/22 on mFT.)

I suppose the thing to do would be to take single shots first and then try a stack, changing aperture/ISO/shutter speed/flash setting as appropriate which in itself can take a little while to get right.

Another complication is that I find a different lens suitable for stacks. I find the Olympus 60mm macro on the G80 best for sweet spot aperture focus bracketing or 4K photo sets, but close-up lenses on a 45-175 zoom lens best for single shots. In practice that could mean carrying a separate camera for stacks, along with the two that I already carry, one for flash-based single shot macros and one for natural light close-ups. I find two cameras ok, but even though I carry a bag around I find three much more inconvenient to handle.
Before buying the P7800 I thought about the FZ200. Because I wanted the best quality allround compact for a small budget (I paid 279 euro) with sufficient zoom, I opted for the P7800 in the end. Now, after almost 2 years, I'd like to continue taking landscape/nature photos, but add macro/close-up to it, without buying multiple cameras. The P7800 has a fantastic lens, so the 1/1.7" sensor is OK-ish for my nature/landscape photos most of the time, but I wouldn't want to go any smaller for that.
I have found that I prefer what I can get from my G80 for botanical and landscape subjects. Before I got the G80 my preference for these was my 70D, but I've found I prefer my G80 for these subjects.
I'll definitely read up on this, including the links in your signature, as I'm not in any hurry to buy something yet.
Yes, best to read around a variety of sources and opinions and match to your own particular needs, preferences etc.
 
Unusual, very interesting and excellent set, Nick.
 
I would take care using f/2.8 on 60mm and 3 seperation.
I haven't noticed any problems, but I can see the logic of it so I will pay close attention to that - or just use 2 anyway. (Actually, I'm not sure wide open at f/2.8 is the best aperture to use anyway. Slightly smaller might actually be better I suppose.)
I think you shouldnt do much editing of stuff when you combine all three.
I don't really understand this. Could you explain a bit what you had in mind here.
I save A,B, C into Tif file. In PS i do Load files into stack. Now you combine A+B and B+C, no matter what is first. On A+B i solve background and halos, i put A bellow B and erase B part with Soft Round, Opacity some 70-80 % (so just background while subject will be solved on B+C). When A+B is done join them and open (Indicate) C layer. Now erase where subject isnt so clear, edges etc on joined (A+B) layer. So A+B layer is above and C is bellow. So on C you never erase. So its about erasing bad part and joining them.
That is very helpful, thank you. I don't know if I can do that with the old version of PS that I have. I'll give it a go.

Do you always use the same parameters for A?

Do you always use the same parameters for B?

Do you use the same parameters for A and B?
Sometimes even C part cant solve some details, there you go manual, on PS. Helicon can do that.
Yes, but you would have to decide what needed doing before going to PS. I can see the logic of using layers for all this. You could also do any cloning in PS. What you couldn't do once you had gone to PS would be to paint from an individual image onto the stack - unless you loaded the individual image into another layer and masked most of it. I can see that getting pretty complicated. Do you ever paint from individual images like Helicon (and Zerene) let you do?
 
I would take care using f/2.8 on 60mm and 3 seperation. I think you shouldnt do much editing of stuff when you combine all three.

I save A,B, C into Tif file. In PS i do Load files into stack. Now you combine A+B and B+C, no matter what is first. On A+B i solve background and halos, i put A bellow B and erase B part with Soft Round, Opacity some 70-80 % (so just background while subject will be solved on B+C). When A+B is done join them and open (Indicate) C layer. Now erase where subject isnt so clear, edges etc on joined (A+B) layer. So A+B layer is above and C is bellow. So on C you never erase. So its about erasing bad part and joining them.
I have been experimenting with some retouching in Helicon Focus using A.4.2, A.30.2, B.4.2, B.30.2 and C. I can see what you mean about 2 being better than 3 for f/2.8. I used 3 for the capture and the differences between frames are big enough that it can be difficult to find one that is just right as a source.

I first tried in Photoshop, loading the five versions into PS and layering them with the C version on the bottom. I put a Show All mask on the top four layers and then painted on the masks to reveal layers below where appropriate. It got complicated and awkward. I then tried the same thing in Helicon Focus and found it much easier. And of course I could paint from individual images as well as painting from other versions of the stacked result.

Overall it reminded me how much effort it can take to get a decent result, depending on the scene.

This is the scene I experimented with. (This is one of the five versions. Each of the five versions had its own issues.)

da667910efc042bdbdd17cdebb8cd741.jpg

Sometimes even C part cant solve some details, there you go manual, on PS. Helicon can do that.


--
Nick
GardenersAssistant Photography Videos - https://www.youtube.com/channel/UCmBgEwRDfiQMYTPORSzDxvw
 
To be able to deal with focus stacking, among other things, I'll need to upgrade my 10-yr old computer as well. What do you use/recommend as a minimum for comfortably using Helicon, for instance?
I'm not experienced enough to give a really solid answer to that question I'm afraid. Here is what the Helicon Help says in terms of hardware:

The recommended system configuration is:
  • 4 core processor or higher
  • 4 Gb RAM or higher
  • Resolution 1920 x 1080 or more
Minimum system requirements are:
  • 2 GHz processor
  • 1 Gb RAM
  • Resolution 1280 x 1024
I am running it on a Windows 7 PC with a four core Intel i5, 16GB memory and a 4 GB NVIDIA GeForce GTX 970 graphics card. I am content with the performance (I am running a 2560 x 1440 screen). Some operations are inevitably going to take a long time - like processing large stacks, or running DXO PRIME noise processing, but apart from that sort of operation I find the system sufficiently responsive that I'm rarely aware of delays that I feel are getting in my way.

The graphics card is fairly powerful but by no means top of the line these days (I got it to help with the games that I play. It was the fastest passively cooled card that I could buy at the time). I haven't been able to find out if the graphics card makes any difference for Helicon focus. Their hardware recommendations don't mention it and there is no option for turning it on/off, so perhaps Helicon Focus doesn't use the graphics card.

The graphics processor (whether part of the CPU or a separate card) may make a difference depending on what other software you will be using. Lightroom for example does (optionally) make use of a graphics card.

My experience is that one thing that can make a big difference to performance in various applications is the amount of memory, which is why I have 16GB.

If you are going to upgrade your system and you are into photography one thing you might want to consider is getting a calibrated screen. This might be factory calibrated, like the Dell UP2716D (may not be the current model) that I am using, or using an external calibrator like I did with my previous screen, an Asus PB278Q, using an X-rite Color Munki Display calibrator. I found I could see more detail and more subtle colour gradations when I started using a calibrated screen.

You might want to ask the question in the PC Talk or Mac Talk forum as appropriate.
 
To be able to deal with focus stacking, among other things, I'll need to upgrade my 10-yr old computer as well. What do you use/recommend as a minimum for comfortably using Helicon, for instance?
I'm not experienced enough to give a really solid answer to that question I'm afraid. Here is what the Helicon Help says in terms of hardware:

The recommended system configuration is:
  • 4 core processor or higher
  • 4 Gb RAM or higher
  • Resolution 1920 x 1080 or more
Minimum system requirements are:
  • 2 GHz processor
  • 1 Gb RAM
  • Resolution 1280 x 1024
I am running it on a Windows 7 PC with a four core Intel i5, 16GB memory and a 4 GB NVIDIA GeForce GTX 970 graphics card. I am content with the performance (I am running a 2560 x 1440 screen). Some operations are inevitably going to take a long time - like processing large stacks, or running DXO PRIME noise processing, but apart from that sort of operation I find the system sufficiently responsive that I'm rarely aware of delays that I feel are getting in my way.

The graphics card is fairly powerful but by no means top of the line these days (I got it to help with the games that I play. It was the fastest passively cooled card that I could buy at the time). I haven't been able to find out if the graphics card makes any difference for Helicon focus. Their hardware recommendations don't mention it and there is no option for turning it on/off, so perhaps Helicon Focus doesn't use the graphics card.

The graphics processor (whether part of the CPU or a separate card) may make a difference depending on what other software you will be using. Lightroom for example does (optionally) make use of a graphics card.

My experience is that one thing that can make a big difference to performance in various applications is the amount of memory, which is why I have 16GB.

If you are going to upgrade your system and you are into photography one thing you might want to consider is getting a calibrated screen. This might be factory calibrated, like the Dell UP2716D (may not be the current model) that I am using, or using an external calibrator like I did with my previous screen, an Asus PB278Q, using an X-rite Color Munki Display calibrator. I found I could see more detail and more subtle colour gradations when I started using a calibrated screen.

You might want to ask the question in the PC Talk or Mac Talk forum as appropriate.
 
I looks like you shot most (all?) of your stacks at f/2.8 - ever tried it at f/4 or f/5.6 or is theat more difficult to dealt with for/in the stacking sofware?

Reason I'm asking is that the 60mm macro is not at its best at f/2.8:

 
I looks like you shot most (all?) of your stacks at f/2.8 - ever tried it at f/4 or f/5.6 or is theat more difficult to dealt with for/in the stacking sofware?

Reason I'm asking is that the 60mm macro is not at its best at f/2.8:

http://www.photozone.de/m43/781-oly6028?start=1
Thanks. I didn't realise that. I hardly ever use the 60mm macro and hadn't researched its characteristics (at least, not recently enough to remember it - my memory is very poor!). I had a vague thought in the back of my mind that mFT lenses tended to be sharp nearly wide open.

I'll use f/5.6 for similar things in the future (not that I do much of this). It may well be advantageous for the stacking as I could use less shots, although from Petar Veliki's comments it may be better to use just as many shots and give the software more data to work on.
 
I would take care using f/2.8 on 60mm and 3 seperation.
I haven't noticed any problems, but I can see the logic of it so I will pay close attention to that - or just use 2 anyway. (Actually, I'm not sure wide open at f/2.8 is the best aperture to use anyway. Slightly smaller might actually be better I suppose.)
I think you shouldnt do much editing of stuff when you combine all three.
I don't really understand this. Could you explain a bit what you had in mind here.
I save A,B, C into Tif file. In PS i do Load files into stack. Now you combine A+B and B+C, no matter what is first. On A+B i solve background and halos, i put A bellow B and erase B part with Soft Round, Opacity some 70-80 % (so just background while subject will be solved on B+C). When A+B is done join them and open (Indicate) C layer. Now erase where subject isnt so clear, edges etc on joined (A+B) layer. So A+B layer is above and C is bellow. So on C you never erase. So its about erasing bad part and joining them.
That is very helpful, thank you. I don't know if I can do that with the old version of PS that I have. I'll give it a go.

Do you always use the same parameters for A?

Do you always use the same parameters for B?

Do you use the same parameters for A and B?
Sometimes even C part cant solve some details, there you go manual, on PS. Helicon can do that.
Yes, but you would have to decide what needed doing before going to PS. I can see the logic of using layers for all this. You could also do any cloning in PS. What you couldn't do once you had gone to PS would be to paint from an individual image onto the stack - unless you loaded the individual image into another layer and masked most of it. I can see that getting pretty complicated. Do you ever paint from individual images like Helicon (and Zerene) let you do?
1. I actually put many time f/8, on 60 mm. Its still macro lens, and made so to be best at f/6.3-f/7.1 So if not problem with background, i leave normal, but to dissolve close back from object than maybe f/2.8 or similar.

2. You shouldnt do much editing because Helicon with A,B,C, covering is solving most. In Adobe PS i have much more problems, and than copying, layers was a need. I also meet this is problem in Helicon, i find finished image very different than original, tone, colors, noise. I always put same parameters, i didnt find much help up to now, so i rather do same and undergo my procedure. Would be problem if changing 4-8 on A, and put 10-2 on B, and then covering them - difference might be seen.

Because i cant use cloning from originals, i use the same image and try to solve with copy-paste, some painting etc. Up to now, i had just one case where all was perfect. Close macro can be more problematic - edges can overcover. I can take a day or two to be top on 100%. For pixle peepers. For some web presentation etc, i wouldn't spoil too much time, they even would see mistakes.

I dont have full option Helicon. Otherwise some tethering and live Helicon Remote would be great.
 
I looks like you shot most (all?) of your stacks at f/2.8 - ever tried it at f/4 or f/5.6 or is theat more difficult to dealt with for/in the stacking sofware?

Reason I'm asking is that the 60mm macro is not at its best at f/2.8:

http://www.photozone.de/m43/781-oly6028?start=1
Thanks. I didn't realise that. I hardly ever use the 60mm macro and hadn't researched its characteristics (at least, not recently enough to remember it - my memory is very poor!). I had a vague thought in the back of my mind that mFT lenses tended to be sharp nearly wide open.

I'll use f/5.6 for similar things in the future (not that I do much of this). It may well be advantageous for the stacking as I could use less shots, although from Petar Veliki's comments it may be better to use just as many shots and give the software more data to work on.
 

Keyboard shortcuts

Back
Top