Category: Ask Tim Grey

Today’s Question: I shoot in RAW, use Lightroom to edit my photos, but don’t want to be dependent either on my Lightroom catalog or even on the Lightroom application to access my photos. I import my RAW captures into Lightroom, make my desired edits, and then export both JPEG and DNG files (checking the “Embed Original Raw File” and unchecking the “Use Lossy Compression” options when exporting the DNG file). I then delete the original RAW file.

I can now print from or make additional edits to my image using the DNG file on any computer in any application that supports the DNG file format without needing to access either my Lightroom catalog or even the Lightroom application, and I am dependent neither on my Lightroom catalog nor even on the Lightroom application.

So if I decide tomorrow to never use Lightroom again, or if Adobe decides suddenly to discontinue Lightroom, I can continue to access all my images in any application that supports DNGs.

Should I abandon this process, and act more normally?

Tim’s Quick Answer: I recommend changing your workflow to make the most of all Lightroom has to offer while at the same time ensuring that your workflow is not completely dependent on Lightroom. I also don’t think it is necessarily a good idea to delete the original RAW capture files.

More Detail: I assume you are creating JPEG images to provide a “backup” copy of images that includes the adjustments you’ve applied within Lightroom. I don’t think this is necessary, and including this step in your workflow greatly increases the time and storage space required to accommodate those additional image files. I just see this as unnecessary clutter, in other words. If you get to the point that you can’t (or won’t) use Lightroom in your workflow, you could create copies of all existing images with a single export process at that point.

I’m also not entirely comfortable deleting the original RAW capture files. That is part of the reason I have not adopted the Adobe DNG file format as part of my workflow. But if you prefer to convert to DNG files and delete your originals it is reasonably safe to do so as long as you have confirmed that the DNG files are readable and have been backed up securely.

Frankly, if you’re not going to use Lightroom as the foundation of your full workflow for managing your photos, it might make more sense to find some other software you’re more comfortable with. However, I do think it is smart to avoid becoming too dependent on Lightroom.

Fortunately, with Lightroom it is relatively easy to adopt a workflow where you can leverage what Lightroom has to offer without creating a situation where it is very difficult to transition away from Lightroom at a later date. Photographers who adopted Apple Aperture for their image-management workflow, for example, can greatly appreciate the challenge involved in transitioning away from one software tool to another.

I recommend that you define a workflow that revolves around standard metadata fields, and then saving metadata updates to the image files themselves.

For example, instead of using collections in Lightroom as a key foundation of your organizational workflow, you might want to employ keywords. That way the keywords you add can still be available to any other image-management software you might use at a later date.

To save metadata to the image files on the hard drive, you can select all images in your Lightroom catalog and then choose Metadata > Save Metadata to Files from the menu. You can also have metadata updates saved to your files automatically by turning on the “Automatically write changes into XMP” checkbox in the Catalog Settings dialog (found on the Lightroom menu on Macintosh or the Edit menu on Windows).

My overall strategy involves retaining the original capture format from the camera, using a workflow that focuses on updating standard metadata fields (such as star ratings and keywords) rather than Lightroom-specific features (such as pick/reject flags and collections). I save the metadata to the files automatically, and also try to maintain an awareness of the current state of software so I can anticipate any issues that might require me to alter my workflow.

Today’s Question: In Photoshop, is there a way to copy a portion of the image, and then “flip it” (left to right) for pasting elsewhere in the original image?

Tim’s Quick Answer: Yes, indeed. You can simply create a selection of the desired area, create a new layer based on a copy of the selected area, flip horizontally or vertically with the Transform commands, and then use the Move tool to move the new layer into the desired position.

More Detail: It is quite easy to duplicate a portion of a photo and then flip that new layer and move it into a new position. One common use of this capability is a “mirror image” technique, which can be quite interesting. You can see a sample image I created using this technique on my Instagram feed here (be sure to follow me!):

https://www.instagram.com/p/BKSZZ0OA3l3/

The basic process is very straightforward. Start by creating a selection of the area you want to duplicate and flip. In the example image above, that would involve a rectangular selection of one-half of the image. You can then copy the selected pixels to a new layer by choosing Layer > New > Layer Via Copy from the menu (or by pressing Ctrl+J on Windows or Command+J on Macintosh).

