Jeffrey’s Lightroom Goodies (Plugins and Tools)

This page lists my Lightroom-related plugins and posts.

Note: everything here is for Adobe's venerable photo-workflow app started in 2006, named at various times “Lightroom”, “Lightroom CC”, and now (as of Oct 2017) “Lightroom Classic” or perhaps “Lr7”.

Nothing here applies to Adobe's new desktop app, debuted in Oct 2017 and given the old app's “Lightroom CC” name.


Plugins for Lightroom:   (All-Plugin Update Log via RSS )

Export & Publish:

Export Plugins:

Other Publish Plugins:

Export Add-Ons:

Geoencoding Plugins:

Utility Plugins:

Plugin-related Info:

Tools for Lightroom:

Etc...

Old Plugin Resources for Lightroom 1 (no longer supported)

Other notable sources of Lightroom plugins include:


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

Hello Jeffrey,

I’m writing from Germany. After upgrading the “Geoencoding Support” plugin today it is deactivated due to an error “Could not find namespace: LrApplicationView”. I’m using Lightroom 3.6 64-bit on Windows 8.1. Following the steps in FAQ (I get “An error occurred while reading the schema …) didn’t help.

Best regards,
Theo

Ooops, sorry, sloppiness on my part. I’ve just released an update that should fix it. —Jeffrey

— comment by Theo Ingenerf on May 6th, 2017 at 5:00am JST (7 months, 10 days ago) comment permalink

I know others have asked about an instagram plugin and it’s not allowed, etc, etc. I recently stumbled on something called LRInstagram. Works well enough but not nearly so slick as it would if it had all your bells and whistles. I had been using gramblr to upload from my computer and it worked nicely except it was completely unintegrated with LR so I found it frustrating.

