Lightroom Metadata Viewer Preset Builder (for Lightroom 1.1+)
Metadata Viewer in Adobe Lightroom 1.1
Metadata Viewer in Adobe Lightroom 1.1

As mentioned in my previous post, Adobe has just released Lightroom 1.1, a free upgrade to their wonderful photo-workflow application. Correspondingly, I have upgraded my Custom Metadata Viewer Preset Builder, a web application that allows you to create custom metadata display configuration templates for use within Lightroom.

This web-based tool is now superseded by my Metadata-Viewer Preset Builder plugin for Lightroom 2 and above.

This description is presented with Lightroom 1.1 as an example, although the config files should work in any version of Lightroom 1.x, including 1.3.1.

A screenshot showing a custom metadata viewer preset in Adobe Lightroom 1.1, created with Jeffrey's Lightroom Metadata Viewer Preset Builder

This post is the introduction and documentation for my template-builder application. If you have used the previous version, you'll find lots of new things here, including new metadata items, new display options, and even the ability to set label text.

Table of Contents


An example of Lightroom 1.1's metadata display panel is shown at right. The panel is capable of showing much more information about an image than anyone's likely to want to see at one time — over 100 items, such as the image filename, the latitude/longitude where it was taken, the shutter speed, a caption, etc.— the volume of which can quickly overwhelm.

To whittle down the display to a smaller set of items, Lightroom comes with a number of built-in display presets (Default, All, EXIF, IPTC, Large Caption, Location, Minimal, and Quick Describe), each showing a different subset of the possible items. But because there are so many items that might be shown, chances are small that a built-in presets shows just the items you wish to see.

This is where my web application comes in: with it, you can create your own display-configuration presets. The one shown at right is the one I made for my own daily use.

Viewer Presets vs. Data Presets

