Capture Time to EXIF updates

I’ve recently added a couple of new features to my Capture Time to EXIF plugin (available here), both requested by users:

  • You can now set much older years – a user wanted to set 16th century dates for some family photos
  • When updating multiple images, you can now add various intervals to each image in the batch. Previously this increment was limited to one second, but not you can choose intervals of up to one day.

I also took the opportunity to update the look, which I hope is clearer.

Why 2.7 so soon after 2.6? Because after I released 2.6 with the earlier dates, I realized that I had forgotten to add the multiple dates increment.

Opinions on Microsoft One Drive?

Adobe have recently said that they’re discontinuing the Creative Cloud Synced files service by February 2024. As the Microsoft 365 account for Office includes 1 TB of free storage, what do you think about it as an alternative?

It works – assuming you have a Microsoft 365 account – but it’s a bit opaque in how promptly it will sync non-MS Office files, though until now I had sufficient cloud space from Dropbox and Adobe and have only really used OneDrive for specific projects which mainly involve MS apps.

One advantage is that MS Office files are continually being saved in the background while you’re working on them, and another is that apps like Excel can reopen recently-opened or pinned files even if you’ve used Explorer to move the files around in OneDrive. You’ve also got browser-based access to these files. I suspect there are more little tweaks for MS apps, but these are valuable to me yet may not be to others.

As a general point I wonder how much trust one can ever place in these “bonus” cloud storage services. After all, you may have received the email telling us that “Adobe is modernising the Creative Cloud storage experience” – in this case “modernising” means discontinuing the Creative Cloud Synced files service entirely. Dropbox could do something similar, reducing the allocation or making it too-annoying with ads. Would Microsoft, maybe, but they’re probably expecting that it’ll be used for MS content rather than for the big bytes that Adobe’s customers would generate, and 1tb means you’ve got plenty of headroom if they ever did decide to reduce the space allocation.

So while I’ve already moved stuff from Creative Cloud folders – some to Dropbox, some as Photoshop Cloud files – I’ll probably move the rest to OneDrive.

Linked Photoshop smart objects

Is there an option to create a linked smart object instead of an embedded one when exporting a photo to PS?

No, in LR there is no option to do that – that’s a shame – so you have to do something like this:

  1. First in LR do a Cmd S (Mac) or Ctrl S (Win) to save edits back to the file, which will help later.
  2. Next do an Edit With, opening the file into PS and essentially creating a document of the right dimensions and with any keywords and other metadata.
  3. Save the file at this point – if you don’t, there’ll be a “can’t place file in itself” error in the next step.
  4. Then still in PS, choose File > Place Linked and add the raw file. It’ll probably take you through ACR, which should pick up the adjustments from that Cmd/Ctrl S earlier, and you should check that ACR is outputing a 16 bit file.
  5. This should open the file as a linked smart object, centred and filling the document space. If not, make sure the resolution is the same in LR’s External Editing prefs and in ACR – so 300 in both cases, or 240 in both.
  6. You can now delete the background layer which is no longer needed.

If you now make changes back in LR and do a Cmd/Ctrl S, you’ll see the Photoshop link being refreshed.

I am pretty sure that’s all the steps.



Conrad Chavez adds: Also, once you’ve got it set up as a linked Smart Object, that makes it possible to send the edits back to Lightroom Classic. If you edit the linked raw Smart Object in Photoshop by double-clicking to open it in Camera Raw, Camera Raw writes the edits back to the external metadata. Which means, back in Lightroom Classic, you can select that photo and choose Metadata > Read Metadata from File, and that will update the original raw file in Lightroom Classic.


Search and Replace 2.2

I’ve just released version 2.2 of my Search and Replace plugin.

As well as a couple of bug fixes for problems reported by people using old versions of Lightroom (as old as 5.7 for example) the main changes are in the Workflow Filters area where I’ve added more fields which can be displayed in Library Filter or smart collections.

The new Workflow Filters fields:

  • Exposure Bias
  • Crop ratio
  • Count of AI masks
  • Count of AI spots heals

For a long time there have also been 5 user-definable fields which Workflow Filters can populate. These now show the name of the field which you have defined.

Two new commands can be run independently or as part of the Refresh Workflow Filters command:

  • Rename masks from “Mask 1, 2…” to reflect what they contain, so “Lin Lin -Rad” is a mask which contains two linear gradients and one radial which is set to Subtract. It’s disabled by default, but I find it makes the Masks panel a bit easier to read.
  • Delete JPEG sidecars for selected raw files to tidy up folders. For a long time I’ve used a separate script to do this, but I thought it made sense to include it as another task in Workflow Filters. Because it’s deleting files, it’s defined quite conservatively.

