.
Jeffrey’s “Metadata-Viewer Preset Editor” Lightroom Plugin

This plugin allows you to create and edit tagset presets for Lightroom's metadata viewer. That is, it allows you to pick and choose which metadata items Lightroom should show for each photo, and in what order they should be shown.

To be clear: this plugin does not allow you to edit photo metadata itself.
It merely allows you to configure the list of items that Lightroom displays.

This plugin works in Lightroom 5 (and older versions as far back as Lightroom 2, though some features depend on the version of Lightroom).

The same download works for both Windows and Mac. See the box to the upper right for the download link (in orange) and installation instructions.

This plugin is an in-Lightroom version of the web-based preset editor that I published a couple of years ago. That application continues to work, but this plugin should prove to be more convenient. Also, this plugin incorporates the ability to include the custom metadata from other Lightroom plugins in your presets, a feature that I have not gotten around to update the online tool with.

This plugin is currently in beta release, without much documentation.

Mini Instructions

After installing it, you'll see a “Configure Metadata-View Presets” button in the Plugin Manager itself. Clicking on it will bring up the preset-edit dialog. Please see the “help” link in its upper-right corner.

Availability

I distribute this plugin as “donationware”. I provide it for free and it is mostly functional for the first six weeks. Until registered, it can not create “static custom presets”, nor import/export presets.

After the six-week trial period expires, custom presets remain usable, but with an ugly “unregistered” heading inserted at the top.

If registered, the “unregistered” heading goes away, of course, and also, the plugin gets the ability to create “static custom presets” that remain even if the plugin is removed, and it also gains the ability to import and export presets (so that you can move them from one computer to another, for example, or share with friends).

Registration is simple and costs the minimum 1 cent PayPal fee; any additional donation you'd like to make in encouragement or thanks is up to you. For details, see my blog post titled Lightroom Plugin Development: Now With Added Encouragement.

Version History
( Update Log via RSS )

20140902.74 New build system
20140731.73 Registration fix for Lr5.6
20140729.72 Previous updates broke support on Lightroom 2
20140720.71 More Creative-Cloud support.
20140715.70

Fixed an issue with Creative-Cloud revalidation.

20140712.69

Lr5.5 and later Creative-Cloud installs can now revalidate themselves if needed.

20140710.68 Sigh, had a bug in the Creative-Cloud support.
20140708.67

Now supports Lr5.5+ Creative-Cloud Installs.

20140704.66 Sigh, introduced an error for some folks with the rebuild the other day.
20140630.65 Build-system update
20140422.64

Fixed a bug in the "smoother revalidation" stuff recently added.

20140418.63

Added a second form of the color-label item. Adobe seems to support two forms, one which is readonly but you can set a custom label, and one that you can edit but you can't set a custom label (and for whatever reason the standard label is included in the value column, so it looks oddly indented).

Make the revalidation process smoother, especially for folks using Lr5.4 and later.

Fixed some Windows dialog-layout bugs.

20131210.62 It seems the save-to-static-preset function had stopped working.
20131023.61 Fixed a bug that stopped the "Label" (color-label label) text from being changed.
20131010.60

Added new "Direction" field (direction of view) that seems to have appeared circa Lr5.

The "Supplier Image ID" entry was broken... would never actually be included in the preset.

20130908.59 Update default text for "Person Shown" to "Person Shown in Image" to match Lightroom
20130613.58 Better support for plugin revalidation.
20130611.57 Yet another Lr5 update
20130524.56 Apparently, a recent change broke things on Lr2, which some folks apparently still use.
20130501.55 Update for Lr5
20130412.54 Build system update.
20130328.53 Fix for the registration system.
20130209.52 More build-system maintenance
20130206.51 Tweak for my registration system
20130122.49

Note: you must restart Lightroom after installing this update.

Added support for my Creative Commons plugin.

Added support for Video and DNG metadata in Lr4.

Added a bunch of other new metadata fields I noticed in Lr4.

Updated the plugin's idea of Lightroom's builtin presets to match Lr4.

20120617.48 Add the ability to include custom metadata from any local plugin.
20120608.47 Fix an "attempt to perform arithmetic on field" error.
20120526.46

Update to handle the Mac App Store version of Lightroom.

Tweak for Lr4.1RC2.

Enhanced the send-log dialog to hopefully make reports more meaningful to me, yielding, I hope, the ability to respond more sensibly to more reports.

20120330.45 Update to handle 4.1RC
20120309.44 Had broken registrations in Lr2; Update to the debug logging to better track down timing issues that might arise.
20120304.43

More updates for Lr4.

20120221.42

More updates for Lr4.

20120207.41

More on the march toward Lr4, including upheaval in the code to handle Lightroom APIs being discontinued in Lr4.

Added data for a bunch of plugins.

Added some extra bulletproofing when reading preset files.

