Panasonic CameraIFD 0x1001

Started by Klaus_Homeister, July 29, 2018, 12:34:16 PM

Previous topic - Next topic

Klaus_Homeister

Hi Phil,

This one is only set to '1' in Multishot-Files.
Otherwise always '0'.
It's present only in new Cams G9/GH5s/GX9.

Type is Panasonic-Bool (257) so there can't be any other option than 0=Standard 1=Multishot.


-Klaus

Phil Harvey

Hi Klaus,

I don't understand what you mean by "Panasonic-Bool (257)".  The variable type is unsigned long.

- 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 ($).

Klaus_Homeister

Hi Phil,
sorry I overlooked this post.

Late answer:

A TagRow consist of Tag 16Bit, Type 16Bit, Len 32Bit, Value 32Bit.

When you are parsing 'Camera-IFD' and look to the _full_ 16Bit of the Type-definition ... then you will see a Type 257 and 258!

They're not defined in the TIFF-Specifications.
{"ILLEGAL","BYTE","ASCII","SHORT","LONG","RATIONAL","sBYTE","UNDEFINED","sSHORT","sLONG","sRATIONAL","FLOAT","DOUBLE"}

When your software reinterpretes a "faulty" Type-definition as 'unsigned long' everything is working fine.

You only miss the information ...
-> that every value of Type '257' can be only '1' or '0' ... never something else.!
-> that every value of Type '258' can be only '0' or '1' or '2' or '3' ... never something else.!

My interpretation is
Type 257 as 'Panasonic-Bool' (TRUE/FALSE,ON/OFF) and
Type 258 as 'Panasonic-HalfByte' (N/A, State1|2|3 )

Camera-CPUs like the Fujitsu-Milbeaut and others allow exactly this:
defining a variable as Bool using just 1 Bit or defining a variable as a HalfByte using only 4Bits.
And I think that such values are stored in those Tags of Type 257 & 258.

Tag 0x1000       BOOL
Tag 0x1001       BOOL
Tag 0x1002       BOOL
Tag 0x1102       BOOL
Tag 0x1200       BOOL
Tag 0x1204       BOOL
Tag 0x1400       BOOL
Tag 0x1401       BOOL
Tag 0x1402       BOOL
Tag 0x140C       BOOL
Tag 0x140E       BOOL
Tag 0x140F     HALFBYTE
Tag 0x3208     HALFBYTE
Tag 0x320C     HALFBYTE
Tag 0x320D     HALFBYTE
Tag 0x3502       BOOL
Tag 0x3503       BOOL
Tag 0x3701       BOOL
Tag 0x3702       BOOL
Tag 0x3707       BOOL
Tag 0x3708       BOOL
Tag 0x4000     HALFBYTE
Tag 0x4001     HALFBYTE
Tag 0x4002     HALFBYTE
Tag 0x4003     HALFBYTE

It is not violating the TIFF-Specifications to use private Types in Private IFDs like the Camera-IFD.

regards
Klaus