To flip this new layer you can simply choose Edit > Transform from the menu, followed by either Flip Horizontal or Flip Vertical based on the direction you wish to flip. With the sample image linked above the Flip Horizontal command was selected.

You can then use the Move tool to move the new layer to a different location within the image. In the case of the “mirror image” technique, for example, I would have selected and duplicated the right half of the image, flipped the layer horizontally, and then moved the new layer to the left half of the image. But of course you could move the new layer to any position you’d like within the image. If for any reason you need to drag the new layer to a position that falls outside the existing image area, you can simply choose Image > Reveal All from the menu to enlarge the canvas so you can see the entire image area.

For readers who subscribe to my Pixology magazine, you can find more details about this technique in the article “Step by Step: Mirror Image”, featured in the August 2016 issue.

Today’s Question: I remember the time that you were very happy with Nik Software, and recommend it with pleasure. I want to sign up for a Photoshop Creative Cloud subscription. Info on the web informs me that difficulties will rise using Photoshop CC and the Nik plug-ins. Can you tell us whether we should be concerned that the Nik Collection will stop working with Photoshop?

Tim’s Quick Answer: I think there is most certainly a reason to be concerned that the Nik Collection will no longer function well in the near future, and to begin looking for alternative solutions if you are currently using any of the tools in the Nik Collection.

More Detail: The Nik Collection is a set of software and plug-ins that were originally released by Nik Software, which was acquired by Google in 2012. Originally the suggestion was that there would not be any future updates with new features, there would be updates to ensure that these software tools continued to function with operating system and host application updates.

