Would love the possibility of adding a line break 🙂

Hi Jeffrey! Thanks for adding this great feature. A suggestion for an alternate syntax, perhaps better than the squelching–

{City “-“}{State|Province}

Right now the braces enclose a single token. Extending that to a sequence would allow for more general squelching, such as

{“©” YYYY “.” |”Image is in the public domain.”}

or using HTML for line breaks:

{Title “”}{Location “” City|City}

(If any token in the sequence were empty, then the whole sequence would fail for the alternative.)

On a practical level, I found some parsing bugs in version 46 (Lightroom 1.4.1):

– {Rating} doesn’t seem to work — it parses it as “{Rating” and complains of a missing closing brace
– Squelching multiple joiners is broken, such as in this case if there is no “State”:
{City}, {State}, {Country}

Hope that helps!

I’m like Caroline at her first comment: I’d love to be able to add a line break, but can’t figure it out, even by experimenting some HTML here and there… What is the correct syntax?

Whether you can send HTML depends on the destination (e.g. Flickr, Zenfolio, etc.). The ones that I know allow HTML have an option nearby the preset pulldown that lets you choose whether the text you write should be interpreted as html or as plain text. The others, as far as I know, allow only plain text. (Let me know if I’ve made a mistake with one.) —Jeffrey

Jefrey, thanks for the reply.
By “indicated line break” I refer to the requested/commented possibility to include a line break in the title or description preset. I’ve not been able to add.

Regarding to preset data being lost, I just updated to your latest version plugin. Now the preset is working as expected (preset template is not lost, and available every time). Looks it’s solved.

Hello,

Thanks for your great plugins. I would like to know if there are/will be tokens for capture time and month of the year, I.E. Dec, December?

Thanks a bunch,

Gonzalo

Added in versions as of Aug 29. —Jeffrey

This is brilliant, almost reason enough to upgrade to LR 2 🙂

However, I’m having a problem that I also had with previous versions – I simply can’t create empty titles! 🙂

Maybe this is a problem with the flickr api, but if a photo doesn’t have a suitable title, I like to use the empty string. I definitely don’t want the filename. I tried this template:

{Title|Headline|””}

But according to the preview that seems to result in the filename. This one also:

{Title|Headline}

I found that the preview was correctly empty if I used

{Title|Headline|Empty}

but when the images were uploaded to flickr, they had the filename as their title. Is it possible to change this?

Thanks a bunch for giving out these great tools!

cheers,
Arnar

Very nice to be able to go beyond title and caption. Are more tokens in the works to be added for other camera EXIF data beyond Focal Length? Only personally interested in Exposure (w/aperture) and ISO Speed Rating, but others might want more.

I added a bunch of these today (Sep 14). —Jeffrey

This is a really really great feature. Thank you!

Whenever I attempt to upload photos to Flickr, it never shows the Album names. As I cant choose an album, the upload always fails. In uploads to Zenfolio, it always shows them, and uploads are successful.

Excellent plugin. The option to create sets dynamically based on folder name, exif data, etc and the ability to create tags from exif data are two things I’ve been searching for. As far as I know, you are the only person to have implemented such a feature, and I think you for adding it.

A couple small requests if you have time..
– At the moment YYYY MM DD SS are all possible, but no hours and minutes. Can this be added, along with JobCode?
– Fantastic to have ISO. For Aperture you currently have Aperture and ApertureNum. Could you do the same for ISO? Ie, so ISO would return ISO320, and ISONum would return just 320? I tried doing ISO{ISO} but in the case {ISO} is not available I am just left with the string ISO
– Fractions in ShutterSpeed do not display properly in flickr (at least for me), and ShutterSpeedNum has very long fractions in some cases – like 0.834289347289347. Could you perhaps add ShutterSpeedNum4 which would truncate to 4dp? or something similar
– Last but not least, Path seems to return a full path, etc “> Users > ABC > Dir1 > Dir2 ….” I tried to use the After option to remove the “> Users > ABC > ” part but it complains “Hierarchical structions not allowed with this plugin”. Can this be fixed?
– Finally, like many others I am trying to work out how to get a newline to appear in the flickr description. I tried the html for br, and backslash n, but to no joy.

Once again, thank you very much for your hard work on this plugin.

Thank you very much. Fantastic plug-in. It would be awesome to have LR Collections. Is it anyway possible? Once again thank you!

Hi Jeffrey, and thanx for the great tool. I have yet to upload my first pics to flickr though, because i’m still trying to figure out the newline thing. I’ve read all the posts, and like others I can’t get it to work.

Seems like we have to insert a somewhere, but where ? I tried differents things like
{CameraModel} {Lens}
{CameraModel } {Lens}
{CameraModel} “” {Lens}
… but none of those worked.

In one of your replies you’re mentionning an option to check, to interpret text as html, but I don’t know where to find that option. Is it on our flickr settings page ? In your plugin ?

Finally, if we manage to get it to work, will the preview display newlines (I tried exporting some pictures to double check that it wasn’t just a preview issue but same result) ?

Can somebody who know how to do this post a sample code ? And explain about the “interpret text as html” option ?

Thanx.

Oops – some html got stripped above, it should be:

“Adding paragraph or break html tags did not work…”

N

Thanx for the tip Nathan, but I think I tried that and it didn’t work, even before I upgraded the plugin, but maybe it has to do with the fact that I’m running OSX.
Still nobody with some kind of clue to help us insert line breaks ?? Please !!

Is there a way to get the “original number suffix” field?

As post above using version 63 to get page brakes do the following (windows only)

open up notepad type in info you want on each line when you need a carriage return hold down the alt key and type 013 on numeric keypad you should see a new line created once done copy back to lightroom and past should text on each line. Tested and used works fine

Heart_and_soul

Thanks Adrian but i use Leopard.

The button “Token Examples” also didn’t work, I don’t know if that’s also a issue related to Leopard.

Hi Jeffrey,
I just changed computer and would like to know where those settings are saved.
Thanks

Your Lightroom Preferences file. —Jeffrey

Jasonn here from Trinidad…

I accidentally updated the NONE preset – and now I cant get it to be well… none lol
If I delete the fields, it disables the update button…so i’m using caption to fake it for the moment.

Just a thought, just like you cant delete the none preset, you should not be able to edit/update it as well…

Thanks,
J

I didn’t think it was possible to delete the ‘none’ preset. I’ll look into it. —Jeffrey

Hi there, is it possible to recieve UserComment or other string so I can automatically pass some Tags via Token?

Thanks
luigi

I’m not sure what you mean, either about what you want or where you want to use it. Could you drop me an email with more info? —Jeffrey

Yes indeed, the new version works perfectly. Now that’s awesome support!

I’ve been using your flickr plugin for some time, and today I’ve discovered this feature. I think it is great! Like all your plugins!

I would like to ask if it could be possible to add a link to Google maps using GPS position. Is it possible right, now? If not, could it be possible that you add this feature in a new release?

Thanks!

You can build up the link in a caption using the token templates that I’ve built into the plugin…. something along the lines of <a href=’http://maps.google.com/?q={Latitude},{Longitude}’>click for map</a> —Jeffrey

I’m using LR3b and I’ve a question regarding the auto-destination. Is it possible to use the name of the collection (as set in the Publish Service) for the PicasaWeb album name?

I think this will be quite handy.

Thanks.

Don’t know yet. Will certainly look for that when I get docs. —Jeffrey

Great work and thanks for all of the plugins you offer that make our workflow as photographers better. cheers

The matter of line breaks in the Caption Preset has been mentioned before but not being a programmer, I don’t quite understand the answer. I’m not sure if you were saying that it might not be possible for some programs. I want to have “Title” line break “Caption”. I have tried “{Title}{Caption}” in both plain and HTML but that didn’t do it. I’m exporting to SmugMug.

Add <br> where you want the line break, e.g. “{Title}<br>{Caption}”, and the line break will be inserted when you have both a Title and a Caption. —Jeffrey

Jeffrey:

I figured out the mystery (sort of) and it’s not a bug with your plugin. It looks as though any of the iPhone apps that post-process photos aren’t setting the date correctly in the EXIF tags. The native iPhone camera app DOES do it correctly though.

Oddly, when I go into Lightroom and “Edit Capture Time” on one of the offending photos, it has the correct date and time that the photo was taken — it’s just not appearing in the “All Metadata” view. I think it’s because Lightroom is looking at the “File Creation” date when the EXIF Date is missing.

So I’m suspecting either there’s a bug in the iPhone overall that doesn’t let the apps write the EXIF data correctly, or all these 3rd party apps are just lazy and not carrying over the EXIF data.

Sorry, very new at this.. How do I create the upload destination so that each folder I create in the PiCASAWEB published service appears? Currently I create each destination separately in the publishing manager? Thanks!

Publish is not really working in the Lr3 beta… best to wait for the real Lr3 to come out, using the normal export until then. —Jeffrey

Gallery Destination Question:
On Zenfolio, I have a group called “Recital 2008 Saturday” which contains galleries of the structure “D 8 The Potter waltz” and “D 9 Steam heat” and so on. I have put the gallery names into the metadata filed Caption in Lightroom.
So, my hope was that I can upload using an Automatic-Destination Preset, like this one:
“Recital 2008, Saturday >”{Caption}
but it tells me: “?:14813: table index is nil”
I also tried:
Recital 2008, Saturday > {Caption}
“Recital 2008, Saturday” > {Caption}
which always results in the same error.
Can you give me the correct string? Also, will the use of the template create galleries if they do not exist yet?
Thanks a ton!
CU
Heiko

What you are trying to do should work… I’ll take a look at it, but unfortunately even if I fix it locally, I’ll not be able to push out a new version for a couple of weeks. I’ll let you know how it goes… —Jeffrey

Keyword filter question:

I have many keywords grouped into sets that don’t export, for example individual animal names, that are also assigned with “wildlife”.

Is there a way to filter and use just those keywords that are contained within the set “wildlife” as the caption for an image?

Thanks

Not that I can think of, sorry. —Jeffrey

still wondering what values the OriginalWidth and OriginalHeight tokens return ? is it the original size of the picture or the cropped size ? i am talking about the cropped size after using the resize tool in lightroom not the cropped size that we give on export ?

Yes, that is ambiguous, isn’t it. They’re for the original (possibly pre-crop) of the master image on disk. I’ve pushed new versions that also include CroppedWidth and CroppedHeight to reference the post-crop size of the image in the library. —Jeffrey

Thanks for the great plug-in. I’m hoping to use Lightroom + Zenfolio for a huge graduation portrait project at our college in Gainesville Florida, Friday April 29, 2011. The question I have is how to Publish each client image so that they are in their own client gallery? I’m using the Caption -FileNumber as a unique identifier and I would like that to also be the client access code. My students will be processing 300-600 portrait sessions with 3-5 images each. I’m trying to setup the publish process as simple and fast as possible. Any thoughts?

Thanks,

Wes

You can use the auto-destination feature to create galleries on the fly based upon metadata, and particularly using the LUA templat you can construct arbitrarily-complex ways of converting the metadata into a gallery name. But if you want more than one image in the same gallery, you’ll need to ensure that those images all share some bit of metadata (e.g. a caption with the subject’s name). There’s nothing in the plugin that will handle setting an access code for the gallery, so that’ll have to be handled separately. But since you can have the plugin open the gallery in the browser after the upload completes, it’s hopefully not too difficult to just use that page to set the access code. —Jeffrey

Hello Jeffrey,

any way to use PhotoDate with a function like “add 1 month”? When we publish to PicasaWeb, we’d like to name the album including a “online until” – date which is 1 months after pictures are created (pictures should be removed after one month) and the visitors should be informed by an appendix in the name of the album.

Of course a template like {Folder}_Album_online_until_{YYYY}/{MM+1}/{DD} is not working. Any way to do this?

Regards from Germany,

{LUA=mm=="12" and sprintf("%04d", tonumber(yyyy)+1) or yyyy}

{LUA=mm=="12" and sprintf("%02d", tonumber(mm)+1) or mm}

{LUA=tonumber(dd) < 28 and dd or 28}

Hi,
When using the plugin to make a “full backup” of all images in 640×480 pixel, I end up getting filenames with a “-2” or “-3” at the end of some – not all – images.

Why is that?
Using Lr 3

Because, I’d guess, your file-naming rule results in the same name for multiple images. This might happen, for example, if you have virtual copies of an image, but you don’t use a file-naming template that accounts for the copy name. —Jeffrey

He Jeffrey, has there been any progress about that issue?

“It is possible for picasa plugin to use LR4 reverse geocoding suggestions whenever address fields are empty when using tokens like {City}, {Country} etc.? Now those suggestions are invisible. Or maybe create tokens like: {CitySuggestion}.”

No, this is not the speed that Adobe works on. At best I’d think it might show up in Lr5, but practically speaking it may well be something they never address. —Jeffrey

Hello,
I want to know if there are possible to convert the following parameters
OriginalWidth and OriginalHeight in cm? to position in the file name
example: {LibraryFilename OriginalWidth} x OriginalHeight pixels
{LibraryFilename} 5907 x 8865 pixels

to

{LibraryFilename} 100.0 cm x 150.1 cm

thank you

Yes, it should be possible with the {LUA} token, assuming you know what resolution you want to convert with. Using your example of 59.07 pixels/cm, you’d want the token:
     {LUA=sprintf("%s %.1f cm x %.1f cm", FILENAME, OriginalWidth/59.07, OriginalHeight/59.07)}
—Jeffrey

How do I call a function from a external lua file, loaded via load() ?
I tried it this way:
{LUA=return load(“/Users/Linus/Documents/lightroom_naming_helper.lua”)}-{LUA=wochentag(DD)}

and

lightroom_naming_helper.lua:
function wochentag (d)
days={‘sonntag’,”montag”,”dienstag”,”mittwoch”,”donnerstag”,”freitag”,”samstag”}
return days[d]
end

return “”

but I get a runtime error: “hey” unknown.

How do I get the localized weekday of the photo date?
I tried
{LUA:LC=os.date(“%A”, DD))}
but it returns the english name.
I also tried something with os.setlocale, but setlocale gives me an error (nil value).
{LUA:LC=sprintf(os.setlocale(‘de_DE’) or os.date(“%A”, DD))}