For those who use Caption Builder, there is a big change which came from user requests – you can now use it write to title, headline, instructions and to the plugin’s 16 custom fields. It’ll still be called Caption Builder but it was an easy change to make.

I should add that while the plugin will continue to support older versions of Lightroom, newer features are disabled – usually hidden. So there’s not much point updating the plugin if you are using an older version of Lightroom.

Open Directly 2.1 released

I’ve just released version 2.1 of my plugin Open Directly which allows you to send raw files directly to other programs. For example, let’s say you want to process a photo in Capture One. If you followed Lightroom’s External Editor method, Lightroom would first convert raw files to PSD or TIF and would defeat the whole purpose of sending them to Capture One. The Open Directly plugin simply sends the photo directly to the other program.

I must admit, it should have been released three years ago.

Back in spring 2020 – just after the first Covid lockdown – someone emailed me asking for a specific improvement to the plugin. As I was already working on big improvements to Search and Replace, it was a perfect time to ask – I certainly had the time, and needed any change of routine. The request was only whether I could increase the number of supported apps from 6, and that was pretty easy, and I ended up polishing a few other aspects of the plugin. As they say, the devil makes work for idle hands….

Quick menu names can display the name of the app which they launch – previously you had to remember which app would be launched

So version 2 has a range of enhancements:

  1. Number of apps increased from 6 to 15
  2. Second quick menu added, so you can send a photo to an external app without going through the dialog box
  3. The user can choose which apps can be launched via each quick menu
  4. Quick menu names can display the name of the app which they launch
  5. Added reset buttons in Plugin Manager
  6. Added a change log

I released 2.0 as a beta, but I really can’t remember why I quickly forgot about it and never released 2.0. At the time I recall mornings lining up outside supermarkets for eggs or flour, and I was pursuing a number projects to make the best of being stuck at home such improving my pasta-making skills (I hadn’t yet learnt to brew beer!). I’d like to think that I must have been thinking through another bright idea but never got round to it. Whatever happened shall remain a mystery, but the plugin is finally available.


The right hand column lets you decide which apps will be available in the quick menus

Photoshop’s beta Generative Fill

Like many people I’ve been giving Adobe’s AI-based Firefly and now Photoshop’s beta Generative Fill a good workover and thought I’d share a few words and examples. While there’s a lot of hype – and fear – about Generative AI, I’m still not sure I’ve been able to use it to produce anything that could fool anyone.

So for example, in the first group of images here, I can do better Photoshopping away the boxes myself, although to its credit I thought it was a nice touch that Generative Fill inserted a reflection of a traffic cone. Yet I did spend a lot of time typing in a variety of phrases for it to use to replace the area, and I got lots of artificial-looking results like the basket of roses (and I asked for four) until I tried puddles and hit on one that worked. So was the big benefit for me that the AI had access to stock examples of puddles? That might be valuable, sometimes, but is it really something to fear?

The second set of images came from Firefly, Adobe’s web-based tool, which I asked to create entirely-new photographs, sorry photograph-like pictures. I deliberately used phrases like “Lake District” to test if it would still produce scenery from New Hampshire rather than north west England, and wondered if using “Derwentwater” or “fells” might steer it to the right region. You can see the phrases under the pictures, and while there’s a lot wrong and some strangely-bred sheep, there’s also a lot that is indeed reminiscent of the Lakes. I can recognise an Ullswater and the rainy colour palette.

What practical use is this, I just don’t know!

But of course, the beta’s available and it’s not hard to try it and inform yourself, which has got to be way better than listening to all the hype.


Photoshop’s Generative Fill:

Adobe Firefly:


Search and Replace 2.1

It’s a pretty good principle that if one person complains or can’t figure something out, there will be many more that I never hear from. Soon after I released Search and Replace 2.0 a few people contacted me with concerns about copying from the four IPTC Location fields, and I had to admit that my changes weren’t as clear as I hoped.

So version 2.1 is released today with more tidying up and polishing, but mainly to bring back the buttons which copy IPTC Locations to keywords and to the IPTC Extension Location Shown/Created fields.

They’re all now on the new Workflow Filters tab:

I’m not sure many people really use the IPTC Extension Location Shown/Created (I certainly don’t) but I’ve taken this opportunity to add some extra detail to make working with those fields less awkward:

  • The new World region box lets you enter it in the dialog box, or leave blank, and you are no longer prompted for it when you copy from the four IPTC Location fields.
  • The new Change region buttons let you select a number of photos and change all their world regions
  • The new Delete buttons let you delete the contents of those fields without opening up the item in the Metadata panel

IPTC Extension Location Shown/Created are now also shown in the Library Filter by the Refresh Workflow Filters command, helping you review entries in those fields.

There are also extra options in the Plugin Manager:

  • When you run Refresh Worklow Filters you can also copy from the four IPTC Location fields to Keywords and to the IPTC Extension Location Shown/Created fields.
  • You can now keyword the top level keyword (a user requested)
  • You can customize the choices for the above World region box

Lightroom 12.3

Lightroom 12.3 came out today and the headline feature is an AI-derived Denoise. I’ll admit that I am ambivalent about it:

  • I’m not so concerned by noise that I’ve bought any of the 3rd party AI-based apps.
  • It’s slow
  • I don’t particularly want an extra (big) DNG in addition to the raw file. Maybe it’s only worthwhile for exceptional high ISO pictures?
  • I’d have preferred Lightroom to save a series of adjustment or offset values, not a fully-baked independent file.

I’d also strongly recommend reading this Denoised demystified article by Eric Chan:

I recommend applying Denoise early in the workflow, before healing and masking. AI-driven, image-based features such as Content-Aware Remove and Select Subject can be affected by noise, so it’s best to use those features on a clean starting point. If you do run Denoise on an image that already has Content-Aware Remove settings or AI masks, Denoise will automatically update those spots and masks. This is handy, but be aware that the content of those spots and masks may change unexpectedly, so it’s best to review the results carefully.

And watch this video by Julieanne Kost.

Search and Replace 2.0

The Lightroom URLs and commands are listed in the Plugin Manager. You don’t need to set up all these shortcuts if you don’t want to do so, just those you think you will use

Version 2.0 is released today with a lot of tidying up and polishing, and a few subtle new features.

What I hope will be most popular is that you can now launch plugin functions from keyboard shortcuts. While the Mac operating system already lets you set up a keyboard shortcut to run the plugin’s menu commands, and this change means you can do the same on Windows too. But it’s more than that because it also lets you run other plugin commands which don’t have menu items and without opening Search and Replace.

This feature is not for everyone, but it should appeal to the plugin’s typical or advanced user. And it does not work out of the box – on your Mac or PC you need to set up these keyboard shortcuts and point them to the lightroom:// URLs listed in the Plugin Manager (right). Note that there is more than one way to set up keyboard shortcuts.

I think it will help to give a practical example of where I like pressing a keyboard shortcut to run one of the plugin’s commands. Imagine you often copy from one field to another, such as the IPTC Location to the Title field, or from the Job to Keywords. You can set these up as shortcuts like lightroom:// The element lightroom:// tells the operating system to interpret the URL in Lightroom with this plugin, and then the following arguments tell the plugin it should copy the location to the title.

Lightroom to Instagram

You may not have noticed this button, and I remember being surprised when I saw it

How do you post to Instagram from Lightroom on your Mac or PC?

About 6 months ago Instagram quietly added a “+” button to their web page. I use this as my usual way to post photos, especially multiple photo or “carousel” posts.

If I am posting a single image, I simply export from LR and use the “+” button, choosing “original” from Instagram’s crop ratio choices.

However I usually make multiple-photo or “carousel” posts, using photos with differing crop ratios, and this causes a small problem. Unfortunately Instagram assumes all the photos have the same dimensions.

So the way I get around this is using Print and a Print template (zip) which outputs square 2048 pixel JPEGs, with white space being added around any non-square photos. After “printing” the photos as JPEGs into a folder on the desktop, I then switch to my web browser and use the “+” button to create the post.

I’ve attached my Print template above, but to create your own these are the key panels:


A second problem is that Instagram strips metadata from your files and doesn’t use the captions or convert the keywords to hashtags. Often I just type them all again, but sometimes I run this little script which displays a dialog box in LR from which I can copy the text. It includes the title and caption,and converts multi-word keywords into single-word hashtags, and notice that it includes some hashtags that I use on many images.


Video Metadata 2.0

I’ve just released version 2.0 of my Video Metadata plugin which reads and writes metadata to video files, something long-available in Adobe’s Bridge but which another Adobe’s Lightroom still cannot do.

The changes are quite subtle but the main ones are:

  • Quick access URLs to allow commands to be launched from keyboard shortcuts (setting up)
  • A new Run in Windows/QuickTime command to play videos in the operating system’s default video player

