Exporting RAW

Facebooktwitterlinkedin

Today’s Question: If I export a Lightroom edited photo in the RAW format, are the edited changes retained in the exported file?

Tim’s Quick Answer: Yes, in a manner of speaking, the adjustments you apply in Lightroom will be retained if you export a RAW capture in the “Original” RAW capture format. Just keep in mind that the actual adjustment settings will be stored within an XMP “sidecar” file, not within the copy of the RAW capture created as part of this process.

More Detail: When you use the “Original” option from the Image Format popup in the File Settings section of the Export dialog in Lightroom, the selected file (or files) will be copied to the destination you defined in the Export Location section. That means, for example, that JPEG images will be exported as a JPEG copy, and that original RAW captures will be copied in the same original RAW capture format.

Interestingly, for non-RAW captures when you use the “Original” option for exporting the adjustments you’ve applied in Lightroom’s Develop module are not included in the copy of the image created as part of that export process. So, for example, if you apply a conversion from color to black and white for a JPEG capture within your Lightroom catalog, if you export that image using the “Original” option you will create a JPEG image that is in color rather than black and white.

For RAW captures, however, the adjustments are included with the copy of the image file being created during the export process. Because the files being exported are proprietary RAW captures, however, the Develop adjustments are not included within the actual RAW capture. In other words, the RAW capture is a copy of the original capture, but an XMP sidecar file is included along with the copy of the RAW capture, containing the adjustments from Lightroom.

In other words, if you export a JPEG image from Lightroom with the “Original” option, the adjustments from within Lightroom will not be included. However, if you export a RAW capture with the “Original” option, the adjustment settings will be included in an XMP sidecar file.

So, if you then open the exported RAW capture in Photoshop, that image will be opened via Adobe Camera Raw, and the adjustment settings contained within the XMP sidecar file will be used as the basis for the initial settings within Adobe Camera Raw. Of course, you could also discard the XMP sidecar file if you truly want to access the original capture without any adjustments applied.

Moving a Catalog

Facebooktwitterlinkedin

Today’s Question: Can a [Lightroom] catalog currently on an external drive just be moved to a location on an internal drive, removing the catalog file from the external drive? Will this create a problem?

Tim’s Quick Answer: You can indeed move a catalog to a different location, such as from an external hard drive to an internal hard drive. As long as you move the entire folder containing the catalog, you’ll be able to re-open that catalog after moving it, with no problems at all.

More Detail: The files associated with your Lightroom catalog can be stored on an internal or external hard drive, and you can move the catalog files from one location to another as needed. Naturally I don’t recommend moving your catalog on a regular basis, as doing so can lead to a degree of confusion in your workflow. But if circumstances warrant moving a catalog, it can most certainly be done.

The process of moving your Lightroom catalog is relatively straightforward. First you need to know where the catalog folder actually is, which you can determine in the Catalog Settings dialog in Lightroom. Then close Lightroom, at which point you can move the folder containing your catalog files.

Out of an abundance of caution, I recommend copying the folder containing your catalog files (rather than moving it) and then renaming the original version to make it clear that it is now just a backup copy of your catalog. For example, you could add the word “BACKUP” to the beginning of the folder name for the original folder after you’ve copied that folder to a new location.

Once you have the catalog folder in the new location, you can launch Lightroom. You’ll receive an indication that the catalog couldn’t be found, since you’ve moved (or renamed) the folder containing the catalog files Lightroom is looking for. Simply direct Lightroom to open the catalog file (the file with the “lrcat” filename extension) from the new location and you’ll be back to working with your catalog, even though the catalog has been moved.

Note that the catalog references the specific location for all of your photos. When you move a catalog, that catalog will still reference the original location for your photos. So as long as you haven’t moved any photos outside the context of Lightroom, after you open a newly moved catalog, all of your photos will still be right where Lightroom expects to find them.

Noise Options

Facebooktwitterlinkedin

Today’s Question: For nighttime shooting with high ISO and/or longer exposures, what produces better results regarding noise: in-camera settings to reduce noise or dedicated software for noise removal?

