Fuji Auto Focus Bracketing, suggested workflow

SrMi

Veteran Member
Messages
7,873
Solutions
5
Reaction score
6,267
Location
SF Bay Area, CA, US
First introduced with X-T4, Fuji has added Auto mode to GFX 100 focus bracketing. The UI is a bit confusing, and there are several ways how to proceed. AFAIK, the following is the simplest. It applies both to X-T4 and GFX 100.

After selecting Focus Bracketing Auto mode, EVF/LCD shows the view through the lens with overlaid bracketing info. The bracketing info disappears after a short while (to help with framing) but can be shown again by pressing arrow buttons (X-T4) or Q/Fn4 buttons (GFX100). Other buttons may also trigger the bracketing info overlay.

Possible steps to follow:

1) focus on the closest point (using MF or AF)

2) press OK button to save it as focus point A

3) focus on the furthest point (shown as point B in the overlaid display)

4) press the shutter to start the sequence

Note 1: As Greg pointed it out, there is no need to save the B point by pressing the DISP/BACK button.

Note 2: Since the live view is active during focus bracketing, in many situations (e.g., landscape), you can handheld the camera during focus bracketing. Helicon Focus is (always?) able to align slight movements.
 
Great - thanks for summarizing.

Regarding the sequences of images that are captured - are they somehow 'marked' so that when you load them into computer it can figure out which belonged to same sequence (I imaging this could perhaps get captured in exif info of the image files ...).

My guess is this does not exist now but figured does not hurt to ask (maybe give Fuji some ideas for some future firmware in case they are reading this forum).
 
Great - thanks for summarizing.

Regarding the sequences of images that are captured - are they somehow 'marked' so that when you load them into computer it can figure out which belonged to same sequence (I imaging this could perhaps get captured in exif info of the image files ...).

My guess is this does not exist now but figured does not hurt to ask (maybe give Fuji some ideas for some future firmware in case they are reading this forum).
Helicon Focus will do this for you in batch mode.



14f4283094fb4fcea2b311f50f9921a5.jpg.png



--
https://blog.kasson.com
 
Last edited:
Great - thanks for summarizing.

Regarding the sequences of images that are captured - are they somehow 'marked' so that when you load them into computer it can figure out which belonged to same sequence (I imaging this could perhaps get captured in exif info of the image files ...).

My guess is this does not exist now but figured does not hurt to ask (maybe give Fuji some ideas for some future firmware in case they are reading this forum).
You are welcome :). Greg suggested that I start a new thread summarizing it.

Unfortunately, the images are not marked that they belong to the same sequence. LR's "Auto-stack by Capture Time" may work, but I have never used it so far. The other option is to take a dummy start image (e.g., hand), and a dummy end image to frame the sequence.
 
To introduce another thought about this firmware update – any idea why the setting of points A and B isn’t also applied to the manual bracketing mode?
 
To introduce another thought about this firmware update – any idea why the setting of points A and B isn’t also applied to the manual bracketing mode?
Wouldn’t the solution then be overconstrained? You’d have to drop either number of steps or step size.
 
To introduce another thought about this firmware update – any idea why the setting of points A and B isn’t also applied to the manual bracketing mode?
Wouldn’t the solution then be overconstrained? You’d have to drop either number of steps or step size.
It would be nice to have a semi-auto mode where the number of steps is dropped, and A and B points are specified.
 
To introduce another thought about this firmware update – any idea why the setting of points A and B isn’t also applied to the manual bracketing mode?
Wouldn’t the solution then be overconstrained? You’d have to drop either number of steps or step size.
The manual mode number of frames is currently constrained by the initial focus point and infinity. Regardless of how many frames are chosen, it stops at infinity. If it's constrained by a point B instead, then I don't see there'd be any difference.
 
Great - thanks for summarizing.

Regarding the sequences of images that are captured - are they somehow 'marked' so that when you load them into computer it can figure out which belonged to same sequence (I imaging this could perhaps get captured in exif info of the image files ...).

My guess is this does not exist now but figured does not hurt to ask (maybe give Fuji some ideas for some future firmware in case they are reading this forum).
Helicon Focus will do this for you in batch mode.

14f4283094fb4fcea2b311f50f9921a5.jpg.png


Thanks. Looks like Helicon Focus could become a must now that this new workflow is available (in the sense Fuji made it more intuitive so perhaps more people are likely to try it).
 
Great - thanks for summarizing.

Regarding the sequences of images that are captured - are they somehow 'marked' so that when you load them into computer it can figure out which belonged to same sequence (I imaging this could perhaps get captured in exif info of the image files ...).

My guess is this does not exist now but figured does not hurt to ask (maybe give Fuji some ideas for some future firmware in case they are reading this forum).
Helicon Focus will do this for you in batch mode.

14f4283094fb4fcea2b311f50f9921a5.jpg.png
Thanks. Looks like Helicon Focus could become a must now that this new workflow is available (in the sense Fuji made it more intuitive so perhaps more people are likely to try it).
Zerene Stacker is the other well-known focus stacking tool and should work well. Currently, I use Helicon.
 
