Bug Reports

Hi, There are various articles on smart collections that check if the "Title" field is filled or not. Because the "Title" field doesn't have an "is empty" like function, the sugested solution is to use: Title doesn't contain a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z But there is a bug in this rule. I found that the letter 't' is causing a problem. The letter 't' seems to include all characters. Situation: Four images that have a their Title field as follows: Image 1: Image 2: 2014-01 - Street Photography.dng Image 3: 2014-01 Image 4: Some Image (Image 1 has an empty title) Four smart collections with the following rules: Collection 1: Title doesn't contain a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z Collection 2: Title doesn't contain 0,1,2,3,4,5,6,7,8,9 Collection 3: Title doesn't contain a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,u,v,w,x,y,z Collection 4: Title doesn't contain t My expected result of the smart collection is: Collection 1: Image 1 and Image 3 Collection 2

I have taken out the subscription for Lightroom and I can not import my videos. I have tried reinstalling the program and nothing works. The videos will play with Quicktime and they can be imported to Photos on my iMac.Please help as I am very frustrated.

Not sure if this is new behaviour or if LR6 has always done this and I've never noticed.I am currently cropping all my images to 2x3 / 4x6 to upload to a school site (outputting with longest edge as 5400 to make 12x18 prints).When I cycle between images and go back to one already cropped the aspect name is reset to say original each time rather than 2x3/4x6.This is extremely confusing as I have no way of seeing if the image has actually been cropped or if I have just forgotten to do it!   I'm sure in the past the behaviour has been to keep the chosen crop aspect visible in the panel.

There is a small but annoying bug if you try to apply the same profile to 2 or more images in the Develop module.Say that you have 4 images: Images A & B in Profile 1, Images C & D in Profile 2. If you select all images in the Develop module (with Auto Sync on), and you choose the same profile for all 4 images, the profile will be changed only if this changes the profile for the most selected image. For instance, if image A or B is the most selected, and you choose Profile 1, then images C & D will not be changed. However, if image C or D is the most selected, then the new profile will be applied to all the images.Lightroom seems to use the (incorrect) rule -- if the most selected image is already in the chosen profile, then there is nothing to change, but if the most selected image would be changed, then apply the change all the selected images.This is an annoying bug because changes in color profile can be subtle, and it isn't always apparent that no change was made.The w

In the following case, a photo is permanently deleted from disk unintendedly:1. In the Library view, right click on a photo and select "Remove Photo"2. In the following Pop-Up "Confirm" select "Delete from disk"3. Abort the following Pop-Up "Delete Permanently" by pressing ESC=> The photo is falsely deleted from diskReproduced with Lightroom 5.5, Windows 7, 64 Bit

I noticed that LR clone and brush tool on my XEON E5-1650 0 3.20GHz (Attention: E5-1650 0 and not E5-1650 v4) can not stress my CPU and after x minutes of working LR slow down, until I have to restart it.Please see the full diskussion with the problem here: https://forums.adobe.com/thread/2210245 (test with different Lightroom versions, confrontation with a weak laptop, that works fine, tests wit other graphic grafic card, test with other bios settings etc. No results. Only restart LR or minor display resolution helps.)Can anyone with an XEON E5-1650 0 3.2Ghz confirm this?

Lightroom Classic CC for Windows (7.0.1)The shortcut keys "Ctrl +," are doubly assigned.1. Preferences2. Zoom outIf you press the key, the environment setting opens.In addition, the operation of the zoom in key "Ctrl +." Is also strange.The result is different from Lightroom Classic (2015).