I would like to combine filters. My current workaround is
{LUA:S2D=string.lower(Folder)}

For the sequence number I use {Filename} and let Lightroom name the file with the tree digit sequence number. It would be easier if there is a sequence number function.

weekDays = {"sonntag","montag","dienstag","mittwoch","donnerstag","freitag","samstag"}
function wochentag()
   if photoTime then
      local timeComponents = { LrDate.timestampToComponents(photoTime) }
      local dayOfWeek = timeComponents[7]
      return weekDays[dayOfWeek]
   end
end

return wochentag()

To have a line break, simply select (the invisible one, unless you have show formatting turned on) & copy one from the end of a paragraph line (before next paragraph) from a word processing app & paste directly where you want it into your picture info’s custom text. Hope this helps! I just tried it & it worked for me (no plugin was required) in Lightroom 4. Your site got me going in the right direction, but then I though I’d just try an old trick.

Hi.

I have some photos (typically edited on my iPhone) that seems to be without correct EXIF data. Lightroom shows the correct capture date/time (but this could be the file timestamp) and is also able to use this date/time in smart collections, but your plugins fails when it tries to extract YYYY. Are you able to use the same logic as Lightroom does to ensure that photos that matches my smart collection criteria using date/time is also correctly handled by your plugins?

Thanks!

