Multiple Derivative Images

Facebooktwitterlinkedin

Today’s Question: How can I save different edited versions of a photo back to Lightroom Classic? If I try “Save As” I don’t have the option to go back to Lightroom, only back to my hard drive.

Tim’s Quick Answer: You can actually use the Save As command to create multiple versions of the image in Photoshop, which will generally then automatically be added to your Lightroom Classic catalog. It is important, however, to only use the Photoshop PSD or TIFF file formats when using “Save As” in Photoshop with this workflow.

More Detail: In the early days of Lightroom Classic (before it was called Lightroom Classic) using the Save As command in Photoshop for an image you sent from Lightroom was generally problematic, with the resulting file not being added to your Lightroom catalog. At some point in the recent past, this issue was resolved, as I’ve found that you can use the Save As command in Photoshop reliably for images sent from Lightroom Classic.

However, you must save the image as either a Photoshop PSD or TIFF file in order for it to be added to the Lightroom Classic catalog. If you save the image as a JPEG in Photoshop, for example, it will not be added to the catalog.

So, the workflow is relatively straightforward if you want to create multiple derivative versions of the same source photo. Start by selecting the photo in Lightroom Classic. Then go to the menu and choose Photo > Edit In > Edit in Adobe Photoshop. If the source image is a raw capture it will simply be opened in Photoshop. If you selected a different image type (such as a JPEG) you’ll be prompted for how you want to process the image, in which case you should generally select “Edit a Copy with Lightroom Adjustments”.

Once in Photoshop, you can apply any adjustments you’d like to the image. When you’re finished, you can simply choose File > Save to save the updated file in the same location as the source image, with an updated filename based on the settings in Preferences in Lightroom Classic.

Before closing the file in Photoshop, you could create an additional derivative version. After saving the first version, apply additional adjustments and choose File > Save As. Make sure you save as either a PSD or TIFF file, and you can otherwise save the image in any location and with any filename you’d like. You can repeat this process for as many derivative variations as you’d like to create. Then close the image, and when you get back to Lightroom Classic you should find all of the derivative versions you created.

If for any reason one or more of your derivative images didn’t show up in your Lightroom catalog, you can simply synchronize the applicable folder where the derivative files are saved (presumably in the same folder as the source image). To do so, right-click on the folder name in the Folders list on the left panel in the Library module and choose “Synchronize Folder” from the popup menu that appears. Click the Synchronize button in the dialog that appears, and the new images will then be added to your catalog.

Resolution with Infrared

Facebooktwitterlinkedin

Today’s Question: If I have a camera body which has been converted to infrared capture and the sensor filter that was installed allows only black & white. Am I only getting use of 1/3 of the RGB pixel sites? If so, would I be better off converting a camera body with an overall resolution of 45 megapixels or getting an infrared (IR) filter conversion that allowed color IR for a 24-megapixel body?

Tim’s Quick Answer: You are indeed getting the full resolution of your image sensor when a camera is converted for digital infrared. The only thing that is changing is the range of light wavelengths that are recorded by the image sensor.

More Detail: Converting a digital camera to infrared capture generally involves two steps. The first is to remove the infrared cutoff filter that is installed in front of the actual image sensor on most cameras. This filter ensures that the sensor will not record infrared light, which could cause artifacts and other issues with a color photo. In other word, the camera is only able to capture light within the visible spectrum based on human vision.

Once the infrared cutoff filter is removed, the image sensor is capable of capturing light within the visible spectrum as well as the infrared spectrum. For infrared photography, you generally don’t want the visible spectrum included in your captures. Therefore, an infrared filter needs to be added for infrared photography.

Some infrared conversions include the addition of an infrared filter to the front of the image sensor, so that the camera is only capable of infrared photography. Alternately, that infrared filter might be left off, which would then require that you use an infrared filter on your lens in order to capture infrared photos. The benefit of the latter approach is that you could use the camera for both color and infrared photography.

As noted above, however, all of the pixels (photo sites) on the image sensor are still being used to capture the infrared information. Therefore, you should select a camera for infrared conversion based on the resolution you want available for the final file size. If you’ll be producing large prints, for example, you’ll want to opt for a camera with a relatively high resolution, all other things being even.

