Search & Replace 1.45

I’ve just released version 1.45 of my Search and Replace plug-in over at Photographer’s Toolbox .

This version is a significant upgrade. As well as including new Lr5 fields, I’ve updated the layout and added some handy new capabilities.

  • New: On Transfer tab, you can now save combinations of fields as Favourites
  • New: Replace characters in a text string (eg 12 through 25) – the beta version was used here
  • New: When appending a sequence number, user can now set the initial value
  • New: Lr5 fields available (smart previews, video)
  • New: Thumbnail of image shown ((Lr4 or upwards)
  • New: Creation and modification date and times available
  • New: Search and replace for text in keyword names
  • User able to switch off translation of fields in plug-in’s dialog boxes
  • Menus available when only video files are selected
  • Fixed: Bug in parse and audit where field length greater than 512 characters
  • Fixed: Bug fixed preventing previous tab being displayed upon startup
preview image

The layout is now clearer and Lr5 users will be able to preview the plug-in’s results next to the affected image.

“Read more”…

Charts too?

Since I know at least 4 (!) people found my “not more numbers” post interesting, I’ve just added a link on this site’s home page to Adobe’s stock price.

I’ve heard plenty of crazies pointing with some glee to a 10% drop since the May’s announcement that Adobe were only offering Photoshop and Creative Suite customers the choice of subscribing. I’m not sure those people have been so vocal about the price’s stabilisation and  then its partial recovery last week after the subscription-limited suite was actually released.

You just can’t pay too much attention to short term movements, or consider Adobe in isolation from the market, consider one factor on its own, or just over-simplify the headline movement.  Adobe have smart people and they’ll have anticipated some stock price turbulence resulting from the business risk they have suddenly introduced. Maybe it’s a success that you’ve not fallen off a cliff after such a leap in the dark?

share-priceSo here you see the year-to-date stock price movements (from Yahoo – I’ll see if I can make it live) with a rolling average which evens out the short term bumps and grinds.

The general trend of the last year or so has been consistently upwards, and it has only levelled off after Adobe’s “Great Leap Forward”.

Only time will tell if this is short term volatility owing to (temporarily-greater?) risk.

Not more numbers!

Screen Shot 2013-06-19 at 20.35.51Look, I spent all those years in accounting, so you’ll have to humour me when I point you in the direction of more financial numbers from Adobe. In fact their stock price never really interested me until recently, so I can readily understand if you have never gone looking for their quarterly results, but do take a look at Adobe Reports Strong Q2 FY2013 Financial Results and the more-digestible powerpoint slides.

There’s probably just one nugget of information worth polishing and keeping in your pocket – they have now reached 700,000 subscribers to their Creative Cloud. So those 700,000 have voluntarily chosen the subscription route over buying a traditional licence. They’ve probably made a rational decision too.

Going forward, new customers and upgraders are no longer offered any choice – you either subscribe, or you don’t upgrade. With the only option being this Hobson’s choice, I wouldn’t be at all surprised if in 6 months’ time they Adobe hit or exceed their published target of 1.25 million subscribers at the year end. The cynic in me, or just the former corporate accountant, believes you don’t publish numbers you won’t meet, so you just have to wonder what the real target is. But prepare yourself for Adobe trumpeting this somewhat-hollow success….

Wouldn’t it be great if you could subscribe and tick a box asking not to be included in the count of the willing?

OS support

percentagesHere’s an updated analysis of visitors to this site comparing the proportions using Mac and PC operating systems.

As I’ve said before, you’d have to be pretty crazy to visit this site of you’re not a Lightroom user, so I think it’s a pretty good approximation to the wider user base.

The 60%:40% Mac:PC split shows a continuing drift to Mac – a year ago it was 50:50.

But for me the most interesting detail is the less than 6% using Mac 10.6 or Snow Leopard. Lightroom 5 will not run on that OS or on Vista, and that figure happens to be about the same level as Windows XP users when Lightroom 4 came out last year.


Lightroom 5 favourite no 5: AutoSync and local adjustments

So we get to number 5, and I think this qualifies as a “you read it here first”! AutoSync now works properly with local adjustments!

To explain, especially for those who have never used it, I’ve always been a huge advocate of Lightroom’s AutoSync. When it is enabled you continue working on one image in Develop, but your adjustments automatically apply to all the pictures that are selected in the film strip.

AutoSync is wonderfulwith any series of frames where you want to make the same adjustments to each shot. Last weekend, for instance, I managed to accidentally underexpose more than 30 frames by about 4 stops. They all needed the same exposure, shadows, contrast, luminance noise tweak etc, and AutoSync meant I could quickly correct them all.

Or consider how workflows like the one shown below where I’m working on the component frames for a stitched panorama. Before they are sent over to Photoshop, they need the same colour corrections and dust spotting:

  • With AutoSync enabled, I just correct one image’s spots and drag adjustment sliders, and all six frames are updated without any further effort.
  • Without AutoSync I would have to pause at some point and sync the adjustments. That means I have to press the Sync button, review the settings dialog and clear any adjustments I don’t want to sync, choose which ones I do want to sync, and click OK.

Because AutoSync means simultaneous adjustment, it’s the fastest way to work in Lightroom, so I leave Develop set to that mode all the time. I’ll only disable AutoSync occasionally, for example when I decide I want an adjustment to apply to a single image, but more often in such cases I’d just deselect the other images while I make that specific adjustment.

Incidentally, you should leave Lightroom set to AutoSync all the time or leave it switched off all the time – one way or the other. I recommend leaving AutoSync on, but other people leave it switched off and go into it when needed. They may not be working as quickly or consistently, but you don’t want to confuse yourself by continually switching between AutoSync and normal modes, and you can easily make annoying mistakes if you’re not concentrating 100%. So I recommend leaving AutoSync on all the time, and keeping an eye on the film strip. Work one way or the other.

Unfortunately, AutoSync always had an annoying limitation – it didn’t include local adjustments. So in Lr4 I might add a graduated filter adjustment and it wouldn’t apply to the other selected images, so I’d be forced to go back and sync. Apart from interrupting my mental flow, it was 5 or 6 keystrokes where a single one would have done the job. What a bore!

That annoying limitation has disappeared with Lightroom 5. It’s something I actually discovered by accident, but apparently it is a deliberate change by Adobe. At last, local adjustments are applied in AutoSync mode! Brilliant!

I’ve exaggerated the graduated adjustment here, but now you can simultaneously adjust multiple images with graduated and radial filters or paint with the local adjustment brush.

Lightroom 5 favourite no 4: PNG files

For some people this is a tiny feature, but I’ve always been a supporter of Lightroom being able to catalogue all types of files, so I welcome Lightroom 5′s ability to catalogue PNG files.

Lightroom is supposed to help manage the workflow from shoot to delivery, so it should be the photographer who decides what types of files are part of photographic projects. After all, while a project will be centred on photography, it can often contain files created in Microsoft Office, PDFs and InDesign files etc. It’s simply a waste of energy, and confusing, to be unable to use a single program to manage all these files.

Sadly arbitrary limits remain in Lightroom 5, but video cataloguing arrived in version 4, and we now have PNG files too.

Progress, one file type at a time.

Lightroom 5 favourite no 3 – Managing hierarchical keyword lists

I’m not a big fan of hierarchical keyword lists, although I gladly acknowledge I am unusual in believing they are more trouble than they’re worth. It’s not that I blame Adobe for introducing them, or that I think people are wrong to use them – more a case of saying be careful what you wish for.

Filter Keywords in Lightroom 4

That doesn’t mean I don’t keep experimenting with adding some structure to my own flat keyword list, and I also encounter them in other people’s catalogues. By their nature, longer keyword lists are always unwieldy and they become even more awkward when there is a possibility that that the same keyword may exist in multiple hierarchy branches. So I’ve always been a fan of the Filter Keywords box at the top of the panel.

You type in a few letters and the long list is filtered to keywords containing those characters. Sure, it could do with improvements and has a tendency to list too many irrelevant keywords. For instance, if you typed “Eng” with the intention of finding England, English and other variations on the country, you would see keywords like engineer, engineering, engine, Stonehenge, Engels etc. How big a problem is that? So you type “Engl” and filter out those false positives.

Filter Keywords in Lightroom 5

However, one huge limitation of filtering a hierarchical keyword list was that you wouldn’t then see the children of the filtered keywords. For example, here I’d typed “IPTC” into Lightroom 4 and I could see that “~IPTC Locations” had keywords below it, but I couldn’t see what they were without clearing the Keywords Filter.

Keyword lists are inevitably long and difficult to manage, so it’s important to have a number of ways to visualize them. No single view can ever be right, and the previous lack of flexibility only succeeded in giving me another good reason for my avoiding hierarchical keyword lists and not gaining any advantages from them.

Lightroom 5 has a new option to resolve this problem. You click the little arrow next to the magnifying glass and check “Show All Keywords Inside Matches”.

Filter Keywords in Lightroom 5 – there’s now an option to display the child keywords too

This changes the behaviour of Filter Keywords so that all the matching keywords are displayed along with their children.

It’s a small, subtle improvement that makes your keyword lists more manageable.

The question for me is, will it make me change my mind about using hierarchical keyword lists? Not yet, but maybe.

Lightroom 5 favourite no 2: Radial Filter

The new Radial Filter was originally envisaged as a movable vignette tool, so when you first drag it over part of the image you’ll find that its adjustment affects the area outside the circle.

In some cases that’s fine, but it does seem counter-intuitive, not least because  you soon find that this Radial Filter seems much more than a vignette tool. To me it feels much more natural when you use it to target the specific area inside the circle rather than affecting the area outside. In fact, very often I’m now employing the Radial Filter instead of reaching for the Local Adjustment Brush.

To do this, just tick the Invert Mask check box.

If you also prefer to use the filter for targeting rather than vignetting, it’s best to change the default. Start a new Radial Filter and immediately tick the Invert Mask check box. From now on, each new Radial Filter will be “inverted”.

Other tricks:

  • Start from the exact centre of where you want to apply the filter. So for example, you don’t apply it to a face by clicking on one ear and dragging to the other – you click the nose and then drag outwards.
  • Shift + dragging constrains the filter to the current shape – usually a circle
  • Reshape a Radial Filter adjustment by holding down PC:Alt Mac:Opt and dragging one side
  • Rotate an adjustment by moving the cursor just outside the circle

You can duplicate and move these Radial Filter adjustments:

  • Move an adjustment by dragging it
  • Duplicate a Radial Filter adjustment by dragging its central point while holding down PC:Alt+Ctrl or Mac:Opt+Cmd

My suggestion is to avoid using the Adjustment Brush for a few hours and use the Radial Filter for most dodging and burning operations. You’ll be surprised how well it works.

Lightroom 5 favourite no 1: the Visualize Spots mask

The most obvious and welcome improvement to dust spotting is that you can now drag the brush over an irregularly-shaped area, so you can wave a fond goodbye to the days of removing telephone cables by pretending they were a series of dust spots. In fact, when you are correcting a straight line you can click one end, then Shift and click the other extreme, making Lightroom draw a correction “spot” along that axis. In an example like this, I might still make a series of corrections in more detailed areas, or even switch to Photoshop, but this can be a big time saver.

A changed shortcut

Incidentally, a tiny change is to the shortcut for correcting a dust spot while simultaneously setting the spotting tool’s default size. Previously you would hold down PC:Ctrl Mac:Cmd and drag, but LR5 changes this shortcut to PC:Alt+Ctrl Mac:Opt+Cmd. It’s a trivial change, not ordinarily worth mentioning, but it will trip you up if you already used that feature or be a pleasant surprise if the tip is new to you.

The wonderful Visualize Spots mask

A much more significant improvement to dust spotting is rapidly becoming a favourite, especially when dealing with landscape photos shot with smaller apertures – Visualize Spots.

Ever since we’ve been able to correct sensor dust spots in a raw converter (something that seemed revolutionary in its day) I’ve always found that the biggest problem has been finding the spots. Some are obvious, of course, but sometimes you only notice the more subtle spots when you are reviewing a print, or in the worst cases when someone else is looking at it. So my old method to avoid this costly or embarrassing moments was to begin dust spotting by applying 4 doses of +100 Clarity in the graduated filter (via a home-brewed preset) which really made the less-obvious spots stand out. Afterwards I’d reset the graduated filter. That workaround is now a thing of the past.

Lightroom 5 adds a little Visualize Spots check box and a slider:

You tick the box, and as I have found no good reason for setting the slider at anything below 100%, I just whack the slider up to 100%.

The photo is shown as a mask with dust spots identified as little white bagel-shaped circles. Even subtle ones suddenly become nice and obvious. Here, for example, you can see 3 or 4 spots that I’d initially overlooked.

For me the only thing that would make this feature completely-perfect is if it followed the visibility setting from Tools > Overlay. I leave this set to Auto, which means I can quickly move the cursor outside the frame and evaluate the final results without the distraction of the spotting tool’s circles.

Sadly this Auto option doesn’t affect the Visualize mask. Instead there’s a keyboard shortcut – A.

  • Pressing A will disable Visualize Spots exactly like unticking the checkbox
  • Hold A down so that the mask is temporarily hidden and reappears as soon as you release the key

While this shortcut is “good enough”, at least for a right handed person whose left hand is free to lurk over the Q and A keys, I wonder what a left handed person would make of it. And it is pretty silly to be forced to use both the mouse and the keyboard when a simple flick of the cursor would do the job. Maybe next time?

That’s a minor quibble though, and this Visualize Spots box is certainly an excellent addition. You do a better job cleaning up those dust spots, and do it faster too. What’s not to like? Apart from discovering that your camera’s sensor isn’t as clean as you hoped….

Lightroom 5

splashAs you may now know, Lightroom 5 was released yesterday, Sunday 9th June. For more about it, see the official Lightroom Journal and Adobe’s What’s New page.

To be honest, there’s not a lot that’s revolutionary in Lightroom 5, and you may reasonably guess that it may have suffered from a development cycle curtailed by Adobe’s decision to kill off the Creative Suite in favour of the subscription-limited Creative Cloud.

So 5 has none of 3′s radically-improvements to shadows and lens corrections, and none of 4′s wonderful control over highlight tones and detail recovery, plus new Maps and Books workspaces.

It’s a bit harder to get excited with a release where the improvements are mostly small and incremental, and I wouldn’t blame anyone for asking if it contains enough goodies to consider upgrading if you’re already happy with 4? On balance, I think one can say yes, and that’s because the improvements include many that are practical and which improve the overall experience.

So in 5 short posts I’ll highlight my favourite, perhaps less-obvious features. One or two might surprise you.

I’m not including the new Upright Lens Correction, although I do like it very much. You can see how a single click fixed the picture below, leaving the column (left) vertical and straightening the wood panelling on the right. If you take a lot of shots with architectural elements, you’ll like Upright.

Nor am I going to include Smart Previews. They’re interesting, especially so if your usual working machine is a laptop and you frequently work away from your originals. That’s not the case for me, so it’s “interesting” rather than exciting.

So in ascending order of delight:

AutoSync does local adjustments. Oh yes!


List View 1.66

I’ve just released version 1.66 of my ListView plug-in which displays images in a list style just like in most other DAM programs and lets you export metadata to Excel or other apps.

The update includes some Lr5 compatibility changes and some extras metadata fields requested by users:

  • Option to replace spaces in column headers (needed for some mail merge operations)
  • Blank column does not export
  • GPS latitude and longitude as decimals (for integration with other systems)
  • Colour label text
  • Smart preview information (LR5 only)
  • UUID

If you use ListView and have your own special requests, just ask…..


To be or not to be?


This was interesting – the Financial Analyst Briefing Slides from last week’s Adobe Max conference. Yes, you read that right – the financial analyst briefings are interesting.

As a former accountant who is genuinely frustrated that the 2013 Q1 earnings report lacks detail, the financial analyst slides count as light reading! And the great thing about financial information, you’ve got to be more truthful in your communications with investors than in mere marketing hype (although such relative truthfulness didn’t help those triple A rated banks that vanished in a puff of smoke).

It’s most interesting from page 24 where there’s a breakdown of Adobe’s Creative Suite revenue (the whole suite, not just Photoshop) showing 10% comes from home individuals. That’s more than I expected, and 25% from education seems reasonable. I’m not sure about the difference between “Creative Professionals” and “@ Work Creatives” – maybe the former are indeed professional, and the latter more anarchic?

One reason for looking at this presentation was that Adobe have been talking about how the Creative Cloud has gained 500, 000 subscribers in the last year, and I was interested in seeing how big a proportion this might be. So the next slide – the installed base – helps put the number in perspective as it shows Adobe have around 8.4 million Creative Suite customers, half on CS6, and another 4 million on “point products”. Obviously there are no figures for the pirate base, which I only mention because it might indicate the potential for new honest customers.

Although one can’t assess the profitability of these 500,000 voluntary subscribers relative to existing customers, there is a price rise hidden in the subscriptions. Taken together with the 500,000 seeming a decent proportion of the user base, it might lead you to infer the switch to compulsory subscription is a sign of Adobe confidence.

On the other hand, the last slides show a forecast of reduced creative product sales for the next 3 years until they reach the promised land of 4 million subscribers in 2015, and that may make you wonder if the switch is as much a response to an existential threat. If they hadn’t gone for a compulsory subscription model, what might have happened?

You’d like to think it is confidence, wouldn’t you?

Other stats worth noting

From the Q1 FY13 investor datasheet

  • Creative Suite/Cloud products account for just under 70% of Adobe’s revenues (sales), while the Marketing Cloud (web analytics, ad serving, business forms ) is 27%.
  • 50% of revenues are in the Americas, 30% in Europe, Middle East, Africa, and 21% in Asia
  • Subscription sales are about 25% of total revenue, although most of this will be Marketing Cloud products, not voluntary Creative Cloud subscriptions
  • These are only sales and they don’t break down the real number – profitability

Subscribe or else? off the press, this letter from Adobe Creative Cloud and the future of the creative process is worth reading. Apart from flattering their customers, rather too profusely, Adobe are making Photoshop and other Creative Suite products subscription-only:

To our creative users,

At Adobe, we believe our customers are some of the most influential people in the world. You are storytellers. You capture and relate the human experience — be it through a Hollywood blockbuster, an interactive iPad app, or photos from your child’s school play…..
[Lots more if you enjoy that kind of thing! ]
Given this, the CC applications will be available only as part of Creative Cloud. We will continue to sell and support Adobe Creative Suite 6 applications, and will provide bug fixes and security updates as necessary. We do not, however, have any current plans to release new versions of our CS applications.

For the first year only, the pricing looks like it’s dropped – CS6 customers get the complete cloud for $19.99 per month, $29.99 if you have an earlier version, and $9.99 a month for Photoshop on its own. So if you look at it closely, the loyal customer deal amounts to paying roughly the same as you would have paid for an upgrade (assuming an 18-24 month cycle). After that first year, the discount expires and those prices appear to double. You can see obvious business logic for the change.

The revenue recognition smokescreen

It’s worth correcting one misconception about the switch – that it suddenly allows Adobe to release new features once they are ready – and the argument is that this wasn’t possible with perpetual licences because of Adobe’s revenue recognition policies. The trouble is, you don’t necessarily need to switch to a subscription model to release those constraints and comply with GAAP.

Well, it’s not totally untrue and it’s not deliberately misleading, you are hearing this from marketing or tech guys. While they might be expected to be aware of and comply with company accounting policy, you probably don’t expect them to possess the professional qualifications/experience to to appreciate the underlying principles or subtleties of GAAP. And before you ask, yes, that’s my shady background.

Certainly, releasing updates in the old 18-24 month cycle could cause accounting problems. But it would partly depend on the value of the revenues and costs associated with the new features – their “materiality” – and they would be evaluated in the context of a business with many income streams. Updates to a single product might not be material to the overall financial results, or you might be updating different products throughout the cycle and even out individual distortions. And while a listed company does not do this frivolously, if necessary another solution would be to change your accounting policies or adjust how they are applied.

For how Lightroom is affected, see Lightroom Journal Q&A. It will continue to be sold, as well as being in the subscription service.

Unsorted keywords

Is it possible to stop Lightroom from re-sorting keywords alphabetically?

No, but why do you need it? If Alamy, look up Jim Keir’s Alamy plugin. It may solve the problem.

paris_dogThe key problem here is how Lightroom writes keywords to exported pictures in alphabetical order, because some stock agencies’ search algorithms are weighted towards the first keywords in the file. Imagine adding keywords in the Keywording panel’s Keyword Tags box. After entering “Paris, Dog” you would see “Paris, Dog” rather than Lightroom’s alphabetical “Dog, Paris”, and the export file would also list them in the user’s order. As a result, the agency algorithm would display this picture near the top of search results for Paris and lower down if a visitor were searching for dogs.

I’ll add that while I understand the problem, I’m not sure I would want Lightroom to be changed to facilitate this workflow. I don’t think sorting is part of the relevant standards, and it’s a pretty blunt search algorithm which is limited to a few agencies. So it’s probably best done by an agency-specific plugin like the one I suggested.

Presets with catalog?

Is it better to uncheck the box that says “store presets with catalog”

store_presetsIn my view, leave it unchecked.

This check box’s purpose is to allow you to carry presets, templates etc with you when your catalogue resides on an external hard drive and you frequently attach it to other computers.

If that is not how you work, I think it is best to leave the box unchecked in normal circumstances.

Lighroom 5 beta

After a few sites like NAPP and Techcrunch jumped the gun and prematurely announced the public beta, the official Lightroom Journal says Lightroom 5 Beta Now Available.

Visualize Spots is quickly becoming my favourite new feature in LR5. Sometimes when you’re dust spotting it’s difficult to identify some spots and you only notice them later on a print. My old trick was to temporarily ramp up the Clarity slider or add a grad filter with +100 Clarity and make the spots more obvious. Now, you just switch on the Visualize Spots mask and increase the percentage.

I don’t think I really have a lot to say about it. A variety of small tweaks such as making a new collection the target collection are nice, but for me the most useful new features are the non-circular healing tool, which is a big step forward, and the new radial filter which is more about saving time than doing something you couldn’t do before.

Both of these are tools I’ll use almost daily, and I suspect the radial filter will largely take the place of the adjustment brush for local adjustment. Upright, the extra perspective tool in Lens Corrections, can be good and quick. But otherwise in Develop there’s no quantum leap forward that compares with LR3′s introduction of lens corrections and its vastly-improved handling of noise and high ISO images, or with LR4′s enormously-improved control over highlight tones.

Elsewhere you can save page layouts in Book as custom “user pages”, and add page numbers, though you still can’t create custom page sizes.

In Library I like how PNG files can now be catalogued, though such it’s a shame that progress supporting file types is being dripped out one format at a time (LR should simply catalogue all file types and let the photographer decide which are part of his or her workflow).

One nice feature for those of us who understand DNG is that there’s now a validation command which takes advantage of the format’s checksums.

Rather like LR3′s Publish took a while to be appreciated, one other innovation may be a slow burner. You can now do editing offline via “smart previews”. smart_previews2Essentially your catalogue creates another subfolder like the existing previews which contains small DNG files or smart previews which you generate upon import or subsequently by a menu command.

I’ve generated them for every photo in my main catalogue (they amount to 52Gb for 60,000 images) and it means I may now take the entire catalogue on the road and make adjustments while using my Mac laptop, and even output the files without having the master images with me – Lightroom uses the smart previews. Upon returning home I copy the catalogue plus the two previews folders back to my desktop PC and it will now use the master files rather than the smart previews.

On the other hand, that 52Gb does take a decent bite out of my 500Gb portable hard drive and would certainly overwhelm my Mac Air’s puny 128Gb, while the old File > Export as Catalog and Import from Another Catalog have always worked perfectly well for roundtripping.

smart_previewsSo in practice I’d probably recommend continuing to use the Export/Import roundtrip method, but choosing to export smart previews instead of including the negatives.

Another potential use for the smart previews feature is to gain speed with bigger image files when you’re not needing to work away from your main computer. Then idea is that after building smart previews you disconnect the drive containing the master images or rename their top level folder, then continue working. LR will now use the smaller smart previews instead of the larger originals, so everything should be faster. Afterwards, reconnect the drive or correct the folder name. OK, some fine adjustments  may be awkward, but it’ll be interesting to see how this is received.

So, are smart previews LR5′s big new feature?

Modified HTML gallery

Since the misty dawn of time, or 2007 to be precise, Lightroom has supplied a set of default web galleries which are suitable for individual sets of pictures, if not providing the complete multi-gallery web sites that many people always expect they’re getting when they see a program like LR offers web output. Little has changed since their introduction – or really needed to be changed, at least not by Adobe themselves.

But if you ever use these default galleries there are little details that aren’t ideal and for a few years I’ve maintained my own shadow version of the built-in HTML gallery. I’ve sent it to various people who have asked “why can’t I change the thumbnail size?” or “how do I show the filename in the grid instead of index numbers?” and after the latest such request I thought I’d just leave it online for anyone who wants it.

It goes in:

  • PC: C:\Users\USER\AppData\Roaming\Adobe\Lightroom\Web galleries
  • Mac: USER\Library\Application Support\Adobe\Lightroom\Web galleries

You may have to create the “Web galleries” folder).

