TIFF Version Config to Include TIFF/EP?

Started by blue-j, September 25, 2022, 08:08:42 PM

Previous topic - Next topic

blue-j

I was curious if it would make sense to expand the TIFF version config to include recognition of TIFF/EP, the ISO spec succeeding v6?  There are a number of fields unique to that specification:

            # TIFF/EP
                41 => 'EXIF:CFARepeatPatternDim', # CFARepeatPatternDim (0x828d)
                42 => 'EXIF:CFAPattern', # CFAPattern (0xa302)
                43 => 'EXIF:Interlace', # Interlace (0x8829)
                44 => 'EXIF:TimeZoneOffset', # TimeZoneOffset (0x882a)
                45 => 'EXIF:SelfTimerMode', # SelfTimerMode (0x882b)
                46 => 'EXIF:FlashEnergy', # FlashEnergy (0x920b)
                47 => 'EXIF:Noise', # Noise (0x920d)
                48 => 'EXIF:ImageNumber', # ImageNumber (0x9211)
                49 => 'EXIF:SecurityClassification', # SecurityClassification (0x9212)
                50 => 'EXIF:ImageHistory', # ImageHistory (0x9213)
                51 => 'EXIF:TIFF-EPStandardID', # TIFF-EPStandardID (0x9216)
            },

Shortcut attempt:

    TiffVersionEPTags => [
'EXIF:CFARepeatPatternDim', 'EXIF:CFAPattern', 'EXIF:Interlace',
'EXIF:TimeZoneOffset', 'EXIF:SelfTimerMode', 'EXIF:FlashEnergy', 'EXIF:Noise',
'EXIF:ImageNumber', 'EXIF:SecurityClassification', 'EXIF:ImageHistory',
'EXIF:TIFF-EPStandardID',
    ],

Anyone game?  I tried to give an alley oop to the best of my ability...

- J

Phil Harvey

Maybe StarGeek remembers the original reason for creating the tiff_version.config file.  I can't say whether adding TIFF/EP would be useful.

But the SaveFormat API option is now documented, so I will at least change the comment at the end of the file.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

StarGeek

Quote from: Phil Harvey on September 25, 2022, 09:15:03 PMMaybe StarGeek remembers the original reason for creating the tiff_version.config file.  I can't say whether adding TIFF/EP would be useful.

Here's the original thread.  I can't comment beyond that.  Barely even remember working on it.
"It didn't work" isn't helpful. What was the exact command used and the output.
Read FAQ #3 and use that cmd
Please use the Code button for exiftool output

Please include your OS/Exiftool version/filetype

blue-j

It's definitely useful to my user community (post production professionals). We are also looking at providing an educational platform, so we have all kinds of references, specs, etc.

I've attached all I can do.  I just don't know how to write Perl loops.  - J

tiff_version_EP_draft.config

blue-j


blue-j

Corrected - both EXIF:FlashEnergy and EXIF:CFAPattern are part of the EXIF namespace and not unique to TIFF/EP.

- J

Phil Harvey

Where did you get the list of tags added by the TIFF/EP specification?  I've looked at the specification itself and I can't see a clear list of changes.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

blue-j

It starts with this, ISO 12234-2:2001, p V:

QuoteIn this part of ISO 12234, references to tags and tag values defined in TIFF 6.0 are shown in bold typeface. Tags and tag values that are not defined in TIFF 6.0 are identified in italic type face.

Then when you follow down to the table on page 13 (as printed), you find a more precise account, where you have to follow the superscript legend at the bottom of the table.  Following that logic, any tag without a superscript should be fully unique to TIFF/EP.

I did find two exceptions - CFAPattern and FlashEnergy, both of which I see in EXIF 2.32; however, at the time of writing the ISO standard it seems EXIF was at 2.1... so that is the cause, or it's human error, or I'm out to lunch?

There you go, that was my thinking.

- J