Mysterious Crop Option

Facebooktwitterlinkedin

Today’s Question: I’ve been trying to get more familiar with the various adjustment options in Lightroom Classic, including with the Crop tool. For the life of me I can’t figure out what the “Constrain to Image” checkbox does, as it doesn’t seem to impact my cropping whether it is on or off. Does this checkbox do anything?

Tim’s Quick Answer: The “Constrain to Image” setting for the crop tool in Lightroom Classic ensures that the crop only includes the actual image area of your photo. It only actually applies if you have applied an adjustment (such as a Transform adjustment) that causes there to be white space outside of the original image area.

More Detail: If you haven’t done anything to alter the actual shape of a rectangular photo, the “Constrain to Image” checkbox won’t have any impact on the behavior of the Crop tool. In other words, if you don’t see any “extra” white space around your photo, the “Constrain to Image” feature doesn’t apply.

If you had, for example, applied some of the adjustments found in the Transform section of the right panel in the Develop module, the overall shape of the image may have been altered to the point that some white space appears around portions of the edge of the image.

For example, the Vertical slider allows you to tilt the image toward or away from you, to correct for perspective issues. With even a small adjustment, you’ll see white triangles appear at the top or bottom corners of the image, depending on whether you apply a positive or negative value for the adjustment.

If such white space appears around the edges of the image, turning on the “Constrain to Image” checkbox for the crop tool will ensure that the crop box can never extend beyond the actual image area, causing any of those white boundary areas to be cropped out of the image.

You can, of course, simply manually make sure that the crop box remains inside the actual image area, but the “Constrain to Image” checkbox makes it easy to ensure you don’t miss a small area, creating what would effectively be a blemish along the edge of the photo.

Preset Review Redux

Facebooktwitterlinkedin

Today’s Question: To see the contents of a Lightroom Classic User Preset you find it by using the “Show Lightroom Develop Presets” command in Preferences, and then open the applicable preset file in any text editor. You can even modify the commands and save the modified preset using the same name or a different name.

Tim’s Quick Answer: It is true that you can review the changes applied by a Develop module preset in Lightroom Classic by reviewing the XMP file that represents the saved preset. However, it can be a little tricky to interpret the information in the XMP file.

More Detail: This is a follow-up to the Ask Tim Grey eNewsletter from April 15, 2020, where I answered a question about reviewing the contents of a Develop module preset. I suggested switching between a “before” and “after” view of an image while watching the adjustment controls on the right panel. However, as noted above, it is actually possible to review the contents of the preset with a text editor outside of Lightroom.

As noted in today’s “question”, you first need to navigate to the location where your presets are stored. You can select “Preferences” from the Edit menu on Windows or the Lightroom Classic menu on Macintosh to bring up the Preferences dialog. Then go to the Presets tab and click the “Show Lightroom Develop Presets” button. This will bring up a window in your operating system showing you the parent folder where the presets are stored. Double-click on the highlighted folder and locate the specific preset you want to review.

When you find the applicable preset, you can open it in any text editor, or a word processor that supports plain text files. There will be a fair amount of information that won’t be especially readable or useful, but you can also find details about the various adjustments included in the preset. For example, in the text from a sample XMP file below you can discover that the Clarity adjustment has been increased to a value of +17 with this preset.

This certainly provides an option for reviewing the information included in a Develop preset, though it can be a little difficult to interpret some of the details. You can get a sense of what is involved with this sample from an XMP file for one of my Develop presets:

<x:xmpmeta xmlns:x=”adobe:ns:meta/” x:xmptk=”Adobe XMP Core 5.6-c140 79.160451, 2017/05/06-01:08:21 “>
<rdf:RDF xmlns:rdf=”http://www.w3.org/1999/02/22-rdf-syntax-ns#”>
<rdf:Description rdf:about=””
xmlns:crs=”http://ns.adobe.com/camera-raw-settings/1.0/”
crs:PresetType=”Normal”
crs:Cluster=””
crs:UUID=”F9006AD0CB864EA18BFA4B2ACCA68A56″
crs:SupportsAmount=”False”
crs:SupportsColor=”True”
crs:SupportsMonochrome=”True”
crs:SupportsHighDynamicRange=”True”
crs:SupportsNormalDynamicRange=”True”
crs:SupportsSceneReferred=”True”
crs:SupportsOutputReferred=”True”
crs:CameraModelRestriction=””
crs:Copyright=””
crs:ContactInfo=””
crs:Version=”11.4″
crs:ProcessVersion=”11.0″
crs:ColorNoiseReduction=”25″
crs:ColorNoiseReductionDetail=”50″
crs:ColorNoiseReductionSmoothness=”80″
crs:LensProfileEnable=”1″
crs:AutoLateralCA=”1″
crs:Clarity2012=”+17″
crs:DefringePurpleAmount=”0″
crs:DefringePurpleHueLo=”30″
crs:DefringePurpleHueHi=”70″
crs:DefringeGreenAmount=”0″
crs:DefringeGreenHueLo=”40″
crs:DefringeGreenHueHi=”60″
crs:AutoTone=”True”
crs:LensProfileSetup=”Auto”
crs:HasSettings=”True”>
<crs:Name>
<rdf:Alt>
<rdf:li xml:lang=”x-default”>Import Develop Preset</rdf:li>
</rdf:Alt>
</crs:Name>
<crs:ShortName>
<rdf:Alt>
<rdf:li xml:lang=”x-default”/>
</rdf:Alt>
</crs:ShortName>
<crs:SortName>
<rdf:Alt>
<rdf:li xml:lang=”x-default”/>
</rdf:Alt>
</crs:SortName>
<crs:Group>
<rdf:Alt>
<rdf:li xml:lang=”x-default”>Tim’s Import Presets</rdf:li>
</rdf:Alt>
</crs:Group>
<crs:Description>
<rdf:Alt>
<rdf:li xml:lang=”x-default”/>
</rdf:Alt>
</crs:Description>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>

Photoshop Workflow Mystery

Facebooktwitterlinkedin

Today’s Question: I must have some setting not correctly configured in Lightroom. When I edit a JPEG image in Photoshop from Lightroom Classic, the image is saved as a Photoshop file but does not appear in Lightroom’s Library in any collection. I’m not using the ‘Save As’ command. I have to import that PSD image manually into Lightroom. What is the setting (or workflow) that would allow me to accomplish an edited JPEG images as PSD directly into the library? Appreciate any advice you may have.

Tim’s Quick Answer: When you send a photo from Lightroom Classic to Photoshop, and then save and close the image, that image will be saved in the same folder as the original file. Note, however, that the new file will only be added to a collection that the original image is in if you sent the photo to Photoshop from within a collection.

More Detail: In this particular case, I suspect one of two things are happening. First, it is possible that the photo is being sent to Photoshop from a folder in Lightroom Classic, and then you are looking for the image in a collection that the original photo is contained in. In that case the PSD file created as part of this process would not appear in the collection. For the PSD to appear in a collection, you would need to send the image to Photoshop by first selecting it within the collection (not the folder) in Lightroom Classic.

The other issue I see somewhat frequently is confusion caused by the application of filters. For example, when you are searching for the original image in order to send it to Photoshop for additional adjustments, you might filter by file type, such as to locate a raw or JPEG capture. If you then send the image to Photoshop, when you are finished working in Photoshop and return to Lightroom, you won’t actually see the new derivative file that was created.

That is because the new derivative image would be a PSD (or TIFF, depending on the settings you’ve established in Preferences), which would not fit the current filter criteria. Turning off the filter would then cause the PSD file to appear.

Locking Search Filters

Facebooktwitterlinkedin

Today’s Question: Is there a way in Lightroom Classic to ensure that when I open the software it will always open with the last filter setting? I generally have my filter set on a user preset I created called “Flagged and Unflagged.” Every time I open Lightroom it defaults to the “Filters Off” filter.

Tim’s Quick Answer: You can indeed ensure that Lightroom Classic will retain a selected filter setting by turning on the “lock” on the Library Filter bar.

More Detail: By default, when you apply a filter in Lightroom Classic, that filter is only active temporarily. However, it is possible to lock the filter so it will be retained until you turn it off.

