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 Classic, and older versions as far back as Lightroom 3, 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 )

20180610.91

Still more plugin-loader fiddling.

20180605.90

More fiddling with the plugin-loader stuff.

20180525.89

More debug logging.

20180524.88

The new "load fields from plugin" stuff I recently added, which entailed building a sort of Lightroom/plugin emulator, didn't work with certain plugins out there that did some fairly hairy things under the hood, that interacted with some Deep Magic in how Lightroom executes things. Finally figured it out!

Clicking on the version number in the Plugin Manager now copies version info to the clipboard

20180511.87

Reworked the "load fields from plugin" stuff to be much more robust. I more or less have to build a Lightroom emulator to load the plugin in and see what kind of custom fields it provides.

20171019.86

Updates for Lightroom 7

20170923.85

Update registration support to handle a stupid bug at PayPal that PayPal refuses to fix )-:

20170208.84

Added support for the "Temperature" field I just added to my geoencoding-support plugin.

Switch the log-sending mechanism to https.

20160821.83

Added support for Alloy Photo's Print Size Calculator plugin.

Highlight more that you can import fields from unrelated plugins.

Try to avoid yet another place where Lightroom gets hung because it can't handle certain kinds of dialogs at the same time.

20151222.82

Added the "At Facebook" item, which somehow got missed earlier.

20150809.81

Added two new items I found in Lightroom 6, "Camera + Lens" and "Camera + Lens Setting".

Added data for Lightroom-Plugins.com's Alamy Picture Manager.

20150209.80

Update the code that puts together the example value for the "Camera" metadata item, to mimic the grotesquely-verbose way that Lightroom actually does it itself.

20150206.79

In the POODLE-vunerability dialog, display a raw URL of a page on my site that discusses the issue, so that folks can be independently sure that the dialog is indeed from me and not malware.

20150125.78 Wasn't working on Lr2 again.
20141211.77

Added data for my Google Drive plugin, for my ipernity plugin, and for my Tumblr plugin.

Registration was broken on Lr2.

20141127.76 Added support for my Geoencoding-Support's "Timezone" metadata field.
20141019.75 Windows Only: Add a one-time check for the POODLE security vulnerability, and alert the user if it exists.
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.


The 30 most-recent comments (out of 72; see all), most recent last...

I love this metadata presets plugin. I have stumbled upon an anomaly though. I am using “At Tumblr”, “At Flickr” and “At PicasaWeb” and would like to use “At Facebook” as I see it in the “all possible items” list (the active, righthand column when your dialog is not active but rather when one is actually working on images) but in the dialog to build/configure my preset, the “At Facebook” field is not provided, only the “Uploaded to Facebook” (and the date/time fields) is listed for use 🙁 🙁

In the “all possible items” list I see this field (At Facebook) is in the jf Facebook “stanza” whereas the other “At …” fields are in the “Jeffery’s Export-to-…” stanzas.

LR CC, and plugins are all up-to-date.

I’m not sure how this got omitted in the first place, but I’ve just pushed out a new version of the plugin that includes it. Thanks for the report. —Jeffrey

— comment by Larry Williamson on December 15th, 2015 at 5:39am JST (2 years, 8 months ago) comment permalink

I could not find shutter count in the list to modify for my metadata presets plugin. Is this not available in this metadata list, it is available in the Metadata Viewer which I have and registerd and works real good, just a lot of data.

Lightroom doesn’t make it available, sorry. —Jeffrey

— comment by Floyd Cantrell on January 8th, 2016 at 8:56am JST (2 years, 7 months ago) comment permalink

A very nice plug-in. I want to ask you where (in which subfolder of the system) to put the exported .lrtemplate file of this Metadata-Viewer Preset Editor-plugin. I work on a Mac. Thanks.

Hans Schäppi from Switzerland

The plugin should put it there for you, but in any case it’s “~/Library/Application Support/Adobe/Lightroom/Metadata Field Lists/” —Jeffrey

— comment by Hansruedi Schäppi on June 12th, 2016 at 5:23pm JST (2 years, 2 months ago) comment permalink

Is it possible to include XMP data as options to view even if read-only?

In particular I am looking for a way to view Panorama / Photosphere data which is saved from software such as PT GUI or Android photosphere.