A photo’s date can appear in Lightroom in many ways… in the Loupe info overlay, in the metadata panel, via the plugin SDK, in how the date is sorted during import, etc. As far as I can tell, unless the photos were taken in the same timezone as your computer is now, the dates all differ among themselves. It’s maddening. I’ve made repeated bug reports to Adobe… nothing else we can do. )-: —Jeffrey

You saved my neck with the image preview -retrieve plug in. 1000 thanks and blessings to you.

Hi Guys, Jeffrey,
Thanks for great job. I’m struggling to extract a folder name from a full path.

With {FolderPath}, I can get :

Volumes/PhotoDabase/NameofAlbum/Datefolder/filename.jpg

With {FolderPath:After=PhotoDatabase/}, I can get :

NameofAlbum/datfolder/filename.jpg

What I only want to get is :

NameofAlbum

How could I do it? I’m searching for a kind of {caption:before=/} token but I can’t find out.

Could somebody provide me some support please?

Thanks in advance, regards

Fabrice

This should do it for you: {LUA=FolderPath:match(“/([^/]+)/[^/]+$”)} —Jeffrey

Hello. I hope someone can help me cause I beat against the wall but still can’t understand how to do what I want to do.
I want to insert the age of the child in Years, Months and Days, but can’t really understand how to do this with LUA… Thank you!