Yes. This problem was fixed in some earlier versions of Lightroom, but appears to have resurfaced in Lightroom Classic. I just reproduced it in Lightroom Classic CC 7.0.1 on MacOS X 10.12.6 (Sierra).Adobe's support team on Twitter have denied that the problem exists, but I can reproduce it reliably on my system.Note: This conversation was created from a reply on: Lightroom: Deleting rejected photos while in Develop doesn't work.Lightroom reports "Error changing modules" after rejected photos are deleted while in the Develop. STEPS TO REPRODUCE1. Launch Lightroom.2. Switch to Develop.3. Flag 1 or more photos as Rejected.4. Choose "Delete Rejected Photos" from "Photo" menu.5. Switch to Library.EXPECTED BEHAVIORSwitch to Library should work correctly.ACTUAL BEHAVIORLightroom displays a dialog reading "Error changing modules". Thereafter, the app is in an inconsistent state; no photographs are displayed in the Library module, and choosing "Quit" causes the app to exit without the normal pr

Lightroom 9.1 doesn't start at all for me on Windows 10. I updated my video drivers to the latest versions (with a clean reinstall), I reinstalled my CC Apps (also using Adobe Creative Cloud Cleaner tool). I event used an older version of LR (8.4) but still doesn't work. I found the error in the Windows Event Viewer and it says Faulting application name: Lightroom.exe, version: 9.1.0.10, time stamp: 0x5de0bfe8Faulting module name: DirectML.dll, version: 10.0.18362.267, time stamp: 0xd1d24d33Exception code: 0xc0000409 Now, I checked the official requirements: I am using a supported version of Windows 10 (1903) and my video drivers are DirectX 12 compatible (I also have DirectX 12 installed and I have no problems with it, checked with dxdiag).I have opened a support ticket but it seems to me that even the support team is clueless. I had to drop the conversation with them today but I'll resume it tomorrow. This upsets me, especially since LR used to work very well on my PC, but it seems t

I have been coalescing my mini travel catalogs in to my main catalog. They import fine, but they show up in the folder panel not in the correct spot in the directory tree. When I do show parent folder it gives me An internal error has occurred: Database "E:\lightroom\lightroom.lrcat": UNIQUE constraint failed: AgLibraryFolder.rootFolder, AgLibraryFolder.pathFromRoot Statement: UPDATE AgLibraryFolder SET rootFolder = ?,pathFromRoot = ? WHEREand an ok button. I tried doing update folder location My folder tree looks like this:2018    trip 12019     trip 2Z  2018        january  2019         january        februarywhere the actual hard drive is:Z 2018     trip 1    january 2019     trip 2     january    februaryIn future I'll make sure to do show parent folder in the mini trip catalog before I import it, bu

When attempting to import photos from my Nikon D850, Lightroom Classic states it is importing photos but status bar is not progressing and no photos are being imported. Restarted system and program along with camera and still has issue. This is all been occurring with macOS Catalina 10.15.

Like title says, the screen of my MacBook 16" turns black for 2-3 secs while (fresh) opening PS. Sometimes the same in LR when switching from Grid View to Develope Module. This happens only on battery mode with Automatic Graphics Switching ON (MacOS settings)Turning Automatic Graphics Switching OFF solves the issue. Turning OFF graphics processor in PS solves the issueBut that's not a solution for me.Anyone experiencing the same?

Lightroom Classic  9.3 Library Preview Zoom interpolation type has been changed to nearest neighbor. Nearest neighbor interpolation uses a simpler and faster algorithm that can create "jaggies" and other artifacts in the image. Presumably this was done to reduce preview building time, but don't know. I checked LR Classic 8.4 and Camera Raw 12.3 (most current) and they both appear to use bicubic or bilinear interpolation, which does not exhibit the artifacts seen with nearest neighbor interpolation.What this means is that the ALL of the Library Zoom view settings less than 1:1 may exhibit artifacts with certain image files that appear as edge "jaggies' or moire' patterns. This makes them less useful for evaluating the image detail at Zoom settings of resized export and print output. Here are examples using Lightroom Classic 9.3 showing PS Image Size panel with 33.33% (1:3 Zoom) image resizing using Nearest Neighbor (top screenshot) and Bicubic Sharper (bottom screenshot) Resample a

