Connect with fellow editors in our Lr Classic community.
Recently active
catalogs have been trouble as I move files to a separate hard drive…. no problem when I have done this in the past but now LRc will not open..
Select all photos and batch run the straighten horizon - this would help so much for large batches of photos where the horizon is slightly off and could just focus on editing the photo without straightening horizon
Hello Adobe TeamIn order to manage and see folders with more clarity and sense of order, I use long folder names. It would be nice to have a wider folder pane in Lr too, to reflect the same sense of order.Sometimes I use colours to mark both files and folders. Please add more colour tags in Lr, at least to reflect those in Finder, and mirror them in finder as well. Also, please add an option to colour the folder itself in Lr, in place of the vertical bar at the end of the folder name line.Thank you.Marco
Hi, when I open photos from Lightroom into Photoshop or just export as JPEG to my desktop, the images are very diffrent. Can anyone help me fix this please. The images show what I’m struggling with. Please help if you can, I’m matching sRGB in Lightroom & PS and it doesnt make a diffrence. This is exported from LR to desktop and produces the same result…. :-/
The new lens blur function generates a depth map from images without depth information. It would be nice to be able to use this depth map for mask creation. Right now only lumance and color range is support here, but depth range is disabled if the image doesn't contain a depth map. In this case an AI generated depth map could be used to enable depth range based masks even if no depth data is recorded in the image.
Lightroom Classic now adds AI content credentials to image exports automatically (just started last week, without warning). For tools such as Remove, for dust spots, etc. This appears not possible to be turned off ?The export options show that Content Credentials are off, but it is still appliedMy use of such tools is for image refinement, not creation of distortions (which is where the content credentials are more appropriate)For minor refinements I do not want my images to be tagged in this way, misconstruing and giving he wrong message about the final image Please let me know how I can stop the CC being tagged, as it appears in Bridge (and beyond)
The option Catalog Settings > Metadata > Include Develop Settings In Metadata is not working correctly -- develop settings are still getting included in the exported metadata and .acr files (which contain develop settings) are sometimes getting exported. The Metadata Status field is also not working correctly. Tested with LR 15.5.1 / Mac OS 26.6.2: 1. Download and open this tiny catalog and select the single photo:https://www.dropbox.com/scl/fi/f32l8iyi85gldfbd1xiew/ccbug.2026-09-01.zip?rlkey=hkwadikr9tkhdxcha1dgparms&dl=0 2. In the Metadata > EXIF AND IPTC panel, observe that Metadata Status is Up To Date. 3. In Catalog Settings, observe that both Metadata > Include Develop Settings and > Automatically Write Changes Into Sidecar are unchecked. 4. Export the photo to Desktop with Image Format: JPEG, using these settings: 5. Using Exiftool, observe that the develop settings are incorrectly included in the XMP section of the exported photo:[XMP] Exposure 2012 : -3.0
[Update: See this reply for a list of third-party plugins providing automatic image tagging: https://feedback.photoshop.com/photoshop_family/topics/automatic-image-tagging-with-google-cloud-vis... -- John Ellis]Hi all,who of you likes organising and tagging pictures in your image catalogue? I don't. I'd love to keep my focus on taking photos. When I read about the Google Cloud Vision API, I thought this cloud be the solution for my problem that I don't like organising, but love having things organised. Cloud Vision is a service that takes an image and returns a set of keywords, places, brancs, etc. it detected. Why not let Google do the work? So I started learning Lua and Lightroom development to create such a Plugin by myself (hold on, it is nothing there yet).When I started thinking about the actual plug-in, the question came up what would other Lightroom users expect it to look like? And what other features do you expect? So I forwarding these questions to you. What do you
AI Denoise consistently fails to complete on my machine. This is 100% reproducible and has persisted across multiple Lightroom Classic and Intel driver versions, including the current pairing of both.System:Lightroom Classic 15.4.1 [202606201310-b9f148a4], Camera Raw 18.4 Windows 11 Home 26200 Intel Core Ultra laptop, 16 logical cores, 32 GB RAM Intel Arc 140T integrated GPU (16 GB shared), driver 32.0.101.8860 WHQL (current, verified in Device Manager) Files: Fujifilm RAF (X-Trans)Symptom:Click Denoise. The background progress indicator (top-left) immediately shows roughly 10% progress, then never advances — waited well over an hour. The photo becomes locked: "AI processing is in progress for this photo. Editing is temporarily unavailable." Task Manager shows the Arc 140T near 100% compute utilisation for the entire time, so the GPU is actively executing something — it just never finishes. Exiting Lightroom during this state leaves orphaned Lightroom processes that must be killed in T
I use Lightroom classic 15.5.1 on a Mac with Taohe OS. I have som pictures that I deleted from one collection that was synced and added to another. They did not upload and now I coannot get these pictures to upload even as a part of a completly new collection. On the web they are not in the collection at all.
I have already Lightroom classic, but i have problems to open Lightroom classic
Unter Windows 11 kann ich mit Lightroom Classic 15.5 ein reproduzierbares GPU-/WDDM-bezogenes Problem beobachten, das nach längerer GPU-Nutzung in Lightroom dazu führt, dass DxO PureRAW 6 extrem langsam wird.System: Windows 11 Build 26100, Lightroom Classic 15.5, Camera Raw 18.5, NVIDIA RTX 2070 SUPER 8 GB, Studio Driver 610.88, HAGS deaktiviert. Der Fehler ist auch mit GPU-Werkseinstellungen reproduzierbar.In einer frischen Lightroom-Sitzung läuft PureRAW normal: ungefähr 100–110 Sekunden für 15 RAF-Dateien, GPU-Leistungsaufnahme etwa 190–200 W, PureRAW hält dabei stabil einen GPU-Arbeitssatz von ungefähr 742 MiB.Später in derselben Lightroom-Sitzung kann PureRAW bei denselben Bildern und Einstellungen extrem langsam werden: 25–30 Minuten für dieselbe Verarbeitung, teilweise mit Restzeitanzeigen von mehreren Stunden. Die GPU-Auslastung bleibt dabei nahe 100 %, die Leistungsaufnahme fällt jedoch auf ungefähr 115–120 W. PureRAW hält dann seinen normalen GPU-Arbeitssatz von etwa 742 MiB
Version: Lightroom Classic 15.5.1Camera Raw: 18.5.1Operating System: macOS 26.5.2 (25F84)DescriptionA navigation error occurs in the Develop module when using a star-rating filter and changing the star rating via the numeric keypad.When only 5-star images are displayed and the currently displayed 5-star image is downgraded to 0 stars using the numeric keypad, Lightroom subsequently displays no image. Navigating with the cursor keys does not then move to the next remaining 5-star image. Instead, Lightroom jumps to the last 5-star image in the filtered selection.However, if the same change is made using the context menu with the mouse, navigation works correctly.Steps to Reproduce Open Lightroom Classic 15.5.1. Switch to the Develop module. Use a collection or folder containing multiple images rated with 5 stars. Set a filter that displays only 5-star images. Select a 5-star image that is not the last image in the filtered selection. Change the rating from 5 stars to 0 stars us
I have found a possible Lightroom and Photoshop integration bug.If Photoshop is already open before I start Lightroom, then I select a photo in Lightroom and choose Edit in Photoshop, the edited file is saved correctly to disk after saving in Photoshop, but it does not appear back in the Lightroom catalog.If Photoshop is closed before I start Lightroom, everything works normally and the edited Photoshop file is added back to the Lightroom catalog after saving.Lightroom Classic and Photoshop Sysinfo attached.Adobe Photoshop Version: 27.9.1 Lightroom Classic 15.5.1Has anyone else experienced this?
JPEG XL 非可逆圧縮時に 16ビット指定をしても実際に出力は8bitになっていました。
I have a three monitor setup. I want lightroom / photoshop on monitor 2, the photo full size on the secondary display on monitor 1. Monitor 3 is used as general purpose, often showing ChatGPT as I edit. I cannot get the full size photo on monitor 1 to stay there if I start typing on monitor 3. It goes blank. Thanks to anyone who can help. Having gone to the time and expense of a three monitor setup I can’t use it.
Hello,I recently posted on Intel's forum regarding problem with heavy gpu tasks on my laptop.They asked me to post here to see if people on Adobe's side have any idea on how to fix this, and to cooperate. My laptop is an Asus Zenbook (UX3405CA) : - I9 285H - Intel Arc 140T 16Go updated with the latest available driver (32.0.101.8331) - The problem is still there with older drivers - Windows 11 pro up to date - Lightroom classic version 15.1 - Tried with older versions of Lightroom - The BIOS has been updated- Cleanded drivers with DDU in recovry mode then reinstalled through intel utility tool - Recleaned them with DDU in recovery mode then reinstalled through MyAsusThe problem persists.I get a LiveEventKernel with the code 141 in the event viewer every time the problem arises.I have attached some relevant files, but can't add the dump because the format is not accepted.I need your help to fix this problem permanently.Thank you
Today after long editing session I noticed that my PC slowed down noticable. I looked up into task manager and saw that Lightroom uses 13GB of RAM + 12GB usage from Photoshop. I thought it isn't that much, because I have 64GB of RAM, but it's usage was at 98%. After I closed Photoshop RAM usage dropped by 15GB and after closing Lightroom usage dropped by 33GB! That's huge amount of RAM usage and it was 20GB more than task manager was showing next to Lightroom process. Is this a bug?LR Classic 13.1Windows 11 Proi7-13700KRTX 408064GB RAM
I have a reproducible printing problem with Lightroom Classic 15.5 and an Epson SureColor SC-P900 on macOS Tahoe 26.6.2.System:Lightroom Classic 15.5 (build 202607291506-b8869fa7) macOS Tahoe 26.6.2 MacBook Pro 14-inch, 2021 Apple M1 Pro Epson SureColor SC-P900 Epson printer driver 13.34 Printer connected via IP Latest printer firmwareProblem:I use a 16-inch roll of Epson Premium Semigloss paper and normally print 40 × 60 cm photographs from Lightroom Classic.This workflow worked previously.With the Epson SC-P900 driver selected in Lightroom Classic, when I open Page Setup / start a print, the printer feeds/ejects the roll and displays:“Paper out in Rear Paper Feeder. Load paper and touch OK. User-Defined / Plain / Bright White.”The printer is actually correctly loaded with roll paper.The important point is that the same printer, same roll paper and same Mac work correctly when using AirPrint.I also tested the Epson driver outside Lightroom using the macOS test page. The printer again
I use Lightroom Classic 15.5 on MacBook Air chip M1 with macOS Tahoe 26.5.2.I usually import photos directly from a card reader, in Copy mode, but it failed in the last tries : when I select the source folder, Import seems running (icon moving in circle on the bottom left), but no image is showing on the panel in the middle.I tried copying a few images in a new folder in “Documents”, and then import it from there, to make sure it is not a permission issue, but I had the same behavior.I also tried in Add mode, unsuccessful.Lightroom Classic is having “Full disk access” in Mac settings, so I don’t know what to try next.Can someone help me ?Thanks in advance for all your suggestions.
I have a folder in which I imported about 200 images from a shoot. Edited them last night as normal. Got a request for two additional images.I import the 2 new images from the SD card as usual. Accidentally see I selected all 1496 images. Click CANCEL import and cancel render previews. Lightroom shows "Previous Import"-view as normal, about 20 images. The original folder with the 200 edited images NOW HAS NO RAWs left. Only .xmps.Only the about 20 images from the canceled import are there. The original files are not in Trash. Not in the folder where I worked on them last ight. Just... gone.SURELY this is not intended behavior? Files on SD card are thankfully still there, lucky me.Windows 11 Home 25H2, OS Build 26200.8037LR Classic 15.2, Build [202602111402-ec4112e8]
Seleziono filtro radiale. Compare l’ovale di modifica. Ma non c’è un elenco di effetti su cui agire, per es. regola esposizione, per modificare la zona dell’ovale., che quindi non serve a nulla
When backing up it states that it only backs up the catalog and not the photographs. How do you back up the RAW photographs from LRC to a hard-drive, especially if they’re already in Collections.
Bonjour l’équipe Adobe Lightroom,Je souhaiterais proposer une nouvelle fonctionnalité IA spécifiquement pour Lightroom, qui serait particulièrement utile pour les photographes immobiliers.L’idée serait d’ajouter une option dans les Masques permettant de :« Détecter les fenêtres »Lightroom analyserait automatiquement la photo et créerait un masque précis correspondant aux fenêtres et baies vitrées, en tenant compte de leur forme et de leur perspective.L'objectif serait ensuite de pouvoir traiter facilement l'extérieur visible à travers les fenêtres, indépendamment de l'intérieur de la pièce.Par exemple, sur une photo immobilière d'un salon avec plusieurs fenêtres, Lightroom pourrait :détecter automatiquement toutes les fenêtres ; créer un masque pour chaque surface vitrée ; permettre de sélectionner l'extérieur visible à travers les vitrages ; permettre d'ajuster séparément l'exposition, les hautes lumières, les ombres, la saturation, la température, etc.Exemple concretUne photo d'intér
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.