Jump to content

Exif Data


Recommended Posts

Advertisement (gone after registration)

That was exactly the GUI that I looked at. However it does not allow for editing of Leica MakerNotes, which is the area that we need to edit in this case. As I understand it this area is not used in a uniform way. The writer only intended to provide some functions for common options which are useful to them. Leica Makernotes are not a standard thing of interest to many, sadly!

Link to post
Share on other sites

  • Replies 70
  • Created
  • Last Reply
.......................................

# Adds lens info for Summilux 50 on M9

-n

-MakerNotes:LensType=32 3

-XMP:MaxApertureValue=1.4

-EXIF:MaxApertureValue=1.4

-EXIF:FocalLength=50

-EXIF:FocalLengthIn35mmFormat=50

-overwrite_original_in_place

.....................................

That's not for the Summilux 50 but for the Summilux-M 50 Asph.

 

 

After that by dragging the files onto the EXIFTool shortcut I saw the correct information now displayed. Deleting the old files, clearing the cache and importing those edited files anew with Lightroom 3.4.1 the metadata still is missing the lens name and focal length (or rather Lightroom is still not displaying it).

Strange! On import, Lightroom (or Bridge) normally will add the missing XMP fields "Lens" and "LensInfo" from the MakerNotes:LensType data. If for some reason it doesn't, you can explicitly add these fields yourself:

 

.......................................

# Adds lens info for Summilux-M 50 mm 1:1.4 Asph on M9:

-n

-MakerNotes:LensType=32 3

-XMP:Lens=Leica Summilux-M 50 mm 1:1.4 Asph

-XMP:LensInfo=50/1 50/1 14/10 14/10

-XMP:MaxApertureValue=1.4

-EXIF:MaxApertureValue=1.4

-EXIF:FocalLength=50

-EXIF:FocalLengthIn35mmFormat=50

-overwrite_original_in_place

....................................

 

 

For the Summarit 50 mm 1:1.5, you would use this argument file (do not include the dotted lines in the file's contents):

.......................................

# Adds lens info for Summarit 50 mm 1:1.5 on M9:

-n

-MakerNotes:LensType=0 0

-XMP:Lens=Leitz Summarit 50 mm 1:1.5

-XMP:LensInfo=50/1 50/1 15/10 15/10

-XMP:MaxApertureValue=1.5

-EXIF:MaxApertureValue=1.5

-EXIF:FocalLength=50

-EXIF:FocalLengthIn35mmFormat=50

-overwrite_original_in_place

....................................

 

 

I have 200 files I want to fix.

Rather than specifying an individual image file or an explicit list thereof, on the command line you can just as well specify the name of the directory which contains the image files to process if there are many of them. Prepare one argument file for each lens you're using. Sort the image files into an array of folders, one for each lens you had used. Then apply one call to ExifTool with the specific argument file to each of the folders.

 

 

But I think that I understand how EXIFTool is meant to be used now (from command line and via dragging files onto shortcut) ...

Ummm—you either use the command line interface (for complex tasks) or you use the droplet interface (for simple tasks) ... but not both.

 

 

That was exactly the GUI that I looked at. However it does not allow for editing of Leica MakerNotes, which is the area that we need to edit in this case.

ExifToolGUI still is useful to inspect the EXIF data, including Maker Notes ... for Windows users, that is (Mac users need something else). I am using it frequently.

 

 

That seems like a lot of work for little reward.

It's very little work and very quick and easy to do.

Link to post
Share on other sites

That's not for the Summilux 50 but for the Summilux-M 50 Asph.

 

 

 

Strange! On import, Lightroom (or Bridge) normally will add the missing XMP fields "Lens" and "LensInfo" from the MakerNotes:LensType data. If for some reason it doesn't, you can explicitly add these fields yourself:

 

.......................................

# Adds lens info for Summilux-M 50 mm 1:1.4 Asph on M9:

-n

-MakerNotes:LensType=32 3

-XMP:Lens=Leica Summilux-M 50 mm 1:1.4 Asph

-XMP:LensInfo=50/1 50/1 14/10 14/10

-XMP:MaxApertureValue=1.4

-EXIF:MaxApertureValue=1.4

-EXIF:FocalLength=50

-EXIF:FocalLengthIn35mmFormat=50

-overwrite_original_in_place

....................................

 

 

For the Summarit 50 mm 1:1.5, you would use this argument file (do not include the dotted lines in the file's contents):

.......................................

# Adds lens info for Summarit 50 mm 1:1.5 on M9:

-n

-MakerNotes:LensType=0 0

-XMP:Lens=Leitz Summarit 50 mm 1:1.5

-XMP:LensInfo=50/1 50/1 15/10 15/10

-XMP:MaxApertureValue=1.5

-EXIF:MaxApertureValue=1.5

-EXIF:FocalLength=50

-EXIF:FocalLengthIn35mmFormat=50

-overwrite_original_in_place

....................................

 

 

 

Rather than specifying an individual image file or an explicit list thereof, on the command line you can just as well specify the name of the directory which contains the image files to process if there are many of them. Prepare one argument file for each lens you're using. Sort the image files into an array of folders, one for each lens you had used. Then apply one call to ExifTool with the specific argument file to each of the folders.

 

 

 

Ummm—you either use the command line interface (for complex tasks) or you use the droplet interface (for simple tasks) ... but not both.

 

 

 

ExifToolGUI still is useful to inspect the EXIF data, including Maker Notes ... for Windows users, that is (Mac users need something else). I am using it frequently.

 

 

 

It's very little work and very quick and easy to do.

 

If you read the beginning of the thread you would see where I state, "I use Aperture 3." This is a Mac Application so a windows command line tool is out of the question. Unless I am way off, I believe the majority on this forum are Mac users. Leica and Mac have a lot in common ;)

Link to post
Share on other sites

If you read the beginning of the thread you would see where I state, "I use Aperture 3." This is a Mac application so a Windows command line tool is out of the question.

ExifTool is not a Windows command line tool. You can use it on any platform.

Link to post
Share on other sites

Advertisement (gone after registration)

I'm with Beyder in hoping for an EXIF editor with Mac-like interface. That interface is important, and I'm not into scripting with Terminal or even Automator. Perhaps the author of M8 Info will put together a nice little application. :)

