Bug Reports

This issue is on Lightroom Classic 7.4.   If you export using Width&Height, Long Edge, Short Edge or Dimensions with no number in the size value fields and then do an export using Percentage than the percentage value is ignored.  If correct values are in the above 4 dialogs than the Percentage export will work correctly.  The dialogs for Width&Height, Long Edge, Short Edge or Dimensions should not allow an export if the length fields are not filled in with valid values.  The problem does not seem to correct itself unless you do an export with a valid value is the above four export choices.  See this U2U thread for more detailed explanations and examples.  https://forums.adobe.com/thread/2508201

This post contains a video, for a full easy explanation of my situation. Videohttps://www.youtube.com/watch?v=sThVzs0Q5pc&feature=youtu.beThe Issue in a NutshellYou might say Import does not detect duplicate photos. So you have no way to point at various folders and be sure you imported that data. So I have no easy way to find out if my master catalog contains all my various drives (that I am sorting out) data.I discovered this after doing a catalog import, I then did a standard import, not clicking import, pointing it at the photos folder of the catalog I just catalog imported, just to check if catalog import had worked. I selecting 'Don't import suspected duplicates', expecting to see zero or only a handful of orphaned files caused by incorrect deletion. It sees everything, every photo in the catalog! The main things I tried which I think relevant to say... Since pointing it at the original /photos location on the other catalog drive did not work... I copied