I know I can sort-of get this info in Lightroom either via Data-Explorer or Metadata Viewer plugins but it gets a little cumbersome to view this info for multiple files.

In particular the XMP fields I’m looking for are:

GPano:ProjectionType
GPano:UsePanoramaViewer
GPano:CroppedAreaImageWidthPixels
GPano:CroppedAreaImageHeightPixels
GPano:FullPanoWidthPixels
GPano:FullPanoHeightPixels
GPano:CroppedAreaLeftPixels
GPano:CroppedAreaTopPixels
GPano:StitchingSoftware

Unfortunately, no, the plugin is limited to arranging from among the specific fields that Lightroom provides access to, or fields defined from other plugins. (If you can get a plugin that imports those GPano fields into plugin custom fields, this plugin can display them.) —Jeffrey

— comment by Matt on August 28th, 2016 at 6:09am JST (2 years ago) comment permalink

With latest LR upgrade all your plugins disappeared.
Was able to reload them and they work after revalidating but the several custom presets made with Metadata Presets havc disappeared.

I tried to puzzle through the instructions at “Robert Camner on April 9th, 2014” but couldn’t find the ones I created anywhere on C: drive.

Any hints on where to find them and where to move them or should I just redo them?

Using Win10 64 bit

TIA,

Lew

It sounds like you lost Lightroom’s preferences file. If you can’t restore it from backup, then yeah, sorry, you’ll have to recreate your presets. —Jeffrey

— comment by Lew Lorton on September 13th, 2016 at 9:10am JST (1 year, 11 months ago) comment permalink

Hi Jeffrey,
thanks for adding support for Alloy Photo’s Print Size Calculator plugin!
Regards Thomas

— comment by Thomas Kemnitz on November 28th, 2016 at 11:24pm JST (1 year, 9 months ago) comment permalink

I really like this plugin, great job. Is it possible (maybe with next release) to include Metadata from Piwigo Export Plugin?

Plugin is available at http://alloyphoto.com/plugins/piwigo/

I assume when you contact the author you will get a full list of Metadata definitions.

Best Regards

Have you tried the relatively-new import feature? There’s an “import fields from plugin” button at the bottom-center of the dialog. —Jeffrey

— comment by Wernfried on January 16th, 2017 at 1:00am JST (1 year, 7 months ago) comment permalink

great plugin –
I figured out how to show the caption field with 2 ore more lines, but how can I show the keyword field with ie 2 lines?
thx Bernd

Alas, Lightroom doesn’t allow it. —Jeffrey

— comment by Bernd on February 19th, 2017 at 12:22am JST (1 year, 6 months ago) comment permalink

Hi Jeffrey,

I have been using registred versions of your plug-ins since Lightroom since version 3. Somehow I have only now discovered the Metadata-Viewer Preset Editor. This may be my favourite of them all. I have been struggling with swapping between various Lightroom meta-data options. Now I can get just what I need and ONLY what I need.

Thank you.

— comment by Khürt Williams on March 24th, 2017 at 4:12am JST (1 year, 5 months ago) comment permalink

Trying to bring all my images from Aperture – ~ 50,000 images using your metadata preset.

Was just about to start after working with it, but I am unable to bring in the GPS data. I have manually set the photos in Aperture to locations, and in Aperture it is listed int he metadata as two fields, the Latitude & Longitude.

I don’t see those fields separately – only as one field ‘GPS’ in LR , but it doesn’t read the information from Aperture separate fields (longitude & latitude). Do you know of a way make this work? Thank you for your time.

Sorry, I don’t know anything about Aperture. Are you using the plugin that Adobe provides, for migrating data? I’d hope that takes lat/lon into account(!) —Jeffrey

— comment by David Barron on March 26th, 2017 at 6:40am JST (1 year, 5 months ago) comment permalink

Hi Jeffrey,
is it possible to display the keywordTagsForExport field?
Lightroom currently supports no way to check which keywords will be export.
Thanks

Even if it’s added to the list of items to display, Lightroom doesn’t display anything… it’s just ignored. )-: —Jeffrey

— comment by Wilhelm Medetz on August 2nd, 2017 at 1:07am JST (1 year ago) comment permalink

Hi Jeffrey, *Great* plugin, thanks so much for taking the time to create it and keep it updated! Sadly it won’t work with LR CC 2017 (the Oct 18 2017 release). Can you publish an updated version that will work with the latest version? Thanks!

