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

Yes, that is correct. A plugin can’t know whether there are suggestions, or what they might be. I hope Adobe will grant this access in the future, but for now it’s not possible. —Jeffrey

“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

Hi Jeffrey,
I’ve tried to have only 4 NEF images located in one folder. The file names are 0001.NEF, 0002.NEF, 0003.NEF and 0004.NEF.

When running the plug-in, they would be outputted in the correct folder, but with these file names
0001.jpg, 0002.jpg, 0003-3.jpg and 0004-3.jpg.

There are no other files in this folder and my settings are following:
Export as JPG and resize to 640×480 at 72 PPI. No re-naming has been set.

All the best,
Chris

This is all controlled directly by Lightroom so I can only guess, but I’d guess that they never want to name a JPG with the same basename as a raw file, because Lightroom normally treats that as a coupled pair, and considers the JPG a sidecar of the raw file. Since that’s clearly not the case when you’re creating the JPGs out of camera, they change the target filename to avoid the conflict. —Jeffrey

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

I know you use Phil Harvey’s EXIF tool for various things in your plugins. Is it possible to build a token that would allow the user to input the field to be read out of EXIF for use in the caption and/or title?

I’m thinking something like {EXIFtool:xmp.film} that would result in “Velvia 50″ or whatever happens to be in that field for that image.

In short, I’m looking for a way to exposure more EXIF data than what lightroom recognizes… inside your title/caption presents.

Thanks,

John

That’s a good idea, except that it then requires that I bundle a full ExifTool executable with each plugin, and fire off a separate process for each caption. Those are not brick walls, but at this point enough of a weight to keep it from bubbling up on my todo list… —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}

No, you’re not missing anything… it’s not there. It’s not necessarily as straightforward as some of the other items, but I’ll give it some thought. —Jeffrey

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