When I use {Date(yyyymmdd)>>} Under the menu options  Library > Rename Photo > Edit >  does not work correctly for videos. It will rename the file with the date of the import into Lightroom.  Please fix this so that the video will rename to the date the videos to reflect when it was shot. When I use  When I use {Date(yyyymmdd)>>} Under the menu options  Library > Rename Photo > Edit > for my photos, it will rename the photo with the date that the photo was taken. This is working great for my photos.Sample of what I would enter into the Filename Template Editor{Date (YYYYMMDD)>>}_FallsPark{Sequence # (0001)>>}for both photos and videos.I process a significant number of photos and videos. (Over 9000 over a 20 days period). I need a fast turnaround. If I have to manually change each of my video file name  with the correct date taken. This will slow me down significantly. Please get it where the rename f

Since the new Adobe Color profile was introduced, I decided to adopt it as my default profile for my raw images. I had previously been using Adobe Standard. I have tried several times to change my default settings to include that profile as part of my default settings. However, every time I import new images the Adobe Standard profile is applied. I have reset my preferences in an attempt to correct the problem, but that didn't work either. I'm using Lightroom Classic CC 7.3.1 on Windows 10.If I update my camera defaults and reset the images, Lightroom will apply the Adobe Color profile as it should as long as I'm using Lightroom following the import. However, if I close Lightroom and then use it the next time to import, it will apply the Adobe Standard profile to the raw images. This is an anomaly that I have replicated several times before I have bothered to report It.Incidentally, I attempted updating the defaults by the alt-reset method as well as using the update default settings o

Unfortunately several of the performance gains you delivered in the last release has been lost in this release.  Particularly slow is the application of presets to an entire shoot. Sharpening is particularly slow, lens profiles are terribly slow.  Also as I edit photos whenever I hit the crop shortcut key I see a flash of a previous crop instead of the photo I am working on. I have also experienced a preset being applied to a photo when I have hovered over it but not clicked on it and then I can't reset the photo without stopping and starting LR.  Exports are still slow and previews are back to being slower.  Not as bad as before but slower than the last release.  I am also experiencing LR Not Responding errors on Exports of large file sets.  I have to kill LR to get it to respond again.  Overall I am disappointed you released a version that was this poorly tested and obviously performs slower than the last release after you made such a big deal of th

Using LR Classic CC 7.3, I've encountered a new problem.  When scrolling through photos in the Develop Module, GPU Rendering will not work at either Fit or Fill zoom levels.  The progress circle in the bottom right spins indefinitely.  When I zoom to 1:1, 2:1, etc., the photo renders almost instantly, which is what I'm used to.  This happens for every photo, every file type.  Zooming to 1:1 always fixes it.  

when importing a live photo from an iPhone, the image and the movie get Date Created times that are 1 hour apart. Background:Since Lightroom doesn't fully support Live Photos, it imports them as a still image and a separate movie file. I would have expected the file system creation date for both of these files to be exactly the same (ok, maybe the movie can be 1 second earlier than the still image). Here is an example:Live photo was taken at July 21, 2018, 2:33PM.When I import this into LR, I get a still photo that has this July 21, 2:33PM time stamp for its creation date. I also get a mov file that has a creation date of: July 21, 2018, 3:33PM. This is clearly a bug since they were both taken at exactly the same time.

In Lightroom 7.3.1 and OSX 10.13.4, clicking the switch to turn OFF the B&W panel does not disable the Black & White Mix sliders.   The photo changes to reflect that the panel has been turned off by showing the photo as if the sliders were zeroed.    Unfortunately the sliders can be moved with no change to the photo but when the switch is turned back ON the changes made while the switch was off and the sliders were supposed to be disabled are applied to the photo.  If you don't notice the switch is off you can really mess up your settings.Screen clip showing sliders enabled with the switch OFFI reset my preferences and the behavior was the same.  This happens on all file types.

When a raw that's been cropped is converted to DNG, its profile incorrectly changes from Adobe Color to Adobe Standard. This is a problem for people importing photos from cameras applying in-camera cropping -- not only does the converted photo have the wrong color profile, but LR thinks the photo has adjustments and will match the smart-collection criteria Has Adjustments and Has Edits.  See this report:https://forums.adobe.com/thread/24841461. Outside of LR, make a copy of a raw.2. Import the two identical raws into LR.3. In Develop, verify their profiles are Adobe Color.4. Crop the first raw to any arbitrary crop.5. Select both raws and do Library > Convert Photos To DNG with these options:6. Observe that the DNG from the first (cropped) raw is now Adobe Standard, while the DNG from the second (uncropped) raw remains Adobe Color.7. Observe that the first DNG (in Adobe Standard) matches the smart-collection criterion Has Adjustments, presumably because the color profile was (i

I tried to load a presentation template, but I keep getting an error message (rebooted, all software up-to-date): Unexpected error performing command: develop controller not available.

[Update: When creating a preset with the same name as an existing one, clicking Replace doesn't overwrite the old version.  See here for a precise recipe:https://feedback.photoshop.com/photoshop_family/topics/preset-not-refreshed-after-adjusting-cc-class...-- John Ellis]I use to create a new preset for every customer-shoot.... say NAMEXX.When customer is on site i shoot colorcards and grey for LR even finer preset-setting....I measure and than always saved overwriting the NAMEXX preset that was created before actual shoot... LR warned that preset already exists but after confirmation overwrites and from there the new-adjusted is used with AUTO-IMPORT reading from the incoming NEF file.Since latest updates this does not work anymore..it seem old one is not over-written or at least not used from there onwards (flushing ??)....  please check !Ps Also in line with this i would LOVE to see the mouse-scoll-button activated rolling though existing presets while selecting the one for

Map Auto-Tag fails on track logs with track points missing timesIf a GPX tracklog has track points with missing times, Auto-Tag Photos fails with "No matching photos", and the progress bar shows an 'Auto-Tag Photos using Tracklog" task that never completes:The fix is trivial -- LR should simply ignore track points missing times.To reproduce:1. Download the following folder containing a .gpx track log and sample photos:https://www.dropbox.com/s/58nq51tpmwuw0xr/Trkpt-missing-time.2018.08.17.zip?dl=02. Import the photos.3. In Map, do Map > Tracklog > Load Tracklog and select the .gpx file.4. Do Map > Tracklog > Time Zone Offset and adjust the displayed start time of the tracklog to be 9:56 AM.5. In the filmstrip, select the photo 2018-31_001.jpg and do Map > Tracklog > Auto-Tag Photos.6. Observe "No matching photos" and the task in the progress bar that never completes.7. Exit LR.8. Edit the .gpx file in a text editor and remove these lines, which are missing times: 1661

Hello, I have some strange behaviour with the clarity effect in Lightroom 2015.8, different from the 5.5 version. If I use the adjustment brush with clarity it darkens also the area. It seems that this happen when a radial filter with exposure adjustment has previously been applied in the area where the clarity brush is applied. I post a video that shows clearly the problem.This problem in Lightroom 5.5 doesn't exist, as shown in the video.Thank you   Edit: It seems that the web control doesn't let to show the video in full screen, this is the link: https://vimeo.com/203712701

This is a reproducible crash that I have found in Lightroom Classic 7.3 running on a Windows 7 Pro 64bit OS Toshiba laptop fitted with a built-in SD card reader.Follow these steps to reproduce:1. Launch Lightroom Classic 7.3 and ensure that Auto Import is disabled and the Preference 'Show import dialog when a memory card is detected' is unchecked.2. Insert an SD memory card. Close the Auto Play dialog if it is displayed.3. Use the Safely Remove Hardware icon in the system tray to Eject SD Card. An error dialog is displayed stating that 'This device is currently in use...' Click OK to close the dialog.4. Open Windows File Explorer, click on Computer to show Devices with removable Storage. Right-click on the SD card icon and select Eject from the pop-up context menu. An error dialog is displayed stating that the drive 'is in use' and to 'Save any open files on this disc...' In this dialog you have three choices: Cancel, Try Again or Continue. The dialog states 'If you choose to continue,

In the develop module, each time I hit "Previous" and/or Copy and Paste (Command C/V) I get this Internal Error. Lightroom 7.3.1 Mac 10.13.4

I use Lightroom Mobile to sync files for uploading to Instagram, and I noticed that the colors in the synced files are different than the originals and photos exported directly from Lightroom. I just started experiencing this problem since the latest update to Lightroom last week. The photos below shows an example.Original exported from Lightroom:Synced copy exported from Lightroom Mobile:

[Update: When the Dehaze slider was moved into the Basic panel, several aspects of the slider didn't get correctly updated for the new location:- The Effects panel toggle switch still disables the Dehaze slider.- The "." and "," keyboard shortcuts skip over the Dehaze slider:https://feedback.photoshop.com/photoshop_family/topics/if-the-effects-panel-is-disabled-the-dehaze-s...- The SDK AP LrDevelopController.revealAdjustedControls(), used by MIDI controllers and such, still thinks the slider is in the Effects panel:https://feedback.photoshop.com/photoshop_family/topics/if-the-effects-panel-is-disabled-the-dehaze-s...-- John Ellis]In Lightroom Classic 7.3 on macOS 10.13.4, if the Effects panel switch is toggled off, the Dehaze slider in the Basic panel also gets disabled.

After any attempt to use the new Folders filter I have to kill Lightroom 😞My catalog contains about 230 000 photos.What happens:1) Write anything into Folder filter2) Folders are correctly filtered, which is nice nad useful, thanks!3) I don't do anything - no clicking, so nothing else changes - same displayed photo, same folder chosen, same photo selection.4) However: The Keywording panel and the Metadata panel both shows "Working..." and this takes very long time (minutes). (Note: It seems that sometimes this happens immediately after filtering, but sometimes after selecting any other photo in the current view)5) During this time, half of LR is unusable. No context menu, Develop is not working, etc. When quitting LR it displays 'There is a task in progress: "Gathering information".' If I proceed with the quitting, the LR is still running in background, so I will kill it and restart.It would be great if you could take a look at it, thanks!

