Yesterday David asked the question… “If I am using CS4 (PS4) and I upgrade to LR3, if I choose “EDIT WITH PS” will I get a warning message regarding ACR versions (6 vs 5)? I assume that PS4 does not support ACR 6 and will thus not maintain ACR mods from LR3 if I edit with into PS4? Is this correct? Implications?”  So here’s an sneak preview from Adobe Lightroom 3 – The Missing FAQ…

What happens if I’m still using an older version of ACR and Photoshop?
If you’re using a mismatched version of ACR, it may not understand all of Lightroom 3’s new settings, and therefore the rendering may be different.  Besides the new camera support, there are a few other changes involved, depending on the version number.  In recent years, there have been changes to the demosaic, new sliders added such as Grain, existing sliders redesigned resulting in the introduction of Process Versions, and now the new lens corrections too.

The demosaic, in basic terms, is the initial translation of the raw data into an image, which applies to all of the photos regardless of your Process Version setting.  ACR 5.6 and earlier use an older demosaic, whereas Lightroom 3 and ACR 5.7 and higher all use the new demosaic.  The visible difference is an increased amount of detail in the newer demosaic, which can affect the amount of sharpening and noise reduction you choose to apply.  If you open a Lightroom 3 photo into a version of ACR with the old demosaic (5.6 or earlier), for example, opening a photo directly into CS3 with ACR 4.6, then it will appear softer and less detailed than Lightroom 3, even if you’ve used sliders that it understands.  If you open into 5.7 or later, the demosaic will match.

There are also new sliders which older ACR versions may not understand, for example, Grain and the post-crop vignette Highlight Priority and Color Priority options are understood by 5.7 but no earlier.

Further down the line are the processing algorithms, including Fill Light, Noise Reduction and Sharpening, which have changed so significantly this time that they now come in 2 different versions – Process Versions 2003 and 2010, more often shortened to PV2003 and PV2010.  We discussed those in more detail in the Develop chapter.

And of course, last but not least, there are the new lens corrections which require ACR 6.1 or later.

Here’s a quick reference of the most recent ACR versions for each Photoshop release, and the differences you’re likely to see if you open the files directly into Photoshop.

In summary:

CS3/4.6 – New sliders are ignored.  If you only use sliders that were available in 4.6, with PV2003, it’s close but 4.6 also uses an older demosaic which can result in sharpening and noise reduction differences.  Best to let LR render the file and then open that into Photoshop.

CS4/5.7 – No lens corrections are applied.  There are other minor differences (i.e. sharpening slightly different) but otherwise it’s very close.  5.7 can read LR’s settings but there’s no UI to change the new settings.  If you haven’t used lens corrections, the differences may not notice unless you’re looking for them, so you can probably open directly into Photoshop.

CS5/6.1 – Fully compatible with LR 3.0

There’s an additional dialog which often appears when the ACR version is mismatched, offering you the choice of ‘Render Using Lightroom’ or ‘Open Anyway’, although it’s currently missing with 5.7. More on the consequences of that dialog soon!

There’s still considerable confusion about the recent Lightroom 2.7 and ACR 5.7 updates and their compatibility with Lightroom 3.  To complicate it further, although LR 2.7′s basic processing matches the ACR 5.7 release, on this occasion ACR 5.7 offers additional features for LR3 compatibility.

For a start, there’s a difference between a demosaic and a process version – they’re entirely different concepts.

In basic terms, the demosaic is the initial translation of the raw data into an image, which applies to all of the photos regardless of your settings. Lightroom 2.6 and ACR 5.6 and earlier use the old demosaic.  LR 2.7, LR 3, ACR 5.7 and ACR 6.0 all use the new demosaic.  It’s such an integral part of the program that you can’t switch between demosaic versions, so if you’re using 2.7/5.7 or later, you’re going to be using the new demosaic.  That means even existing photos show more detail than 2.6, but they may also show a little more noise.

Further down the line are the processing algorithms, such as noise reduction and sharpening, which have changed so significantly this time that they now come in 2 different versions – 2003 and 2010.

• LR 2.7 just has the new demosaic and doesn’t understand process versions or the new LR3 features such as grain.  Those new LR3 settings will not be backwards compatible to LR2.
• ACR 5.7 for CS4 has the new demosaic, and it also understands PV2010 and the new features (grain, etc) in PV2003, for full compatibility with LR3 beta 2.  It doesn’t, however, have a UI to change those settings.
• ACR 6.0 for CS5 has the new demosaic, is fully compatible with LR3 beta 2, and it now has a UI to be able to adjust those settings using the ACR dialog if you wish to do so.  It is missing the new cameras which were added in 5.7, due to a difference in timing, but those will be added in 6.1.