For example, let’s assume you have set a filter so that only images with a three-star or greater rating are displayed. You can browse the current folder, and will only see images with a star rating of three stars or more. However, as soon as you navigate to a different folder, the filter is reset to “None”. The same holds true if you quit Lightroom Classic and then launch it again.

You can change this behavior, however, by clicking the “lock” icon to the far right of the Library Filter bar at the top of the grid view display in the Library module. If the Library Filter bar is not visible, you can enable it by pressing the backslash key (\) or by choosing View > Show Filter Bar from the menu. Note that the Library Filter bar is only available in the grid view in the Library module, so if you are in the loupe view for example the above options will switch Lightroom to the grid view.

By default, the lock icon will have the shackle of the lock up, indicating that it is unlocked. You can click the icon to toggle between “locked” and “unlocked”. Admittedly, because of the design of the icon, it is a little difficult to tell the difference between the two, but the taller icon means unlocked, and the shorter icon means locked.

When you lock the filters, the current filter settings will remain in place until you turn off the lock. That includes the ability to navigate among different folders with the same filter settings, for example. It also means that when you quit Lightroom Classic and launch it again, the filter will still be in place.

Reviewing a Develop Preset

Facebooktwitterlinkedin

Today’s Question: I have been using a custom User Preset [for the Develop module in Lightroom Classic] that I created one year ago to be applied to every photo upon import. After completing your first class in “Optimizing Photos in Lightroom Classic”, I wanted to see what this preset was actually doing. How do I look at the “content” of an existing User Preset to see if it is still appropriate, or if I need to modify some parts of this preset?

Tim’s Quick Answer: Lightroom Classic doesn’t provide a way to review a list of which adjustments and settings are actually included in a preset. So I recommend using a “before and after” approach to evaluating the differences applied by the preset.

More Detail: First I recommend finding a “test” image that you’re not concerned about the adjustments for. This could be an outtake from a recent photo shoot, for example. Click the Reset button at the bottom of the right panel in the Develop module to set the image to the default adjustment settings.

Next, apply the preset you want to evaluate by selecting that preset from the Presets list on the left panel in the Develop module.

To compare the “before” version of the image without the preset, versus the “after” version with the preset, you can use the History section of the left panel. Simply click back and forth between the Reset Settings step and the Preset step. As you do so, watch the change in adjustment settings on the right panel.

I recommend checking each section individually, so you can be sure to consider all of the various adjustments that are included in the preset, and the actual settings being used for those adjustments.

If you decide you want to make changes to the preset, first make sure you have the preset actually applied to the image, such as by selecting the “Preset” history state in the History section on the left panel. Then change any of the adjustment settings you want to update for the preset on the right panel. Then right-click on the preset in the Presets list on the left panel, and choose “Update with Current Settings” to save the updated adjustments for the existing preset.

Reuniting XMP with Raw

Facebooktwitterlinkedin

Today’s Question: Recently I noticed the dreaded exclamation point appeared in Lightroom Classic on some treasured images. All I could find on my main drive and on my 1st backup were the XMP files. But after a bit of deep breathing, I found the RAW originals on my trusted 2nd backup drive–but only the RAW (CR2) files, no XMPs. Now need to reimport the RAW files into Lightroom Classic. Is it possible to reimport the RAW files so that they pair up with the XMP files and I can keep my ratings and edits?

Tim’s Quick Answer: Yes, you can put the raw captures and the XMP files in the same folder, and then import the photos from that folder. As long as metadata updates were saved to the XMP files, upon import you would have all of your photos and most of the updates you had previously applied to those photos. However, in this case a better approach would be to simply copy the backup copies of your raw captures into the folder where they belong, so they are no longer missing in the context of your Lightroom Classic catalog.

More Detail: One of the reasons I highly recommend enabling the option to “Automatically write changes into XMP” in the Catalog Settings dialog in Lightroom Classic is that it ensures that most of the updates you apply in Lightroom Classic are saved to the source images, in addition to having those updates in the catalog. In the case of proprietary raw captures, the metadata updates are saved to XMP sidecar files that are co-located with the raw capture, with the same base filename and an “xmp” filename extension.

If your Lightroom Catalog became corrupted, for example, you could simply create a new catalog and import all of your source photos into the new catalog. Most of the metadata, which would have been written to XMP sidecar files for raw captures or to the source image file in the case of other supported file formats, would then be imported along with your photos into the new catalog.