20120127.40

There's a bug in Lightroom that causes the whole plugin to fail for some users. This failure happens when the "build a preset" dialog tries to pull up example image data saved by other plugins (e.g. an export plugin's "Uploaded to..." flag).

This is just for the display of example image metadata while building a preset, and it'd be nice to show actual data, but not at the expense of crashing, so I've disabled it. The resulting preset, when used with Lightroom, of course does show all the data as appropriate to the preset you've built.... this bug is only related to how example metadata is shown in the builder dialog.

Also, removed registration-related restrictions from the Lr4 beta, since you can't register in a beta.

20120114.39 More tweaks for Lr4b
20120112.38

Update for Lr4 beta: explain in the plugin manager that the plugin can't be registered in the beta.

20111210.37

When doing a plugin upgrade, offer the ability to flush all the old copies of the plugin.

Had issues with the registration button sometimes not showing.

Added a system-clock check and reports to the user if the system clock is more than a minute out of date. An incorrect system clock can cause problems with various kinds of communication and authentication with some of my plugins, so I've just gone ahead and added this to every plugin.

20110910.36 Work around a bug that caused the plugin to crash in the Lr3.5 beta.
20110207.35 Was dorked in Lr2... now fixed.
20110110.34

More debugging to try to crack this tough dialog-won't-open bug. The best I can figure at this point is that it's a bug in Lightroom.

One workaround that just came to mind: before invoking the plugin manager, make sure that no photos are selected (e.g. that when in Loupe, "no photo selected" is shown, via control-D or command-D). That should, in theory, bypass the area of the dialog-creation code that's running into the bug. I can't reproduce the bug myself, so I can't test this workaround myself.

20110107.33 More debugging to try to crack this tough dialog-won't-open bug.
20101219.32 Added support for new IPTC in Lr3. Updated display for recent versions of my megapixel-sort plugin. Added yet more debugging to try to track down a missing-dialog problem some have been seeing.
20101209.30 Fixed an "ISO ISO" typo. Added a bunch of debug logging to try to track down a missing-dialog problem some have been seeing.
20100829.29 Made the revalidation process much simpler, doing away with the silly need for a revalidation file.
20100820.28 Discovered a bug in my plugin build system that caused horribly difficult-to-track-down errors in one plugin, so am pushing out rebuilt versions of all plugins just in case.
20100712.27

Added support for my focal-length sort plugin.

20100625.26 Yikes, shaking out some more build issues.
20100624.25 Discovered a nasty build bug; pushing a new version in case it affects this plugin.
20100609.24

This version can be registered in Lightroom 3. It can run in Lightroom 2 or Lightroom 3; it does not work in the Lr3 betas.

It uses my new registration system when run on Lightroom 3, which avoids some of the silly issues of the old one. Please take care to note the details on the registration page: use of this version (or later) of the plugin in Lightroom 3 requires a new registration code, even if you had registered some older version of the plugin.

20100525.23 Turns out that "Metadata Date" is not available to the Lr3 beta, so the plugin wasn't working there. Made it always empty in the Lr3 beta preset-building screen.
20100520.22 Fixed the data used for the "Metadata Date" sample data in the preset-building dialog... I'd been showing the last-edit date by mistake.
20100516.21 Update for the Lr3 beta.
20100315.20

Completely changed how the one-click upgrade applies the newly-downloaded zip file, in the hopes that it'll work for more people. Rather than unzipping over the old copy, it now unzips to a temporary folder, then moves the old folder out of the way and the new folder into place. Prior versions' folders are now maintained (with the version number in the folder) in case you want to revert a version; you may want to clear them out from time to time. Of course, it won't take affect until you try to upgrade after having upgraded to or beyond this version.

20091205.19 Minor internal debugging tweaks.
20091027.18 Minor UI tidyup for OSX.
20091027.17 More LR3b fixes... actually seems to work now.
20091022.16 Added a first draft of some rudimentary support for Lightroom 3 Beta. See this important note about plugin support in Lightroom 3 Beta and Lightroom 3, including future plans for features and my registration system.
20090714.15

Enhanced the one-click upgrade stuff quite a bit, now detecting ahead of time when it will fail because the plugin is installed where Lightroom can't write (if Lightroom can't write to it, it can't update itself). I also added a progress bar, and now download in smaller chunks to avoid 'out of memory' errors on the larger plugins. Do remember that this new functionality becomes available after you upgrade to or past this version, when you then upgrade with it.

20090626.14 Added another new Video-Asset Management plugin field.
20090624.13 Added fields in support of my new Video-Asset Management plugin.
20090617.12 Added the new upload date/time fields for my other upload plugins (Zenfolio/SmugMug/Facebook/PicasaWeb).
20090603.11 Added support for the new "Flickr Upload Date" and "Upload Time" fields that I just added to my Flickr plugin.
20090601.10 Seems some Mac users were still losing presets each time... thought I tamed that bug, but indeed found another bug and fixed it. Hope this is the last one.
20090521.9 Fixed a "loadstring" error some users got.
20090511.8