I must be clear up front that this post is about selecting which fields to display, in what order, and with what labels. It is not about “this field is assigned this value” Metadata Presets that Lightroom already allows you to create and edit. (For what it's worth, you can access those presets via the “Preset” selector seen just under the red-circled “Jeffrey's View” in the screen capture shown at right.

Obligatory Disclaimer

Custom metadata-viewer presets, from this or any source, are not supported by Adobe. There are no guarantees that the presets you build for Lightroom Version 1.1 will be at all useful with later versions of Lightroom. In fact, there are no guarantees that they'll be useful with any version of Lightroom.

“Use at your own risk.”

Quick Overview

To build your own preset, use my web application to select the metadata items you want to see and arrange them in the order you prefer. You give your configuration a title (I used “Jeffrey's View”) and then a file is generated for you that you then download and install in one of Lightroom 1.1's system directories.

Your preset is available the next time you start Lightroom, in the Metadata Panel drop down box as shown at right.

Using the Application

When you visit Jeffrey's Lightroom Metadata-Viewer Preset Builder (finally, that's the link to the application!), you are presented with the view shown below.

(For a clear view, you can also remove the annotations.)

An annotated screenshot showing Jeffrey's Lightroom Metadata Viewer Preset Builder

The Menu
Choose from over 100 items

To create your own presets....

  1. Select one of Lightroom's built-in presets to use as a starting base, or choose from among one of the extras I've included (“None,” “All 1.1 Supported Fields,” and “Jeffrey's View,” my own daily-use preset).

  2. Read the instructions, then press the “hide header” button to devote more of the screen to the preset builder itself.

  3. Create your preset, adding and removing items by checking them in the menu (seen at right), adding headers and rules with the buttons at the top of the menu, and by adjusting item options.

  4. An example view of your custom preset is shown in the lower-left of the application, with fake metadata filled in from one of my images, just to give a sense of how it'll look in actual use.

    In the custom list, you can drag items to reorder them, and you can drag them to the trash (the pink stripe at far the left) to remove them. This goes for header and rule lines as well.

  5. Once everything's as you like it, bring back the application's header by clicking the hide-header button again (which had become a show-header button) and enter a title for your preset. The title you choose here is what Lightroom shows in the drop-down list of presets (as shown earlier), so choose a short but descriptive title.

  6. Finally, press the “Generate Preset File” button.

After pressing the generate-preset button, you're presented with a page from which you can download the template, as discussed a bit further down.

Menu Buttons

The top of the menu area contains six buttons grouped to provide three unrelated functions (placed together for convenience):

  1. The “Expand/Collapse All” buttons work on the menu list itself, revealing or hiding the 100+ metadata items supported by Lightroom. You can, of course, expand and collapse individual subtrees with the boxed “+” by head menu header item.

  2. The “Unhide/Hide All Options” items are for revealing each item's option list (when the item itself is revealed, of course). The box of options (like the red-boxed controls for “Dimensions (+ crop)” in the menu image above right) can be long, and are not often needed for most items, so by default they appear first as a “click to show options” placeholder.

  3. The “Add Header Text” button inserts a new header line into the template, which you can then click on to edit. “Add Rule Line,” unsurprisingly, adds a new rule line.

Some items in the menu have more details than others. Here's an example that illustrates everything, with the display options showing (unhidden).

Display Options

Each item has its own mix of display options, from among the following. My web application attempts to reflect the visual effects option, but the descriptions below are for how they affect the display once loaded into Lightroom...

  • Shown when not blank vs. Shown always — Some items, by default, are not shown by Lightroom when the item's underlying data is missing from the image. For example, even if a template includes the “Shutter Speed” item, Lightroom doesn't show it if the shutter-speed data is missing from the image. By selecting “shown always,” the label will be presented but the value area will be blank.

  • Readonly — when this is turned on, editable items become static display items. This might be helpful during client presentations, but is of limited usefulness because any “click to edit” icons remain.

  • Enter finalizes vs. Enter included — Normally while typing text into one of the metadata editable fields, hitting enter causes the input to be finalized, returning control from the field to the larger Lightroom application. When Enter included is selected, enter inserts a newline into the metadata value.

  • Lines — how many rows the item value should occupy in the display. This is the most useful for free-format editable fields (“Caption,” “Copyright,”, etc.) and is the minimum size: the field grows as needed for longer text. Most other fields (“Rating,” “Filename,” etc.) use only one row regardless of this setting, so adding further rows simply adds padding under the value.

  • Width Normal vs. Width Wide — the normal presentation is a two-column approach, with the label on the left and the value on the right. When choosing Width Wide, the value is presented with the whole width of both columns, and the label is presented above it. (An example is shown below.)

  • Label — Choosing None is similar to Width Wide in that the value is presented using the full width of both columns, but the label is not shown above the value. When Custom is selected, the label text input field appears, allowing you to override the label with your own choice. There are some cautions about doing this, discussed below.

Overriding Label Text

The labels for metadata fields can be changed in three ways:

  1. By Adobe, when they put out a language/region-specific version of Lightroom
  2. With my Lightroom Configuration Manager (not yet upgraded with new items from 1.1)
  3. By entering label overrides in this metadata configuration manager.

The preset display shown at the top of this post is my personal “Jeffrey's View” preset, with many of the label text set with this application (method #3). Most changes were to make labels shorter (such as “Dimensions” → “Size” and “Capture Date” → “Date”) because the label column in Lightroom is only as wide as needed for the longest label, so making long labels shorter means more overall width is devoted to the values.

I also changed some labels to change their meaning. For example “Copy Name” became “View Name” for reasons I'll explain in another post. “Job Identifier” became “Blog URL,” because I use that field to record the URL of the blog post or posts that an image was part of.

I also used a blank custom label for a couple of items, so as to reduce visible clutter. One was the ridiculously verbose “ISO Speed Rating”, which I made blank because the value has “ISO” in it, and placed right below “Exposure,” it's certainly not ambiguous.

I did the same with “Capture Time,” since “8:312:17 AM” right below “Date” is pretty clear.

There's one concern you should be aware of if you intend to use multiple presets or share your presets with friends: labels changed with this application are seen only when the specific preset is selected, and override any changes made by the other methods. That means, for example, they override the language-specific labels found in localized versions of Lightroom.

If you want to change a label for all presets (including the original built-in presets), use my Lightroom Configuration Manager instead of overriding while making a preset.

As a convenience, the per-preset download page offers an extra “no label overrides” download if the preset contains label text overrides. That allows those who don't care for your label text (because, for example, they prefer labels in their native language) to use your preset without losing their labels.

Wide, No Label, Empty Label

The various permutations of Label and Width display options can be a bit confusing, so here are some examples (the first being the default):


After pressing the “Generate Preset File” button, you're taken to a page that offers a download for a “.lrtemplate” file. You can bookmark that page, and share its url with those you'd like to share your preset with; they can then download the same preset, or use yours as a basis from which to build their own. For example, here's the page for my main daily-use preset that's been the subject of these examples.

On the download page, click the link and save the preset file to disk.

Before installing your first preset, you must first create a “Metadata Field Lists” directory in Lightroom's application support folder. To find that folder, from within Lightroom invoke the Help > Go to Lightroom Presets Folder command to bring up the “Lightroom” folder, within which you should create the “Metadata Field Lists” folder that holds the “.lrtemplate” file downloaded.

For reference, the folder you create will likely be:

Mac OS X:
~/Library/Application Support/Adobe/Lightroom/Metadata Field Lists/
Windows XP:
C:\Documents and Settings\username\Application Data\Adobe\Lightroom\Metadata Field Lists\
Windows Vista:
C:\Users\username\AppData\Roaming\Adobe\Lightroom\Metadata Field Lists\
or perhaps
C:\Users\username\Application Data\Adobe\Lightroom\Metadata Field Lists\

Preset drop-down where your
preset title appears in Lightroom

(On Windows, you may have to visit the Folder Options dialog to allow the normally-hidden Application Data folder to be seen.)

Finally, drop the .....lrtemplate file you downloaded into the directory you just created, and start (or restart) Lightroom.

The left side of the header in the Library Mode's Metadata Panel likely says “Default” — click it to see your preset among those in the drop-down list.

General Notes

Here are some cautions about Lightroom's metadata viewer, whether with a custom preset or one of the standard ones:

  1. All 100+ metadata items are new in this version in the sense that they all now have display options, but those items totally new in this version are marked in the menu with a bright “new” label. Click the [Expand All] button and scroll through the Menu to see them all.

  2. The preset builder shows a very wide view of the Metadata viewer panel — perhaps wider than most people will want their Lightroom panels to be (since widening the panels takes away from the Grid/Loupe area). So, keep in mind that long data (e.g. lens information, camera make+model) may be too wide to actually fully appear in normal use. (Yet another reason to use shorter labels.)

  3. Some items seem almost identical, but are really quite different. For example, both the “File Path” and the “Folder” items display the name of the folder that the file is in, but they differ in how they interact with the mouse: clicking on one brings up the file in Explorer/Finder, while the other switches Lightroom to viewing the images in that same folder (something I find much more useful).

    The similarity among some of the items is one reason that the standard “All” preset really doesn't have all the items. It's also one reason that you'll want to take care when building your presets, so you'll get what you think you're getting.

  4. As you move from image to image in your library, the metadata items missing from an image are not shown in the metadata panel unless they're editable, or have the “Shown always” option selected.

  5. Click on an item in the metadata field list to automatically bring up the corresponding controls in the menu.

  6. The metadata viewer simply reports metadata in the file (or in Lightroom's database about the file). For example, Lightroom could potentially compute a value for “Focal Length 35mm” (full-frame-35mm-camera effective focal length), but it reports it only if that Exif field is actually present in the image metadata.

    (Actually, Lightroom doesn't display this particular field even if it is present in the image; I've submitted this bug to Adobe.)

  7. Lightroom does not generally show metadata from the “Maker's Notes” section of metadata placed by many cameras. For example, Nikon cameras place the distance to the subject, if known, into the Exif “Subject Distance” field of JPG images it creates, but for NEF (raw) images, Nikon puts that data only into the Maker's Notes. Thus, Lightroom does show the subject-distance field for Nikon JPGs that have it, but not for Nikon NEFs that have it.

    (On an odd but encouraging note, Lightroom does pick up the Lens information from Nikon raw files.)


The colophon for the first version tells how this project came about.

This project was made much easier to develop by the Yahoo! User Interface Library, and two Firefox extensions: the most excellent Aardvark and mind-blowingly-supreme Firebug.

It was a lot of work just to get this application working in a first-class browser like Firefox, not to mention then getting it to work in IE. I hope you'll find that it was worth it.

All 40 comments so far, oldest first...

Thanks Jeffrey, not only for this updated metadata viewer preset builder, but also for drawing attention to the 1.1 release, which looks have some pretty exciting features.

Your previous preset builder was a real boon and, now I am becoming more familiar with Lightroom and what I want from it, I look forward to using the new version to tweak my 1.1 set-up.


— comment by Peter on June 28th, 2007 at 6:08pm JST (12 years ago) comment permalink

(same message as on the old page)
Just to say I encountered a bug : the preset freezed Lightroom on startup, with the following error message :

An unexpected error occured while loading a module:

Assertion failed: lua_pcall(L, 2, 1, 0) == 0

The preset is here :
I didn’t have had time to tinker with it, and maybe find a compulsory field missing in it?

I downloaded and tried the preset on my system, and it worked fine. This is very odd. I’ve seen that kind of error before when there’s a syntax error in the file. Perhaps it’s getting corrupt during the download? Try this version and let me know whether it works….. —Jeffrey

— comment by Nicolas on July 4th, 2007 at 5:18pm JST (12 years ago) comment permalink

Thanks for the efforts…this is really a productive tool. I’ve run into a couple of issues I wanted to pass along (running on Firefox on a Win XP system):

On the field “Original Filename (if applicable)” (and others), when you are modifying the custom label, if you hit the enter key the page turns blank with the word “null” at the top. The page title is javascript:null. All of he work to that point is lost, and you have to start over.

Since what looked a server crash at your end yesterday (7/4), when I specify my last saved template as the starting point, I keep getting an older version from a couple of days ago. I tried resaving it as a new template and so far it seems to be working with the new template.

The are some fields where the options description refers to “depending on the Always option” but the option isn’t present. Again, the field “Original Filename (if applicable)” is one of those.


— comment by Jim on July 6th, 2007 at 5:23am JST (12 years ago) comment permalink

Hi Jeff, thanks for that really neat metadata display organizer; works great on LR ver 1.1.
Next isn’t a ‘Comment’, but couldn’t locate a tech-help email address.

Two Questions:

1) After installing the Preset, there always are some minor tweaks you wish you had done.
Went through a complete redo of my original, but wonder if I can somehow upload the current preset and re-start direct from there — rather than starting all over.

2) The proliferation of the caption “Location” appears in several locations … EXIF, IPTC and lord knows where else. Somehow I seemed to have trouble getting LR 1.1 to accept entries in their ‘Location’ setting; the city entry [Columbia (SC)] just didn’t seem to stick.
Finally ended up nar the bottom in the IPTC section to display THAT location, and it stuck. Now, however, the ‘Metadata Browser’ (left panel) shows several layers of “Unknown” Country, State and City — with Columbia (SC) finally showing as subentry below “Unknown City” — not very pretty for a compulsive neatnik.
Any suggestions as to which of the numerous ‘Locations’ – not to mention City etc would (or could) be recommended? All I want to show is an easily located [Find using Metadata] location where the photo was taken without bothering with copyright, authorship, etc.

Appreciate your suggestions, and the energetic promotion of LightRoom. I think LR has enormous potential, and ver 1.1 was a considerable step forward. But it’s got a ways to go yet with database management and other Forum issues. Certainly Windows users seem to have a diproportionate number of nasty/disappointing issues as against the Mac.

Best Regards, -=Rudy=-

— comment by Rudolph de Jong on July 9th, 2007 at 11:29pm JST (12 years ago) comment permalink

Just wanted to say that I discovered your preset builder while searching various forums (fora?) for various LR questions. It is the answer to (at least one of) my LR prayers! I had started to search for info on the various metadata token names, the format for preset building, and the language for template building, and I found you. Very nice work — a real service to the community.

Regards, dds

p.s. Now, can I do a “preset” to set the default to the crop drop-down to something other than Original? e.g., I’d like it to start with 8×10, because that’s how I usually crop my pics.

— comment by Dennis Steinauer on July 12th, 2007 at 12:41am JST (12 years ago) comment permalink

I created my dream preset, Title, Caption and Keyword… however I can’t get the keyword field to be editable. I’ve tried Wide and Normal, 1 line or multi-line, with read-only ticked on and off… I even went into the text file and changed:
‘com.adobe.keywords’, heightInLines=2, readOnly=true, topLabel=true }
‘com.adobe.keywords’, heightInLines=2, readOnly=false, topLabel=true }
in hopes that would fix it.