Calculating a time difference like that is more difficult than one might think, but yeah, I’ve wanted the same kind of thing myself, so your comment prompted me to add it. After upgrading the plugin, see the date_diff() function in the LUA template token docs. —Jeffrey

1. I would like to suggest a “replace slash with space” (or underscore).
2. Is there a way to combine/stack filters, processing the result of one with another?

I had an idea (for the Collection Publisher) where I would like to shorten the FolderPath down to the actual Lightroom structure names – and thn convert it to one string by replacing dashes to spaces (or underscore) “/some/base/directory/MyPhotos/2014/june/birthday” -> 2014_june_birthday”

I would like to be able to do something like this: {FolderPath:After=MyPhotos/:SL2S}

Your best bet is to use the {LUA} token, off the top of my head, {LUA=FolderPath:gsub(‘.*MyPhotos/’,”):gsub(‘/’, ‘_’)}

Hi Jeffrey,

In the Facebook plugin’s Metadata Management section, Sublocation/the {Location} token, City, State, and Country tokens are showing up blank in the Token Samples view and in the Example under the Caption preset setting window. Those caption fields are also blank on the final Facebook posting. However, when using those fields for filename in the File Naming Rename to: section, those values are read correctly and showing up in “Example:”. I had several caption presets for Image Caption under the Facebook:Metadata Management section, but upgrading (Lightroom? Or the plugin?) at some point may have reset the drop-down as all the presets I previously created disappeared, but not sure if that’s related? Do you have insight on the missing tokens in the caption?

Thanks,
Jen
California

Check the “Location Privacy” section of the dialog. I suspect the location has been marked “private” in the Map Module, and in the “Location Privacy” section it’s set to respect that WRT my plugins tokens. It’s a setting you can change. —Jeffrey

First of all, a big thank you to Jeffry for making these plugins and supporting users in this way. The plugings are really great and make the workflow in Lightroom so much easier.

Now I’d like to share a tip. I was looking for a way to include double line breaks. After some try and error I found a way and I’d like to share it with you.

To make a double line break, you’ll make the first line break, make a white space character, and then the second line break.

type
make a white space character by holding down ALT then type 0160 (Alt+0160) on the number keypad at the right side of your keyboard.
type

Hope this is helpfull.

A couple of questions:

1. Anyway to connect Lightrooms People to Google Photos Faces?
2. I have the People plugin along side the Picasa plugin to upload to Google Photos. I notice the {People} tag only shows up if you set a birthday on each of the People. The people lightroom plugin finds all the people but it appears to only expose them to the {People} tag if the birthday is set on a given “person.” Am I missing something here to help just get the names/faces of people in a photo to show up in Google Photo’s meta data?

The goal is to use Lightroom to set the people and then upload to Google Photos. I would love for the faces in Google Photos to be tagged via the Light room data but update the web site on Google.

I can get the {People} tag to show up as “random” meta data, but only if you set a birthday. And I can’t get it to set the Face tag in Google from lightroom. It sounds like this is supported in Facebook.

Thanks for these plugins! They are really cool.

corban

Now way to connect faces to Google yet… hopefully they’ll create an API. About the {People} tag, doh! I forgot to update that for Lr6. Will do so soon. I had indeed updated the plugin so that {People} should work with Lr6, so if it doesn’t seem to be working, please send a log with specifics about exactly which keywords are not working as you expect. —Jeffrey

Jeff:

Great stuff here.

Here’s my challange: upon import into LR, I rename all of my image files {Import Date} {Shoot Name} {Original Camera Filename}. So, for instance, the Nikon image DSC1101.NEF which I shot on August 1, 2015 during my day at the Zoo would become “20150801 Zoo DSC1101.NEF”.

When I publish on Flickr, the images are grouped differently and I’m not especially interested in displaying the shoot name, yet I want to be able to easily identify the image in LR. I’m using the LR Caption as the Flickr Title, which works well. I’d like to use the Capture Date plus the Original Camera Filename as the Flickr Caption. The problem being I can’t find the Original Camera Filename in the tokens. If there was a way to extract the rightmost portion of the LIBRARYFILENAME up to the first space, I could do this.

Possible?

Thanks,
Scott
New Jersey, USA

Lightroom doesn’t give plugins access to prior filenames, so the best you can do is try to extract it from the current filename, with something along the lines of {LUA=LIBRARYFILENAME:gsub('^.* ', '')}. Be sure to copy-and-paste exactly… the exact spacing and quote types are important. —Jeffrey