When I check "Remove chromatic aberration" checkbox I get artefacts on the left border of the image. Artefacts looks like 1-pixel vertical straight green and/or purple lines of random length.Images where I noticed this problem - are panoramic 360ox180o DNGs (6080x3040px) exported from Insta360 Studio app. I see this lines very clearly in VR-viewers later.I see this artefacts not only in preview inside Lightroom but also in exported TIFFs. Inside Lightroom I see mostly green, and in exported TIFFs I see purple. See attached video for examples.I don't see this lines with unchecked "Remove chromatic aberration" chackbox and I don't see them in other apps, like Apple Preview.I don't see this artefacts on other my files (JPEG, HEIC and DNG from iPhones).I Use Lightroom Classic on MacBook Pro 2018 15" with Radeon 560X 4 GB. I tried to turn On and Off using of Radeon in Lightroom - no difference.DNG with the problem:https://yadi.sk/i/EUC6Ztr-GjKXvw  

When you import a .heic containing a face name saved to the photo's metadata, LR doesn't import the face name. But this works correctly with .jpgs. To reproduce:   1. Make a new catalog.   2. Import a .heic photo containing a face, export it as a .jpg, and import the .jpg into the catalog.   2. In Loupe, label the face in both photos with "John".   3. Select both photos and do Metadata > Save Metadata To File.   4. Remove both photos from the catalog.   5. Reimport both photos into the catalog.   6. In Loupe, observe that the .jpg's face is still labeled with "John" but the .heic's face has "?".  Observe that both photos have keyword "John".   See the attached screen recording.   Tested with LR 11.0.1 / Mac OS 11.6.  

Ever since Lightroom CC 2015.7 there has been a performance issue with Lightroom and Sony ARW files. When working in the develop module, when you first move to an image, the sliders will operate, but have no effect for several seconds. On non-sony images this does not seem to be a problem. This issue only started with 2015.7 and has not been resolved by subsequent updates. In some cases it can take up to 10 seconds after an image loads in the develop module before the sliders become responsive. I have tried using a new catalogue with no other images in it, to see if it was my catalogue, but to no effect. Others have reported this too, but as they are not using other cameras, they did not realise it was specific to sony ARW files. One user posted a video on YOu-Tube showing the problem.  https://www.youtube.com/watch?v=XPFujo_tNY8 This is not my video, but the person is having the exact same problem that I am having. My setup is a MacPro 12 Core with 20GB ram. I've also tried it on

Lightroom Classic V11 Mac OS Monterey    The Copy/Sync feature is not working when I want to turn off a panel.     For example, I edit photo A and turn off Color Grading...copy the settings (making sure Color Grading is checked) and paste on Photo B...the Color Grading panel is still on for Photo B.     This is most troublesome for me because I convert all my photos from color to B/W and I don't want the color grading panel on my black/white photos.  So my previous BW preset is no longer working and I cannot batch turn off this setting.     Let me know if there is a work around.  

Nachdem ich die xmp-Speicherfunktion in der neusten Lightroom-Version aktiviert hatte, stürzte Lightroom nach einiger Zeit ab. Bei jedem Neustart kam es erneut zum Absturz.Erst ein Einspielen eines Backup-Katalogs löste das Problem.Ich konnte das Problem durch Aktivieren der xmp-Speicherfunktion reproduzieren und lasse jetzt die Finger von dieser überarbeiteten Funktion.Vermutlich hängt das Problem mit meinem großen Datenbestand zusammen. Mein Katalog umfasst knapp 400,000 Fotos. Lightroom scheint nach Aktivieren der xmp-Speicherfunktion die alle Fotos des Katalos dies Speicherung der xpm-Dateien durchführen zu wollen. Meine Vermutung ist, dass dies das Programm bzw. den Katalog überfordert.   -------------------------------------------------------- Moved to Bugs sub forum by Forum Moderator