Is this a lightroom thing, I have a vague recollection to that effect but the read-only tick box got my hopes up, or is there indeed some way to make that field editable as if it were in the Keyword panel?

Yes, unfortunately, it’s a Lightroom thing. That metadata element doesn’t allow for editing in the metadata panel. (Adobe intends for keyword editing to be done in the keyword panel, I guess.) I’ve updated the tool to reflect the read-only one-line-only nature of that element. —Jeffrey

— comment by Jonathon Brown on July 20th, 2007 at 3:50pm JST (12 years ago) comment permalink

Hi Jeff,

Thanks a lot for your great tool and for your efforts 🙂

Regards, Manfred

— comment by Manfred Schneider on July 24th, 2007 at 6:09am JST (12 years ago) comment permalink

I, too, received the “Assertion failed: lua_pcall(L, 2, 1, 0) == 0” error and a frozen LR 1.1 upon LR startup after adding my presets file.

Investigation revealed that some of the methods possible to use when saving a file from a link result in files that generate the above error. For examble, left clicking on the link of the generated preset file (displays the contents of the preset file) and selecting File->Save As… from the IE7 toolbar ‘saved’ a file that was not usable as a preset file. The actual preset file data was encapsulated by HTML doc header/footer which caused LR to generate the error.

The correct file contents could be generated using File->Save As… providing the file type ‘.txt’ was selected and a suffix was not typed in. The ‘my presets.txt’ file could then be renamed to my ‘presets.lrtemplate’ and it would work.