Tim’s Quick Answer: While results will vary among different cameras, in general I have found that “black frame” long exposure noise reduction in the camera provides an advantage, but other in-camera noise reduction options are generally inferior to the use of software for reducing noise after the capture.

More Detail: For most cameras there are two basic noise reduction options available in the camera. The first is “black frame” long exposure noise reduction, and in general I have found the use of this option to be advantageous.

The main disadvantage is that this option will double the time required to capture a photo. That’s because this type of noise reduction operates by capturing a second exposure of the same duration but with the shutter closed. This creates a black capture is then used by the camera to remove the noise in the actual exposure based on the noise patterns in the black frame.

In my experience the other in-camera noise reduction options produce results that are inferior to what is possible with the best noise reduction software. In addition, for many cameras this option will only apply to JPEG captures, not RAW captures. In any event, I prefer not to take advantage of this type of in-camera noise reduction.

Again, the results will vary from one camera to the next, so it is worthwhile to perform some testing with your own camera to see how it performs. By testing the noise behavior of your camera you can determine which in-camera settings are best used, and also get a sense of the relative noise levels at different ISO settings.

Auto ISO

Facebooktwitterlinkedin

Today’s Question: What are your thoughts about the use of the Automatic setting for ISO?

Tim’s Quick Answer: My personal preference is to not use Auto ISO, but I certainly recognize that some photographers find it to be a convenient way to help ensure they are always using an adequately fast shutter speed.

More Detail: Most cameras that feature an Auto ISO option also enable you to set an upper limit for the ISO setting. This would enable you to ensure that the ISO will only go as high as you are comfortable with in terms of noise in your final image. That certainly mitigates my primary concern about Auto ISO, which is that the ISO will be set higher than I would like it to be.

That said, I still prefer not to use Auto ISO simply because I prefer to establish a fixed setting for ISO based on the current lighting conditions. When the light changes significantly or my preferences for the overall exposure settings change, I’ll dial in a new ISO setting. But in general I simply prefer to make a conscious decision about changing the ISO setting, rather than having the camera make that decision for me.

But again, I don’t think there is anything wrong with using the Auto ISO setting if you find it to be helpful in your photography, provided you set an upper limit for the ISO based on the noise behavior of your camera, and that you monitor the actual ISO setting that the camera is establishing for your images.

Eyeglass Coating

Facebooktwitterlinkedin

Today’s Question: I recently got a new pair of eyeglasses for computer use. The optician suggested a coating that reduces or eliminates the blue cast from computer monitors. The sample lens did make things appear warmer. Is this a good option? My monitor is calibrated, but if I get the coating should I recalibrate to compensate?

Tim’s Quick Answer: My personal preference would be to not use eyeglasses with this type of coating when making color corrections based on a monitor display. Alternatively, you could attempt to calibrate the display to compensate for the color shift your eyeglasses produces.

More Detail: I suspect your optician was thinking more about the overall viewing experience and perhaps eye strain, rather than color accuracy. Naturally, if the photos on your display look warmer (more yellow) than they actually are, you’re going to have a tendency to shift the color balance to a value that is too cool (blue).

You could, of course, simply remove the eyeglasses when you need to make a critical decision about color, if you prefer to have the effect of the coating at other times. Another option would be to calibrate to a different white point target for your display. The idea would be to make the display appear cooler (more blue) with a target value that offsets the effect of your eyeglasses.

There are two challenges involved with that. First, it will take some trial and error to figure out what target value will provide a good result. Second, the more entry-level display calibration tools don’t allow you to customize the target you’ll calibrate to for the white point.