What are my tweaks? Mostly they affect the thumbnail pages:

  • Rounded corners
  • Choose size of thumbnails
  • Set size of thumbnail number text
  • Filenames or characters from filenames (unique ID numbers) instead of thumbnail numbers
  • Show star ratings under thumbnails
  • Thumbnail grids with more or fewer rows
  • Clicking large images takes you to next photo instead of returning to the grid
  • On main photo page, clicking the image advances to the next image instead of returning to the thumbnail grid
  • You can suppress the titles and contact areas – easier to cut and paste into existing HTML pages

This is supplied “as is” and without any support. If you like it, great.


Twice recently I’ve seen people asking about getting a simple list of filenames to copy and email, and I wrote this little script for one of them. But I just saw someone asking again, so here it is (zip file) – free in celebration of my having gone through January without a beer, glass of wine, sip of single malt etc.lrdownload

In your LR application support folder (find it by Preferences > Presets > Show Lightroom Presets Folder), create a folder called Scripts. This new folder should be in the same Lightroom folder as ones like Smart Collection Templates, Text Style Presets etc.

Unzip the file and save the little lua file in there, restart LR and you’ll have a scripts menu to the right of Help. Select a bunch of pictures, run the Filenames script, and you’ll see something like this:

Screen Shot 2013-01-31 at 19.15.23

 Update (to celebrate Pancake Day)