A ‘better’ way to ‘save the file’ is to right click on the link “save this link to disk” and select Save Target As… which always resulted in a proper preset file even when ‘.lrtemplate’ was specified as the file suffix.


— comment by Ron on July 26th, 2007 at 4:30am JST (12 years ago) comment permalink

Great tool! I was referred over to your site by several people in the Adobe forum after I posted a question about the Keyword field. My question was how to get the field to show up in the Metadata panel, and the answer is to use your tool for a custom preset.

I did use the tool and it works! However…for some reason I can’t get ALL the keywords to show up. I entered the keywords in LR with parents. So for example my keywords include “San Francisco” with a parent of “USA”. After I use your tool, I can see “San Francisco” but NOT “USA”.

However, “USA” does in fact show up in the Keywording Panel upper right side of the screen, and also in Keyword Tags left side of the screen. So I know it’s in there somewhere. It also shows up in Bridge and another program ACD Pro when I view this same image in those programs.

Any ideas? Sounds like another LR ‘feature’…

Hi Bob, I replied to this over on the Adobe forum (finally… sorry for the delay), in two posts starting here. In summary, I think what you’ve run into is a reflection of the Keyword Panel being the intended UI for keywords, so that the Keyword field in the metadata panel was not intended to actually be used. That’s my guess, at least… —Jeffrey