This is good stuff. It took me a lot of test shots and experimentation to finally figure out that you don't need to save Focus Point B by hitting the display back button. That just creates confusion and flips you to another earlier screen.

Glad you started a new thread on this. The other threads were getting loaded and confusing.

Here are some notes that I jotted down in my notes taken from all the other threads this past week, mostly stated by Jim, SrMi and Theia.

……………………………………………

Jim: Greg, do yourself a favor. Use Helicon Focus vs PS for focus stacking. It is much easier and does a great job and works well as a LR plugin. (So I bought it)

Jim (on step size decisions not on auto): With Fuji Focus Bracketing, focal length and distance don’t affect the step size you should use. The subject matter and the application do. Focal length and distance affect the number of shots you’ll need.

SrMi (responding to Greg's question about how LR can export either tif or DNG files to Helicon focus, and Helicon Focus can then render them with a tif result, or DNG result. But the DNG it renders after the stack is not a true raw file as we think of raw files, like a raf file coming out of a Fuji camera and into LR.
SrMi said: Let's talk about three formats - DNG (raw) output of the Leica Q2, linear DNG output of Helicon, and TIFF. The DNG (raw) output of Q2 is not demosaiced. X-Transformer, LR, and C1 all use different demosaic-engines. Once a raw file is demosaiced, you cannot run another demosaic tool on them, so you are stuck with whatever LR/C1/X-Transformer has done. The good thing about (linear) DNG output of Helicon Focus is that it has not been mapped to a color space, has not been white-balanced, etc. You can transform any raw file into a DNG without demosaicing. But, to process the files, Helicon Focus must demosaic the files first. On another note, make sure that you always have the latest Adobe DNG Converter installed. Helicon Focus does not check if it is out of date and Adobe does not include it in the LR / PS updates.

Jim: Helicon demosaics before stacking and writes out a demosaiced DNG.

Jim (explaining to Greg about DNG files): a DNG is not necessarily a raw file. Some raw files are DNG's. Some DNGs are not mosaiced. The key element here is that the DNG remains scene-referred. (I don't know what scene referred means)

Greg said to Jim and Jim agreed: Processed demosaiced output from processes like Helicon have to be a TIF or JPEG or demosaiced DNG (something not-raw).

Jim, explaining to Greg what a Step Size really is:

The red circle on the diagram indicates the blur circle in the sensor plane for an object in the near plane when the camera is focused on the middle plane. Let’s call that the single-step-CoC. When you use focus bracketing, what controls its diameter?
The surprising answer is: just the step size. That’s right. Not the focal length of the lens. Not the distance from the camera to the subject. Not even the f-stop. The camera takes care of all that. You don’t need to understand how the camera manages that feat to successfully use focus bracketing, but for those who are interested, I’ll explain now. The diameter of the blur circle is the shift in the image space focal plane from the sensor divided by the f-stop. The subject distance doesn’t enter into the calculations, since we’re working in image space. The focal length of the lens doesn’t matter, either, since it is handled by considering the f-stop. So all the camera has to do is look at the f-stop and the step size, and move the image side-focal plane so that the blur circle doesn’t change when you change the f-stop.
The beauty of this is that you can think of the step size strictly in terms of the blur circle that you are willing to have."

SrMi to Greg: I think once you understand what CoC means, you would also understand how step-size works. Let's say you manually shoot a two-shot focus stack, with a near focus point and a far focus point. If the two focus points are far enough apart, you will notice that the focus stacked image (after Helicon) contains a blurry area between the two points. The step parameter specifies how blurry that area may be.
The blurriness between the two focus points depends on the DOF at near and far focus and the distance between the focus points. The camera changes the focus only so much that the specified blurriness (as defined by step parameter) remains constant. If the step size parameter is unchanged and you close the aperture, the focus will be moved in larger 'steps' because of increased DOF.

Greg says to SrMi: Yes, that is another way of saying exactly what I said and what I have thought from my very first post. The step is changing the plane of focus either a tiny bit (one) or a larger slice (10) and at ten, you run the risk of having some OOF area between shots because the "slice" between shots has widened, or the plane of focus has moved on forward beyond the point that is in focus at that aperture.

Jim responds to Greg's above statement. Jim (to Greg) So far so good. But what you're missing in your other posts is that the aperture, focal length, and subject distance don't affect the blurriness of the in-between shots subject matter.
 
To introduce another thought about this firmware update – any idea why the setting of points A and B isn’t also applied to the manual bracketing mode?
Wouldn’t the solution then be overconstrained? You’d have to drop either number of steps or step size.
The manual mode number of frames is currently constrained by the initial focus point and infinity. Regardless of how many frames are chosen, it stops at infinity. If it's constrained by a point B instead, then I don't see there'd be any difference.
In manual mode, it stops at infinity no matter when you want the stack to stop. Are you suggesting that it just stop at the "B" point no matter how many frames you tell it to shoot?
 
Slightly off direct topic here. The other thread on focus bracket reached its limit - but wanted to comment on Jim’s blog post explaining focus bracketing for those of us (ME) who have trouble understanding. THANK YOU, Jim. That was really helpful.