This update affects Mac users only

It seems that many (all?) Mac users had problems with Lightroom forgetting presets each time it restarted. I've discovered a bug in Lightroom that I think I've been able to work around in this version, but the change is not backward compatible, so Mac users who were actually able to make Custom User Presets will lose them upon upgrade. Sorry. This happens only when upgrading from before this version to this version or after, and subsequent upgrades should be lossfree. (Static User Presets, and all presets on Windows, are unaffected and should carry through unharmed.)

20090510.7 Added a link in the Plugin Manager to the plugin's update-log RSS feed.
20090428.6 Added custom metadata from my Megapixel Sort plugin.
20090426.5 Added a bunch of debugging stuff to try to track down why presets are not saved for a few users.
20090425.4 Oops, the one-button upgrade stuff didn't work due to a typo on my part, sorry. Upgrading to this version will still need to be manual, but upgrading from this version to whatever's next will hopefully work.
20090423.3 Fixed "ID_PREFIX" bug that popped up when converting a custom prefix to static.
20090420.2

Wow, this plugin continues to be one of the most complex I've ever worked on. Tons of new stuff this time, including...

  • Now donationware.
  • Lots of UI cleanup.
  • Added "label" and "separator" links at the bottom, so that you can easily add labels and separator lines without scrolling to those entries at the bottom of the right-side master list.
  • Added a "show photo data from" toggle in the bottom-right corner, allowing you to toggle between photo data from the image selected when you invoked the dialog, or fully-filled-out fake sample data. (If no images are selected when you invoke the dialog, you get only the fake sample data.)
  • If you click on the active line in the left-side preset preview, the associated item in the right-side master list is scrolled into view and highlighted.
  • Some have been confused by how a new preset's title is entered, so I've added a bunch of visual hints (big flashing "EDIT HERE!!!" signs :-) ) until I can figure a more intuitive interface.
  • The "Blank Slate" built-in preset didn't really work. Does now, and has been renamed to "Empty (No Items)"
  • Added the ability to edit/save/create static user presets, and to import/export presets. I've left these as candy for when the plugin is registered.
  • Added a help page describing the different types of presets the plugin works with (Lightroom default, Plugin default, User custom, and Static user custom).
  • Added the "map" metadata item from my geoencoding plugin
  • Lots more I can't remember.

One of the big todos is to add the ability to set attributes to items, such as the the number of lines of a caption.

20090330.1

Initial public beta release.

The UI for this plugin has been by far the most difficult to do, and that's mostly what this plugin is about: a snazzy interface for editing a simple preset file. Lightroom's plugin infrastructure is still in its infancy and understandably Adobe has not yet filled out every feature required to make a rich, interactive presentation. Taking it almost as a personal challenge, I've expended enormous effort to try to work around some of the limitations. This is the best I can do for now.

At this first-beta-release stage, I'd appreciate comments via email, so I've turned off comment-submission for this post.

Because this is an early beta that I don't want to hang around very long, the plugin expires after a month. It'll certainly be updated well before then.


Comments so far....

Hi Jeffrey,

I really like your plugins! I’ve registered 3 just now. I was wondering if it was possible to get your Metadata Preset Editor plugin to “work” with Mr. Rob Cole’s “Custom Metadata plugin”. I can get your plugin to “see” his, but I can’t edit which one(s) I want to show up in LR3′s panel. Or maybe I’m just doing it wrong? Advice please.

Sincerely,

Ray

I’m not familiar with that plugin, but I have instructions on my plugin page for developers of other plugins wishing to have their other plugins supported by the metadata-viewer preset, so have him contact me with the requisite info. (update: I’ve heard from him.) About a “custom metadata” plugin, I’d be curious to see how he did it. I developed a spectacularly useful custom-metadata plugin in the spring of 2009, but at the end realized a fatal flaw that prohibited it from being used with multiple catalogs, and with prospect of catalog corruption too great, I shelved it. Adobe almost got the fixes into Lr3, but not quite, so it remains on the shelf. )-: —Jeffrey

— comment by Ray on July 5th, 2010 at 2:02am JST (4 years, 3 months ago) comment permalink

Hi Jeffrey,

Thanks for the quick reply. I have already contact Rob Cole, the writer of the plugin and following your note in your plugin he has emailed you the info you’ve requested (I got the cc from him). Hope everything works out for all of us. Thanks again for the awesome plugins.

Ray

— comment by Ray on July 5th, 2010 at 3:09pm JST (4 years, 3 months ago) comment permalink

Hi Jeffrey