Link to post
Share on other sites

Because its a command line app which is clunky, the complete opposite of user friendly and not very easy to use for someone who has never really got into DOS.

Sorry, but you are mixing up exiftool and exiftoolgui. Have a look at the latter please.

Link to post
Share on other sites

Sorry, but you are mixing up exiftool and exiftoolgui. Have a look at the latter please.

But exiftoolgui is for Windows only, and won't run on a Mac... or am I mistaken?

 

The best hope now may be GraphicConverter, which I've used for years, but didn't realize might be able to edit EXIF... So, digging into the latest version for a look-see...

 

There are many small uses of portions of EXIF data, and the EXIF can be copied various places and to text. Specifically, I want to add missing focal length and aperture info. But it you edit the EXIF in a text editor, GC won't Paste it back to the file it was copied from. It appears that there is no function in the program for editing EXIF/EXIFTool data as a whole.

Link to post
Share on other sites

If one really wants to nitpick, the MakerNotes are properly part of the EXIF metadata (tag 927C), it is just that the value of this field isn’t standardized and can be used whichever way the camera vendor thinks is appropriate.

Link to post
Share on other sites

... the MakerNotes are properly part of the EXIF metadata (tag 927C) ...

The EXIF data don't contain MakerNotes but just a reference to them, that is, a pointer that says if a MakerNotes section exists and if so, where. That doesn't make the MakerNotes a part of EXIF. Only the pointer to the MakerNotes is part of EXIF.

Link to post
Share on other sites

No, it's not.

 

Instead, it's in the MakerNotes section; the tag's name is CameraTemperature, and the number is the temperature in degrees Centigrade (°C).

 

Thanks for the help. I didn't know exactly where it was, but only that it was in Notes and could be extracted by ExifTool.

 

And there is a way, a bit of a kludge perhaps, to search files for CameraTemperature. Dump all files CameraTemperature using one command with output redirected to a text file and grep for the info.

Link to post
Share on other sites

Why don't you guys just run Parallels or VMware for such specialized stuff?:confused:

 

I simply refuse to use Windows in any capacity. Also, can you imagine the pain of not only using this clunky Windows only application (ExifTool) but then using it on Windows, not getting everything needed out of it anyway (Leica MakerNotes), and then having to export all files from Aperture on the Mac to Windows, running ExifTool, and then exporting back to Mac and then to Aperture. You feel that is a legitimate solution? (Im not even mentioning the cost of a Windows OS and VM Software).

Link to post
Share on other sites

... can you imagine the pain of not only using this clunky Windows only application (ExifTool) but then using it on Windows, not getting everything needed out of it anyway (Leica MakerNotes) ...

ExifTool is not Windows-only; it can be used on any platform. And it sure will extract all metadata out of your image files, including all MakerNotes. For direct reading and manipulation of image metadata, it's the most powerful tool available. When you're having an issue with your images' metadata then turning down ExifTool just out of ignorance is not a very clever move. And when you feel ExifTool was too clunky to use then my suggestion is to leave your image files just the way they are.

 

And oh, didn't you say you already tried ExifTool before? So why do you keep purporting it was Windows-only; you should know better. Sure, it's not the most comfortable software product to use ... but tinkering with image metadata is a low-level task, so you better get used to a low-level (hence universal and powerful) tool.

Link to post
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...