If you prefer to calibrate to compensate for the effect of your eyeglasses, I would recommend the X-Rite i1Display Pro (http://timgrey.me/i1prodis), which provides you with the ability to set a custom white point target, among other advanced controls.

sRGB for Digital Sharing

Facebooktwitterlinkedin

Today’s Question: I saw your recommendation to convert photos to the sRGB color space for digital sharing such as slideshows. How do I do that in Lightroom?

Tim’s Quick Answer: In Lightroom you don’t actually convert an existing image to the sRGB color space, but rather apply that conversion when exporting an image, in the process creating a copy of the image to be used for sharing.

More Detail: Converting to the sRGB color space is a strategy employed to help ensure the most accurate appearance of your photos in situations where color management isn’t being employed. The idea is that because the sRGB color space was original designed to encompass the color range of a typical monitor display, it provides a good foundation for colors that will be shared digitally.

In applications such as Photoshop you can open a photo, convert it to the sRGB color space, and re-save the image, thus converting your master file to the sRGB color space. In Lightroom that option doesn’t exist, so instead you convert to sRGB when exporting a photo for sharing.

So, for example, you could select the photo (or photos) you want to share digitally, and click the Export button at the bottom of the left panel to bring up the Export dialog. In the File Settings section of the Export dialog you can choose the file type (such as a JPEG image for many types of digital sharing), and then choose sRGB as the color space from the Color Space popup. When you perform the export, new copies of the selected photos will be created, having been converted to the sRGB color space in the process.

Removing Duplicates

Facebooktwitterlinkedin

Today’s Question: I recently bought software (Duplicate Cleaner Pro) for checking for duplicate Images, and found an abundance on several of my external drives. The software gives me the option of getting rid of all the duplicates outside of Lightroom, but my question is, how can I do this in a way that lets LR know what’s being deleted? Any other tips you might have for deleting duplicate images safely?

Tim’s Quick Answer: My recommendation is to first make sure there are no missing photos in your Lightroom catalog. Then remove duplicates from your hard drive, and remove the resulting missing photos from Lightroom.

More Detail: Lightroom unfortunately does not have a built-in feature for locating and removing duplicate images. Therefore, a third-party utility is necessary for this task. However, you certainly want to coordinate that task to keep your photos properly organized in Lightroom.

The first step is to make sure that you don’t have any missing photos in your Lightroom catalog, so you can use the “missing” status later to synchronize the removal of duplicates. Start by going to the Library module in Lightroom, and choosing Library > Find All Missing Photos from the menu. If there are any missing photos, they will be presented in a “Missing Photographs” collection under the Catalog heading on the left panel. Resolve those missing photos by reconnecting them to the source files, or by removing them from your Lightroom catalog.

Once you no longer have any missing photos in your Lightroom catalog, you can employ software to search for and remove duplicate photos on your hard drive. Once those duplicates are removed, you then want to update your Lightroom catalog to reflect the changes.

Because you know there were no photos missing from your Lightroom catalog when you initiated this process, you can now use that “missing” status to remove the duplicates that had been deleted outside of Lightroom. First, choose the Library > Find All Missing Photos command once again. Then, once you are in the “Missing Photographs” collection in the Catalog section of the left panel, select all of the missing photos by choosing Edit > Select All from the menu. Finally, choose Photo > Remove Photos from the menu.

At this point, all of the duplicate photos that had been removed from your hard drive will also be removed from your Lightroom catalog.

Multiple Drives

Facebooktwitterlinkedin

Today’s Question: When I started in Lightroom a few years ago, I put my photos on an external (4TB) hard drive. That is where my catalogue resides as well. The drive is close to full, so I need to switch to a fresh external drive. What do I do about the catalogue? If I copy it to the new drive and work from it, when I plug it into Lightroom most of the photos won’t be available if I don’t have the first drive hooked up. Is there a real downside to starting a new catalogue on the new drive, for the new photos going forward? Then I would only need that external drive attached. If I want to work on the other photos, I can hook up the other drive. Am I missing something key?

Tim’s Quick Answer: I would actually recommend putting the Lightroom catalog onto the internal hard drive of your computer, both for improved performance and the ability to access your catalog regardless of whether the drives with your photos are connected. If possible I also recommend using a single hard drive for storing all of your photos.

More Detail: My preference is to use a single Lightroom catalog to manage all of my photos. With this approach, you don’t have to think about which catalog you need to open in Lightroom in order to locate a particular image. Instead you simply open your only Lightroom catalog, knowing that all of your photos are being managed by that catalog.

Whenever possible, I also prefer to have the Lightroom catalog stored on the internal hard drive of your computer. This enables you to open your catalog and even apply updates to the metadata of your photos, for example, without needing to connect the external hard drive that contains your photos. This approach will also generally provide improved performance in Lightroom, since an internal hard drive will generally be faster than an external hard drive (though not always, of course).

If at all possible, I also prefer to have all photos stored on a single external hard drive, simply to streamline the overall folder structure to reside on a single drive. In the context of Lightroom this approach also makes it a little easier to find a particular folder, since you’ll only have one list of folders in the Folders section on the left panel in the Library module.

RAW Support Workaround

Facebooktwitterlinkedin

Today’s Question: I have Adobe Photoshop CS5. It does not support the ARW files from my Sony Alpha a6000. I want to start my editing of a photo in Photoshop rather than Lightroom. Can the files be changed to a DNG by Photoshop instead of taking it into Lightroom?

Tim’s Quick Answer: Yes, you can convert your RAW captures to the Adobe DNG file format, and then open those DNG files directly in Photoshop via Adobe Camera Raw.

More Detail: For photographers who have chosen not to sign up for an Adobe Creative Cloud subscription or to use Adobe Lightroom as the central tool in their workflow, new or recently updated RAW capture formats may not be supported. The Adobe DNG Converter is a free utility that provides a workaround for this situation.

You can simply use the Adobe DNG Converter to convert your photos to the DNG format and then open those in Photoshop via Adobe Camera Raw. You can find a download link for the Adobe DNG Converter on the Adobe website here:

https://helpx.adobe.com/photoshop/digital-negative.html

The only caution I would add is to make sure that you are either always using Lightroom as the starting point for your workflow, or that you are never using Lightroom. A mixed approach to using Lightroom can create some serious organizational challenges.

But again, for photographers who have not upgraded to the latest version of Lightroom or signed up for an Adobe Creative Cloud subscription, the free Adobe DNG Converter does provide a workaround for updated RAW format support.

Smart Object Issues

Facebooktwitterlinkedin

Today’s Question: When you send an image from Lightroom to Photoshop for editing, do you choose the option to “Edit in Adobe Photoshop” or “Open as Smart Object in Photoshop”? What is the practical impact of each choice?

Tim’s Quick Answer: My preference is to use the “Edit In” command, and to not open the image as a Smart Object in Photoshop. While there are some very nice benefits to the use of Smart Objects, there are also some challenges related to a layer-based workflow.

More Detail: Smart Objects in Photoshop provide for some very interesting and potentially helpful features. In the context of applying a filter effect, for example, adding that filter as a Smart Filter (the variation on a Smart Object used for filters) enables you to refine the settings for the filter effect after that filter has been applied, with no degradation in overall image quality.

When sending a RAW capture from Lightroom to Photoshop (or opening a RAW capture as a Smart Object separately in Photoshop if you’re not a Lightroom user), you are essentially embedding the RAW capture into the file you’re creating in Photoshop. That allows you to simply double-click on the Smart Object layer to bring up the Adobe Camera Raw dialog so you can make changes to the original adjustments applied to the RAW capture.

That capability can certainly be very helpful in a variety of situations. However, it also creates some potential challenges related to a layer-based workflow.

As just one simple example, let’s assume a workflow that involves some image cleanup work with an image opened as a Smart Object. You make use of the powerful Content-Aware technology with the Spot Healing Brush tool to cleanup some dust spots and other blemishes in tricky areas of the photo. You apply this cleanup work on a separate image layer to maintain flexibility with a non-destructive workflow.

Later, you decide that the color isn’t quite right in the image, and you decide to refine the adjustments you applied to the original RAW capture. So you double-click on the Smart Object layer, and apply color changes via the Adobe Camera Raw dialog. The color in the image is improved, but now the color in the areas you cleaned up no longer matches the surrounding photo.

Ultimately, I think Smart Objects are an incredibly powerful feature in Photoshop. Unfortunately, for my purposes they aren’t quite “smart” enough, creating challenges for my preferred layer-based workflow. So until Smart Objects get a bit smarter, my preference is to not use Smart Objects in most cases. And therefore I simply use the “Edit In” command when sending a photo from Lightroom to Photoshop, rather than the option to open the image as a Smart Object.