LrC 11.0, but it happened in 10.x (I reported it a year or so ago but it was not even acknowledged back then) Windows 10 Pro x64   When using the Print module, a thin white line often shows at the bottom of the displayed image.   It happens only onscreen (i.e. not in the output JPEG file or print) and depends on the actual display size of the image. If I change the LrC window size or hide some panels, in sometimes disappear. In this case (outputting an aspect ratio of 4x5 portrait), just pressing T to hide toolbar makes the displayed image a bit bigger and the line disappears. With an output of 3x4 portrait, for instance, it doesn't show with the toolbar either shown or hidden, but if I hide the top panels (F5) it appears (with or without toolbar). In 5x7 portrait, it appears with or without toolbar. In 16x10, it appears with the toolbar hidden. And so on... as mentioned, it's purely based on the actual displayed image size.   It would be nice if at least it weren't ig

[Update: The bug is caused by the Develop zoom interpolation algorithm incorrectly including input pixels from outside the crop boundary.  See here: https://community.adobe.com/t5/lightroom-classic-bugs/small-display-glitch-in-develop/idc-p/12456139#M20245]   Develop at Fit zoom shows a small glitch on the bottom edge of a LR-made panorama.  The glitch appears at zooms of 25% and smaller but disappears at zooms 33% and larger. Disabling the GPU has no effect. The glitch doesn't appear in Library Loupe at any zoom. LR 10.4 / Mac OS 11.6.    Here's the offending DNG: https://www.dropbox.com/s/1nu6fvp9d26lmn0/DSC00452-Pano.dng?dl=0   

Mobile version. When I move masking tool (brush/linear/radial) above top toolbar (will attach picture), it cannot be accessed anymore and have to removed and recreated, but effectively top of the pic cannot be used without zooming in or out, is there other walk around or zoom in out is the only way?   On pic attached, any mask tools above green line are not accessible without zooming, if display clicked once to remove toolbars touching and dragging becomes picture graging or bringing back toolbar if just touch. Thank you, Pavel  

Lightroom Classic v11 is crashing over and over within minutes of start up. I originally had LRc isntalled on a standalone SSD but when I began having issues I uninstalled and re-installed LRc onto the C drive and turned off GPU assistance in hopes it would help. I selected to send error/crash reports automatically yesterday so I have not sent one personally as of today, although its happened about 5-6 times in the last hour. This issue only seems to be LRc since Bridge and Photoshop are working fine with no issues (bridge and photoshop are on a standalone SSD as well).   this is also on a clean install of windows 10 pro   below is my system settings I copied right before this last crash:   Lightroom Classic version: 11.0 [ 202110120910-0bccc70d ]License: Creative CloudLanguage setting: enOperating system: Windows 10 - Business EditionVersion: 10.0.19043Application architecture: x64System architecture: x64Logical processor count: 24Processor speed: 3.6GHzSqLite Vers

Right-clicking Mark Favorite in the Folders panel can incorrectly create two folder favorite groups. To reproduce:1. Start with no favorite groups defined.2. Select folder A.3. Right-click folder B and do Mark Favorite (sic).4. Observe there are two favorite groups, Folder: B (correct) and Folders: A, B (incorrect):

Running Lr CLassice on annual subscription which expieres in Dec 2021 on a pc using Win 10.  The develp module stopped woriking.  The Adobe community support lists 262 like concerns with no hint or reply on fixes.  So, Lr Classic is USELESS and money being spent for a system.  NOT happy

Lightroom Classic-Version: 11.0 [ 202110120910-0bccc70d ]OS Version Number: Windows 10 21H1 (Build 19043.1288) In Library Mode, my daily workflow is: Import photos,set to Grid view (G)select all photos and set a ranking of three stars to all images.I set a filter -> attribute Rating = 3 Stars (This still shows all Photos) Then I select the first phot with the mouse: Now the frame of this image is highlighted Using the Num-Pad I set the rating of the first photo to 0 or 4 Stars so it will disapear due to the filter settings.In former LRc Versions, now the next image is highlighted and is ready to receive the ranking. Now, in Version 11, I am able to set the ranking to a few images - normaly less then 5 - and the process stuck:no image ist highlighted and no image receive a ranking until I manualy click on a photo. Then I can go on until again no photo is selected. If I set to Loupe View (E) and select the first image in the Film Strip I find the same behavior.The only differnce is, t