— comment by Capt'n_Bob on August 10th, 2007 at 8:02am JST (11 years, 11 months ago) comment permalink

Hello Jeffrey,

Thank you for this tool, it looks great! Unfortunately I have problems using it. I made a “lrtemplate” I copied on my hard disk. But I don’t know why, LR doesn’t show me this template in the list of metadata views. I made a custom view, and then downloaded yours. But both don’t appear in LR. Do you know why? Already had such an experience?

Thank you, you made a great job!

(It turns out that he’d placed the file in the wrong spot. He’s put it into the correct spot and it now works…. —Jeffrey)

— comment by Etienne on August 16th, 2007 at 6:04am JST (11 years, 11 months ago) comment permalink

I should’ve been more specific in my above comment -can I make the navigator and histogram modules disappear? I know it seems picky, but it’s critical for us to have as simple of an interface as we can manage. PLEASE let me know if you’re working on or know of a Metadata Browser editor. It’d be helpful to see Filetype, Date and Creator, but not the rest. I’m also hopeful that I can find or create an Image Processor which wouldn’t require Photoshop (it could probably use multiple exports from Lightroom with different settings (we need TIFF, DNG, small JPEGs, and a hard copy of everything and every time we shoot).

— comment by Mat Pearson on August 31st, 2007 at 10:11am JST (11 years, 11 months ago) comment permalink

Is this working with version 1.2? I’m using windows XP and LR is not loading my templates. I have tried both this folder:

C:\\Documents and Settings\\username\\Application Data\\Adobe\\Lightroom\\Metadata Field List

and this:

C:\\Documents and Settings\\username\\Local Settings\\Application Data\\Adobe\\Lightroom\\Metadata Field List


It works fine in 1.2. You need to be sure your username is in the path (where I inserted it above), and you want the final folder name to end with the plural “Metadata Field Lists”, not the singular “Metadata Field List” you cited. That’s probably the issue you’re facing. —Jeffrey

— comment by kurka666 on November 1st, 2007 at 7:45pm JST (11 years, 9 months ago) comment permalink

oh – it was the “S” that was missing in the end. I must ble blind…

Thank you so much!

— comment by kurka666 on November 1st, 2007 at 10:10pm JST (11 years, 9 months ago) comment permalink

So near and yet so far! I am desperate to add some two line captions to a slide show this afternoon. Your template maker seems to permit this. Unfortunately, when I generate a template, I get this error (even when I use only the default settings):

An unexpected error occurred while loading a module.
Assertion failed: lua-pcal(L,2,1,0)==0

I am using Lightroom 1.3. Will your program only work on 1.1?


PS I am aware that there is a problem with multi-line keywords. However, this error occurs even when I don’t try to use multi-line.

— comment by Stan Armstrong on December 8th, 2007 at 2:35am JST (11 years, 7 months ago) comment permalink

I’m Using LR 1.3 on a Leopard Mac and multi line caption was not working with the Preset Builder. A little digging in the app led me to this fix:

old: { formatter = ‘com.adobe.caption’, heightInLines=3 },
new: { formatter = ‘com.adobe.caption’, height_in_lines=3 },

Just edit your downloaded preset with a text editor and make the change.

Ack, good catch! I wonder when Adobe made that change (and my goodness, why didn’t they run it by me for approval? 🙂 ). I’ve updated the tool to create both heightInLines and height_in_lines so that it’ll work with any of the versions since 1.1, so someone merely needs to re-download their config file to pick up the changes. —Jeffrey

— comment by Grrr on December 20th, 2007 at 2:24pm JST (11 years, 7 months ago) comment permalink

I’d like to know if I could use this tool to completely change the data fields for a project. I’m working on a directory and I need to ask all the photo subjects if the current info I have for them is correct. So, I’d want to change the field names to things like ID#, Address (5 fields), Phone, Degree, Specialty, Leadership Positions, and a Photo.
I’ve been trying to get FileMaker Pro and Dreamweaver to work nicely together and I don’t have a clue about PHP.
I bought FMStudio from but then learned that I’d have to buy FileMaker Server Advanced (expensive), or pay for FileMaker hosting – not in the budget.

Will this tool allow me to edit the fields and more importantly export the database and display it on the web for the 650 people to view their data with their photo and then email me changes (or possibly edit their data on the website that I create).

Thank you so much for what looks like a beautiful solution!


Standard image metadata does not include provisions for most of the fields you mention, but using this tool, you can relabel random other fields for your own needs while within Lightroom. Outside applications won’t understand that you’ve relabeled those fields, but you can probably use something like Tim Armes’ LR/Transporter Export Plugin to do a lot of the subsequent output processing you mention. —Jeffrey

— comment by Jay Levan on January 17th, 2008 at 10:23pm JST (11 years, 6 months ago) comment permalink

Is there a way to increase the font size in the metadata panel? I tried increasing it using Edit > Preferences > Interface tab > Panel Font Size > Large, but the font size is still too small for me to read comfortably.

Windows Vista, Lightroom 1.3.1

— comment by Willie on January 19th, 2008 at 9:44am JST (11 years, 6 months ago) comment permalink

I noticed a Metadata Viewer update to 0.29, is there a changelog available somewhere or would it be possible to include one with the possible future updates?

— comment by Age Bosma on January 21st, 2008 at 8:18pm JST (11 years, 6 months ago) comment permalink

Hi Jeffrey
I have been trying to download your Metadata Viewer Preset Builder for days , and I am very frustrated , since I keep having this Lua_pcall(L,2,1,0)==0 errror.
Your Preset Builder is exactly what I want, it’s fantastic, all the info I need in one glance.

I have tried many tricks like download as text and rename as lrtemplate, remove what I think are comments, reduce the panel to one separator, always this Lua error

What an I doing wrong , as if some rare persons signal it , many can use your work without problems

I work with LR1.3.1 , Vista v6 , and in FRENCH,
Thinking French was my damnation, I switched to an English version of LR and got the LUA story again.

May be someone has the answer

Thank you for answering me

— comment by Herve on January 23rd, 2008 at 7:29am JST (11 years, 6 months ago) comment permalink

Hello Jeffrey (and all others)
I am thinking of on feature in the metadata
It seems that for the moment I can only sort by lens, not by range of focal for a given lens (zoom of course) , say 17 to 28 for the 17/85 Canon EFS-IS, then 29-50, then 51-85 for example .
My goal is to automatize imports (or at least select and batch process)with some minimal corrections such as vignetting , and purple fringe (which depends on focal length and aperture), waiting for LR to have a distortion correction.
One could have presets for each lens by range of focal length and aperture which would correct these defaults, and may be automatize the process (as in DXO)

— comment by Herve on January 23rd, 2008 at 7:49am JST (11 years, 6 months ago) comment permalink

I found that using your Configuration Manager, I was able to increase the font size in the metadata panel.

LR does not currently show a JPG or TIF file’s bit depth or embedded color space. Is there a way for you to enable viewing of those two items?

No, sadly, those are not exposed to the metadata panel. —Jeffrey

— comment by Willie on January 23rd, 2008 at 1:09pm JST (11 years, 6 months ago) comment permalink

Hi Jeffrey,
Thank you for all this thourough info so far!!
I was wondering if there is any way to export medadata from LR (without the images) into a simple text file (csv, etc.).

I think Tim Armes’ LrTransporter plugin will do the trick

Or inversely, how to import existing image metadata into LR, matching unique image file names and fields, and populate the fields automatically. For example, I have 1’000 images in LR, and metadata in an ACCESS database – it would be nice to transfer in batch this info 😉
Any ideas?

This is not currently possible with the plugin infrastructure, but you may be able to build .xmp sidecar files and load them into Lightroom that way. It’s not necessarily straightforward and perhaps not even possible. I’m not sure; I’ve never done this.

Hopefully, some future version of the plugin API will allow for this. —Jeffrey

— comment by Mario on February 6th, 2008 at 1:40am JST (11 years, 5 months ago) comment permalink

I really like the tool. I was wondering is there any way to display extra exif tables which are normally not shown by light room.
For example on my E-3 there are focus points used, if the camera focused or not, etc. How would it be possible to include these?

Sorry, it can’t be done. The entire universe of what’s available – at least as much as I could figure out – is shown in the tool. —Jeffrey

— comment by tony spore on February 11th, 2008 at 5:13am JST (11 years, 5 months ago) comment permalink

Hi, this is a very useful tool. I made my own metadata display but discovered that the — to ,e vital — information: the focal length in 35mm equivalent ist not showing, even though there is an option for it and the tag (FocalLengthIn35mmFormat) is in the image (as shown e.g. by Phil Harvey’s tool). Is there a workaround to display this tag?
Thanxx, Mixx

There’s no workaround that I know of, but your posts reminds me that I should submit the couple bugs I discovered, such as this one, to Adobe so they’ll get fixed in 2.0! Had I done this before, perhaps they would have been fixed by 1.3 or 1.4. Sorry. —Jeffrey

— comment by Peter Mischer on April 14th, 2008 at 5:15am JST (11 years, 3 months ago) comment permalink

Hi, Jeffery. Am I missing something or does Lightroom not have a collapse all facility for the keywords tags. It’s driving me mad trying to use and manage a large keyword hierarchy in that left hand Keyword Tags panel. I have to manually collapse each hierarchical keyword to make space to scroll down the list. I’ve searched everywhere and tried various Ctrl/Shift etc. options while clicking the triangles – to no avail. A keyboard shortcut to collapse all of them would be a time and frustration saver.

Hope you can shed some light. Thanks.

I dunno, sorry. I don’t really use keywords. Perhaps try the Lightroom forums? —Jeffrey

— comment by Rob Smith on May 28th, 2008 at 9:37am JST (11 years, 2 months ago) comment permalink

Hi Jeffrey

Great tool!

This looked exactly what I needed to add GPS co-ords to my photos in the Metadata fields without buying additional hardware/plugins. I have GPS co-ords of sites visited from the car sat nav so why do I need all this other stuff?

I added a new GPS Preset ato the metadata files and it is coming up on the listing. But the additional fields added as per


are not visible.

Can’t see these fields in the V2 Beta for lightroom either… Sometimes it’s easier to add manually rather than the hit or miss using Google over bushland!

Help please!

Sadly, those fields are not editable within Lightroom, so they only show up when the data is already associated with the photo. Currently, Lightroom offers no way to geoencode photos with Lightroom, but I’m working on something that might allow it for when 2.0 is released. Until then, the best I can suggest is a hybrid approach like this. —Jeffrey

— comment by Vicki on June 3rd, 2008 at 9:11pm JST (11 years, 1 month ago) comment permalink

Hi Jeffrey, I stumbled upon your site and blog while googling about Lightroom export presets. Great site and photos (especially love the wet bird incidents). Thanks for allowing everyone access to these great tools.

– Mark

— comment by Mark Stanczak on August 8th, 2008 at 3:18am JST (10 years, 11 months ago) comment permalink

Great tool!
Are there any additional features planned for Lightroom 2.0 or works it just the same way as before?

It all still works fine for 2.0, although there are new things that I should add if I ever find the time. —Jeffrey

— comment by Matthias on September 8th, 2008 at 9:20pm JST (10 years, 10 months ago) comment permalink

If you ever find the time to update this fantastic tool, please consider adding the plug-in metadata fields created by your export plug-ins.

— comment by David on September 10th, 2008 at 1:58am JST (10 years, 10 months ago) comment permalink

I was just trying to use this excellent tool to update my preset because I want to be able to directly edit the Flickr tags for my photos that have been uploaded using your Flickr Uploader, but I see that that particular tag is not available. Can it be added??

— comment by Sean Phillips on October 4th, 2008 at 10:26pm JST (10 years, 9 months ago) comment permalink


Is there a way to add custom EXIF fields? I need to see the FRAME NUMBER EXIF FIELD but cant seem to find it…

I have tried the following unsuccessfully:


I found this field via Photo Mechanic… and in EXIF I believe it is field number:
0x9211 ImageNumber

Thank you

— comment by Manny Gonzalez on November 23rd, 2008 at 5:15am JST (10 years, 8 months ago) comment permalink

Super tool, thank you very much, but in my (german) Lightroom 2.1, the GPS field won’t show up in the list, regardless if there are GPS data in the photo or not. Might this be a problem of the localization? The external function to call Google Earth e.g. to show the spot is ok.

— comment by Jochen on November 25th, 2008 at 2:13am JST (10 years, 8 months ago) comment permalink

Hi – I was just directed to this site via Lightroomforums user – but does this preset builder work with LR 2.2? I’m looking for a way to see the original filename in my metadata – something that was there until I upgraded to 2.2. The filename is still in there, but not viewable. They suggested your preset builder would solve the problem. Thanks

— comment by Brenda Tharp on December 13th, 2008 at 2:27pm JST (10 years, 7 months ago) comment permalink

duh – I should have seen the comments above and would have the answer! Sorry about that. I just went to end of page quickly and didn’t see all of the postings.

— comment by Brenda Tharp on December 13th, 2008 at 2:31pm JST (10 years, 7 months ago) comment permalink

Thanks Jeff. I made a video tutorial on how to set this all up with additional metadata workflows. I appreciate you taking the time to make this preset. Has saved me so much time 🙂

— comment by Tyler Ginter on December 22nd, 2008 at 10:54pm JST (10 years, 7 months ago) comment permalink

Hi Jeffrey.
Firstly, many thanks for creating this!

Secondly, I would be willing to pay for a simple, stand alone app for customising lightroom.
That lets you save and open templates etc…

Just an idea.

— comment by Richard on January 22nd, 2009 at 10:41pm JST (10 years, 6 months ago) comment permalink

As a big fan of your other work for LR I use export to Facebook/Picasa and your GPS-plugins.
Q. Is there any way to add them to my custom metadata preset?

Great work btw

Stan, Herve and everyone else: I got the same error message first (Lua_pcall(L,2,1,0)==0 errror.) Because I did NOT read the instructions. It says to put the file in the …Lightroom\Metadata Field Lists\ folder. ‘should be created if it doesn’t already exist’

You can add them via info.regex.lightroom.export.facebook2.uploaded and info.regex.lightroom.gps.* (the individual items being Location, Altitude, Speed, Bearing, and Geoencoded). Note, though, that I’ll soon be releasing a new plugin that will allow you to manage all this from within Lightroom. —Jeffrey

— comment by Bo on March 21st, 2009 at 11:53am JST (10 years, 4 months ago) comment permalink

Hi Jeffrey, I’m wondering if this is an appropriate tool to add camera data to scanned (film) files. I’d like to add camera make, ISO etc to the files, which is not an option with LR, as far as I can tell. Thanks. Paul

This is almost impossible to do with a plugin, if not impossible. There are some metadata items that Lightroom reads during import and only during import (they are ignored even when refreshing metadata from the file). So any reasonable solution has to stuff the data into the file or sidecar before import, where a plugin doesn’t really have much access. Some kludgy tools may be hiding for a clever developer to build, but it would be a lot of work (the plugin would have to recreate the whole import dialog) for an unsatisfying result. Better to use exiftool or the like to stuff the data in ahead of time. —Jeffrey

— comment by Paul on March 24th, 2011 at 11:47pm JST (8 years, 4 months ago) comment permalink

Ugh. I’ll just put them in the keywords. Thanks for the help. Paul

— comment by Paul on March 25th, 2011 at 12:02am JST (8 years, 4 months ago) comment permalink

Hello Jeffrey,

I just came upon your great work! Excellent.

Do you have any idea if it is possible to automate and convert crop factors to FF format so that you can read the 35mm equiv of what you have shot with a cropped sensor?

Not exactly, but you can get a good sense, in terms of 35mm-equiv focal length, of what you shoot with both my data-plot plugin and my focal-length-sort plugin. —Jeffrey

— comment by Coen on September 5th, 2011 at 7:38am JST (7 years, 10 months ago) comment permalink
Leave a comment...

All comments are invisible to others until Jeffrey approves them.

Please mention what part of the world you're writing from, if you don't mind. It's always interesting to see where people are visiting from.

You can use basic HTML; be sure to close tags properly.

Subscribe without commenting