These two features work well in combination. I don’t know about you, but I remain very frustrated that Lightroom doesn’t play videos as quickly or reliably as the operating system, and that’s why I added the Run menu command.

While this simply launches the Windows player or QuickTime, I wanted to avoid having to navigate through the menus each time. So the Run menu can now be launched from a quick access URL.

For example, here in Windows I created a new shortcut on my desktop and copied the URL (see above) into the shortcut’s properties, then set the shortcut key to Ctrl+F1 which doesn’t seem to be used by any other program (the shortcut can be anything you want).

This means that I just select a video in Lightroom, hit Ctrl+F1, and the video is launched in Windows Player.

Lightroom 11.2

Released a couple of days ago, Lightroom 11.2 just has a couple of little tweaks to masking and “improved responsiveness in the Library module, especially during multitasking” (see this short video).



Lightroom 11 – Masking

A couple of days ago Adobe posted a sneek peek of a feature coming in the next version of Lightroom – bringing together local adjustments as Masking and adding significant new capabilities.

I use local adjustments extensively, mainly the Radial and Linear Gradients, the brush to a lesser extent. For example, I frequently add a little Clarity as a local adjustment, often with a small boost to Shadows. To my eye rather than making the whole image area “shout” with the Basic panel Clarity (which I rarely use), this combination of local adjustments make faces or other key details stand out. It’s a modern dodging and burning, if you’re familiar with darkroom techniques!

So I’ve been one of the lucky ones who has been able to try out these new features, and have been given permission to give my impressions publicly.

Old frustrations

Adobe have addressed some of the frustrations I used to have with local adjustments. One is how they were in different “silos”. What I mean here is that I often want to fine tune a photo, sometimes from a year or more ago, and suspect that I might have done a local adjustment over a face. So first I’d look in the Radial adjustments, not see one, and then see if I’d used the Brush, or vice versa. They have now brought all adjustments together in a floating Masks panel, and that means I can instantly see all the local adjustments at once. Great, that’ll save time.

Another similar frustration was that I often want to make similar adjustments in different parts of a picture but was forced to fine tune each local adjustment individually. For instance, imagine there’s more than one face that I want to emphasize, so I might add a couple of my Clarity/Shadow Radial filters. But then if I wanted to change both adjustments, I’d have to select one and then the other. I much prefer Nik’s SilverEfex where you could group and fine tune multiple control points at once. Adobe have fixed that inefficiency, so here you can see that Mask 4 is a group or “layer” of three Radial Gradients sharing the same slider values. Again, this is great.

So you’re now wondering what if you now want to adjust one of the three Radial Gradients independently? In that case you just drag that Gradient and drop it on the Create New Mask button. The Gradient is now moved onto its own mask with the same initial settings.

One downside is that this dragging and dropping – which is so useful – isn’t mentioned on the Help panel that appears when you click the little ? button they’ve hidden at the top of the Masks panel. This Help lists a lot of keyboard shortcuts, probably too many, but doesn’t give the user a hint about dragging and dropping.

New features

Four new ways to select image areas for local adjustment

So they’ve united the old splits or silos between the different local adjustment tools, and they’ve allowed you to group local adjustments. For me those are big, practical wins.

But new features are what usually draws the eye, and Adobe have added new ways to select image areas for adjustment:

  • Automatically select the subject
  • Automatically select the sky
  • Automatically select a colour range
  • Automatically select a luminance or brightness range

The first two will probably attract most attention, and no doubt there will be many images which fool the AI-based logic and no shortage of “it didn’t recognize my kangaroo” complaints.

Yet while subject and sky selection are handy enough on their own, for me the real power of these tools comes once you combine them with the other local selections – adding or subtracting. There’s also an “intersect” which I suspect few people will ever need or use (even if they find it via its Alt/Opt modifier key).

Here for example I first selected the sky using the new tool, but initially it produced a sharp edge. Fair enough, the shape is from a modern building. So I then added a Linear Gradient and set it to “Subtract”

Notice how subtracting a gradient from the sky blurs the outline

– ie subtracting from the sky selection – and this combination of two selections has produced a softer edge around the building.

A couple of thoughts on the Sky feature:

  • I am surprised that Adobe didn’t add some kind of sky replacement feature.
  • It’s a shame that there’s no feathering control that would allow you to smooth the edges of the adjustment. As shown on the right, you need to add one or more subtractions.