It’s now available. —Jeffrey

— comment by Rogier Gruys on October 19th, 2017 at 5:59am JST (9 months, 29 days ago) comment permalink

I am a registered user of this Metadata-Viewer plugin, and it has been working perfectly before. However, Adobe just released the latest version of Lightroom today (Lightroom Classic CC), and during installation I received a warning message, which says “the version of the Jeffrey’s Metadata Preset Builder plugin you have does not work in Lr7”. Please update this wonderful plugin, so it is compatible with the latest version of Lightroom (classic CC).

The update is available now. I almost made it in time. —Jeffrey

— comment by Feng Wei on October 19th, 2017 at 6:23am JST (9 months, 29 days ago) comment permalink

Thank you for having an update ready to go. I have become very dependent on your metadata plugin. I kicked in a few more dollars for you.

— comment by Monty VanderBilt on October 19th, 2017 at 10:12am JST (9 months, 29 days ago) comment permalink

Hi Jeffrey,

first of, many thanks for your great plugin, been using it for a while and loving it.
There’s a slight annoyance that came up since the last update for LR CC 2017. Up until I yesterday, I had my custom metadata viewer template set as default.

Since the update to LR CC 2017, each time I start up LR it reverts back to the “Default” view. Not sure if this has anything to do with your code or if it’s just the new LR acting strange, but I thought I’d let you know, in case there’s something you can do about it 😉

It should continue to work as before, so perhaps Lightroom’s preferences were created in a corrupted state? Maybe try flushing your preferences, then see whether it sticks….. —Jeffrey

— comment by Mariosch on October 20th, 2017 at 8:33am JST (9 months, 28 days ago) comment permalink

To reply to last user’s comment – I also installed the latest update to LR CC 2017. When I start up LR, it does NOT revert back to the default view. there might be some specific settings related to your LR, which is causing this behavior.

— comment by Feng Wei on October 21st, 2017 at 12:50am JST (9 months, 27 days ago) comment permalink

I noticed today that my custom presets are gone. I don’t know when this first happened although it may have been when I updated to Lightroom Classic CC and re-registered the plugin. Is there a way to recover the custom presets or do I need to start over?

The ones that haven’t been saved to a file are stored in Lightroom’s preferences file. They should have been carried over along with all your other preferences during the upgrade, but perhaps some corruption happened? If they had been saved in files, they should be there in the Application Support folder, and so I’d think they’d also just work. If you can still fire up Lr6, you can save your presets to files that way, and they should then immediately be available in Lr7. —Jeffrey

— comment by Marc Sontag on December 9th, 2017 at 12:39am JST (8 months, 8 days ago) comment permalink

Sometimes, I want to know which PASM mode I used to take a photo. The only metadata I see in LR (and your metadata preset plugin) is “Exposure Program” and the value simply shows “Normal” which isn’t a mode on my camera. Using your “Metadata Viewer” plugin, I get different results. Exif (blue) data is “Exposure Mode: Manual” and “Exposure Program: Program AE”, which are conflicting. MakerNote (green) is “Exposure Mode: Program”, which is probably correct.

So, how can I get Lightroom to show my actual PASM mode right in the metadata panel?

Not easily. Lightroom’s “Exposure Program” certainly comes from some field in the original image file, but which field, and how that’s mapped to the possible values in Lightroom, is not known. To get some original-file field to show directly in the metadata panel, you have to copy its value to one of the fields that Lightroom does show, such as the Caption or the Title. My bag-o-goodies plugin can perform this copy, but you have to remember to run it every time you import photos, as, unfortunately, Lightroom doesn’t provide any hooks in this regard. —Jeffrey

— comment by Joe on December 19th, 2017 at 1:23pm JST (7 months, 28 days ago) comment permalink

Hi Jeffrey,

merry Christmas to to and your Family!
is it possible to create an preset showing Canon Makernotes?
Using your “Metadata Viewer” it shows “Bracking Mode”, “Bracket Shot Number”, “AEB Bracket Value” etc., which are very helpful to selcet all pics done with an AEB Bracking Sequence.

Or any other way to copy the above-mentioned fields directly into the meta tags and make them search/selectable?

With kind regards!
Ulrich