Thank you for this update. I used the earlier version with LR2 and I’ve just go around to finding out how to do it in LR3.

I love the “everything is done via this button” button! It saves a lot of time :-)

In the UK

Patrick Cunningham

— comment by Patrick Cunningham on July 21st, 2010 at 8:47pm JST (4 years, 2 months ago) comment permalink

Jeffrey

Could you add Paul Kamphuis’s Lightroom uploader Plugin?

Thanks

Patrick

There are instructions there for plugin authors wishing their plugins to be represented here…. ask Paul to send me what I need to include his stuff here. —Jeffrey

— comment by Patrick Cunningham on July 21st, 2010 at 8:59pm JST (4 years, 2 months ago) comment permalink

I’ve just got to say this: I’m working right now with your LR Flickr plug-in and have just downloaded this as well. You deserve every penny you get and more! My husband and I would not know what to do without your plugins, and instead of asking you any questions, I’m just saying: THANK YOU BIG BIG! We will be making payment by tomorrow for the plugins we are using and I encourage others to think about giving you a little bit more than they originally thought they would, thinking about the added value these plugins give their lives and routines. Where would they be without them…? Assign a value to that!!!

— comment by Lisadawn Schram on July 29th, 2010 at 1:16am JST (4 years, 2 months ago) comment permalink

Hi Jeffrey,

I tryed your plug in and I find ir really great.
I would be happy to see the “modified date” in the metadata viewer and it seems currently impossible. Modifed date is seen from lightroom as it is possible to rank order “time of change” but i never find a way to see it without having to open explorer.

May be a suggestion for next update of the plug in would be to see “modified date” or modified date and time” in metadata field ?

best regards,

Thibaud
from France

— comment by Rebour on August 15th, 2010 at 2:23am JST (4 years, 1 month ago) comment permalink

Hi Jeffrey,

I have a problem with Nikon AF-S VR Micro-Nikkor 105mm f2.8G IF-ED and D90.
At reproduction ratio 1:1, Nikon manual says 314 mm and the pluggin displays 349,99 mm.

best regards,

Jean-Luc from France.

The plugin just reports the metadata, which originates in the lens/camera. It’s not at all exact… I would guess that if you put the camera on rapid fire and slowly change the focus from one extreme to the other, and then inspect the subject-distance metadata for all the photos, you’ll find that there is a small set of lengths … maybe a dozen.. that everything is reported at. The same goes for a zoom and the focal lengths. Give it a try and report back with your findings…. —Jeffrey

— comment by JLD95 on November 28th, 2010 at 5:59pm JST (3 years, 10 months ago) comment permalink

Can I create custom metadata fields with this plug-in?

I added a field labeled “label” and then changed the label to be “My label” but that didn’t carry over into Light Room. It was labeled “label” in Light Room.

Thanks for any info. I’m trying to add custom metadata fields.

Drew,
Upland, CA

No, sorry. I don’t understand what “added a field” means, but this plugin lets you strip selected metadata, not add any. BTW, the Adobe product is “Lightroom”, not “Light Room”. —Jeffrey

— comment by Drew on February 23rd, 2011 at 4:26am JST (3 years, 7 months ago) comment permalink

I just registered MetaData Preset Builder and Metadata Data Viewer. My primary goal was to be able to see Flash settings both on and off Camera. I was pleased to find this information in the Data Viewer, but their is so much information there I was hoping by registering Preset Builder I could build a customized preset that contained this as well as other EXIF data already in LightRoom 3. I’m probably missing something but all I see when I select All Possible items or any other starting point are those settings already in Lightroom, not the additional Flash related ones I find in Data Viewer. I don’t think Preset Builder is much help to me if it doesn’t include Data Viewer elements. My only reason for adding it was to simplify workflow. It takes Data Viewer a few seconds to load for each photo, my goal is to compare two photos in Lightroom Survey mode and click back and forth the see the camera settings.

Hope that makes sense, can you tell me what I’m missing?

You’re not missing anything… what you want to do makes total sense… except that (for whatever reason) Lightroom doesn’t allow it. The preset builder works within the confines of what data Lightroom has made available to plugins in the metadata panel, while the Data Viewer jumps out of Lightroom to use ExifTool to grab all the data from an image, then sends it back to the dialog for presentation. As you’ve noted, it’s a slow round trip. Why doesn’t Adobe make all the data available to the plugin? I don’t know, but I suppose like everything else it’s part of the ongoing tug of war between resources (or lack thereof) like time/money/engineers and the never-ending tsunami of feature requests. —Jeffrey

— comment by Glenn on April 17th, 2011 at 4:27am JST (3 years, 5 months ago) comment permalink

Hi Jeffery,

I apologize if this has been addressed already, this is in regards to the Original File Name. In your wonderful plugin, I can see the original file name, but is there anyway to embed that into the metadata when you export the file? Is there another plugin of yours that will do this?