However, more recently Google has updated the page for the Nik Collection (https://www.google.com/nikcollection/) to indicate that no future updates of any kind will be released. The existing Nik Collection (which is still available as a free download) will only function properly with Mac OS X through version 10.10, Windows through version 8, and Adobe Photoshop through version CC 2015.

I have run into some minor issues with several of the software tools in the Nik Collection, and suspect those problems will only increase with future updates to Photoshop and the operating systems.

I will be providing more details on recommended replacements for the various tools in the Nik Collection. In the short term I know many photographers are particularly interested in options for creating high dynamic range (HDR) images. I have found that Adobe Lightroom’s built-in feature for HDR assembly works very well, and that Aurora HDR 2017 is also an excellent solution. Keep in mind that Aurora HDR 2017 is currently only available for Macintosh users, but Macphun Software has indicated that a Windows version will be coming soon.

I will provide more recommendations in the future related to replacement recommendations for the Nik Collection.

Today’s Question: I purchased a new laptop for travel and teaching. I want to use the same Lightroom catalog and images on both machines [laptop and desktop]. What do you recommend?

Tim’s Quick Answer: In this type of situation my recommendation would be to keep both your Lightroom catalog and your photos on the same external hard drive. You can then open the catalog from that external hard drive on whichever computer you’re currently using to work with your images.

More Detail: Lightroom does not offer a native solution for effectively working with your full catalog on more than one computer. That includes the inability to store your catalog on a network storage location, preventing you from being able to access the catalog from multiple computers on a network.

Some photographers have employed an online synchronization service such as Dropbox (https://www.dropbox.com) to make a catalog available on more than one computer. While this can most certainly be a workable solution, I do have concerns about the potential for synchronization failure, and of course this type of approach would require that you have access to an Internet connection in order to synchronize the actual files you’re working with.

As a result of the various limitations related to working with a catalog across two computers, I recommend simply keeping the catalog itself on an external hard drive along with the photos being managed by that catalog. You can then connect the external hard drive to whichever computer you want to work with currently. Within Lightroom, you can then open the catalog directly from the external hard drive, so that you’re always working with the actual catalog files (without the need for synchronization), and you always have your photos readily available as well.

The only potentially significant drawback to this approach of storing the Lightroom catalog on an external hard drive is degradation in performance. Most external hard drives are slower than a comparable internal hard drive, and there are also latency issues that can further degrade performance. For some photographers this reduction in performance is reason enough to work with only a single computer for Lightroom. For example, I keep my Lightroom catalog on my laptop, so that I always have access to the catalog whether I’m at home or traveling with my laptop.

Today’s Question: I get a message about metadata confusion in Lightroom when I work on the image in both Lightroom and Photoshop without closing and reopening the image. I don’t know which choice to check, Import Settings from Disk, or Overwrite Settings. Would you please explain these two choices and the benefits of each?

Tim’s Quick Answer: The solution here is actually to never open an image directly from Photoshop or otherwise update the metadata outside of Lightroom. If you ensure that all tasks related to your images are initiated within Lightroom, you won’t experience this data mismatch in the first place. Resolving the issue for images that have already been impacted requires making a decision about which updates to keep versus discard.

More Detail: If you update metadata for an image outside of Lightroom, the result will be a mismatch between the metadata stored with the image and the metadata in your Lightroom catalog. Even opening a RAW capture directly in Photoshop will cause adjustment metadata to be updated. Updates made outside of Lightroom will not be reflected in your Lightroom catalog, causing a mismatch and potential confusion, as well as the risk of lost data.

For example, let’s assume you add a keyword in Lightroom. If you have enabled the option to automatically save metadata out to the actual files on your hard drive (or you have manually saved that metadata) then you can see the updates in other software. So, for example, the new keyword you added would be visible if you browse the image with Adobe Bridge.

However, if you add a keyword with Adobe Bridge, that keyword will not be visible within Lightroom, because Bridge can’t add the keyword to your Lightroom catalog. Lightroom can recognize when the metadata in your catalog doesn’t match the metadata in the image file on your hard drive, and alert you of this mismatch.

To resolve the issue for images that were processed outside of Lightroom, you’ll need to decide which updates to keep and which updates to discard. For example, if you added “Bridge” as a keyword from Adobe Bridge and you added “Lightroom” as a keyword from within Lightroom, you can’t retain both keywords. You’ll need to choose whether to keep the metadata from the file on your hard drive (“Bridge” in this example) or to keep the metadata within Lightroom (“Lightroom” as a keyword in this case). In this example, one of the two keywords will be lost when you choose an option.

If you choose the “Import Settings from Disk” option in the metadata mismatch dialog, then the Lightroom catalog will be updated with all of the metadata contained in the image on your hard drive, overwriting the metadata for that image in the Lightroom catalog. If you choose the “Overwrite Settings” option, the metadata from your Lightroom catalog will be saved to the image file on the hard drive, overwriting the metadata that was there. In either case, of course, the metadata mismatch will no longer exist.

As noted above, the real solution is to avoid this problem in the first place. Once you start using Lightroom to manage your photos, it is critical that you initiate all tasks related to your photos from within Lightroom. This will ensure that your Lightroom catalog always remains up-to-date.

Today’s Question: When opening an in image in Lightroom for editing in Photoshop I’ve always had a pop up that asked if I wanted a copy, copy with Lightroom edits, or the original file to export to Photoshop. After an update, it’s gone, no pop up at all, and it exports the original RAW file. How do I get this pop up back so I can export copies to edit in Photoshop?

Tim’s Quick Answer: Actually, Lightroom is still creating a copy of the RAW file. The only change is that you’re not seeing the dialog, but really the dialog isn’t necessary since a copy would always be created, and your original RAW capture would remain untouched. So having the dialog no longer appear is actually a good thing, although perhaps a bit confusing.

More Detail: A relatively recent update to Lightroom caused the dialog in question to no longer appear when you are sending a RAW capture to Photoshop from Lightroom using the Photo > Edit In command from the menu. With other file types (such as JPEG, TIFF, or PSD) the dialog will still appear, since in those cases you could choose whether you want to make a copy or simply open the source file directly.

With a RAW capture, the source image is processed and sent to Photoshop, creating a TIFF or PSD file in the process. You can choose which file type (and the basic settings for that file) on the External Editing tab of the Preferences dialog in Lightroom.

The adjustments you have applied to the RAW capture in Lightroom will automatically be reflected in the derivative image that is created as part of this process.

Today’s Question: I have kept my photo collection on my C drive on my laptop, organized by year and month. I have duplicates of the collection on two external hard drives (J and G drives). Now I wish to delete all photos off my C (internal) drive, and work only from the J drive, with backup to the G drive. How do I manage this transition?

Tim’s Quick Answer: Assuming you have already made an exact copy of the photos on your internal hard drive to the external hard drive, with the exact same folder structure, I would recommend connecting the existing catalog to the external hard drive. This will involve fewer risks than trying to create a new catalog or deleting the photos from the internal drive from within Lightroom.

More Detail: It is important to keep in mind that your Lightroom catalog is simply managing information about your photos and referencing the source image files in their storage location. If you copy photos from one location to another outside of Lightroom, it is important to avoid creating a mismatch between the Lightroom catalog and your overall photo storage.

Normally the approach I would recommend in a situation like this would be to start by creating a reliable backup (or two, or more) of the photos on your internal hard drive. Then, within Lightroom, I would move all of the folders from the internal hard drive to the external hard drive you want to use moving forward.

In this case you have already copied photos from the internal hard drive to an external hard drive. As long as the copy is an exact match of the original (such as by using synchronization software), then you can connect the existing references to your photos to the new storage location.

The first step here is to “hide” the photos on the internal hard drive from Lightroom. This can be as simple as renaming the top-level folder for the overall storage structure, so that Lightroom will no longer find the folders and photos where they are expected. You can then right-click on any of the folders that now appear to be missing within Lightroom, and choose the option to reconnect the missing folder. In the dialog that appears you can then select the corresponding folder on the external hard drive. Lightroom should then recursively reconnect all folders on that external hard drive, so there are no longer any missing photos or folders within Lightroom.

In effect, what you’re doing here is redirecting Lightroom to the exact same folder and photo structure on a different drive. In the process you will not lose any information for your photos, since the catalog information is still available and you are simply referencing different copies of your photos.

Once that overall process is complete and you have confirmed that everything is in order in Lightroom, you can make yet another backup of your photos on the external hard drive, and then delete all photo folders on your internal hard drive to free up space. This last step, of course, should be postponed a little while to make sure all of your photos are safely being managed from your external hard drive before removing the photos altogether from your internal drive.

Today’s Question: I’m puzzled by the extreme variation in file sizes after I resize in Photoshop then compress in JPEG format. My regular work involves processing a group of images starting with a RAW capture, and then processing in Lightroom, then exporting to Photoshop as a 16-bit TIFF. I convert to 8-bit, do routine adjustments, save, and then resize to specific pixel dimensions of 1024 x 681. Then I save as a JPEG at a Quality level of 8, which is where the question arises. The size of the final JPEG images ranges from around 200KB to sometimes 4MB. Is there a good explanation for this?

Tim’s Quick Answer: There can actually be a tremendous degree of variation in file size for JPEG images, based on the contents of the photo. In addition, additional variation can be caused by the amount of metadata embedded in the image as well as whether an ICC profile is embedded as part of the image.

More Detail: It is very common to see file size variations for JPEG images that represent about a factor of six or more. In other words, after processing a group of photos to create JPEG images with the same overall settings, if the smallest file size is around 100KB I would not be surprised if one or more images had a file size of around 600KB.

If you have an embedded profile for some images but not others, this would generally create a file size difference of around 200KB. That can obviously create a larger spread. Metadata will, of course, generally not cause a tremendous variation in file size, though that obviously depends on how much additional metadata (such as keywords) you’re adding to the images.

If some of the images are HDR captures, there is certainly a greater potential for variation in file sizes. That is because HDR images often contain more detail that non-HDR images, and greater detail results in a larger file size with a JPEG image.

I would say that a 4MB file size for a JPEG image that has pixel dimensions of 1024×681 pixels is highly unlikely. I would check to see which ICC profile you are embedding (if any), and the size of that profile. If you are consistently converting the images to the sRGB color space then you shouldn’t see this variation. But if a different profile with a larger file size is being used in some cases, that could certainly explain the larger file sizes in some cases.

Today’s Question: Suppose you have a folder named “tigers” and in this folder you have identified some of the images as “mom”, “dad”, “son”.  But you also have some that were simply tagged “tigers” without further classifying and now you want to go back to put them in mom, dad, or son. Is there any way to sort the tigers folder for the images that are NOT mom, dad, son? Otherwise, you have to go back through the entire folder watching the keyword list and stop when you don’t see mom, dad, or son, which would be very tedious.

Tim’s Quick Answer: In this case you could simply filter the images based on a text filter based on the “Don’t Contain” option for Keywords, entering “mom, dad, son” into the search field. If you want to further filter the images so you are only seeing those with the “tiger” keyword but without the “mom”, “dad”, or “son” keywords, you can use the Keyword option with the Metadata filter to specify that you want to see images that include “tiger” as a keyword.

More Detail: The filtering options within Lightroom are surprisingly sophisticated, though the many possibilities for locating images aren’t necessarily all that obvious. In this case a combination of filtering by a keyword and also filtering by the absence of several keywords will provide the desired solution.

In the Library module you can display the Library Filter bar (if it isn’t already displayed) by choosing View > Show Filter Bar from the menu or by pressing the backslash key (\) on the keyboard. Be sure you have navigated to the folder that contains the images you want to filter, and then set your filter criteria.

To filter the images to show those that do not have certain keywords added, you can use the “Don’t Contain” option. Click the Text header to bring up the text filter fields, and set the first popup to “Keywords” so you can filter specifically by the Keywords field in metadata. Then choose “Don’t Contain” from the second popup, so you can filter based on an absence of specific keywords. Then enter the keywords that are absent from the images you’re looking for, separating each by a comma. In the example from today’s question you could enter “mom, dad, son”.

You can then choose the Metadata option to filter based on images that do contain a specific keyword, such as “tiger” in this example. Click the header for the right-most column in the Metadata section, and choose “Keyword” from the popup menu. That column will then display a list of all available keywords, so you can choose one or more keywords that you want to filter based on those keywords being included in metadata for the image. In this example you could choose “tiger” from that list.

In this way you will be filtering the images so that only those containing one or more keywords (just “tiger” in this case) and that don’t contain any of another set of keywords (“mom”, “dad”, and “son” in this case). That, in turn, will enable you to review the images, perhaps in this example enabling you to add the “mom”, “dad”, “son” keywords that hadn’t yet been added for all images.

Today’s Question: I made a duplicate copy of an image in Lightroom and tried to add it to a new folder in Lightroom. It transferred both images so I “removed” the duplicate. Unfortunately it also removed the original. Is there an easy way to find it and put it back in Lightroom?

Tim’s Quick Answer: If you removed the image from the catalog without deleting it, you can simply synchronize the folder to recover the image. If you deleted the image itself, the only possible solution is to recover the image file from the Trash/Recycle Bin in your operating system.

More Detail: When you create a copy of an image within Lightroom, you are actually creating a “virtual copy”. This is essentially just a second set of adjustments so you can create two different interpretations of a photo in the Develop module. The source file is not duplicated on your hard drive, so you still only have a single copy of the source image.

If you move an image from one folder to another, any virtual copies associated with that image will also appear to be moved to that destination folder. This is because the virtual copy isn’t an actual file, but rather just a set of additional adjustments within Lightroom.

This can certainly lead to some confusion when it comes to removing a photo from your catalog. If you select the option to remove a virtual copy (by right-clicking on the virtual copy and choosing the “Remove Photo” command), you will simply be asked to confirm that you want to remove that virtual copy, since doing so won’t cause the source image to be deleted.

If you choose the “Remove Photo” command after right-clicking on the source image (rather than the virtual copy) then you’ll have a couple of options. You can remove the image from your Lightroom catalog without deleting the source file, or you can delete the source file from your hard drive. With either option, by removing the source image the virtual copy will be removed as well. Note that choosing the option to delete the source file will actually move that file to the Trash or Recycle Bin for your operating system, so you can still recover the file from that location as long as you haven’t “emptied” that Trash/Recycle Bin.

If you used the “Remove” option, then you can bring the source image back into your catalog by synchronizing the applicable folder. Simply right-click on the folder in question and choose “Synchronize Folder” from the popup menu. In the Synchronize Folder dialog be sure the “Import new photos” checkbox is turned on, and click the Synchronize button to add the images that had been removed back into your catalog.

If you deleted the source image, you’ll need to first recover the files from your Trash or Recycle Bin, and then use the “Synchronize Folder” command to bring those images back into your Lightroom catalog.