I have tried the new edited/unedited filter, which could be very useful. BUT, every image which is imported to Lightroom Classic via Lightroom mobile (e.g. images taken with the iPhone) is marked as edited, even if there are no edits. I would consider this behaviour a bug, which makes the feature much less useful as it could be.As a Lightroom Classic user, who embraced the mobile workflow just as Adobe marketing pushed me to the last couple of years, I need a consistent and performant mobile workflow. I would really appreciate, if the product development of Lightroom would rethink their decision to cut off the further development of the sync between Lightroom Classic and Lightroom CC. Features like the "edit/unedit filter" or "making a collection set from folder hierarchy" are not very usable or useful with the current state of syncing.Note: This conversation was created from a reply on: Lightroom Classic 7.2 is now available!.

Seven times now over the last couple of weeks LR has crashed when I have wakened my laptop from sleep mode. I am running 7.2 on an ASUS laptop running Windows 10.I will process some photos in LR then close the lid and return to it several hours later. When I open the lid I see the crash report option which I have always sent so you will have  - hopefully - all the technical details you need.Any idea what the problem could be?

Have just upgraded to Lightroom Classic CC 7.3 on Windows 10. I do not see the Profiles section in my Basic panel. I can see from other posts where it is supposed to be but it simply does not show up at all. Have uninstalled and re-installed 7.3 with the same sad result. System Info and screen dump appear below.SYSTEM INFO WINDOWS 10Lightroom Classic version: 7.3 [ 1164630 ]License: PerpetualLanguage setting: enOperating system: Windows 10 - Home Premium EditionVersion: 10.0.16299Application architecture: x64System architecture: x64Logical processor count: 4Processor speed: 2.9 GHzBuilt-in memory: 16256.6 MBReal memory available to Lightroom: 16256.6 MBReal memory used by Lightroom: 1852.3 MB (11.3%)Virtual memory used by Lightroom: 2275.0 MBGDI objects count: 700USER objects count: 2451Process handles count: 1936Memory cache size: 52.9MBInternal Camera Raw revision: 933Maximum thread count used by Camera Raw: 3Camera Raw SIMD optimization: SSE2,AVX,AVX2Camera Raw virtual memory: 1132M