In my photo library system I have, I rename all the files, but would like to keep the original file name in the metadata in case I need to go back to the original RAW file.

Thank you!

-Stephanie
Houston, TX

Nothing easy comes to mind, mostly because it sounds like you’re using Lightroom in a nonstandard way. Normally, the only files in your library *are* the original raw files, but it sounds like you’re exporting versions of the raw files, then reimporting those derivatives. You need to do this for copies that you’ve edited externally (e.g. in Photoshop), but otherwise one generally works with their raw files directly. The best I can suggest is that you use exiftool to copy the original filename into a metadata field that Lightroom does handle natively (e.g. caption, job id, …) and then “metadata > read from file”. (But be sure to do a “metadata > save to file” before, so that when you read back in later, you’re getting all the changes you’d already made in Lightroom along with the new original name copied to the new field.) —Jeffrey

— comment by Stephanie on August 17th, 2011 at 1:48am JST (3 years, 1 month ago) comment permalink

I think I have a pretty good idea of what this does, but would love to see the ability to analyze my development pre-sets and have them tell me the difference between the two or taking an original and a virtual copy and telling the differences or what was adjusted.

This plugin is unrelated to develop presets. —Jeffrey

— comment by Christopher Souser on September 2nd, 2011 at 2:19pm JST (3 years ago) comment permalink

Could I suggest a little, helpful enhancement ?
I find it would be great to have an “EV” parameter – exposure value (computed from exposure time and aperture, adjusted for ISO sensitivity as well), the same as in your Data Plot plugin.
It would greatly improve understanding on situations where light conditions are the same, but I change exposure parameters (or auto program does that for me) and want to know when camera build light meter has failed.
Thank you for great job!

Sadly, Lightroom doesn’t offer that as a bit of data that can be displayed, so in the Metadata Panel we’re out of luck for this idea. —Jeffrey

— comment by Rafal Magda on September 17th, 2011 at 5:52pm JST (3 years ago) comment permalink

I use your other plugins and they’re great. I’m evaluating this one but I have a question. The concept is great, but the number of fields I have to choose from (seemingly) are very limited. Does this change once I register it or am I missing something now? The ones I’m seeing are very basic but I see no scroll bars or another way to see others. I’m near Atlanta, GA by the way :)

Thanks,

John

There should be a scrollbar to the left of the list (more or less in the middle of the dialog). The list has 150 or so entries, and is limited by what Lightroom supports. —Jeffrey

— comment by John Cothron on October 19th, 2011 at 12:14pm JST (2 years, 11 months ago) comment permalink

Hi Jeffrey

I find your plugins extremely helpful.

I have a question re the Metadata Preset Builder. Will this plug-in (or another of yours) allow me to change the default choices within a field. Specifically, in the Copyright Status field, I am trying to add choices to the 3 default choices; is this possible?

Thanks in advance.

– Luis

Sadly, Lightroom doesn’t allow for that, sorry. —Jeffrey

— comment by Luis Mederos on December 31st, 2011 at 7:42am JST (2 years, 9 months ago) comment permalink

Jeffrey, is it possible to force LR to load a metadata list (created with this plug-in) other than “Lightroom – Default” on startup? I can not see an obvious way in LR3, how about LR4?

Thanks, Richard, (Victoria, BC)

Whatever list you choose should be remembered across invocations of Lightroom, though I recall a bug early in Lr4 that caused it to reset to “default”, that shouldn’t impact your use with Lr3. It could be because your Lightroom preferences file has gone corrupt… when that happens, random settings start reverting to defaults. —Jeffrey

— comment by Richard on May 29th, 2012 at 12:47pm JST (2 years, 4 months ago) comment permalink

Jeffrey’s latest version supports metadata from all my plugins so far, including ExifMeta (and CustomMetadata). – thanks Jeffrey!

— comment by Rob Cole on June 17th, 2012 at 8:54pm JST (2 years, 3 months ago) comment permalink

Hi Jeffrey,
Just upgraded my LR 4.1 to 4.2. Plugin is also active, but it seems my custom presets are lost. Should these be automatically converted/upgraded, or can I move them over from an older version ??

Johan

I would have thought they’d not be affected by the upgrade, but if they seem to have been, yes, just move them over yourself…. —Jeffrey

— comment by johan on October 3rd, 2012 at 8:03pm JST (2 years ago) comment permalink

Next time around for this plugin to be updated, could you add Lightroom’s video fields? (duration, Frame Rate, Audio Rate, etc). I see that it supports your Video Asset Management plugin (which I had but later removed once LR3 came out) but there doesn’t seem to be any access to the native fields.

This plugin did indeed need some love… I’ve now updated a bunch of things for Lr4. —Jeffrey