However, some key features are not included in the metadata for XMP sidecar files. For example, Pick and Reject flags would not be included, nor would any collections those photos had been added to. The History in the Develop module would be empty for those images, and no virtual copies would be retained.

So, it is preferable to locate missing photos within Lightroom Classic rather than re-importing the raw captures, even if you have the XMP files that contain most of the metadata for the photos.

In this case, since the original raw captures have been located, they can simply be copied to the applicable folder. As long as the filenames are the same, that will cause the photos to no longer be missing. And the advantage of this approach is that you won’t lose any of the information about those photos from your Lightroom Classic catalog.

Backup Including Edits

Facebooktwitterlinkedin

Today’s Question: In your opinion what is the best strategy for backing up Lightroom Classic images while keeping image edits?

Tim’s Quick Answer: I recommend using a synchronization approach to backing up your photos, and using the built-in backup feature in Lightroom Classic to backup the catalog.

More Detail: One of the most important attributes of a good backup strategy is that the backup copy of your data needs to be stored on a separate storage device from the originals. This helps protect against the loss of data due to a failure of the storage device.

By default the Lightroom Classic backup saves a copy of your catalog in a “Backups” folder within the same folder where your original catalog is stored. Therefore, I recommend either changing the location in the dialog for the catalog backup, or making sure you are using another backup to copy the catalog (and the Backups folder) to another device.

For example, if the catalog is on the internal hard drive on your computer, and you keep the catalog backups on the same drive, you’ll want to be sure you are also backing up your internal hard drive through other software. This, of course, is something you should be doing regardless.

It is important to keep in mind that the backup feature in Lightroom Classic does not backup your photos. Backing up the catalog is important, because the catalog contains the information about your photos. But it is important to also backup the photos themselves.

For backing up photos I recommend a synchronization approach, so that the backup storage is a perfect match of the master photo storage. This makes it much easier to recover from a hard drive failure or other issue that causes a loss of photos.

I use GoodSync as my synchronization backup solution, which you can learn more about here:

http://timgrey.me/greybackup

In addition, I created a video course that demonstrates my workflow for backing up my photos with GoodSync, which you can find on the GreyLearning website here:

https://timgrey.me/goodsync

Choosing by Histogram

Facebooktwitterlinkedin

Today’s Question: I shoot in raw and I have multiples of the same or almost the same images because I use exposure bracketing. As a rule of thumb, can I use the histogram in the Lightroom Classic Development module to help me in the process of selecting the best photo? By that I mean relying only on the histogram, if I choose the image that is most exposed to the right without being clipped, will I be making the right selection everything else being equal?

Tim’s Quick Answer: Yes, you can use the histogram as a tool for deciding which photos to keep versus discard, all other things being equal. Just keep in mind that the histogram is not a completely accurate reflection of the original capture data.

More Detail: The histogram reflects adjustments applied to an image. That means if you make changes to the settings (such as with a preset applied at import) the histogram will reflect those changes. Furthermore, the histogram reflects the changes inherent in the default processing of the raw data by the software (such as Lightroom Classic in this case) that is rendering the preview of the image. The histogram is based on the rendered preview, and that preview will be rendered differently by different software applications.

For example, if you see a minor amount of highlight clipping on the histogram for an image you have not applied any adjustments to, that doesn’t mean detail in the highlights has necessarily been lost forever. Slightly reducing the value for Exposure or Whites, for example, would likely cause there to be no clipping at all, and not loss of detail. Just because the default interpretation of the raw capture shows some clipping doesn’t mean the detail that appears to be lost can’t be recovered.

If the clipping is significant, it is quite likely that detail has been lost in the original capture, and you won’t be able to recover it. Of course, it isn’t easy to determine whether detail was clipped completely or if that detail can be recovered. In other words, the histogram isn’t a perfectly reliable tool for evaluating which image has retained the best detail. That said, provided no adjustments have been applied to the image, the histogram can be used to select the best of a series of photos, all other things being equal. In general, you want to choose the image where the histogram shows the exposure was as bright as possible with very little clipping (or ideally no clipping at all) for the highlights in the photo.