Hello Jeffrey,

any solution to export a photo with replacing the Master File? I know that Lightroom is non-destructive but I need this option to prevent Duplicates.

I tried this without success:
Command to execute for each exported picture: copy “{FILE}” “{Path}\{LIBRARYFILENAME}”

Command to execute upon export completion: del {FILES}

Thanks

I know that there are as many different workflows as there are people, but I can’t imagine that what you’re trying to do is a Good Thing. At best you’d be destroying your original files; at worst you’d corrupt your Lightroom catalog. —Jeffrey

Is there a way to use other plugin’s properties (similar to PluginProperty) within a {LUA } block? I wanted to check if the property is non-empty and include it with some text if it is.

No, unfortunately, Lightroom’s thread design for some reason limits certain kinds of database calls from certain situations, and this seems to be one such situation. I added the code to make the call, but it yields an error that I can’t work around. )-: —Jeffrey

Hi Jeffrey! I’ve just started to use your plugin, and it’s doing wonders for my workflow 🙂
I wanted to know if it’s possible to add “Flag Status” to the “Metadata that triggers republish” section?

I mark all of my edited photos as Picked, and since I have the flag status in the “Enhanced file renaming” section, it would be really helpful if picking a photo would cause a republish, so the filename would get updated in the publish service once a photo has been edited.

Would it be possible for you to add that?
Thank you!

Ligthroom is full of “Metadata that triggers republish” errors, so even if Adobe adds it (which I doubt they will… they have not made any updates since it was first released, despite many bug reports and feature requests), it probably wouldn’t work reliably. )-: —Jeffrey

Hi Jeffrey,
Many thanks on the plugins, you are the go-to guy on all things lightroom in my mind.

Im looking to add gps location onto images from another already geotagged photo with the same folder.

Essentially, when you were to drop an image into the folder the plugin is scanning, it would automatically geo-tag the image, and move it into another folder. ( possibly one connected to google earth to then display the images on a map module accessible to more than just the lightroom user.)

Is it possilbe to do this using Lua to copy location data from one image to another?

Many, many thanks,

Tom

It all sounds possible, though you’d have to develop your own plugin to do it. My Geoencoding-Support plugin can copy the location info from one image to others, but it’s manual, not automated as you describe. —Jeffrey

Hi Jeffrey,

ust wanted to say thank you for putting all this amazing info together and many thanks for all these great plugins. So much info will have to digest. Well done, thank you and have an amazing week.

Kindly Simon

Is it possible, in a photo caption to tag a Facebook Page (or person) so that when it’s uploaded to Facebook, it is understood as a tag and not just caption text?

You can tag people this way, via my People Support plugin. Other things, sorry, no. —Jeffrey

I’d like to be able to upload images to specific Flickr albums based on keywords.

Can this be done using tokens?

Not with tokens, but you can make keyword-based Smart Publish Collections that target specific FB albums. —Jeffrey

Hey Jeff,

Thx for this Plugin. You have listed the “Newline” token here but when I want to use it on my template Newline is not recognized.

My Version: facebook-20170403.401

Thy for your help

Oops, sorry about that, I hadn’t pushed out all the affected plugins yet. I’ve just updated the Facebook plugin. —Jeffrey

Hi Jeffrey,
First, thank you very much for this plugin, it’s a real life saver!

I’d like to rename my photos using my collection structure, as it seems to be possible with the folders (with the =+8 for the 8th level of hierarchy for example).
Is it possible to add a token like this?
Thanks in advance and keep up the good work!

No, sorry, not easily possible at all. Lightroom doesn’t give a plugin easy access to the list of collections that a photo might be in, but even if it did, what should be done when a photo is part of more than one collection? It would be computationally-intensive just to get to the point of this can of worms, so it doesn’t seem worth it. —Jeffrey

I’m seeing that the various filename tokens that claim to return a value “without path” do indeed include the full path for the file. (Using Run Any Command.)
Ferg — Bellevue, WA

Would you mind sending a plugin log after encountering the problem? Thanks. —Jeffrey

Hello Jeff,
I was wondering if there is a way to extract the date and time from whatsapp images name and put this in the lightroom field of “Date Time Original”.
For example the file name is “WhatsApp Image 2018-04-25 at 00.44.58.jpeg” and I want to extract the “2018-04-25 at 00.44.58” and fill the “Date Time Original” with this information.
I think that this a useful procedure when your have a lot of whatsapp images and are importing them to lightroom.
Let me have your thoughts about it and how to create this procedure.
Regards,
Thales

Sadly, a plugin can’t update Lightroom’s idea of the photo date, so you have to do it with Lightroom’s date-changing UI, or perhaps inject the date metadata into the file before importing it into Lightroom. —Jeffrey

I am using the Enhanced File Renaming feature in Collection Publisher. My Filename Template value is

{LUA= load(“/Users/pearsonb/Documents/Adobe/Lightroom/PublishFileRenamingX.lua”) }

and the PublishFileRenamingX.lua file contains the following:

function x()
return “Brian”
end
return x()

and I am getting the following results in the Example field:

bad argument #1 to ‘?’ (function expected, got string)

This used to work just fine; I don’t when thing changed… after an update of LR or Collection Publisher.

Note, the example here is a simplified version of my ‘production’ code; I dummied it down for this comment.