If you want to test any of this for yourself, open a file into LR3 beta 2 and apply a heavy grain setting.  Save the metadata back to the file using Ctrl-S / Cmd-S and then open the file in LR 2.7 and ACR 5.7.  LR3 and ACR 5.7 will show the grain, but LR 2.7 won’t.

Clear as mud?

There seems to have been a recent flurry of plug-in releases, with many being real time-savers, and adding great new functionality to Lightroom. Here’s a few of the latest additions for you to explore:

SLR’s with video have quickly become popular, but until now, Lightroom hasn’t had the facility to import or manage those video files along with your photos. Jeffrey Friedl has done a great job of incorporating that into Lightroom, with his Video-Asset Management plug-in.

You’ll also want to explore his many other plug-ins, including uploads to SmugMug, Flickr, ZenFolio, Picasa Web, and Facebook. He’s also the author of my favourite Metadata Wrangler tool, GPS tools, and a few others besides.

Tim Armes, author of the well-known LR2/Mogrify plug-in has also been busy writing, and has released LR2/Tree Exporter, which can replicate your folder structure when exporting. Very neat! LR/Transporter is another of my firm favourites, as well as LR/Enfuse and LR/Blog.

Sean McCormack of Lightroom Blog has been busy with Twitter plug-ins, with export plug-ins for both TweetPhoto and TwitPic.

Many people have asked recently about an FTP export plug-in – if you download the SDK and unzip it, in the Samples folder you’ll find a ready built FTP upload plug-in. Don’t worry, there’s no programming involved! Install just like any other plug-in, and it’ll appear in the dropdown list at the top of the Export dialog, where it currently says ‘Files on Disk’.

There are more plug-ins appearing every day, so keep an eye on Lightroom Exchange for the latest.

It’s true, the watermarking facilities currently in Lightroom 2 are a bit limited. Ok, very limited! But all is not lost… Lightroom plug-in programmer Timothy Armes came to the rescue with the well known LR2/Mogrify plug-in, and LR/Mogrify before that, adding fully configurable presentation options. LR2/Mogrify is donationware, and the trial allows you to process up to 10 images at a time, so you can see how well it works.

At first glance, the LR2/Mogrify interface can looking a little complicated, but that’s just because it’s so powerful. Let’s cover some of the basics that you’ll use when watermarking or signing your images.

The first thing you’ll need to do is install the LR2/Mogrify plug-in. Tim’s written full instructions on his website, so I won’t cover that here. In short, Windows users need to install both ImageMagick and the plug-in, whereas Mac users only need to install the plug-in.

Once LR2/Mogrify is installed correctly, you’ll see the Post-Process Actions section in the lower left corner of the Lightroom Export dialog. LR2/Mogrify can be used in conjunction with any of the other standard export options, such as resizing, sharpening, etc., and before any other export plug-ins.

First of all, let’s look at borders. Click on Borders in the Post-Process Actions and press Insert to add that panel to the Export Options. To add a border, select the width for each edge and the colour – and repeat for additional borders. You can alternative different widths and colours to create more interesting borders, or you can just keep it simple. The results of layering multiple borders can be seen below.

Now how about signing your image? Going back to the Post-Process Actions section and selecting Text Annotation is one option. You can choose the size, font, and positioning of the Text Annotation. You can even use that same Text Annotation section to add the EXIF data about your image using the ‘Add Token’ button to select the information to show.

One thing to be aware of – if nothing seems to be happening with the Text Annotation, try a different font. Mogrify can be a bit fussy about which fonts it will use! If your preferred font isn’t working, you can always use a graphical watermark instead – we’ll come back to those in a moment.

And here’s the result of those combined settings:

But what if you need to overlay a heavier watermark, or you want to add a graphical logo instead? Again, it’s simply a case of selecting the correct Post-Process Action – in this case the ‘Graphical Watermark’ option. You’ll need to have created your watermark image in a pixel editor such as Photoshop, and if you want to include transparency, you’re best off using PSD rather than PNG files, as there are some controls unavailable for PNG resizing.