So, if LRInstagram (https://www.lrinstagram.com) and gramblr (http://gramblr.com) are able to do this, could you not consider it for your suite?

No, sorry. It’s enough work to keep a plugin going with the support of the remote provider; doing it expressly against their wishes and against the terms of their service is both not my style, nor my idea of fun. Sorry. —Jeffrey

— comment by Larry Williamson on May 7th, 2017 at 10:07pm JST (7 months, 8 days ago) comment permalink

Hi Jeffrey,

Have you written a LR keyword management program that would allow editing in a larger window/panel than LR affords? My keywords are a CF, and reorganizing them directly in LR is an onerous task at best. I understand that it is possible to edit by exporting as a text file and then reimporting, but that strikes me as a formula ripe for disaster.

Best,
Jerry (in torrid Tucson, AZ)

No, I’ve not done much with keywords, sorry. Perhaps check out Jerry Cagle on May 15th, 2017 at 12:30am JST (7 months ago) comment permalink

Hi Jeffrey,

Thank you for your plugins, very helpful on many fronts.

I am trying to set up a shortcut for “View selected locations as KML in Google Earth”, have been trying though the normal route of setting it up through the zprefercens on my mac to no avail. Any tips? Directions for this?

Many thanks

Jacob

Lightroom prefixes plugin commands with three spaces, so be sure to include those in the System Preferences dialog when setting up the shortcut. —Jeffrey

— comment by Jacob McIntyre on June 23rd, 2017 at 9:08pm JST (5 months, 22 days ago) comment permalink

Hi – I’m from the Margaret River region in West Australia.

I saw an earlier comment from Manuel asking about exporting face frame images from Lightroom. I have (badly) written a python script that does that using Imagemagick and Exiftool. I have looked into writing a LR plugin to do this but until the LR SDK supports accessing the associated metadata it would be difficult. The script reads the xmp files in a directory and outputs a batch file that uses Imagemagick and Exiftool to crop the face regions found from the images and place the results (as small jpg files) in a “faces” subdirectory.

In order to use my Python script it is necessary to install python 2.7 with LXML installed. You also need ImageNagick and Exiftool installed. So you need some computing skills. There are a few “gotchas” such as LR not writing to XMP files for jpg files so the originals must be raw files (or use Exiftool to fix this).

If anyone wants to do this I am happy to make it available. If there is any interest I will make the relevant files available somehow, and some brief documentation on how to use it.

— comment by Ian Wiese on July 16th, 2017 at 9:10am JST (4 months, 30 days ago) comment permalink

Jeffrey,

I just upgraded my PC and tried to reinstall your Lightroom Collection Publisher plugin, which I’ve been using for years.

However, Norton AV on my new PC now quarantines cygwin.dll and hence the plugin fails.

Any suggestions?

Sigh, that dll file has not changed in years, but they still come around every so often to flag it. Please send them a copy (or point them at the plugin) and ask them to investigate, and, ultimately, stop flagging it. Thanks. —Jeffrey

— comment by Alan on August 3rd, 2017 at 1:50am JST (4 months, 13 days ago) comment permalink

Hy

I dont know where to ask this questions, so feel free to kill the comment. I love your plug-ins and I sed them since a long time (..and I regularly donate as well 😉 ). I am using the data explorer a lot recently, is there a option to export out all the fields, or at least a selection of fields, to text/spreadsheet/… currently I am always exporting one property and then match the database via filename.

thx

Data Explorer works with just one field at a time, sorry. You might consider the Lr/Transporter plugin to export a series of fields to a spreadsheet. —Jeffrey

— comment by Diruas on August 10th, 2017 at 2:47pm JST (4 months, 5 days ago) comment permalink

Hi Jeffrey,
I dont know if my question here is appropriate, so feel free to hide the comment if needed.

Since a while, when I backup my Lightroom Catalog I am getting this message: “An internal error has occurred: Attempt to make a request on a closed server.”
Sometimes when these messages appear, after pressing OK through all of them the backup seems to complete without errors and Lightroom quits. Some other times I had to revert to task manager to kill lightroom without completing the backup process.

Now the point is that it ***seems*** that disabling ALL plugins (not only yours) solves the problem, but I am not able to identify if the error is really related to one or more plug-in(s) or getting lightroom working when plugins are disabled it’s just a coincidence.

Could you be so kind to advise if in your opinion this kind of errors could be in some way related to plug-in(s) or I’m totally wrong and need to investigate in other directions?

Thanks a lot in advance
Paolo – Milano – Italy

I’ve never seen this kind of error, though I know it’s deeply related to Lightroom’s internal communication. As best I can guess, some part of Lightroom is trying to update the catalog after some other part of Lightroom has shut the catalog down. I can’t guess whether it’s related to a plugin, but if it is, I’d think it’s a Lightroom bug. Your best bet, I suppose, is to report it to Adobe. —Jeffrey

— comment by Paolo on August 10th, 2017 at 6:03pm JST (4 months, 5 days ago) comment permalink

Do you have / Are you planning a plug-in to export specifically to Google Photos now that PicasaWeb is closed?

Neither my Photo Upload nor your jf-PicasaWeb will export to a new album on Google Photos, they both merely offer local folders as export locations, even when “Choose folder later” is selected.

Currently I have to export to a local disk and use Google Photos to upload from there.

Thanks
(London, UK)

Google doesn’t offer an API to allow third-party apps to upload to Google Photos. It’s only been six years, so maybe they just haven’t gotten around to it yet. /-: —Jeffrey

— comment by Keith on August 16th, 2017 at 5:56am JST (3 months, 30 days ago) comment permalink

Hi Jeffrey,

I’ve used your plugins for years -they’re fabulous. Thanks for all that work. I have been searching for this answer for weeks . I have a new PC. Moved all the photos and LR Catalogue to the new HD. But none of the Publish Collections came along. I use them extensively and have for over 10 years so the thought of recreating them and trying to connect up what I’ve published where is a nightmare. I can’t believe this information isn’t somewhere in the catalog, or a config file somewhere in the Lightroom folders somewhere. I thought if anyone would know, it would be you.

Thanks for you help.

Jeri
Mill Valley, CA

It’s all in the catalog file (the “*.lrcat” file). If you moved that actual file to the new machine, it will all be there. You’ll have to re-add each plugin via the Plugin Manager to ungray the Publish Services and actually use them, though. —Jeffrey

— comment by Jeri Mearns on September 1st, 2017 at 1:07pm JST (3 months, 14 days ago) comment permalink

Hi Jeffrey, for me, the number one missing item in Lightroom is the ability to display the Canon Focal Points. I am a Canon shooter and the only way to find out where I pointed the focus is to view the image in the Canon DPP program. In DPP the focal points are displayed as red dots. Obviously the focal point position info is stored somewhere in the Canon Raw proprietary image but I have not found any LR lug-in that would allow to view them. Do you know if anyone has come up with a LR solution?
Thanks
Franz

I’ve no personal experience with it, but this plugin seems to be exactly what you’re looking for. —Jeffrey

— comment by Franz Zihlmann on September 16th, 2017 at 12:00pm JST (2 months, 29 days ago) comment permalink

Thank you Jeffrey for pointing me to the “Show Focus Points” LR Plug-In. I installed the plug-in and it works great. Btw, the Author of “show focus points” gives you credit for helping creating this product.

— comment by Franz Zihlmann on September 20th, 2017 at 3:50am JST (2 months, 26 days ago) comment permalink

Hi Jeff, do you have a plugin or workaround that will work with ProSelect by Time Exposure. I’m trying to get purchased image numbers a client selects and have those show up in Lightroom so I can flag or star them for album building, etc. Thanks for all you do.

I don’t think so, no, since I’ve never heard of it, sorry. —Jeffrey

— comment by John Naccarato on September 23rd, 2017 at 2:43pm JST (2 months, 22 days ago) comment permalink

Hi Jeffrey,
After a reinstall of Lightroom CC and moving some folders my Metadata Viewer plugin called for registration again. I use this plugin quite often, so I happily made a $5 donation today, Oct 2/17. The confirmation number on the PayPal receipt was rejected. After a number of tries and rejections, I dug out a PayPal receipt from July 10/16. Lightroom was happy to accept it.

Odd. Or not?

Thanks for all of the interesting work that you do.

John Sanders
Vancouver, BC

Thanks for your kind gift(!) Did the new registration number perhaps end with three digits instead of four? PayPal has a bug whereby if the first digit is a zero, they omit it and shift everything over, so it ends up in a “####-####-###” pattern. It’s a really stupid bug that I reported a year ago. Since it seems that they won’t fix it, I’m in the process of updating my plugins to handle the broken code, but I haven’t pushed them all out yet. —Jeffrey

— comment by John Sanders on October 3rd, 2017 at 1:54pm JST (2 months, 12 days ago) comment permalink

I just re-donated due to the Lr7 upgrade, and the confirmation number I got from PayPal is not in the pattern you give in your previous reply. It looks like this:

91727117TN0449439

I’ve changed a few digits to other digits in my example. I’m in the US. The same number appears twice in the email from PayPal, identified as both a “Confirmation number” and a “Transaction ID.”

That seems like a valid pattern… they sometimes give a “transaction id” that looks like that, and sometimes digits only in hyphen-separated groups of four. —Jeffrey

— comment by mph on October 19th, 2017 at 8:49am JST (1 month, 27 days ago) comment permalink

Thanks for your quick reply; when I enter a code in the jf Tumblr plugin in Lr 7, I get a “bad hash” error as shown here:

https://imgur.com/xVPxavb

I have Tumblr plugin version 20171019.66.

Sorry about that, there’s one update since that fixes this bug. —Jeffrey

— comment by mph on October 19th, 2017 at 9:24am JST (1 month, 27 days ago) comment permalink

Hi Jeffrey
Above you say “Nothing here applies to Adobe’s new desktop app, debuted in Oct 2017 and given the old app’s “Lightroom CC” name”. Do you mean “cloud app” rather than “desktop app”?

No, I mean “desktop app”. Adobe now has two almost-unrelated desktop (MacOS/Windows) apps with the name “Lightroom”. One is the venerable app now in its 7th major release, now called “Lightroom Classic CC”. This desktop app can upload your images to the “Lightroom Cloud” if you like, but the master copy of images are what you have stored locally. The other desktop app is one that keeps the master copy of the image in Lightroom Cloud, and is more integrated with that cloud and the other interfaces to it (mobile apps and Lightroom Web). This new desktop app used to have the code name “Nimbus”, but has now been given the name “Adobe Lightroom CC”, which is what the first desktop app had been called. It’s confusing. —Jeffrey

— comment by Rob Fairhead on October 20th, 2017 at 9:39pm JST (1 month, 26 days ago) comment permalink

Will you be porting your plugins to “New Lightroom”? Or do “plugins” even make sense in the new Cloud ecosystem? Should we run as fast as possible in the other direction, clinging to LR 2017 or whatever it’ll be called?

Currently there’s no plugin infrastructure for the mobile stuff. Not sure how it’d work there anyway. Personally, I’m sticking with the venerable desktop app. —Jeffrey

— comment by Graham Charles on October 22nd, 2017 at 2:33pm JST (1 month, 24 days ago) comment permalink

Gracias Jeffrey, una ayuda muy grande, acabo de actualizar el complemento y todo bien. Gracias nuevamente, desde Chile un abrazo, Claudio.

— comment by Claudio on October 22nd, 2017 at 10:45pm JST (1 month, 24 days ago) comment permalink

Hi Jeffrey,

Been a registered user of your plugins for years—don’t know what I’d do without them. I was really hoping Adobe was going to add better support for syncing Smart Collections to LR mobile app in the 7.0 release. Clearly, they are heading in a new direction and I don’t expect much in terms of new cloud support for Lightroom Classic. Any chance of you creating a new plugin/modifying something in to keep a Smart Collection synced with regular Collection so we can sync that to the Cloud?

I’m told syncing of Smart Collections was high on people’s wish lists so I’d think such a plugin from you would get a lot of adoption. Would be so helpful!!!

Mark

I think you can already do that with this plugin, but be warned that things could seem crazy if you forget that the source of images in that collection is the other, smart collection. If you delete or add on the mobile device, it’ll get undone by the plugin. —Jeffrey

— comment by Mark Chernis on October 23rd, 2017 at 7:08am JST (1 month, 23 days ago) comment permalink

Hi Jeff

Love your export from LR, but I cannot find an Instagram export from Zenfolio or LR.

Do you have any?
Tom

No, Instagram specifically disallows it. —Jeffrey

— comment by Tom on October 25th, 2017 at 1:42am JST (1 month, 22 days ago) comment permalink

hey, just wondering if there is going to be an update of your fade time lapse settings for the newest version of lightroom?

thanks

I’m not sure exactly what you’re asking, but my Timelapse Support plugin works with Lr7 (“Classic”). Lr7 (“CC”) doesn’t support plugins of any kind. —Jeffrey

— comment by Corey on October 27th, 2017 at 1:37pm JST (1 month, 19 days ago) comment permalink

Hi Jeffrey

Big fan of your plug-ins for some time.

I’m trying to help someone import from latest Apple Photos App into Lightroom CC.

Was wondering if you were working on a plug-in for this. Upon searching around it looks like the community are really struggling with this and may provide me and others with a solution we can pay for? Fingers crossed!

Kind regards,

Scott

I wouldn’t hold much hope, sorry. Apple has traditionally kept things in its walled garden. —Jeffrey

— comment by Scott on November 7th, 2017 at 8:30pm JST (1 month, 8 days ago) comment permalink

I am writing from UK, Brighton.

Saying my copy of the Jeffreys Folder Watch plugin is too old for this version of Lightroom. Lr7. Need to upgrade my copy?

Thank you Sharon

Yes, if the plugin copy you have is too old for the Lightroom you have, please upgrade the plugin. —Jeffrey

— comment by Sharon on November 8th, 2017 at 11:08pm JST (1 month, 7 days ago) comment permalink

Hi Jeffrey,
Instagram! Sure would be nice to figure out how to post from Lightroom!
Can you help?
Julie

You have to ask Instagram to allow it. Last I checked, they specifically disallowed that kind of integration. —Jeffrey

— comment by Julie Cortens on November 9th, 2017 at 11:45pm JST (1 month, 6 days ago) comment permalink

Hi Jeffrey, I am writing from the UK, Brighton

Adobe updated my lightroom CC to Classic. What do I need to update my lighroom plug in manager jf Folder Watch?

What comes up is – my copy of the Jeffreys Folder Watch plugin is too old for this version of Lightroom. Lr7. Need to upgrade my copy?

Can you help please,

Sharon

I’m not sure what to say beyond what the self-explanatory error message says… please upgrade the plugin. There’s an upgrade button in the plugin manager. —Jeffrey

— comment by Sharon on November 10th, 2017 at 4:37pm JST (1 month, 5 days ago) comment permalink

I have many of your plugins installed, and installed correctly, however, within the LR Plugin Manager on the left column I can not seem to get rid of duplicate listings of the same plugin – the REMOVE button is grayed out.

Any workaround to clean this up ?

Please see this FAQ —Jeffrey

— comment by Scott Rogers on November 15th, 2017 at 11:57am JST (1 month ago) comment permalink

Hi from Bellevue, WA

I use and enjoy a number of your plugins – thank you!
As I accumulate photos through various routes, I end up with many duplicates. I wonder if you have considered developing a duplicate finder plugin. (The existing ones haven’t worked for me.) In my case, I’m interested in finding copies of the exact same source image with different names or in different folders.

I’ve long thought about it, but it’s difficult and time-consuming (CPU and disk) to do well. I guess it’s always been a case of “Perfect is the enemy of good enough”. I’ll bump it up on the todo list. —Jeffrey

— comment by Steve Weil on November 20th, 2017 at 6:44am JST (3 weeks, 4 days ago) comment permalink

Hi Jeffrey – Great work – I really enjoy seeing the technical challenges your plugin’s overcome.

I wanted to ask if you’d ever looked at addressing Lightroom’s inability to filter on ‘Likes’ ?

https://feedback.photoshop.com/photoshop_family/topics/be-able-to-filter-sort-and-isolate-images-based-on-likes-comments-and-individual-users-who-are-viewing-the-online

I haven’t paid much attention to Lightroom’s mobile aspect, but considering how little they’ve paid to the plugin SDK in the last five years, I highly doubt there are any hooks to make the mobile metadata available to plugins. )-: —Jeffrey

— comment by Dale Harper on November 25th, 2017 at 6:58am JST (2 weeks, 6 days ago) comment permalink

Jeffrey – if/when you create a new LR plug-in do you announce it in the Home page of your blog or just list it in the Lightroom Goodies page?

I’ll usually announce it with a small blog post. —Jeffrey

— comment by Dave B on November 26th, 2017 at 3:35am JST (2 weeks, 6 days ago) comment permalink
Leave a comment...

Please do not report bugs or other comments related to my plugins here. Please do those on the appropriate per-plugin page (linked from my Lightroom Goodies page).


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