I am running LR 7.3.1 on Windows 10. Any suggestions?

Goodness, that’s my fault, sorry. Law of unintended side effects from another change. Good catch. I’ve pushed out a fixed version. —Jeffrey

Hi,

I’d like to run some {LUA} code with the “Run Any Command” plugin, but whatever I try, it fails.

I tried the very same function as Brian posted back in June (http://regex.info/blog/lightroom-goodies/template#comment-58089) .

For instance in a custom commad :
echo ‘{LUA= load(“/path/to/my/script.lua”)}’ >> “{desktop}/test.txt”

where script.lua is
function x()
return “Brian”
end
return x()

It fails with this message: Runtime Error: bad argument #1 to ? (function expected, got string)
but the same token works with the “Collection Publisher” plugin.

Any idea ?

Thank you

macOS Sierra 10.12.6
Lightroom Classic CC 7.4
Run Any Command Export Filter 20180527.99

It’s working for me… are you sure that you’re using “dumb” quotes, and not the smart quotes that my blog uses when displaying comments? If you cut-n-paste, you have to go through and update both single and double quotes to be the old dumb kind used in programming. (Also, in your script, you don’t need to use a function… you can just have your code ending with the “return” line. m—Jeffrey

Hello,

i am a beginner.

Are the following things possible with the plugin “Run any Commads”?

During the export with a command to convert uppercase letters in the file name to lowercase?

And is it possible during the export to let umlauts erupt through them?

Or does something work with another plugin?

Many Thanks. Thomas

Umlauts should be preserved during case conversion. If you see some error, please send a plugin log with a note about exactly what is happening, and how it’s different from what you expect. Thanks. —Jeffrey

Hi Jeffrey. Thanks for your brilliant plugins.

I’m using your Folder publisher plugin and I’m trying to get it to include keywords below a certain parent keyword to be included in the file name, up to a set maximum length. For some reason this doesn’t seem to work.

Here’s what I’ve put into the Enhanced File Renaming:
{Filename} {Keywords:DescendantOf=NAME:Length=194}

The point is to include people’s names in the filename, but without breaking the maximum character limit in Windows.

Would be very greatful for any suggestion as to how I could do this.

I had a bug that stopped the standard filters from working with the keyword-special ones; I’ve just pushed a new version of the plugin that fixes it, so your example should then work. Thanks for the report. —Jeffrey

Hello! I really need your help. I use the plugin ” run-any-command”.
Code that execute:
“{home}\AppData\Roaming\Adobe\Lightroom\Software\ImageMagick\convert.exe” “o:\OneDrive\Work_Lightroom\logo\_for_ViewBug_{PluginProperty=lr.CustomMetadata.DMI_Side}.png” -channel RGB -fuzz 99% -fill #000000 -opaque black “{folder}\000000.png” && “{home}\AppData\Roaming\Adobe\Lightroom\Software\ImageMagick\convert.exe” “{folder}\000000.png” -fill #{LUA= load(“C:/Users/ADrobkov/AppData/Roaming/Adobe/Lightroom/SingleFile/ColorMain.lua”)} -font Rosarina -pointsize 61 -annotate +18+54 “DROBKOV” -fill #{LUA= load(“C:/Users/ADrobkov/AppData/Roaming/Adobe/Lightroom/SingleFile/ColorMain.lua”)} -font Rosarina -pointsize 27 -annotate +232+84 “FOR” “{LUA= load(“C:/Users/ADrobkov/AppData/Roaming/Adobe/Lightroom/SingleFile/ColorMain.lua”)}.png” && “{home}\AppData\Roaming\Adobe\Lightroom\Software\ImageMagick\composite.exe” -dissolve 90 -geometry +1000+100″{folder}\{LUA= load(“C:/Users/ADrobkov/AppData/Roaming/Adobe/Lightroom/SingleFile/ColorMain.lua”)}.png” “{FILE}” “{FILE}”

Swears on the line: {LUA= load(“C:/Users/ADrobkov/AppData/Roaming/Adobe/Lightroom/SingleFile/ColorMain.lua”)}
Error: Runtime Error: “import” unknown

Tell me, is there a way to fix this? I’m not a programmer, do everything to search the Internet, but here I can not understand how to do

Hello Jeffry,
my Lightroom setup relies heavily on your plugins, but I have a few issues with “FolderWatch”:
1st: is it possible to backup my configuration because I’ve already lost my Lightrom config a few times.
2nd: When importing Videos, the timestamp for the filerename is usually wrong. How can we find the issue? I know, Lightrom itself has massive problems with file-rename of videos depending on the timestamp “video created”
3rd: I know, it is possible to watch more than one folder – but is it also possible to move into according subfolders during import?
Thank you!
The configuration is saved in your Lightroom Preferences. If some part of your preferences are suddenly lost, they might be going corrupt, so please see this FAQ. I highly recommend Matt Dawson’s LR Backup plugin to save a copy of your preferences (and other non-catalog data files) on a regular basis. About video times, given Lightroom’s atrocious handling of them, and Adobe’s apparent lack of caring, I feel it’s a lost cause. )-: I don’t understand your third question, sorry. Feel free to mail me with more details. —Jeffrey

Is there any chance to add the hashtags by the instagram plugin?

Depending on how that plugin works, you may be able to access them via the {PluginProperty} tag —Jeffrey

Hello Jeff,

I tried to understand your example of “The special {NOJOINERS} token”, but I couldn’t. Can you provide me with another and be more clear? What is the span? is a token? A field?

Another thing:
On the zenfolio Metadata Management section, I want to create a preset for the Title somehow like this:
{Title|Headline|Filename} – {JobIdentifier} – {###},
but if the value of {Title} is equal to the value of {JobIdentifier} I want to exclude the JobIdentifier, otherwise, the information will be in double.
The result will be something like this if {Title} is equal to the value of {JobIdentifier} the output will be:
{Title|Headline|Filename} – {###}
I tried to figure it out but nothing seems to handle this case. Maybe a code in LUA could handle the situation, but I don’t have any knowledge of LUA language.
Can you provide me with some guidelines to handle this situation?
Thanks

{LUA= A=Title or Headline or Filename return A==JobIdentifier and A or  A.."-".. JobIdentifier} - {###}

Hi – love this plugin – thanks so much. Is there an escape character such that i can include brackets in the command, such that I can use exiftool commands that themselves require (as far as i know) braces (e.g., “-subject<${subject;NoDups}")? If no escape character, any clever syntax I can use to get around the issue of the plugin trying to recognize the brace as signaling a token? Thanks so much!

Unfortunately, no. The way that the token language evolved over time has left it quite fragile, and so I’m reticent to make big changes. There may be a way around it (perhaps using a file holding exiftool args), but I suppose it depends on how you’re using it, and what you want to acheive. Perhaps drop an email with more info… —Jeffrey

Thanks for your help, no idea why but the syntax {LUA=} is works after I re-install the Adobe Lightroom and the plugins,

Regards, George

Is there a way to make the whole path lowercase, I can get the filename lowercase, but I need the whole path lowercase

I’m not sure which path you’re referring to, nor in what context, but (for example) {FullExportedFile:LC} gives the full path of the exported copy, lowercased. —Jeffrey

Hi, I am very happy with your tool. But know I have to solve a big problem.
I need to change some special german charactes during export in the filename and Foldername.

E.g. \Brüssel Äpfel\Brüssel Mögen Tour.jpg

should be exported as:

\Bruessel Aepfel\Bruessel_Moegen_Tour.jpg

So, all spaces should be “_” and some characters have to be changed. “ä” “ö” “ü” “ß” “+” “&” should become “ae” “oe” “ue” “ss” “_und_” “_und_”

Is this easy possible with a function?

Thx – and Stay healthy! Stefan

This is much more difficult than one should think it should be. How to integrate with Lightroom so that it gets the new names depends on where you’re trying to use it, but in any case there’s the problem with identifying the characters that you want to target. Lua, the underlying language for Lightroom plugins, doesn’t understand Unicode, so it doesn’t understand that “ä” is one character. And even if it did, “ä” might not actually be one character… Unicode allows it to be expressed in two ways (as the single-character “ä”, and as the combination of “a” and a zero-width umlaut). It just makes everything a mess. You could probably use the LUA tag to get something that mostly seems to work, but it wouldn’t be guaranteed to work in all cases. —Jeffrey

Hello, and thank You for Your plug-ins. I installed Your Run Any Command but I am an absolute novice and in need of some help. How do I make LR to actually do something? I should do this: on export LR should add the exported images to a certain dumb collection. But I could not find any help concerning the actual commands how to do this? What are commands I use, what is the syntax? I do not not how to begin. As You see I have absolutely no experience in this but I realize that I could do much more with the plug-in.
Could You please help me a bit? Just give me a push:)

Yours

Väinö Louekari

Just leave the command stuff blank, and choose your target dumb collection from the dropdown near the bottom. —Jeffrey

Hi Jeff,

In version 9.2.1 there is no “Use typographic fraction” on the “Interface” tab.
Image of the tab here:
https://drive.google.com/file/d/1QkRWZvaaZ70ZtxG_pvHMlPAqmhcWH_qZ/view.
Want to add any comments?

Cheers

Wow, I didn’t realized that the option is a MacOS-only option. I can’t imagine why that would be; I’ve reached out to Adobe to ask. —Jeffrey

bit confused. Is it possible to geoencode AND put what3words into caption/keywords or whatever… whats the token. Im feeling very blond hehe

There’s no Template Token for what3words, because in order to compute it the plugin has to call out to their servers, and technical limitations with how Lightroom works makes this very difficult to handle as a token. That’s why it’s a separate process in the “Etc” tab. However, if you know that you’ve put the w3w code into a specific metadata field, you can then access that metadata field via a template token…. —Jeffrey

Hi Jeffrey,
I’m writing from Fairfax, Virginia, located outside of Washington, DC. I’ve just started working with Metadata Wrangler and I’m really enjoying the capabilities of this plugin!

I’m using macOS Catalina version 10.15.7, Lightroom Classic release 10.0, and Metadata Wrangler version 20201017.189. I’ve got a couple of token formatting questions.

When using the {GPSCoordinates} token is there a way to limit the total number of digits? For example can the GPS location 37°56’43.9442″ N 23°38’39.9981″ E be shortened to 37°56’43.94″ N 23°38’39.99″ E?

Also, similar to the Khürt Williams question back on May 3, I’ve got the “Use typographic fractions” option turned off, but {ShutterSpeed} still exports as a typographic fraction. Any ideas?

The token {LUA=GPSCoordinates:gsub('(%.%d%d)%d+', '%1')} should give you the coordinates that you want. Lightroom doesn’t honor the “Use typographic fractions” option for plugin metadata requests, but I just added something to work around it: {ShutterSpeed:PF} should work (after upgrading your version of whatever plugin you’re using it in). —Jeffrey

Hi Jeffrey,

(1) I’m using Template Token to rename files when exporting collections with your collection publisher – I found strange thing when using {HH} with some files :
{HH} and {T2} refer to the same hour of the day (ie 10) but with {ISO8601Date} the hour is different (ie 19).
In my case the {ISO8601Date} is correct – it shows the same time like LR. Might be correlated with timezones / time shifting

(2) how can I export {HH} and {ISO8601Date} to a txt file to check the differences? I used LUA code and “collect data for spreadsheet export” but after using “data explorer” with >1k files there seems a problem with the export buttons in the generated output window

Any ideas? THX

The way Lightroom handles dates is a royal mess. It could be a timezone issue (between the timezone where the photo was taken and what your computer is set to now), or it could be that you used Lightroom to update the time. Or just yet another Lightroom bug. You can try using my Geoencoding plugin to set the timezone for the relevant photos to see whether that fixes things. If it doesn’t perhaps export a few of the images to a stand-alone catalog and send it to me to test with? As for looking for photos that this happens to, using Data Explorer with “{LUA=ISO8601Date:sub(12,13)==HH}” should do it. —Jeffrey

Feature Request

Hi Jeffery, I am using several plugins, to interoperate between Lightroom, WordPress and Alamy.
My goal is to link images presented in WordPress pages to Alamy selling pages.
The Fieldname produced by the LR Plugin Alamy Lightroom Bridge is called “Alamy URL”
I am using WP/LR Sync to publish from LR to WordPress. This Plugin understands the following list of custom fields: https://meowapps.com/wplr-sync-custom-fields/

Something that could fill the gap, would be, if your “write data filed” could read the Alamy URL and write it to any of the available fields

As per the PluginProperty token, I’d guess it’d be along the lines of {PluginProperty=com.jkeir.lightroom.alamyupload.url}, but you’ll have to ask the plugin author whether that last “url” part identifies the field you want, and change it if not. —Jeffrey

Hi Jeffrey.

I’m using your Folder publisher plugin and I’m trying to get it to include keywords to be included in the file name, up to a set maximum length, without breaking the maximum character limit in Windows. For some reason this doesn’t seem to work.

Here’s what I’ve put into the Enhanced File Renaming:
P{YYYY}{MM}{DD} {HH}.{MM}.{SS} ({Keywords:Length=100})

I know this topic has been posted before, but it still seems not to be working.
I’m using LR Classic CC version 7.2

Would be very greatful for any suggestion as to how I could do this.

I think I’ve fixed it. Either that, or made it worse. Due to poor design on my part more than a decade ago, the code in this area is just horrible, and really fragile. If I were to fix it and make it right, I might break things that people rely on, so I have to tread gingerly. —Jeffrey

Is there a substring function? I accidentally named my files incorrectly.
Ex. PHOTO_12345 Should be PHOTO_22345. The “_1” should be “_2”. I was hoping to extract the “2345” portion and then just add a “2” when I renamed the file.

You can use the LUA token to access the power of the underlying language, e.g. “{LUA=Filename:gsub('PHOTO_1', 'PHOTO_2')}” —Jeffrey

Thank you Jeffrey! I appreciate your help! 🙂

Regarding my keyword “OFF” issue. I am using the Metadata Wrangler plugin which I just found when I was wondering how to add rating keywords for LR Published Services exports for Photos app for iPhone synchronization (as iTunes Folder Sync is very unreliable). Photos sync in iTunes seems to work better. So I am very happy I can add “5star” and “4star” etc. keywords at the export automatically from my ratings.

But I also have keywords in LR ending with the word OFF. Let’s say I have a coworker who mostly is in pictures regarding work and I mostly present photos at work. Some photos are from vacations and I have given those an extra keyword “JimOFF” so that I can have exports with only work related photos (in LR Smart Folder “does not contain OFF”). Now for Photos and iPhone I would like all my pics to have either yesOFF on noOFF keyword. Then I can search on my iPhone for photos “noOFF” and only work photos would show. Or vice versa, searching for lets say “yesOFF” would let me share fun moments out of work.

So, can the IfKeyword have a “contains” or “does not contain” option so that I could make it search for etc. “JimOFF” and then an extra keyword like “yesOFF” would be written in the exported photo and if no “OFF” word is found then “noOFF” would be the written keyword.

I am trying to set up your export to tweet plugin.

I am entering the following into the token space ‘{Title|Filename}, Shot at {Keywords:DescendantOf=.places}, {YYYY}.{Keywords:NS=#%s}’

intending the keywords to come out as hashtags. However I have only been able to get either spaces removed from the keywords, or a # added before the keyword. I can’t work out how to get both working together. Also I can’t work out how to remove the commas between each keyword (if that is indeed possible).

Could you tell me what I am doing wrong please? This sort of thing is not my forte lol.

Thanks

Lisa

Officially the “=#%s” thing doesn’t work with filters such as “:NS” (because the code was designed poorly early on, and grew into a horrendous patchwork of kuldge), but I just added another patch that should get it working in this case. Currently it’s not possible to change the commas inserted between each keyword. —Jeffrey