Bug Reports

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

When Automatically Write Changes Into XMP is enabled, LR won't write the develop settings of the current photo when it exits. To reproduce:   1. Enable Automatically Write Changes Into XMP.   2. Edit a raw in Develop.   3. Change the Exposure slider to -5.   4. Exit LR.   5. Edit the raw's .xmp and observe that the Exposure slider is not -5.   See the attached screen recording.  Prior to LR 11, this behaved correctly. With the current performance enhancements to writing .xmp, there's no performance reason why LR shouldn't write the .xmp of the current photo on exit.   Tested on LR 11.0 / Windows 10.

When I select multiple images in lightroom and hit "open as layers in photoshop", photoshop launches and opens the first couple images and then stops opening the remaining images. It leaves a layer called "load images" at the bottom of the image stack.   Often if I close the file, and try again, it will work the second time. This has been a repeated issue for several years. I manage a facebook group for architectural photographers with 3.5k members and this issue is regularly brought up.   I'm currently using PS 22.5.0 and lightroom Classic 10.4 on a iMac running Big Sur 11.5.2.   Please address this issue!!!!

I am trying to use the embedded previews from my Sony A1 raw files.  I know they're there because I can open them with Photo Mechanic.  But when I use embedded previews on import the previews I get are nowhere near full size.   Does anyone know how to work around this, or is Adobe working on a fix?     ---------------------------------------------- Moved to Lightroom Classic 'Bugs' forum by Forum Modertor

I updated Lightroom Classic to 11.0.  Once I did that, I click on Mask, add a new mask, and select the brush tool. When I do, there are no brushes to select from. I cannot use dodge, burn, soften skin, iris enhance, etc.  They're missing.  Any help on how to fix this?     Thank you!   

When zooming into an image in library mode, the color changes suddenly and differs from all the consistent colours shown in develop mode or library mode (fit image). I just updated to LR10.1 and appreciated other fixed bugs. I am using an external BenQ display calibrated to AdobeRGB profile using xrite. The images have Adobe profiles (AdobeVivid) applied.

Hola, estoy con un problema el Lr. Estoy editando fotos de un evento hace unos dias. El viernes se me actualizo la version de Lr, por lo que el sabado cuando lo abri para seguir, me dijo que tenia que actualizar la version del catalogo dada la actualizacion del prograa. Lo hice, y contnue trabajando sin problemas. Hoy cuand abro para retomar el trabajo y entregar al cliente, no me deja abrir e catalogo actualizado, y tampoco el anterir! No se como seguir trabajando   Por favor ayuda!!    

Lr 11 update is causing a major problem with developer profiles.The profiles are not showing up when a preset is applied, or the slider is there but greyed out.As part of a team that has developed many preset collections with custom profiles, this a HUGE problem that needs to get fixed asap!

  I have a preset for sharpening. When I select multiple images and apply this develop preset there is a weird behaviour. The preset is applied but also all other images get develop settings from the active image in the selection.   This started happening in 10.4. I use this regularly and it never behaved like this.     Lightroom Classic version: 10.4 [ 202108071231-af9219b9 ]License: Creative CloudLanguage setting: enOperating system: Windows 10 - Business EditionVersion: 10.0.19043Application architecture: x64System architecture: x64Logical processor count: 12Processor speed: 3,1GHzSqLite Version: 3.34.0Built-in memory: 49076,1 MBReal memory available to Lightroom: 49076,1 MBReal memory used by Lightroom: 4036,5 MB (8,2%)Virtual memory used by Lightroom: 5463,4 MBGDI objects count: 818USER objects count: 2310Process handles count: 3956Memory cache size: 3950,8MBInternal Camera Raw version: 13.4 [ 872 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD opti

I found a design error in LRc regadring the creation of HDR or Panos.When rendering a new image either as HDR or as pano and use 'Auto Correction' settings LRc will create a new rendererd image and doing some Auto Corrections on that picture.  If you take a look into the protocol you find only one entry, that is 'Import'. This would be fine if importetd picture would be the rendered pic with auto corrections. But if you click onto 'Import' in protocol the picture gets reseted. I think this is an design error. Protocol should either show two entries for Import and(!) auto corrections or 'Import' should be the picture with(!) applioed Auto corrections.

[See here for how to reproduce the bug and an easy workaround: https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-editing-cr3-files-in-ps-from-lr-lose-color-profile/5f9043b035f40c2520b9e964?commentId=5fb3495d014b4c3c8a0da305 -- John Ellis]   Editing a picture in Photoshop 2021 from within LR 10.0 makes the color profile disappear and the image loses all it's vibrancy... Any idea how to fix that? Top image is what I see in LR. Bottom is how it shows up in Photoshop... 

Updated LRC and now tethered capture window doesn't even show. Files are not transferring to computer regardless.    LR Classic 10.4 Canon 5ds Catalina 10.15.7   I rolled back to version LRC 10.3 because I have to shoot today but here are my specs   Lightroom Classic version: 10.3 [ 202105281559-8dc50eb4 ]License: Creative CloudLanguage setting: en-AUOperating system: Mac OS 10Version: 10.15.7 [19H1323]Application architecture: x64Logical processor count: 20Processor speed: 3.6GHzSqLite Version: 3.34.0Built-in memory: 131,072.0 MB   Also - is it possible that the software has updated when I have preferences set to no automatic updates for this very reason?