I’m now off to practice.

Rand
 
To introduce another thought about this firmware update – any idea why the setting of points A and B isn’t also applied to the manual bracketing mode?
Wouldn’t the solution then be overconstrained? You’d have to drop either number of steps or step size.
The manual mode number of frames is currently constrained by the initial focus point and infinity. Regardless of how many frames are chosen, it stops at infinity. If it's constrained by a point B instead, then I don't see there'd be any difference.
In manual mode, it stops at infinity no matter when you want the stack to stop. Are you suggesting that it just stop at the "B" point no matter how many frames you tell it to shoot?
Wait Jim - are you sure? I don't think so. It stops when it stops if you don't give it a high enough number, and sometimes that is way too soon. The more shots you tell it to take, the farther it will go, and then stop at infinity. I had cases where the focusing stopped half way through that board game or even sooner if I didn't give it enough shots.

In my examples last week the focusing would stop too soon if you didn't tell it to do enough shots, even at Step 10.

So what we decided was to in the field shoot so many that you know it will go far enough and then in post you could delete the ones that focused past where you wanted it to.

But that was before this new auto feature came out a couple of days ago where we can pick our focus end point.
 
To introduce another thought about this firmware update – any idea why the setting of points A and B isn’t also applied to the manual bracketing mode?
Wouldn’t the solution then be overconstrained? You’d have to drop either number of steps or step size.
The manual mode number of frames is currently constrained by the initial focus point and infinity. Regardless of how many frames are chosen, it stops at infinity. If it's constrained by a point B instead, then I don't see there'd be any difference.
In manual mode, it stops at infinity no matter when you want the stack to stop. Are you suggesting that it just stop at the "B" point no matter how many frames you tell it to shoot?
 
To introduce another thought about this firmware update – any idea why the setting of points A and B isn’t also applied to the manual bracketing mode?
Wouldn’t the solution then be overconstrained? You’d have to drop either number of steps or step size.
The manual mode number of frames is currently constrained by the initial focus point and infinity. Regardless of how many frames are chosen, it stops at infinity. If it's constrained by a point B instead, then I don't see there'd be any difference.
In manual mode, it stops at infinity no matter when you want the stack to stop. Are you suggesting that it just stop at the "B" point no matter how many frames you tell it to shoot?
Yes. In manual mode, the Step Size should always remain at the value I set. But I don't care about the number of frames, as long as I get a 'sharp' photo from A to B.
 
To introduce another thought about this firmware update – any idea why the setting of points A and B isn’t also applied to the manual bracketing mode?
Wouldn’t the solution then be overconstrained? You’d have to drop either number of steps or step size.
The manual mode number of frames is currently constrained by the initial focus point and infinity. Regardless of how many frames are chosen, it stops at infinity. If it's constrained by a point B instead, then I don't see there'd be any difference.
In manual mode, it stops at infinity no matter when you want the stack to stop. Are you suggesting that it just stop at the "B" point no matter how many frames you tell it to shoot?
Wait Jim - are you sure? I don't think so. It stops when it stops if you don't give it a high enough number,
Yes, I meant if you gave told it to take enough shots. Sorry for the confusion.
and sometimes that is way too soon. The more shots you tell it to take, the farther it will go, and then stop at infinity. I had cases where the focusing stopped half way through that board game or even sooner if I didn't give it enough shots.

In my examples last week the focusing would stop too soon if you didn't tell it to do enough shots, even at Step 10.

So what we decided was to in the field shoot so many that you know it will go far enough and then in post you could delete the ones that focused past where you wanted it to.

But that was before this new auto feature came out a couple of days ago where we can pick our focus end point.
 
To introduce another thought about this firmware update – any idea why the setting of points A and B isn’t also applied to the manual bracketing mode?
Wouldn’t the solution then be overconstrained? You’d have to drop either number of steps or step size.
The manual mode number of frames is currently constrained by the initial focus point and infinity. Regardless of how many frames are chosen, it stops at infinity. If it's constrained by a point B instead, then I don't see there'd be any difference.
In manual mode, it stops at infinity no matter when you want the stack to stop. Are you suggesting that it just stop at the "B" point no matter how many frames you tell it to shoot?
I'm not sure what you're telling me here.
 
To introduce another thought about this firmware update – any idea why the setting of points A and B isn’t also applied to the manual bracketing mode?
Wouldn’t the solution then be overconstrained? You’d have to drop either number of steps or step size.
The manual mode number of frames is currently constrained by the initial focus point and infinity. Regardless of how many frames are chosen, it stops at infinity. If it's constrained by a point B instead, then I don't see there'd be any difference.
In manual mode, it stops at infinity no matter when you want the stack to stop. Are you suggesting that it just stop at the "B" point no matter how many frames you tell it to shoot?
Yes. In manual mode, the Step Size should always remain at the value I set. But I don't care about the number of frames, as long as I get a 'sharp' photo from A to B.
Got it. Yet another mode.
 

Keyboard shortcuts

Back
Top