Recent Posts

Pages: [1] 2 3 ... 10
1
Darn, you're right.  I just tested this out.  I had made a last minute change to the GIF module to move the extensions to a different table and I seem to have broken this.  Sorry. 

This will be fixed in the next release.

- Phil
2
Metadata / Some new FUJI X30 tags
« Last post by ChrisSchucker on Today at 07:01:24 AM »
0x1031 (Picture mode):
  if value = 0 and 0x1425 (Short) present --> SR+
  if value = 0 and 0x1425 not present --> Auto

0x1425 (short), Scene recognition:
  Highbyte
    0: None/Unrecognized scene
    1: Portrait image
    2: Landscape image
    3: Night
    4: Macro
I think, there are more values for other scenes (beach etc.)

0x140A (short): Kind of Bitfield:
   Bit 2 (0x04): Red eye detection on
 
In case of red eye reduction is on, 0x4200 - 0x4203 is not identical to 0x4100 - 0x4103:
0x4200 (short): Number of "face/eye" rectangles

0x4201 (short array): Kind of rectangles
    1: Face
    2: Left eye
    3: Right eye

0x4202 (byte array): Number of coordinate of each rectangle (?)

0x4203 (short array): left, top, right and bottom coordinates
in full-sized image for each element (face, left eye, right eye) detected

3
I am redirecting > OUTFILE and the OUTFILE created is zero length.
I am using CMD on windows 7.
4
Are you redirecting the output as in Phil's post?

Are you using CMD if on Windows and not Powershell?  Powershell does not work for binary redirection and you must use CMD.
5
Alas using the sample file of the OP on v10.57, the command exiftool -midisong -b FILE *does* recognize the MIDISong tag  but  produces a nil output. The tag http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/GIF.html doesn't appear to be processed.
6
You should be able to do this already:

exiftool -midisong -b FILE > OUTFILE

- Phil
7
I just noticed, starting with Exiftool 10.55 GIF MIDIControl Tags (MIDICTRL/jon) are now shown.  :)

Thanks Phil!

More greedy request: any chance to also extract the MIDISong (MIDISONG/Dm7) PCM data? Perhaps -b storing it in an external binary file?
8
Metadata / Re: Post your LensType / LensID discoveries here
« Last post by Phil Harvey on June 23, 2017, 06:54:26 AM »
Hi Steve,

I will add support for the Sigma, thanks.

The Tamron should already be properly identified in original camera images.  If not, please send me an original image shot with this lens (phil at owl.phy.queensu.ca).

- Phil
9
Newbies / Re: Export to CSV separator switch not working or missunderstanding
« Last post by Phil Harvey on June 23, 2017, 05:41:28 AM »
Hi Bastel,

The -csv option only outputs comma separated, but it will properly quote values which contain commas, so all should be good.

- Phil
10
Metadata / Re: Post your LensType / LensID discoveries here
« Last post by stevebates on June 23, 2017, 04:26:50 AM »
Hi,

I have a couple of lens that aren't registering correctly. I use a Canon EOS 550D and these are

"Sigma 18-300mm F3.5-6.3 DC MACRO OS HS" shows as:

Code: [Select]
Lens Info                       : 18 300 undef undef
Lens                            : Canon EF 75-300mm f/4-5.6 IS USM
Lens ID                         : 197

"Tamron AF 70-300mm f/4-5.6 Di LD 1:2 Macro" as:

Code: [Select]
Lens Type                       : 28
Lens                            : 70
Lens ID                         : 28

Is there anything I can do to improve the detection as the correct lens?

Regards,

Steve.
Pages: [1] 2 3 ... 10