When LR 7.3.1 imports a Sony or Canon MP4, if the THM sidecar is also present, then LR doesn't read the dimensions of the video and display them in the metadata panel. It also doesn't read the capture time properly -- instead, it uses the MP4's file modification time as the capture time, and it appears to set the multiple internal catalog fields inconsistently, causing inconsistent sorting by capture date in grid view. Details of dimensions bug:https://feedback.photoshop.com/photoshop_family/topics/lightroom-dimensions-and-capture-date-for-mp4...Details of capture-time bug:https://feedback.photoshop.com/photoshop_family/topics/lightroom-dimensions-and-capture-date-for-mp4...

[Update: If you try to include some special characters in the name of a preset being created or imported via Import Presets, LR 7.3.1 silently fails to create the preset, both on WIndows and Mac. See this post for details: https://feedback.photoshop.com/photoshop_family/topics/lightroom-classic-cc-7-3-bug-not-saving-new-p...-- John R. Ellis]If I save a new preset and I use a "|" symbol in the name it disappears. I only noticed this because I was making presets using the "|" as a separator. It worked fine before the update. It does not work now. For example, I have a preset I made called "SPLIT | Heavy Blue". The ones I made before the update work fine (thankfully). But now if I make a preset called "SPLIT | Heavy Green" it disappears. I immediately try again, same settings only changing the name to "SPLIT - Heavy Green" and it saves fine. Loads fine. Works fine.Weird.I'm not too upset. It's not a big deal. But it took me a couple hours to figure out what was going on and if i

I have a problem trying to get lightroom catalog backup files backed up using my backup software LiveDrive. The people at LiveDrive tell me that the files cannot be backed up because they have 'extended attributes'.If I unzip and re-zip the backup then it gets backed up OK, so clearly there's some difference between the zip files created by Lightroom and those created directly by Windows.Can anyone cast any light on this? I'm tempted to just write a powershell script to remove extended attributes, but not sure which would be safe to remove (would Lightroom be able to restore properly afterwards), and not entirely sure which would need to be removed to allow the backup to happen anyway.

The filmstrip in LightroomCC ist overlapping / partially covering the filter- / breadcrumb bar