Fujifilm 0x102e field (C-AF settings)

[Richard_Butler]

Hi

A bit of trial-and-error trying to check my AF settings led me to the following finding (sorry if the explanation is clumsy: I don't have a coding background).

The field called "Fuji Film 0x102e" by EXIFTool stores the 'AF-C Custom Settings' values

On the camera there are three parameters that make up custom settings:
Tracking Sensitivity (values 0-4)
Speed Tracking Sensitivity (values 0-2)
Zone Area Switching (Center, Auto, Front)

These are stored as the sum of:
Zone Area Switching (Center=512, Auto=256, Front=0)
Speed Tracking sensitivity (0=0, 1=16, 2=32)
Tracking sensitivity (0=0, 1=1, 2=2, 3=3, 4=4)

So a value of 548 = 512 (ZAS=Center) + 32 (STS=2) + 4 (TS=4)

So the output would ideally be: 4,2,Center

Alternatively, there are in-camera presets based on these values, so you could also report:
258 = Set1 (2,0,Auto)
515 = Set2 (3,0,Center)
290 = Set3 (2,2,Auto)
016 = Set4 (0,1,Front)
291 = Set5 (3,2,Auto)
All other values could simple state 'Set6', since this is the user-adjustable custom preset, if you didn't want to specify the exact parameters.

Does that make sense?

Richard

[Phil Harvey]

Hi Richard,

This looks great, thanks!  I'll implement this when I get a chance tomorrow and post back here if I have any questions.

- Phil

[greybeard]

There are a lot of additions/changes to the Fuji Makernotes from recent cameras - especially the X-T3.

Examples are: Drive Mode/Frame rate, B&W Adjustment, AF Custom Settings, Sports Finder Mode, Pre Shot, Flicker Reduction, D Range Priority, Focus Mode (size), Focus Priority

(and an addition to the Shutter Type).

Is the best way of getting ExifTool updated to add them here as they are found?

Some of them (such as D Range Priority and File Simulation) are really a combination of multiple tags - do you normally handle them as composites (or just leave the individual tags)

[Phil Harvey]

If they are different settings I like to split them out into separate tags, which is what I will try to do for 0x102e.

Feel free to post any new Fuji discoveries in this forum.  It is easiest for me if you create a new topic and add all of your discoveries under the same topic.

- Phil

[Phil Harvey]

Richard,

I have implemented 0x102e.  How does this look?:

Code Select Expand

> exiftool ../pics/FujiFilmGFX50R.jpg "-af-c*"
AF-C Tracking Sensitivity       : 2
AF-C Speed Tracking Sensitivity : 0
AF-C Zone Area Switching        : Auto

- Phil

[greybeard]

0x1050 ShutterType

There is an addition option with value 2 - this is Electronic Shutter

It is assigned when Long Exposure Noise Reduction would have been activated (but wasn't because LENR does not apply to the Electronic Shutter)

[Phil Harvey]

Thanks Greybeard.  A value of 1 is "Electronic", so how about if I call 2 "Electronic (long-exposure noise reduction unavailable)" or "Electronic (long-exposure NR selected but unavailable)"?

- Phil

[greybeard]

A bit wordier than I would have used - but accurate

[greybeard]

0X1049 B&W Adjustment

           9 => '+9 (warmest)',
            8 => '+8 (warm)',
            7 => '+7 (warm)',
            6 => '+6 (warm)',
            5 => '+5 (warm)',
            4 => '+4 (warm)',
            3 => '+3 (warm)',
            2 => '+2 (warm)',
            1 => '+1 (warm)',
            0 => '(unchanged)',
            255 => '-1 (cool)',
            254 => '-2 (cool)',
            253 => '-3 (cool)',
            252 => '-4 (cool)',
            251 => '-5 (cool)',
            250 => '-6 (cool)',
            249 => '-7 (cool)',
            248 => '-8 (cool)',
            247 => '-9 (coolest)',

[Phil Harvey]

A bit wordier than I would have used - but accurate

I don't like the wordiness myself.  Can you suggest a shorter alternative?

- Phil

[Phil Harvey]

0X1049 B&W Adjustment

I don't have any samples with this metadata.  What model is this?  Can you email me a sample (philharvey66 at gmail.com)?  Thanks.

- Phil

[greybeard]

Yes - sorry - all the examples I have will come from the recently released X-T3.

Some are additions that arrived with the X-T3 but others also apply to other recent Fuji cameras such as the X-T2.

For example the AFC Custom Modes were used in other cameras but B&W Adjustment is X-T3 specific (and probably future cameras).

Would you prefer that I email other examples or would it be better to continue documenting them here?

[Phil Harvey]

For now, continue documenting them here.  I'll let you know if I need more samples.  I have a X-T3 sample, but it doesn't contain tag 0x1049, so if you could email me one of those it would be good.  Thanks.

- Phil

Edit: I got the X-T3 sample with tag 0x1049 - Thanks!

[greybeard]

On its way - you will only see the 0x1049 tag for B&W Film Simulations

[greybeard]

AutoBracketing 0x1100

For the X-T3 these are the correct values:

            0 => 'Off',
            1 => 'On',
            2 => 'Pre-Shot',

Pre-Shot is a new function for the X-T3 and only applies with shutter type of Electronic Shutter and Continuous High drive mode

[Phil Harvey]

Pre-Shot is a new function for the X-T3 and only applies with shutter type of Electronic Shutter and Continuous High drive mode

This is unfortunate.  I can decode this specially for the X-T3, but it won't be forward-compatible for future models.

- Phil

[greybeard]

Which camera(s) does 'No flash & flash' apply to? It doesn't mean anything to me.

[greybeard]

0x1443, 0x1444 and 0x1445 D Range Priority

They could be named:
0x1443 D Range Priority
0x1444 D Range Priority Fixed
0x1445 D Range Priority Auto

This is a new function with the X-T3

0x1443
  0=> Auto
  1=> Fixed

0x1444 only applies where 0x1443 is Fixed
  1 => Weak
  2 => Strong

0x1445 only applies where 0x1443 is Auto
  1 => Weak
  2 => Strong

(I can't be absolutely certain of 0x1445 because I have no way of knowing for sure which auto setting was chosen - I can send examples if necessary)
 

[greybeard]

Drive Mode 0x1103

This applies to other cameras in addition to the X-T3

Includes both the Drive Mode (Single, Continuous Low and Continuous High) and the Frame Rate

Here is how I decoded it in order to test:

    0x1103 => {
        Name => 'DriveMode',
        Writable => 'int16u',
        ValueConv => q{
           my $hex = sprintf("0x%X", $val);
           my $rt = ($val >> 24) & 0x0ff;
           my $dm = $val & 0x0ff;
           my $out;
           if ($dm == 0) { $out = "Single" };
           if ($dm == 1) { $out = "CL ${rt}-fps" };
           if ($dm == 2) { $out = "CH ${rt}-fps" };
           $out="$hex : $out";
        },
    },

Given your standards you might split this into two different values

[Phil Harvey]

Which camera(s) does 'No flash & flash' apply to? It doesn't mean anything to me.

The F30 apparently (from 2006).

[Phil Harvey]

0x1443, 0x1444 and 0x1445 D Range Priority

I'll need a sample for these too.  Thanks.

- Phil

[greybeard]

The F30 apparently (from 2006).

Hmmm

[greybeard]

0x102d Focus Mode

This expands on your existing tags 0x1021 FocusMode and 0x1022 AFMode and differentiates between AF-S and AF-C and adds the size of the focus area.

Most of this applies to other cameras but the size of the focus area has been added for the X-T3.

The following three concepts are included:
- Focus Mode (AF-M, AF-S and AF-C)
- AF Mode (Single, Zone or Wide/Tracking)
- AF Area Size (applies to Single or Zone)

Here is how I decoded it for testing:

    0x102d => {
        Name => 'FocusModeX',
        Writable => 'int32u',
        ValueConv => q{
           my $hex = sprintf("0x%X", $val);
           my $fm = $val & 0xf;
           my $tp = ($val >> 8) & 0xf;
           my $ss = ($val >> 12) & 0xf;
           my $zs = ($val >> 16) & 0xf;
           my $out;
           if ($ss == 0) { $ss=""; }
           if ($zs == 0) {
              $zs="";
           } else {
              $zs="${zs}x${zs}";
           }
           my $fmx;
           if ($fm == 0) { $fmx = "AF-M"; }
           if ($fm == 1) { $fmx = "AF-S"; }
           if ($fm == 2) { $fmx = "AF-C"; }
           if ($tp == 0) { $out = "Single Point $ss"; }
           if ($tp == 1) { $out = "Zone $zs"; }
           if ($tp == 2) { $out = "Wide/Tracking"; }
           $out="$hex : $fmx - $out";
        },
    },

[greybeard]

0x102b Focus Priority

This applies to other cameras in addition to the X-T3 and has become increasingly more detailed

It allows you to set Release or Focus priority for AF-S and AF-C modes

Here is how I decoded it for testing:

    0x102b => {
        Name => 'FocusPriority',
        Writable => 'int16u',
        ValueConv => q{
           my $hex = sprintf("0x%X", $val);
           my $f1 = $val & 0xf;
           my $f2 = ($val >> 4) & 0xf;
           my $out="";
           if ($f1 == 1) { $out="AFS Release"; }
           if ($f1 == 2) { $out="AFS Focus"; }
           if ($f2 == 1) { $out=$out." - AFC Release"; }
           if ($f2 == 2) { $out=$out." - AFC Focus"; }
           $out="$hex : $out";;
        },
    },

[greybeard]

Noise reduction

For all current Fuji cameras your existing Noise reduction tags are confusing

What you currently have as  0x100e HighISONoiseReduction is actually what Fuji refers to as Noise reduction

I have never seen anything other than n/a for 0x100b NoiseReduction

Fuji has added Long Exposure Noise reduction which I am working on decoding (possibly tags 0x1026 and/or 0x102c but results have so far been inconsistent)

[Phil Harvey]

Drive Mode 0x1103

How is this?:

Code Select Expand

> exiftool ../testpics/FujiFilm/X-T3/XT3_BWAdj5.JPG "-drive*"
Drive Mode                      : Single
Drive Speed                     : 0 fps

0x102d Focus Mode

How is this?:

Code Select Expand

> exiftool ../testpics/FujiFilm/X-T3/XT3_BWAdj5.JPG -focusmode2 -afmode2 "-afarea*"
Focus Mode 2                    : AF-C
AF Mode 2                       : Zone
AF Area Size Single Point       : 0
AF Area Size Zone               : 3

0x102b Focus Priority

How is this?:

Code Select Expand

exiftool ../testpics/FujiFilm/X-T3/XT3_BWAdj5.JPG "-*priority*"
AFS Priority                    : Focus
AFC Priority                    : Focus

What you currently have as  0x100e HighISONoiseReduction is actually what Fuji refers to as Noise reduction

I have never seen anything other than n/a for 0x100b NoiseReduction

Unfortunate, but it will either be confusing for older models, or for newer models, and to maintain backward compatibility I don't like changing previous behaviour.  However, I'm open to suggestions.

- Phil

Edit: I still need a sample for the D Range Priority settings

[greybeard]

Looks good except:

For AF Area Size - if you split the size between single and zone then it should depend on your "AF Mode 2"  which is visible.

AF Area Size Single Point       : 0 is meaningless if the AF Mode is zone (and vice versa).

and for zone it would be more readable as:

AF Area Size Zone               : 3x3

=======================================

Similarly drive speed is really only applicable for CL and CH

[Phil Harvey]

For AF Area Size - if you split the size between single and zone then it should depend on your "AF Mode 2"  which is visible.

Ah.  So you are saying that the AFAreaSizeSinglePoint is always 0 unless AFMode2 is "Single Point"?

I was hoping that both sizes would be valid.  Sort of makes me wonder why they used two different fields.

Similarly drive speed is really only applicable for CL and CH

Right.

- Phil

[greybeard]

Unfortunate, but it will either be confusing for older models, or for newer models, and to maintain backward compatibility I don't like changing previous behaviour.  However, I'm open to suggestions.

I'm not sure what the answer is but all the recent Fuji cameras (I've checked XE series, XH series XT series and GFX series) use the new definition of Noise Reduction

[Phil Harvey]

all the recent Fuji cameras (I've checked XE series, XH series XT series and GFX series) use the new definition of Noise Reduction

Thanks.  I'll have to think about this.

So far I have this for the new tags you have given me and the samples you sent:

Code Select Expand

> exiftool ../testpics/FujiFilm/X-T3 -bwadjustment "-drive*" -focusmode2 -afmode2 "-afarea*" "-*priority*"
======== ../testpics/FujiFilm/X-T3/DRng3.JPG
Drive Mode                      : Single
Focus Mode 2                    : AF-C
AF Mode 2                       : Zone
AF Area Size                    : 3 x 3
AFS Priority                    : Focus
AFC Priority                    : Focus
D Range Priority                : Fixed
D Range Priority Auto           : Weak
======== ../testpics/FujiFilm/X-T3/DRng_auto3.JPG
Drive Mode                      : Single
Focus Mode 2                    : AF-C
AF Mode 2                       : Zone
AF Area Size                    : 3 x 3
AFS Priority                    : Focus
AFC Priority                    : Focus
D Range Priority                : Auto
D Range Priority Fixed          : Strong
======== ../testpics/FujiFilm/X-T3/XT3_BWAdj5.JPG
BW Adjustment                   : -3
Drive Mode                      : Single
Focus Mode 2                    : AF-C
AF Mode 2                       : Zone
AF Area Size                    : 3 x 3
AFS Priority                    : Focus
AFC Priority                    : Focus
    1 directories scanned
    3 image files read

[greybeard]

0x1446 Flicker Reduction

Only applies to X-T3

Note that this does not apply to Electronic Shutter

There must be information other than Flicker Reduction embedded in this tag

Code used to test:

    0x1446 => {
        Name => 'FlickerReduction',
        Writable => 'int16u',
        ValueConv => q{
           my $hex = sprintf("0x%X", $val);
           my $v1 = ($val >> 12) & 0x0ff;
           my $out="Off";
           if ($v1 == 3) { $out = "On"; }
           $out="$hex : $out";
        },

Samples to follow

[Phil Harvey]

0x1446 Flicker Reduction

Great, thanks!

Here is what I did for this one:

Code Select Expand

> exiftool ~/Desktop/XT* -flickerreduction
======== /Users/phil/Desktop/XT3_Flicker3.JPG
Flicker Reduction               : Off (0x0010)
======== /Users/phil/Desktop/XT3_Flicker4.JPG
Flicker Reduction               : On (0x3110)
    2 image files read

[Phil Harvey]

Going back to the AFArea stuff... I have some samples with Single Point AF, but the area size is zero.  I was thinking of re-doing the decoding to show "n/a" for a zero point size, but is zero actually significant for Single Point mode.  This is what I have after changing it (I also changed "AFMode2" to "AFAreaMode"):

Code Select Expand

======== ../testpics/FujiFilm/X-T3/DRng3.JPG
AF Area Mode                    : Zone
AF Area Point Size              : n/a
AF Area Zone Size               : 3 x 3
======== ../pics/FujiFilmX-T3.jpg
AF Area Mode                    : Single Point
AF Area Point Size              : n/a
AF Area Zone Size               : n/a

- Phil

[greybeard]

Did the example XT3 file with Single Point but no size come from me? I haven't seen any X-T3 file for Single Point or Zone without size.

I wouldn't show the tag with "n/a" - I probably wouldn't show it at all in the same way that other tags that don't exist in the EXIF aren't shown by Exiftool.

Other earlier cameras (such as the X-T2) may show Single Point or Zone from the tag but won't have size in either case.

[greybeard]

0x1401 FilmMode

Additional Film Simulation 0x700 Eterna/Cinema

Example email sent

[greybeard]

0x1048 ColorChromeEffect

X-T3 specific

0 = Off
32 = Weak
64 = Strong

Example jpeg in email

[greybeard]

0x1047 Grain Effect

At least since the X-T2, X-Pro2 and X-H1

0 = Off
32 = Weak
64 = Strong

Example jpeg in email

[greybeard]

0x1045 Lens Modulation Optimizer

Applies to most recent Fuji cameras X-Tx, X-Ex, X-Hx and GFX

0 = Off
1 = On

All the examples sent to date have Lens Modulation Optimizer set to On

[Phil Harvey]

Did the example XT3 file with Single Point but no size come from me?

No.

I wouldn't show the tag with "n/a" - I probably wouldn't show it at all in the same way that other tags that don't exist in the EXIF aren't shown by Exiftool.

But the value does exist (it is zero).  So it is different than tags that don't exist.  The value in showing "n/a" is that the value will be set properly when copying all tags.

- Phil

[greybeard]

But the value does exist (it is zero).  So it is different than tags that don't exist.  The value in showing "n/a" is that the value will be set properly when copying all tags.

Maybe I'm misunderstanding how this works - I thought you were converting a single tag into three "virtual" tags?

I couldn't find an existing example under the FujiFilm Makernotes where a single tag created multiple results.

[Phil Harvey]

Maybe I'm misunderstanding how this works - I thought you were converting a single tag into three "virtual" tags?

I'm decoding this as a binary data block.  NikonCustom.pm has many examples of similar decoding.

I'd send you my working copy of FujiFilm.pm, but I'm currently in the process of changing the way this decoding is done.

- Phil

[Phil Harvey]

0x1401 FilmMode

Additional Film Simulation 0x700 Eterna/Cinema

Added.

0x1048 ColorChromeEffect

Added.

0x1047 Grain Effect

Added.

0x1045 Lens Modulation Optimizer

Added.

Thanks!!

- Phil

[greybeard]

OK good - the only one I still have outstanding is Long Exposure Noise Reduction which I'm still trying to decode consistently.

[Richard_Butler]

Sorry I took my eye of this for a day. The AF-C customization stuff looks great (unless anyone is begging to know which preset was used).

It's amazing to see so all the contributions coming in here.

Let me know if you want me to check whether the GFX 50S and R use the same values for Color Chrome Effect (or send you JPEGs).

R

[Phil Harvey]

Let me know if you want me to check whether the GFX 50S and R use the same values for Color Chrome Effect (or send you JPEGs).

I don't see a need to check this unless you have some reason to suspect it may be different than the X-T3.  But I will probably be releasing the new version tomorrow -- please let me know if you find anything that should be changed or added.

- Phil

[greybeard]

Richard - that is a good point about the AF Custom presets - I'm sure a lot of users would be interested in knowing which preset was selected  - and it's particularly interesting in cameras that do not allow the individual values to be selected (such as XT-20).

It does have to be inferred though as you can't tell the difference between one of the preset options 1-5 and option 6 where the user has just selected the same values as a preset.

[Phil Harvey]

I would rather not try to infer an AF-C preset number for a few reasons:

1. It is ambiguous for models which have a custom preset as you mentioned.

2. These presets may be likely to be model-dependent, and if so, keeping this up to date with the new models would be a problem.

3. The way to implement this would be a Composite tag based on the values of the three other AF-C tags, and I don't know if this is really worth adding to the production version (a user-defined Composite tag could be created if anyone really wanted this feature).

- Phil

[greybeard]

I am already planning composites for all the tags you are splitting apart

Understand your reasoning

[Phil Harvey]

Hmmm.  If you really want composites for these tags then maybe I shouldn't be splitting them apart in the first place...

Combining the AF-C settings into one tag would be difficult since the tag names provide useful information:
AF-CTrackingSensitivity
AF-CSpeedTrackingSensitivity
AF-CZoneAreaSwitching

but keeping the FocusPriority, FocusSettings and DriveSettings together as greybeard was doing is possible... it just makes coding of the inverse conversions (for writing these tags) more difficult.  What do you think?  Should I keep these together?

Oh yeah... but then the Tag Name documentation wouldn't be as useful since it wouldn't be able to show the lookups for each value.  That would be unfortunate.  I knew there was another reason why I split these apart.

- Phil

[greybeard]

I think you should stick to your instinct and separate them - if I want the composites I can add them

[Phil Harvey]

OK, thanks.

Last night I thought of a way to add AF-C custom set number without the need for a Composite tag, so that removes point number 3 in my list, and I'm willing to overlook point number 1.  Point number 2 may become a problem, and if it does I may remove this later, but I think I'll add this tag (as AF-CSetting) to the next release just for the fun of it.  It does have the added benefit of documenting these settings.

- Phil

[Phil Harvey]

OK.  I've just released ExifTool 11.15 with the new FujiFilm tags.  We've discussed most of these changes already, but I'm open to more discussion if there is anything you want done differently.

Here is a link to the documentation for the new tags.

- Phil

[greybeard]

Thanks Greybeard.  A value of 1 is "Electronic", so how about if I call 2 "Electronic (long-exposure noise reduction unavailable)" or "Electronic (long-exposure NR selected but unavailable)"?

- Phil

A correction to this one.

It seems that value 2 means Electronic Shutter when Shutter Speed is longer than one second - which isn't long enough to trigger LENR.

The only thing I can think of is that one second is the longest shutter speed that can be selected directly using the shutter speed dial and longer speeds require the use of the "T" setting.

(It doesn't actually mean, however, that the "T" setting was used).

[Phil Harvey]

Could you suggest a name for this setting?

- Phil

[greybeard]

Maybe "Electronic Shutter (Long Shutter Speed)" ?

I will continue to think about all the changes - mostly looks good.

The use of AF-C for the prefix of the AF Custom Settings is confusing as AF-C implies continuous autofocus.

AFAreaPointSize this should just be a single digit e.g. 1 or 2 not 1 x 1 or 2 x 2 which only applies to zones

The FujiFilm.pm file in the full distribution is broken (there are a bunch of lines with just A or B starting at line 870 - deleting them seems to fix it).

I finally found the case you had where Single Point with the X-T3 did not have a point size - this seems to be where the camera is in manual focus mode - and even though you can change the focus point size for manual focus mode its not recorded in the EXIF.

[greybeard]

I'm planning to put some posts on the various Fuji oriented message boards encouraging users of Exiftool to test the changes.

Not sure how many Fuji Exiftool users there are as most prefer the GUI based tools but it does come up occasionally.

I assume that is OK with you?

[Phil Harvey]

Maybe "Electronic Shutter (Long Shutter Speed)" ?

Done.

The use of AF-C for the prefix of the AF Custom Settings is confusing as AF-C implies continuous autofocus.

The owner's manual calls these "AF-C CUSTOM SETTINGS".

AFAreaPointSize this should just be a single digit e.g. 1 or 2 not 1 x 1 or 2 x 2 which only applies to zones

Fixed.

The FujiFilm.pm file in the full distribution is broken (there are a bunch of lines with just A or B starting at line 870 - deleting them seems to fix it).

Try re-downloading the distribution.  I think that something must have happened at your end because I don't see this.  (in the full .tar.gz distribution -- which one are you using?)

I finally found the case you had where Single Point with the X-T3 did not have a point size - this seems to be where the camera is in manual focus mode - and even though you can change the focus point size for manual focus mode its not recorded in the EXIF.

Ah.  Makes sense.

- Phil

[Phil Harvey]

I'm planning to put some posts on the various Fuji oriented message boards encouraging users of Exiftool to test the changes.

I assume that is OK with you?

Sure

[greybeard]

Try re-downloading the distribution.  I think that something must have happened at your end because I don't see this.  (in the full .tar.gz distribution -- which one are you using?)

My mistake - I should have checked