You can’t show them directly because Lightroom doesn’t support them, but you can use the Write Data Field feature of my Bag-o-Goodies plugin to copy the fields to ones that Lightroom does display. (BTW, perhaps check out the Find Next Photo Group feature, which may help with your bracketing sequences.) —Jeffrey

— comment by Ulrich on December 24th, 2017 at 8:46pm JST (7 months, 23 days ago) comment permalink

I tried to “import fields from plugin” from the Smugmug publish service plugin (theirs, not yours), and received a “Could not load toolkit script: SmCommon” error, which I presume means that their plugin is doing something incompatible with Metadata Presets. Is this something fixable at your end, or must they make a change at their end for Metadata Presets to support their plugin?

(In general, I prefer your SM plugin for its more robust feature set, but it doesn’t support nested folders the way your Zenfolio plugin does, and that’s essential to my setup at SmugMug.)

Give it a try with the latest version of my plugin… there’s a better chance it’ll work now. —Jeffrey

— comment by Robert Camner on February 10th, 2018 at 3:30am JST (6 months, 7 days ago) comment permalink

Hi Jeffrey

Love your presets. Thanks for all your work.

One question for you. Is it possible for a user to edit the name of the plug-in folder and or the name of the plug-in as it appears in the Plug-in Manager.

I find it very confusing that for example the folders are titled
data-explorer-jfriedl.lrplugin, while the plug-in is called jf Data Explorer.

My simple brain finds this confusing if reading down lists. Today I had to reset preferences following a suggestion from Adobe support, so had to re-install all plug-ins, and the naming issue is a bit confusing.

Thanks

I see what you mean, but it’s not easy to change things, sorry. —Jeffrey

— comment by Colin McDonald on March 8th, 2018 at 3:51am JST (5 months, 9 days ago) comment permalink

Hi,

trying to import fields from plugin, to be specific, the #hashtags field from LR/Instagram plugin. When I choose the folder and hit ‘open’ it gets opened; clicking a file [no idea which one includes the metadata fields, hence I checked for a couple of almost randomly chosen files] gives me an error ‘not a plugin folder’.

I am a bit baffled what to do.

When you choose the plugin folder, don’t click “open”. Instead, click on “Choose” or “Okay” or whatever other option the OS dialog is offering. —Jeffrey

— comment by Dierk on April 18th, 2018 at 7:13pm JST (3 months, 28 days ago) comment permalink

Hi Jeffrey

My “metadata view preset” I’ve tweaked is all of a sudden gone from the drop down. I’ve built a new PC and want to move that setup over. I can’t find where it is stored.

Help!

The data is stored in your Lr preferences file, unless you export it to a file, in which case it lands in the “Metadata Field Lists” subfolder of the “presets and templates” folder mentioned here. —Jeffrey

— comment by Kristian on April 18th, 2018 at 7:30pm JST (3 months, 28 days ago) comment permalink

Thank you, Jeffrey!

The button is so unusual and the font on it didn’t change much between ‘not clickable’ and ‘clickable’ I didn’t notice it.

— comment by Dierk on April 20th, 2018 at 7:19pm JST (3 months, 26 days ago) comment permalink