— comment by JasonP on January 21st, 2013 at 10:39pm JST (1 year, 8 months ago) comment permalink

Hi Again Jeffrey.

Lightroom 4.3, Windows 7 64 bit, Metadata-Viewer Preset Editor 20130209.52

I’m continuing to refine my custom metadata panel with your plugin and I’ve come across a small problem. In the list of available metadata fields in your plugin there’s one called “Image GUID” in the IPTC Extensions section. I can select that field and include it in my preset in the plugin, but when I reload the plugin and select my preset Lightroom does not display the Image GUID field. I’ve tried moving the field up and down but whereever I place it Lightroom does not display it. It also doesn’t appear in the “All Possible Items” built in preset when that is selcted in Lightroom either.

Hope it’s a problem you are able to fix within the plugin.

All the best

Roger

For reasons I’m not privy to, that field is read-only within Lightroom, so it’ll show up only for images that already have it. You have to add it outside of Lightroom before import, or before syncing metadata from the file into Lightroom. If the image doesn’t already have it, the row does not appear. —Jeffrey

— comment by Roger Byrne on February 20th, 2013 at 2:42am JST (1 year, 7 months ago) comment permalink

>> For reasons I’m not privy to, that field is read-only within Lightroom, so it’ll
>> show up only for images that already have it. You have to add it outside of
>> Lightroom before import, or before syncing metadata from the file into
>> Lightroom. If the image doesn’t already have it, the row does not appear. —Jeffrey

Thanks for the explanation Jeffrey, your reply motivated me to “get down and dirty” with exiftool and I’ve successfully add a GUID value to a canon RAW file and it does indeed show up in Lightroom after import.

Now I just have to decide if modifying original raw files is something I actually want to do :-)

Thanks again – Roger

Yeah, it sucks that it’s this way… it makes no sense to me. I also modify my raw files before import, to set the lens data for shots taken with a non-CPU lens. Just silly that they go out of their way to make these fields readonly. It took about five years, but I was happy to at least find writable geolocation fields in Lr4. —Jeffrey

— comment by Roger Byrne on February 21st, 2013 at 7:50pm JST (1 year, 7 months ago) comment permalink

Hi. I have used your plugins for several years, but now my Windows has failed, and I am manually transfering all my data to a new computer. Is there a way to find my presets on the old computers hard drive? It is not possible to start Lightroom on the old computer…

I am very pleased with your plugins, and if you have a solution for me on this problem I will definitely re-register with a noticeable donation :-)

Look at the docs for the Lr/Backup plugin for places where Lightroom stores stuff. (I highly recommend this plugin to help with exactly these kinds of situations.) Many plugin settings are stored in your Lightroom Preferences file. —Jeffrey

— comment by Frode Evensen on March 29th, 2013 at 8:43am JST (1 year, 6 months ago) comment permalink

I have created a “static” preset using your plug-in but can’t figure out where to put it! Spent a long time Googling for answers and am completely stymied. I need to know for both Mac and PC –

Thanks!

The plugin should install it for you when you ask, but FIWI, on OSX the location is in your user-local Library/Application Support/Adobe/Lightroom/Metadata Field Lists/” folder. On Windows, it’s along the lines of C:\Users\username\AppData\Roaming\Adobe\Lightroom\Metadata Field Lists\”. You’ll need to create this folder if it’s not already there. —Jeffrey

— comment by tom on May 25th, 2013 at 2:05am JST (1 year, 4 months ago) comment permalink

Hi there!
Currently testing the metadata plugin.
All working well, I have made a preset based from Large caption.

I was wondering if you could tell me where my newly created preset lives on disk so I can quickly (assuming it is possible) go in and alter the preference designating the size of the box which I am after reducing slightly.

Thanks!
Richard.

If you’ve saved it as a static preset, it’s in the folder named in the comment just prior to this one (which wasn’t yet visible when you posted your comment, in case you’re wondering how you missed it :-) ). —Jeffrey

— comment by Richard Costin on July 31st, 2013 at 11:57pm JST (1 year, 2 months ago) comment permalink

Hi, I try to find the spot to copy a saved irtemplate preset for use on another PC. C:\Users\BK\AppData\Roaming\Adobe\Lightroom\Metadata Presets seem not be it.

So where to go to – Bernd

It’s there only if you’ve saved it as a static preset. Otherwise, it’s only within the running plugin. —Jeffrey

— comment by Bernd on August 10th, 2013 at 3:51pm JST (1 year, 1 month ago) comment permalink

Hi Jeffrey,

Just a heads-up about two small bugs in Preset Builder 20130613.58: The IPTC Extensions field “Person Shown” shows up in my preset as “Person Shown in image” and “Location” in the IPTC Image Description turns out as “Sublocation”.

Really small issues indeed but I thought you may want to know, if you don’t already do.

Keep up the great work!

Daniel, a German in Singapore