These are just a few of the options available – have a play, and see what you can come up with. To get you started, I’ve uploaded the Export Templates and watermarks that I’ve used – you’re welcome to download them from here: http://www.lightroomqueen.com/downloads/mogrify-downloads.zip If you unzip the downloaded folder, you’ll find 2 folders inside – ‘Export Templates Mogrify’ and ‘Watermarks’. To install the Export Templates, put the ‘Export Templates Mogrify’ folder inside the Export Presets folder – you can check the location on your system by going to Lightroom’s Preferences dialog, choosing the Presets tab, and pressing the ‘Show Lightroom Presets Folder’ button. Obviously the presets are looking for watermarks and fonts on my system, so you’ll need to update the locations to point to the files on your own computer system.

If you have any problems, drop by www.lightroomforums.net and we’ll talk you through it!

Tim Armes has just released an update to his LR/Transporter Lightroom plug-in. This is hot off the press – it’s not even documented yet.

The new feature is for Lightroom 2 only. Many online ordering cart systems will provide a text file with a list of the files that the customer has chosen. Particularly for large orders like weddings, it can take a long time to manually select all of the images in Lightroom ready for ordering – but no more! LR/Transporter will now read that text file and mark the files for you.

To use:
Download LR/Transporter http://www.photographers-toolbox.com/products/lrtransporter.php A trial version is available to see how it works, and it’s well worth a donation to unlock it.

Installation instructions are here: http://www.timothyarmes.com/lrtransporter.php?sec=install

As with any plug-in that modifies the catalog, make sure your backups are current.

Open your catalog and select the files from the wedding in question.

Go to Library menu > Plug-in Extras > Mark Images using LR/Transporter

In the dialog, navigate to the text file containing the list. It just needs to be a basic text file, with 1 filename per line, and nothing else. (It’s also possible to use CSV files using the Import Metadata using LR/Transporter).

Choose the options you want – the examples below show which filenames will be matched as you change the dropdown lists.

Press OK, and the matching images will be marked.

To find and filter those images, select the Metadata filters from the Filter Bar and select Marked by LR/Transporter in one column. Your options will be Yes or No – yes being the ones that matched the text list.