When I attempt to load custom metadata fields from the plugin “jb search replace transfer” (http://photographers-toolbox.com/products/jbeardsworth/findreplace/) version 1.59.0.1 in latest Lightroom CC Classic on Windows 10:

I get a popup from your plugin v 20171019.86 saying “error loading toolikit script `LRLib_InterOp’ (Could not load script LrLib_InterOp.lua: doesn’t seem to be in the toolkit.)” The .lua file is there in the directory.

I have successfully used this function of your plugin to add metadata fields from other plugins.

I’m not sure whether the problem importing this plugin’s fields is a problem with your plugin, a problem with jb’s plugin, or simply a situation where this import function isn’t going to work because jb’s plugin is more complicated than the function is prepared to deal with. I wonder if you can shed light on the best way forward to the goal of including the custom fields from jb’s plugin into a custom metadata viewer preset generated by your plugin. Note that jb’s plugin has some fixed custom metadata fields, and also a user option to enable an additional set of custom fields. I tried the import function both with and without the optional additional fields selected in jb’s plugin configuration. Same result both ways. I do use the custom fields and would like to include some of them in a custom metadata viewer preset.

It was an issue of my “read this plugin” routine being too simplistic. Lightroom doesn’t give an easy way to do this, so I’d hacked up something simple. John’s stuff is rich and complex, so what I had wasn’t good enough. So, I more or less built a virtual Lightroom sandbox inside Lightroom in which to properly load the plugin, and now it works (I hope). Give the new version a try…. —Jeffrey

— comment by Matthew Swift on April 30th, 2018 at 11:27pm JST (3 months, 16 days ago) comment permalink

You make all the remarkable coding you do seem so easy! Well, just a virtual Lightroom sandbox is all it needed…. I encountered an issue with the new version, however, and bug report is on its way now. Reason for post here is to ask about keeping some prior versions available on an FTP server or the like. Haven’t scoured your site, maybe you do this already, but if I hadn’t kept my own copy of the previous version of this plugin, I could have been stuck.

— comment by Matthew Swift on May 21st, 2018 at 12:06am JST (2 months, 27 days ago) comment permalink

Hi Jeffrey,

Posting from Sonoma County, in northern California, USA.

Very happy to have found your plugins!

In your response to another person’s question about automatic updates not always working smoothly, you said “just delete all the old copies of the plugin from your machine (you won’t lose any data… none is kept in the plugin files), download and unzip a fresh copy.”

My Lightroom catalogs, as well as *all* of my other photo and document data is on a portable external drive, so that I can easily work on my laptop or my desktop (or on some other computer) by simply mounting the external drive. At home, I may switch between laptop and desktop more than once in a day.

My question: where is the data from your plugins stored if not in the plugin?

I want to be certain I have regular backups of the presets I create and make changes to, as well as being able to switch computers and continue working where I left off, just by mounting my data drive, without having to fetch copies of the plugins/presets and reinstall them in the new work location.

For those apps that will install and read plugins, presets, etc directly from a custom location (like your plugins) I have them in specific folders on my external drive.

And for those apps that want presets, templates etc to be on the computer hard disk in (user)/Library/Application Support/AppName/ (etc), I’ve made symbolic links in the expected sub folders which point to my custom locations.

Thanks,

Muiz

Plugins generally store their data in the catalog and the user preferences. The latter are not easy to move around from machine to machine, and how inconvenient that makes things depends on the plugin. For some you may have to replicate configuration on each of your machines… —Jeffrey

— comment by Muiz Brinkerhoff on May 28th, 2018 at 4:26am JST (2 months, 20 days ago) comment permalink

Upgrading to 20180525.89 causes the following error when attempting to edit an existing preset:
“PluginLoader:175: attempt to call field ‘?’ (a nil value)”.

Reverting to previous version eliminates this error.

Marc

Could you try again with the latest version, and send a log if you encounter the error again. Thanks. —Jeffrey

— comment by Marc Sontag on June 5th, 2018 at 6:37am JST (2 months, 12 days ago) comment permalink

Hi Jeffrey

I am just a newbie with everything around photography (RX100, Lightroom, GPS Logging. and so on) and try to create a workflow for my personal travelling blog. I have HoudahGeo for reverse geocoding and write this data direct into the image file. With Lightroom I can sync this data with my catalog and see it afterwards in the IPTC Extension Metadata. The problem is, this data is not availlable in your addon, or at least I could not find it.

Albert

Lightroom presents only certain metadata fields to the user; my plugin merely allows you to select/arrange from among those that Lightroom allows. Normally, reverse-geocoding fills in fields like “City” and “Country” that Lightroom (and the plugin) handle, but if you’re filling some other field that Lightroom offers no access to, you’ll be out of luck viewing that in Lightroom. )-: —Jeffrey

— comment by Albert Eberli on August 13th, 2018 at 8:37pm JST (3 days, 4 hours ago) comment permalink

Hi Jeffrey

Sorry to write again, but the required field is filled up in IPTC Extension view of Lightroom, and in your list is the same field listed, but not filled with the value. I send you a screenshot about this. Still hope this is a bug 🙂

Albert

Oh, I see, you’re looking at what’s shown in the dialog as you prepare the list of fields you want to see. What’s shown there is just sample data, sometimes taken from the currently-selected photo, sometimes made up, and sometimes (such as this field) always blank. When you save the preset and actually use it within Lightroom, everything will appear properly. —Jeffrey

— comment by Albert Eberli on August 13th, 2018 at 11:58pm JST (3 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.


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

Subscribe without commenting