While it’s likely that the Sky and Subject selections will draw most attention, don’t ignore their Color Range counterpart. For some photographers, it will be at least as useful, and here you can see how it allows one to select and adjust the blues in this image.

In this screenshot the cursor is over the mask and the red overlay makes the blues purple, if you’re wondering.

Notice how I used Shift + click to add different shades of blue to the range – these are the Color Pickers on her headdress. Shift + click is already standard elsewhere in LR whenever you use a Color Picker.

Yes, it was always possible to use the HSL panel to change all the blues throughout this image.

But remember my earlier comment that the real power comes from combining the tools, so here the Color Range selection can be used in conjunction with other selections. For example, I might add Radial Gradients to subtract her t shirt and her face paint, and this would allow me to change the blues only in the headdress and wings.


This is going to be a major upgrade to how many of us work with images. I’d say that in some ways I do find Masks less pleasant an experience, more fiddly than the old local adjustments. The Help panel shows how in some ways it’s over-specified. On the other hand, they’ve successfully unified the local adjustments into a single feature, and the new ways to select image areas make Masking an altogether more powerful tool. Even fewer trips to Photoshop?

No excuse for not using a mask

To finish, while I have shown screenshots from Classic Lightroom, I have always been a big fan of Lightroom Mobile and would advise anyone to explore what they can do with it. Sometimes on the train home I’ll import new raw files using my iPhone, or I’ll play with adjustments to pictures I imported earlier when I was at home. It’s so damned convenient to have this mobile extension of Lightroom. And as you’d hope, the new Masking does work in all parts of the Lightroom world.

So here I added a Select Subject – but doing it on my phone. Mine’s not the latest phone – it’s an iPhone 8 – and the raw file isn’t in the cloud which means Lightroom Mobile is working from a smart preview.

In this case the selection isn’t perfect, even if it is pretty good. But for me Lightroom Mobile is not the final stage before printing or whatever, and I don’t expect perfection. What I want is, as I say, the convenience of trying these things when I’m on the move, and I can easily refine the Select Subject in Classic Lightroom.

I’m not being cruel when I say that I can’t tell you when you’ll be able to get your own hands on Lightroom 11. But it can’t be too far away now, can it?

Update November 1, 2021

When I wrote this post in late September I wasn’t allowed to write about other features, but one of the most handy is that you can now filter on months and dates. So imagine you want to find all the pictures you’ve taken at Christmas or in the first week of November, this long-requested little feature is ideal.

Capture Time to Exif 2.1

I’ve just released version 2.1 of Capture Time to Exif which refines how it handles Exiftool on Mac versions from Catalina and Big Sur.

The plugin’s Exiftool component should now execute, and it should no longer be necessary to install a separate copy Exiftool.

Capture Time to Exif 2.0

Today I released version 2 of my plugin Capture Time to Exif. You can download it from Photographers Toolbox or allow it to automatically update. The main changes are:

  • Major update of the interface’s layout
  • Better handling of Exiftool on Mac

The latter is the more important and was necessary because Catalina and Big Sur users often found that the plugin wasn’t working. Everything looked fine, there were no error messages, but nothing was happening to the images because its Exiftool component was being blocked by Apple’s recent changes. Many users read the documentation and tips to install a separate copy of Exiftool, then tell the plugin to use this copy, but this method is now mandatory for Mac users and should be automatic.

Other changes in 1.30:

  • Added thumbnail showing the photo referenced by the current command line
  • On Windows the command line preview can be saved automatically to the desktop as a batch file
  • On Mac the command line preview is displayed in a dialog box which can be copied
  • Exiftool commands are saved in a jb Plugins subfolder of Documents (to avoid clutter)
  • Changed text message when user writes to raw files
  • Can now set blank values for the Additional Fields


Syncomatic 4.0

I am releasing Syncomatic 4.0 today.

As well as the performance improvements which the Coronavirus lockdown gave me an opportunity to write, this version was triggered by a feature request to allow the user to choose which metadata fields should be included in the sync operation.

Previously, while you could choose Title and Caption on their own, most people seemed to be fine syncing all metadata between two groups of images or within stacks. This produced a simpler interface, which people readily understood. To throw in a couple of clichés, “less is more” and “be careful what you wish for”.

With the easing of lockdown in the UK, I did plan to mark my second vaccination by officially releasing the big plugin updates of the last year. That process begins with Syncomatic 4.0.

Lightroom 10.0

Lightroom 10.0 has just been released, and you can see the new features listed here.

