Bug Reports

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

Vertical scroll bar on the right side in the Develop module disappears when using tools with larger panels, like the adjustment brush.  When this happens, you can't scroll down to access all the options/sliders in the current tool panel or access the standard Basic, Tone Curve, etc. panels below.  Changing the size of the filmstrip resets/fixes the problem, in some cases.See video here for an example.Troubleshooting steps already tried & failed - - Turned the GPU on/off.- Updated graphics drivers to the latest versions.- Forced Lr to use OpenGL instead of DirectX according to this post.- Reset Lr preferences.- Replicated behavior on 2 computers    - Win10 laptop - Intel HD 4400 GPU - 1920x1080 built-in display & 2560x1440 external display.    - Win10 desktop - NVidia GTX 960 GPU - dual 1920x1080 displays Behavior is the same on both computers.  The only difference is the point where the problem occurs varies, depending on Lr window size &

When using Lightroom Classic CC on my Mac Book Pro 15" with Intel Iris Pro 1536 MB, 2,2 GHz Intel Core i7, 16 GB 1600 MHz DDR3 and MacOS High Sierra 10.13, I have the following issue:when I open corrective brush I can't see the values on the right. They disappear! I tried to delete preferences, I have deactivated GPU, de-installed and re-installed but no way.The only way to resolve is to reduce image space, close LR Classic, re-open and it works....but it's quite a nonsense to reduce image space when you have to work with an..image!So if I use the old version of Lr (named CC 2015) I have no issue. If I use the new one (Lr Classic CC) the issue can be fixed only reducing image area.At the end of the story I had to reinstall the LR CC 2015 which works fine and in my opinion has a much better workspace, especially with a 15'' display.

It has some terrible bugs in it. When changing presets the profile resets back to Adobe standard, even if profile isn't checked within that preset. It is making editing a real pain.LR is also crashing. Please fix these bugs quick as I have tons of work to get done!Is it possible to roll back a version? 7.3 can't be used in this state.

I have the newest Version from Adobe Lightroom Classic CC. My Version Info:Lightroom Classic-Version: 7.1 [ 1148620 ]Spracheinstellung: de-DEBetriebssystem: Mac OS 10Version: 10.13.1 [17B1003]Anwendungsarchitektur: x64Since this current Update the incrementTargetAdjustmentValue  does not work anymore on pressing # I've checked the TranslatedStrings file an also here the settings are correct.Maybe there must be a bug somewhere.

Create/Save a Profile in ACR that includes a Post Crop Vignette and a selection of other adjustments. Load Lightroom and apply this profile and all develop sliders work as before except for PCV. The PCV sliders can be adjusted (they are not disabled/greyed out) but have no effect. All other adjustment sliders will work as normal except the PCV slider which does nothing.Note: In ACR the slider is disabled but there is an additional drop down (set to Profile) that allows you to disable the PCV set in the profile and this reactivates the sliders and allows you to adjust the PCV.

In LR 7.3.1  when creating a virtual copy ((Mac) CMD'  the sync dialog box appears. I am sure this is a bug

As required by the new European privacy protection laws (thanks a bunch, data miners), photographers are required BY LAW to record every single change made to an image. This stems from future video surveillance regulations, but obviously someone didn't finish thinking there and just generally applied that, indeed very important, regulation to digital imaging in general.Now, we could, of course, spend 95% of our client's time typing our logs, but maybe it would be easier if you could implement a log file like in Photoshop. Otherwise, I could no longer use the development module in LR realistically or, basically any functions that alter the image or any of its data.So please, is there a way to work this out, until thes laws are being refined? It's slightly more than a month now.

When trying to install the last couple updates to Lightroom CC or Lightroom Classic CC, I get errors and it fails to install.  This was reported at the last one as well, See this thread.  The Photoshop and RAW updated without issue, before applying the workaround.Windows 10-based PC with multiple drives, build 1709 (OS build 16299.192). Exit Code: 156-------------------------------------- Summary -------------------------------------- - 2 fatal error(s), 0 error(s), 3 warnings(s) FATAL: Error (Code = 156) executing in command 'CreateSymlinkCommand' for package: 'AdobeLightroomCC-mul', version:1.2.0.201801311556FATAL: Error occurred in install of package (Name: AdobeLightroomCC-mul Version: 1.2.0.201801311556). Error code: '156'WARN: Unable to delete directory "D:\Cloud Storage". Error 32 The process cannot access the file because it is being used by another process.. Check and correct folder & parent directory permissions and then try again.WARN: Warning (Code = 149) exec

In slideshow, the audio slider to mix or choose audio over video file does not mute video when all the way to the right. In LR5 this worked fine. But the same slideshow from the same catalog in LRCC 2015 does not fully mute the video sound....tried it on 2 different computers, same result, needs to be fixed.

When you are in B&W mode and have custom settings in the B&W Mix panel and then convert the image to colour and then back to black and white the B&W Mix panel sliders are all reset to zero.This is changed from the previous version of Lightroom Classic where the settings were retained. This is an issue because if you switch back to colour (maybe to find the colour of what you are changing so you can grab the right slider) and back (to adjust that slider) all your previous settings are lost.I'm assuming this is a bug that someone can fix for the next version.

After applying one of the new B/W presets, and then zooming in, the app crashes.  Re-opening and zooming agin on same image, usually no problem, but if applying a new preset to same image or a new preset to another image and zooming in, it crashes again.  Happens consistently with B/W, seems to be OK with color presets, but have  only tried a few.

With the release of CC 2015.8 / 6.8, it's no longer possible to modify TranslatedStrings.txt for English users on Mac. LR ignores the file:/Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Resources/en.lproj/TranslatedStrings_Lr_en_US.txtWhereas on Windows, LR does read:C:\Program Files\Adobe\Adobe Lightroom\Resources\en\TranslatedStrings_Lr_en_US.txtI confirmed this using "dtruss" on Mac and Process Monitor on Windows.This affects a large number of users who had relied on editing TranslatedStrings.txt:- To provide keyboard shortcuts for commands that don't have them and that don't appear in the menus (e.g. Toggle5Shortcut for assigning the purple label).- To change keyboard shortcuts for commands that don't appear in the menus, e.g. BrushDecreaseKey. Some users report using keyboards for other languages (e.g. German) that they use with LR running in English, and the English shortcuts don't always map well to non-English keyboards.- The Keyboard Tamer plugin relies o

My Lightroom Classic is crashing constantly.  I'm working on a Mac.  Any help would be great right now.

Updated to Classic.  It crashes each  time I close, whether asking to test integrity and optimize and save when exiting, or even when asking to 'skip' these steps and close.  Confidence is low that changes won't be lost, so can't really use this upgrade until this is fixed.  Crash reports sent each time.  Win7Pro SP1, 64bit, GPU acc is off.  No problems with the last 2015.12 release.  I need the latest (Classic) to support a new camera. Thanks.

Beginning with at least the iPhone 4S, and continuing with the 5 and 5s, I see that videos shot with those devices show a capture time that seems to relate to GMT, when it was actually shot at GMT -5. The videos show a correct creation time in Finder prior to import, but this odd shift occurs upon import. I know that the capture time can be edited in Lightroom, but I'd rather see the correct time on import. This happens in Lightroom 5.3, but also occurred all the way back into 4.