You can easily modify this script to get other fields. The key line is getFormattedMetadata(‘fileName’) where the script calls a function and passes LR’s internal field name as an argument. So you just need to copy the script and change that field name?

sdkWell, not quite. How do you know the internal field names? And some fields need to be called with the getFormattedMetadata function, others with getRawMetadata. So while you can guess the field name or work it out by editing a metadata template in Notepad/TextEdit, you really need to look up the field in the Lightroom 4 SDK under LrPhoto.

In the comments Hans asked about the full folder path, so in this case you’d just change getFormattedMetadata(‘fileName’) to getRawMetadata(‘path’). Restart LR and you’re done.

Incidentally, if you have Photoshop or the Creative Suite, you can use the Extend Script Toolkit as your editor instead of Notepad/TextEdit. It allows you to format the code for Lua and it’s not over the head of those like me who’re unnaturally frightened of real programmers and their very clever integrated editing environments.

Mac vs Win 2013

mac_vs_win_jan2013Out of curiosity I revisited my analysis of visitors to this site which I last did in June last year.

Since you’d have to be crazy to visit this site for anything other than Lightroom, such stats are about as good an approximation of Lightroom’s user base as one can get from public data, and it is interesting to see such as shift from Windows to Mac over the period since Lightroom 4 came out.


Changing the case of text

cycleI’ve just uploaded version 1.41 of my Search and Replace plug-in.

It has a bit of tidying up, more language support, and also adds a button to change the case of text. Each time you click the button, it cycles on to a different case. So if you type some captions in capitals, it can convert them to lower case, capitalize only the first letters of each word or the first letter in the field.