[Warning - this is quite long. I had originally intended to split it over a number of blog posts, but it'll be easier to reference as one post.]

Who has never said “hurry up Lightroom”?  Speed is one of the most popular feature requests from Lightroom users everywhere, and no doubt the engineers will continue working on Lightroom’s performance over time, but for now, there are plenty of things you can do yourself.  Some are obvious, some not so…

Speed Tips in Library module
There’s a big difference between rendering previews that have never been built or that need updating, and loading those ready-built previews from disc.  How can you tell the difference?  The overlay in Loupe view will tell you exactly what it’s doing – and therefore what you can do to help.

“Rendering Preview…” means it’s rendering a preview for the first time – and you’re having to wait for it!  You could set Lightroom rendering the previews when it imports, by selecting your chosen preview size in the import dialog – it’ll slow you down initially but once it finishes rendering, it’ll be much quicker.  For files that are already in your catalog, select them all in Grid view and go to Library menu > Previews > Render Standard Previews or Render 1:1 Previews, and go off and leave it until it’s finished.  It’ll skip any that already have current previews, and you’ll find browsing much quicker when it’s finished.

So what size previews should you render?  If you want to quickly zoom into 1:1 view in the Library module (not Develop), then it’s a no-brainer – render 1:1 previews rather than Standard-Sized previews, either in the Import dialog or using the menu command noted above.  On the other hand, if you rarely zoom in Library module, you’re better off using Standard-Sized previews, as they’ll take up less disc space and be quicker to read from the cache.

If you see the “Rendering: Higher Quality…” overlay, it means the existing preview is too small or too low quality.   If you’re seeing that overlay in Fit or Fill view, you’ll want to reconsider your Standard preview size.  You’ll find those settings in the Catalog Settings dialog under the Edit menu (Windows) / Lightroom menu (Mac).  Generally speaking the Medium quality setting is fine, but you may decide to increase the Standard preview size from 1440 to a larger size if you have a high resolution screen and regularly see the “Rendering: Higher Quality…” overlay.

“Rendering: File Changed…” means, well, that’s the file’s changed since the preview was created.  That could mean that you’ve made changes in the Develop module, using the Quick Develop panel, or by applying a preset.  Using the Render Standard Preview menu command to update those previews while you do something else will speed up your browsing.

“Loading from Previews…” is the overlay you’re aiming for – that means your existing preview is being loaded from the preview cache, which is the quickest option.

Speed Tips in Develop module (or making Quick Develop changes in Library)

First, you need to understand the difference between Library module and Develop module.  Library shows you lower quality previews from the previews cache.  Develop, on the other hand, assumes you need an accurate view, so it first shows you the preview from the preview cache, then does a quick read of the raw file, frees up the sliders for you to start working, and then finishes loading properly, before it turns off the “Loading…” overlay.  You don’t have to wait for the overlay to disappear before starting work on the image – and if you find it distracting, you can turn it off in the View menu > View Options > Loupe panel > ‘Show message when loading or rendering photos’.

That’s all well and good, but that’s still a lot of raw data to load and process each time you switch images.  Have you ever noticed, though, that when you adjust a file in Develop, move to another image, and then come back to that first image again, it loads much quicker than it did the first time?  That’s where the Camera Raw cache, also known as the ACR cache, comes in.  When Lightroom reads the data the first time, it adds it into the shared Camera Raw cache.  When you load that image into Develop module, where possible, it will load that cached data, which is much quicker than reading and processing the original raw file data.

By default, that Camera Raw cache is only 1gb in size, and when new data gets added, the oldest data is removed.  With only 1gb of space, that happens quite quickly, so you’re not seeing the benefit.  If you go to Lightroom’s Preferences dialog, and look in the File Handling tab, you can change the cache size to suit – up to a maximum of 50gb.  Bigger is better!  You can also change the location if you wish to – but make sure it’s on a fast hard drive.

Once that data is cached, it’s much faster moving between images in the Develop modules – almost instantaneous on high end machines.  Of course, that is only helpful when Lightroom has recently read the raw file, and added it to the cache – and there isn’t currently a menu command to pre-load the Camera Raw cache.  All is not lost!

There’s a trick to pre-loading the Camera Raw cache – in addition to actually viewing the image in Develop module, there’s another obvious time when Lightroom has to read (and therefore caches) the raw data – namely, when rendering previews.  If you haven’t already rendered previews for your files, simply using the Library menu > Render Standard-Sized Previews command will do the trick.  If, however, you already have current previews, you can force them to re-render by making a minor or reversible change to the images (i.e. by using a Quick Develop button) and then using the Render Standard-Sized Previews menu command.  Leave it to finish, and by the time you come back, even the Develop module should be moving through the images at a much more comfortable speed.

Dispelling the Catalog Myths

It’s true that large catalogs can be a little slower than small catalogs – but we are talking BIG catalogs.  It’s not generally a good reason (any more) to split your library into 300 different catalogs – that just defeats the object of having a DAM system like Lightroom.

If you find Lightroom is feeling a little sluggish, find the Catalog Settings dialog under the Edit menu (Windows) / Lightroom menu (Mac), and press the “Relaunch and Optimize” button to perform database optimization.  It’s worth doing regularly, and any time you make significant database changes like importing or removing large numbers of files.

Finally, Hardware Tips & OS Tweaks
There is no question, Lightroom loves good hardware, but it can still run nicely on older systems too.  Do make sure you’re running the latest Lightroom release (currently 2.3) as performance improvements have been made to each release.

The system requirements are listed as Intel Pentium 4 or equivalent (i.e. a processor with the SSE2 instruction set or later), with 1gb of RAM and 1gb of hard drive space.   Now let’s be clear – those are minimum system requirements.  It’ll run – well, it’ll walk!  But if you start trying to feed 5d Mk2 files into Lightroom with a computer that was in the Ark, don’t expect it to be fast, and don’t complain about the speed.  If you’re going to spend money on the latest and greatest cameras, bear in mind that your computer hardware may also require a helping hand with those new super-size files.  Yes, even those sRAW files. 

If you’re working with existing hardware on Windows, check your graphics card.  You don’t need a heavy-duty graphics card to run Lightroom, but you will benefit from the latest drivers that are available from the graphics card manufacturers.  If you haven’t checked recently, that’s your first port of call for a free and easy performance fix.

Next, if you have an nVidia graphics card (Windows again), a quick Google will bring up numerous pages of tweaks which can make a massive difference to Lightroom’s speed, particularly for sticky sliders, slow preview refreshes, and Adjustment Brush problems.  Most notably, disable the nView software which is installed along with nVidia drivers, as there are known conflicts.  Other nVidia tips can be found on these posts:
http://www.thejohnsonblog.com/2008/09/06/lightroom-2-and-nvidia-performance/
http://www.flickr.com/groups/adobe_lightroom/discuss/72157607074073712/

Hard drives are another obvious place to look.  For a start, you’ll want plenty of space on your hard drives, particularly the boot drive, as your computer will get slower as you start to run out of space.  If you’re on Windows, defragment your hard drives regularly too.

Hard drive connections can also slow down Lightroom, due to the amount of data transfer when working with large files.  Internal drives will usually be quickest.  If you have to work from external drives, eSata and Firewire800 will be much quicker than Firewire400 or USB.  Ideally your catalog (and the previews alongside) will be on a different physical drive to the image files themselves (just another partition of the same drive won’t help).

If you’re looking for new hardware, you may be wondering if Lightroom can make use of multiple cores – and yes it certainly does.  I’ve seen it use up to 650% of my 8-core machine when running processor intensive tasks such as multiple exports or rendering previews.

Lightroom also loves plenty of RAM, but bear in mind that you’ll need a 64-bit operating system to really take advantage of large amounts of RAM.  If you have more than 4gb of RAM, you’re most likely to see improvement in the responsiveness of Develop module by using the 64-bit version.

And finally, a little logic.  Virus protection constantly scanning the same files that Lightroom’s trying to use will slow you down.  Consider excluding the catalog (*.lrcat), the previews file (*.lrdata next to the catalog), and the ACR Cache (check the Lightroom Preferences dialog for the location) from the live scan, and perhaps the images themselves.

The less junk you have running in the background, the better, particularly on older slower machines.  That includes those fancy little system tray programs that load on startup.

That’s all for now – if you have any favorite speed tips, feel free to drop them in the comments below!

Edit a file in Lightroom using the new local adjustments – the gradient tool or adjustment brush – and then open that file in Photoshop CS2 via Edit in Photoshop or Export…. and if you try to save it as a jpeg, Photoshop will complain with an error message which says “Could not complete your request because of a program error”.  Why?

Ok, it’s a bug… but for once, it’s not a Lightroom bug.  Photoshop CS2 trips up on some perfectly legitimate metadata that Lightroom saves into the files when you’ve used local adjustments.  CS3 and CS4 behave nicely with this metadata, but CS2 is no longer updated and so the bug will never be fixed.  What can you do about it?  You have a few options:

1. Update to CS3 or CS4.
2. Check the ‘minimize embedded metadata’ checkbox in the Lightroom Export dialog, which will strip ALL of the metadata.  It solves the problem, but leaves you short of any metadata in your files.
3. Use Jeffrey’s Metadata Wranger to strip just the problem metadata from the file.  By far the best option!

How to use Jeffrey’s Metadata Wrangler

To use Jeffrey’s Metadata Wrangler export plugin, you’ll first need to download it from: http://regex.info/blog/lightroom-goodies/metadata-wrangler and install it using the instructions here: http://regex.info/blog/lightroom-goodies/plugin-installation/

Then select the plugin in the lower left of the Export dialog, and you’ll see the additional section appear in the main Export options panel – scroll down if you can’t see it.

The only part you want to remove is the ‘crs’ block marked in red in the screenshot – all of the rest of the data can stay.

Any images exported with the ‘crs’ block removed will quite willingly save as a jpeg even with Photoshop CS2.

If you’re just starting out with Lightroom, there are a few CRUCIAL bits of information which will save you hours of headaches and untangling. They’re the kind of thing that just make you say “I’d wish I’d known that before….” These are my top ten gotchas, direct from the forums.

1. Lightroom is all about non-destructive editing – so don’t try to save over your originals.
2. Lightroom doesn’t ‘contain’ files, it just holds data about them – so don’t go deleting your originals thinking that they’re safely stored in Lightroom.
3. Lightroom’s backups don’t back up your originals – you still need to do that.
4. Lightroom’s catalog is just a database, and databases can become corrupted – backup regularly, and keep older backups for a while.
5. Lightroom needs to know where the files are – don’t move or rename files outside of Lightroom, i.e. in Explorer or Finder, otherwise you’ll have a long job fixing all of the links.
6. Lightroom will not match your cameras rendering when working with raw files as it’s just raw data, but you can use the new profiles to emulate the manufacturer’s look for some cameras, or you can build your own profile to match.
7. Lightroom offers a choice of different colour spaces when you output, and AdobeRGB/ProPhotoRGB will look odd in programs that aren’t colour managed (like web browsers). Use sRGB for screen output like emailing or uploading to the web.
8. Lightroom’s Grid view behaves differently to other views – anything you do in Grid view applies to all selected images, whereas other views only apply to the most selected image.
9. Lightroom has 3 different levels of selection, not 2. Notice the difference, otherwise you could accidently apply a setting to multiple different images.
10. Lightroom’s Flags are local to the folder or collection, whereas star ratings and labels are global. This means that a photo can be flagged in one collection but not flagged in the folder.

Any more gotchas or blinding flashes of the obvious that you wish to add? You know, the things that make you go ‘Duh!’

Lightroom automatically chooses its own primary External Editor, based on registry entries on Windows and preference files on Mac.  It’ll generally default to the newest version of Photoshop, and if it can’t find Photoshop, it’ll use Photoshop Elements instead. There’s an old TechNote which explains further: http://www.adobe.com/go/kb401629

However, what if you want to use an older version of Photoshop, for example, to use plugins which are unavailable in the latest version?  It’s really simple – open that version of Photoshop yourself.  If Lightroom sees a Photoshop open, it’ll ignore its own preference, and use the open version instead.

It’s a question that comes up over and over again, because people expect it to be complicated.  It’s not really!  Even moving Windows to Mac is a straightforward operation.

First, a bit of preparation will go a long towards preventing headaches…

1. Make sure your regular backups are up to date.
2. Set Lightroom’s folder panel to show just a few top level folders, to make it easy to relink them if they get confused in the move.  Instructions are here: http://www.lightroomqueen.com/blog/2008/12/17/i-have-a-long-list-of-folders-can-i-change-it-to-show-the-folder-hierarchy/
3. Install Lightroom (the program) on the new computer.  No need to install off the cd and then install updates, as each update is the entire program, so just skip along to the latest update which can be downloaded from Adobe’s website.

Now we’re ready to move.  Think about how you’re going to move the files – an external hard drive is the easiest option.

If you’re switching from Windows to Mac in the move, remember that OS X can’t natively write to a NTFS formatted drive, so either format as FAT32, or remember you’ll need to copy the data off and reformat again once you’ve finished moving.

You’ll want to transfer all of your presets, which are entirely cross-platform, over to the new computer, and possibly your preferences file too, if you’re moving Windows to Windows or Mac to Mac.  Don’t forget any plug-ins, and custom DNG profiles that you’ve created too.  You’ll find all of the file locations here: http://www.lightroomqueen.com/blog/2008/12/15/default-file-locations-lightroom-2/ Bear in mind that these are hidden locations on Windows, so you’ll need to turn go to Start menu > Control Panel > Folder Options > View > Advanced Settings and turn on ‘Show hidden files and folders’ in order to find them.

You have 2 options for the catalog and images move – either moving and relinking, which is generally my preferred option, or using Export as Catalog, which is handy if data is scattered across your computer.

Option 1 – move and relink

1. Find and copy your catalog to the new computer.  If you don’t know where to find it, go to Edit menu > Catalog Settings (Windows) or Lightroom menu > Catalog Settings (Mac) and it’ll be listed there.
2. Find and copy your images to the new computer.  Personally I like to use File Synchronization software to make sure I don’t miss anything.
3. Open your catalog on the new computer – double clicking on it is the quickest way.
4. There may now be question marks all over the place, if it can’t find the files.  It’s just a question of relinking those top level folders with the updated folder locations.  Instructions here: http://www.lightroomqueen.com/blog/2009/02/21/lightroom-thinks-my-photos-are-missing-how-do-i-%ef%ac%81x-it/
5. Double check everything is up and running before you delete the old computer!

Option 2 – export as catalog

1. Open Lightroom and go to File > Export as Catalog.
2. Select a location on your external hard drive, and ‘include preview files’ and ‘include negative files’ so that everything is taken along.
3. Press Export and let it run.  It will take some time.
4. Now on your external hard drive should be a catalog, with an Images folder containing all of your negative files.  It should warn you if it couldn’t transfer some files.
5. Transfer the external hard drive to the other machine.
6. You could transfer the catalog itself (the *.lrcat file and *.lrdata file) to the new machine’s internal hard drive if you wish.
7. Double-click on the catalog to open it.
8. If you move the images, the drive letter changes between machines, or you’re moving between operating systems (i.e. Windows to Mac) you may still have to do the relinking listed in option 1.
9. Double check everything is up and running before you delete the old computer!

You’re all set!