It’s not a radical upgrade and the new features seem barely worth a full version number. But that indicates a database upgrade and also, unfortunately, the dropping of older operating systems. I just wish Adobe would drop their “3 versions back” policy and only force an OS upgrade when really necessary, but I don’t expect that to change!

For me the good features are:

  • Upgrade filename now defaults to include the Lightroom version, something I have suggested a number of times to Adobe. It’s goodbye to helping clients figure out whether Lightroom Catalog-2-2-2.lrcat is their latest catalogue!
  • Split toning becomes Color Grading and is much improved. See this in-depth description.
  • Zoom is now scrubby. Use Shift or Ctrl for different effects. It’s an improvement but it’s a “so what?” for me.

Syncomatic 3.3 (ie 4.0)

UPDATE – version 4.0 released

Not much has changed in 3.3 – except for performance….

Over the years I’ve heard from a few people using the plugin to sync metadata between far larger numbers of files than I really anticipated – not thousands but tens of thousands. They were finding that the plugin worked, but very slowly indeed.

So I had looked over the code and occasionally experimented with different approaches, but I didn’t want to risk fixing a plugin that wasn’t broken. After all, no matter how slow it may have been, it was always a lot faster than synchronising large amounts of metadata manually!

Earlier this year someone had reported that the slowdown wasn’t linear and suggested that processing bigger numbers of images made the plugin exponentially slower.

The Covid-19 lockdown and my low opinion of the UK government’s abilities gave me lots of home-time to mull over the problem, and the exponentially-slow performance theory did make a lot of sense. The code was written to allow for multiple occurrences of the target filename, so each source photo was being compared against each target photo, even after a match had already been found.

So my initial optimisation was rather inspired by how people often delete dating apps after meeting the perfect match. That’s the Unique Match option (right). With my test sample of 776 pairs of photos, it completes 4 times faster than the old method.

The second idea was a complete rewrite of the matching process, and there I had the benefit of 10 years’ more experience of programming in this environment. That’s the New Matching Process option, and with my test sample of 776 pairs, it completes 33 times faster than the old method. With more photos, the improvement should be even more noticeable.

My recommendation is to enable the New Matching Process, which is now the default. Please test it carefully and let me know your thoughts. I’m not planning other changes to the plugin, but if you make a persuasive case….  Update: The new process is now the standard process.
I’ll also share my stats below:


Lightroom 9.3

9.3’s out now and while it’s not terribly exciting it does contain three small improvements:

  • You can now create ISO adaptive presets without hacking xmp – select some low and high ISO images that you’ve adjusted and just save a preset, making sure you choose the adaptive ISO option.
  • There is a new local adjustment to shift the Hue. It’s useful enough to change the colour in a part of the image, but Hue really only comes into its own when you combine it with the Range Mask.
  • HEVC video files are finally supported in LR on Windows. This is important because it’s now the default video format on iPhones and made it awkward managing those video files with photos shot on the samer mobile phone.

This image shows what I mean about how the Hue shift slider comes into its own once you combine it with the Range Mask. Here I sample the colours in the mask (coincidental choice of picture!) using the Range Mask’s dropper. In this case a single click with the dropper was sufficient but one could also hold down Ctrl and drag over the mask or use the Shift key to select multiple sample points.

Big PSBs and fooling Lightroom

I don’t often use the PSB file format which Photoshop requires for files bigger than TIF and PSD can support, so I was unmoved by 9.2 adding support for PSB files.

The problem of managing PSBs remains for any PSBs which are bigger than LR’s 65,000 pixels long edge or 512 megapixels limits. But maybe my indifference was deepened by knowing that there was already a way to manage PSBs and that it can help with files of any size.

Essentially, you can create a proxy file representing the PSB and catalogue the proxy, be it a JPEG or whatever. In my view it’s more effective to take advantage of Photoshop’s File > Place Linked command and place a link to the big PSB in a smaller TIF or PSD which LR can catalogue and even adjust.

So here on my desktop (left column) you can see a 60k*40k PSB that I couldn’t import into LR, but which I added to a 6k*4k PSD using File > Place Linked. And in LR I’m making adjustments to the PSB.


As an alternative, you can get the proxy file into LR, then make it go missing and fix the missing link by pointing to the PSB. So here you can see how I renamed the PSD on my desktop, and then pointed LR to the PSB. The advantage is that I have the actual PSB catalogued in LR, so I can see and manage it, but metadata won’t save to the file and I can’t adjust it in LR.

I’d go for the first method, but I just wouldn’t hold my breath waiting until there’s no need for any such stopgap.