This is “as designed” according to Adobe. Unless you manually change a label in the preset builder, the preset merely references a field by an internal code and leaves it up to Lightroom to call it whatever it calls it (which may change from version to version, and certainly from language to language). In any case, you can always override the label with your preferred text. —Jeffrey

— comment by Daniel on September 2nd, 2013 at 2:48pm JST (1 year ago) comment permalink

Hi Jeffrey,

I’m just evaluating your great Metadata-Viewer Preset Editor, version 20131010.60 (and will definitely pay for it). I works just fine – but there’s one field I can’t seem to rename. It’s the “Label” field (for the color labels), called “Beschriftung” in my German Lightroom UI (version 5.2). While I can change the labels of the other fields, this field just resists all changes. It’s saved in the plugin, but doesn’t show up in Lightroom after reloading the plugin. Is this a bug in the plugin? Or in Lightroom? Or is it just simply impossible to change this because of a reason I don’t know?

Thanks in advance for your help!

Greetings from Kiel, Germany,
Jan

Thanks for the report… I’ve just pushed a fix. —Jeffrey

— comment by Jan-Christoph Ihrens on October 22nd, 2013 at 7:09am JST (10 months, 30 days ago) comment permalink

Hi Jeffrey,

thank you very much for fixing this so quickly, now it works perfectly. After updating, the renamed field was removed, but I could add it again and then rename it successfully.

BTW: In the meantime I registered the plugin. Thanks for your great work! :)

Cheers,
Jan

— comment by Jan-Christoph Ihrens on October 23rd, 2013 at 12:42pm JST (10 months, 29 days ago) comment permalink

Hello, I’m French and I do not speak English, so excuse me if the computer translation is not correct.
In the list of metadata fields available in your plug-in, there is one called “title” in the IPTC Status section. I choose this field and include it in my preset in the plugin, it also appears in LR but the field “title” is empty, I had filled with the original “title” field LR .
The reverse is exactly the same.
I have not seen other metadata “title” in the plugin.
Thank you for the help.
Jerome

The “Title” entry in “IPTC Status” is the same as Lightroom’s default “Title” entry, so I don’t understand why you are not seeing the title. Perhaps you switched images? If you save your preset to a file, perhaps mail it to me and I’ll take a look… —Jeffrey

— comment by Jérôme on November 13th, 2013 at 7:05am JST (10 months, 8 days ago) comment permalink

I’m quite confused by the date/time fields that this plugin shows as available. Here’s a link to screenshot that shows the available date/time fields: http://camner.mm.st/screenshots%20for%20forums/friedl%20metadata%20viewer.png.

I see multiple fields with the field name “Capture Time.” The first shows just a time, and the other one farther down shows a date and a time.

There are also two fields called “Date Time.” These show identical values.

So, my first question is: why are there multiple fields in the LR database that have identical field names but seem to have different data in them?

What brought this up is that I have two images that should sort (by Capture Time) together, but do not. Here are links to screenshots showing what your plugin shows for these two images…

Image 1: http://camner.mm.st/screenshots%20for%20forums/screenshot1-LR.png
Image 2: http://camner.mm.st/screenshots%20for%20forums/screenshot2-LR.png

Image 2 (the tiff file) has several fields missing, and it sorts in LR between two files with dates on either side of the “Date Time digitized” date.

So, question 2: What field exactly does LR use when sorting images by “Capture Time”?

And finally, question 3: What can I do to provide the tiff image with the data values necessary to get these two images to sort together?

(FWIW, when I use LR’s “Edit Capture Time” menu item, both images show up as having exactly the same Capture Time!)

Thanks for your plugins and for your help.

If you mouseover each item and pause, the tooltip will explain the difference. The two “Date Time” entries, for example, show the same value, but the second one simply disappears if it’s the same as the Capture Time. As to why there are two different fields labeled “Capture Time”, that is a good question whose answer I don’t know. The plugin merely mimics what Lightroom itself does, and Lightroom has the two separate fields labeled the same. As for the sorting, Lightroom has bugs in this area, especially with videos. I’ve reported many. I *think* it uses “Date Time Original” for sorting, which your TIFF doesn’t have. For best results, make sure that all the various date/time fields agree, and then cross your fingers and hope Lightroom does something reasonable. /-: —Jeffrey

— comment by Robert Camner on February 23rd, 2014 at 11:18am JST (6 months, 26 days ago) comment permalink

Thanks for the quick and helpful response! I’ll do my best to figure out how to get a value into the Date Time Original field when no value currently exists.

You might try ExifTool to inject it (perhaps copying it from another date field), then “Metadata > Read Metadata from File”, but be sure to “Metadata > Save Metadata to File” before so that when you do the read, the only thing different is the date. If you don’t write it first, you’ll wipe out anything you’d changed in Lightroom. I sure wish Adobe made this easier. —Jeffrey

