Hi

First of all I wanted to say, “Thank you” for sharing your knowledge of photography and everything that is associated with it.
My knowledge of for instance, Metadata viewer, is very slim. I am trying to learn by reading your blog and trying to make sense of it but it is so much information to remember lol.
I have some very old pictures of my ancestors and I was wondering if there was a way to get any date stamp or GEO coordinates of any of them?

Thanks Again!

P.S. Your photographs are just gorgeous

Bonjour,

Je suis sur Nantes en France.
J’ai téléchargé ce Plugin car je souhaite connaitre plus de détails sur mes photos.
Mais je n’ai pas trouvé le nombre de déclenchement de mon Canon EOS80D ?

Merci à vous de votre réponse,
Laurence.

That camera does not include the shutter count in the image metadata, sorry. —Jeffrey

First, thank you for all that you’ve done for the photography and Lightroom communities Jeffery!

Long story short I think I need a way for Metadata Wrangler (or another tool) to also write the Caption field data to the IPTC:Caption-Abstract field in addition to the EXIF:ImageDescription field. I think I’m observing that Google Photos only looks at the IPTC:Caption-Abstract field so trying to use Metadata Wrangler to modify the photos’ description field only works for Google Photos if Metadata Wrangler is also writing to the IPTC:Caption-Abstract. There’s a note about how Metadata Wrangler works in this regard on the change log, reproduced below.

Is there a setting or way to force Metadata Wrangler to also overwrite the IPTC:Caption-Abstract field even if there was no text in there originally?

Best regards,

R. Moore

“20190817.180 – Added “Artist” to the “Add/Overwrite” section, and updated the internals so that when overwriting an item, it overwrites all copies of that item in the metadata (e.g., when updating the “Caption”, the tag actually filled in is “EXIF:ImageDescription”, but if “IPTC:Caption-Abstract” and/or “XMP:Description” exist, they are also filled in). Also fixed the “Speed” item in this area.”

This ended up being a minefield, so I’m reticent to change semantics now. Consider instead using the Run Any Command plugin to invoke ExifTool to copy the metadata fields as you like on each exported copy. —Jeffrey

Hi from Belgium,

I saw your geocoding plugin for lightroom (v4 for me)> Unfortunately Icannot geocode from GE. As Google has change the way to works with maps years ago, is it in your pkan to move from google to openstreetmaps for getting info for geocoding ?

Thanks,

You can use Google if you get your own API developer key and enter it into the Plugin Manager. The plugin also already lets you use OpenSteetMaps. —Jeffrey

Hello there from HK,

I am going to geo tag my old Nikon DSLR (D7000) photos taken in past 10 years. Over 20,000 of them. Your Geotagging plugin for LR is really a time saving tool. Wouldn’t even think about this daunting task without your tool. 100% well worth for the denotation I made in registration!

Thank you!

Hi from Sedona, USA,

Any chance you’ll develop an export plug-in creating webp files, with improved browser support I’m think of serving these up instead of jpegs for browsers that support them.

Thanks, I use your geocoding plug-in all the time

No, sorry, Adobe will have to add it to Lightroom natively. —Jeffrey

Hi Jeffrey,

I wrote to you earlier today asking about custom orders in synced collections. Anyway, I decided to try it out for myself (with success) and confirmed the following (FYI):

1) you can create a custom order in the resulting “companion” collection which doesn’t change when you sync updates from the smart collection. New photos are placed on the end:

2) I was able to maintain my custom ordered collections I’d already made by giving the smart collection and companion collection the same name:

3) the plugin doesn’t “companion” subfolders from a parent folder, I had to “manage” each subfolder individually (no big deal):

4) consequently the companion set doesn’t divide into subsets… I had to place all the companion collections into one folder (again no big deal).

Thanks again for they great work.

Walter

I can’t get the “Smart Colection Sync” plug-in to work. I just get the message “The catalog has no smart collections to be processed by this plugin.”. What am I doing wrong?

You have to be sure to mark the smart collections that you want to work with. The default is with “<!>” in the title, but it can be changed in the plugin settings. See the docs on this page. —Jeffrey

Hello hello Mr Friedl;
Hoping all’s as well as can be with you & yours.
I have enjoyed your Flickr photo sync tool greatly over the years and have watched with pleasure and & joy as you continue to improve it. Thank you.
I have begun to integrate Capture One (version 20.0.4) into my photo workflow and am really enjoying the multitude of differences between it and LR CC. Tho it has a scripting function I am extremely loath to try my hand as those tasks end poorly for me, always. I wonder if you might consider the challenge. I’d be (and likely there’d be others) happy to pay for your fine work, along the lines of your current LR plugins.

Best regards,
Michael Mazzola
Lighting Designer
Portland, OR, USA
IG: mjmazzola

Thanks for your kind words, but I won’t be expanding to anything beyond Lightroom. —Jeffrey

Do you know of any way to export a text file of your Collection Set/Collection tree?
I’m just looking for something that looks like the output of “dir > tree.txt /a” but for Collections…
I’ve used a number of your plugins over the years, and I know how useful and skilled as a programmer. My scripting days/programming days died in my brain many years ago.

Thanks in advance.

I’m afraid that I can’t think of any way to do this, sorry. —Jeffrey

This is some excellent work. I just registered and donated $25 for your Collection Publisher. It’s kind of mind-blowing that this functionality is not part of core Lightroom. You’re doing work Adobe can’t be arsed to do and ask for essentially nothing in return. Amazing!

It’s also such a basic functionality, really… yet, here we are.

Your plugin allowed me to reach what feels like 90% automation in my flow: take new photos, import, edit, add to a new, manual collection. Then hit “refresh and publish” so that new collection is picked up by the mirrored collection from your plugin. This publishes it to the NAS, which my Nextcloud can access. Visit Nextcloud, hit “Share” on that folder, done. Takes seconds. Through your addon, I have constant peace of mind that full sync is reached (or know when it’s not). Through Nextcloud, I can track exactly what stuff is shared with whom, set passwords, expiration dates etc. All at full JPG resolution, too. No more duplicates, SSOT all the way. This is the world I always dreamed of, facilitated through your excellent plugin. Amazing what one can do with some spit and Lua, in the Adobe-constrained playground.

The only bitter pill in all this is that your work ties me down with Adobe even more, receiving my money that in fact you earned for a good part.

Greetings from Germany

Hi, do you do custom development for lightroom plugins?
I have specific needs if you’re interested. email me.
thanks!

No, sorry, I don’t. —Jeffrey

Hi, thanks for your geo plugin. After Adobe has stopped support of maps for LR 6 it helps me a lot. It’s much clever anyway. Do you have plans to develop any plugins for Capture One Pro?

No, sorry.—Jeffrey

Jeffry
Do you have a plugin for the capacity to Publish directly from LR to Instagram?
Thanks
Doug
dougtesta@comcast.net

Facebook doesn’t allow it, except for official Business accounts. (At least they allow that, now; for a long time, they required uploads to be from a phone.) I haven’t made a plugin for Business accounts, but I’m considering it…. —Jeffrey

Hello Jeffrey,

I’m Olivier from Canada, first thing first, thank you for your fabulous work in the photography community. I’m a big fan of the LR sync adon and I wonder if it will be available for the latest version of Lightroom classic ?
Thank you for your work again and have a great day

Olivier

I’m not sure what plugin you’re referring to, but it doesn’t sound like one of mine… —Jeffrey