— comment by Robert Camner on February 24th, 2014 at 11:16am JST (6 months, 25 days ago) comment permalink

A couple of questions..

1. Where does this plugin store the custom presets I create? If I export one of the custom-created presets, it creates a .lrtemplate file with a name obviously connected with the name of my custom preset, but I can’t find any other file on my filesystem with that name.

2. If I understand correctly, a static preset can be used OUTSIDE the plugin (the help says “Static presets and be copied to other computers”). If I generate such a status preset, where does it go within ~/Library/Application Support/Adobe/Lightroom on another computer?

Thank you.

Custom presets are stored either within the Lightroom preferences, or exported as the lrtemplate file you noted. Lightroom’s built-in metadata-viewer presets are indeed built in, so the only metadata-viewer preset files you’d find are ones you create. They go in “~/Library/Application Support/Adobe/Lightroom/Metadata Field Lists” —Jeffrey

— comment by Robert Camner on April 4th, 2014 at 1:38am JST (5 months, 17 days ago) comment permalink

Hmmm…I don’t have a Metadata Field Lists folder in ~/Library/Application Support/Adobe/Lightroom; it jumps from “Locations” to “Metadata Presets.” But I do have several metadata presets I created with your plugin. From the absence of that folder, I presume you store the presets created by the Metadata Preview Viewer preset in the LR prefs, yes?

So, I want to edit the preset so that a field has multiple lines (such as happens by default with “Caption”), and I did the following:
1. Build the preset the way I want with your plugin
2. Export the preset
3. Using TextWrangler edit the .lrtemplate file to add the code to make the item show 2 lines
4. Changed the title of the preset within TextWrangler and saved the file
5. Imported the new .lrtemplate file

That worked fine, but the old custom preset is now marked “disabled.” It has a different id field.

Why did the original preset get “disabled” and what magic step am I missing?

Thanks again.

Lightroom has three ways for presets to exist… its internal default presets, “*.lrtemplate” files in the “Metadata Field Lists” folder (if it exists; it doesn’t originally), and via a special plugin mechanism. My plugin does save your non-static preset data in the Lr preferences file, but needs to provide them to Lightroom via the special plugin mechanism, which it does upon startup.

Anyway, that’s the background. To do what you want, you’ll want to “Convert to Static Preset” to save the file in your Metadata Field Lists folder (which the plugin will create as needed), then edit that file in place. I’m not sure what you meant by “imported the .lrtemplate file”, but you don’t need to import anything… once the template is saved, just edit its fields as you like. —Jeffrey

— comment by Robert Camner on April 9th, 2014 at 12:18pm JST (5 months, 12 days ago) comment permalink

Great plugin! Is there any way you could add bit depth?

No, unfortunately that’s not one of the fields that Adobe exposes to plugins (nor to users). However, FWIW, you can inspect the bit depth on an individual-file basis with my metadata-viewer plugin, and group photos by their bit depth with my Data Explorer plugin. —Jeffrey

— comment by Matthew Turley on April 10th, 2014 at 2:23am JST (5 months, 11 days ago) comment permalink

Really sorry for the dumb question: how to I get it to show? I reloaded it after configuring which fields I need it to show, the Manager says it’s enabled but I can’t find it anywhere in the menus? I’m using a Mac with Mavericks. Thanks!!

There’s a dropdown list in the metadata panel itself, as illustrated in the image just under this page’s title (with the cursor pointing to “Jeffrey’s View”). —Jeffrey

— comment by Danny on May 6th, 2014 at 5:04pm JST (4 months, 15 days ago) comment permalink

Thanks!
One more questions: would it be possible to get it to show some of the “green” items from your Viewer Plugin like the AF Micro Adjust Value?

No, Lightroom allows for only certain items in the metadata panel. The metadata-viewer plugin goes outside Lightroom to access the metadata, then displays it in a custom dialog. —Jeffrey

— comment by Danny on May 6th, 2014 at 11:41pm JST (4 months, 14 days ago) comment permalink

Hi Jeffrey,

Thx for this plugin. It comes very handy to display only what I need on the limited space of my laptop.

I’d like to add the altitude from the Geoencoding plug-in. You explained how to do it in another message – here or on the Geoencoding page: edit the LR Template.

Do I have to save a static preset to do that ? Because I don’t the file that I’m supposed to edit.

Thx — Philippe

There’s been no separate “geoencoding plugin altitude” since Lr4 when Adobe gave plugins the ability to update geodata, so just use this metadata-viewer-preset plugin to create a preset that includes the normal altitude. No need to edit any files. —Jeffrey

— comment by Anonymous on August 10th, 2014 at 8:18am JST (1 month, 11 days 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.

More or less plain text — see below for allowed markup

You can use the following tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Subscribe without commenting