Questions

So, I have used AI masking to detect the clothes on a subject, and I am using Point Color to change some of the colors on those clothes. I want to turn up the saturation on the green spots on a military suit.   Now, as a test, just to make sure the change is noticeable, I turned the hue all the way to the left, basically the military green is now cherry red. This is only to make sure I am not going blind and that I have actually found a bug.I am NOT using global point color because I have tested global point color with the military green and if I am using global point color then half the image becomes red. When I am using just the chothes mask then only the green spots become red.   If I then export as JPG then the point color is fully ignored. If I export as PNG things behave as expected (with minor color differences)I also tested this with saturation. I turned the saturation of the military green to 0 in the point color, making it gray, exported as JPG, camo spots are green

‘compare’ has a lock, which(unlocked) allows independent movement of each image.  Is there a shortcut key to toggle to lock on/off?

Ich nutze die neuste Version von Lightroom Classic und musste mir eine neue Bibliothek anlegen.Beim Importieren der Nikon NEF-Dateien mit XMP-Dateien musste ich feststellen, dass in der neuen Bibliothek die dazumal (ab 2022) getätigte Bildbearbeitung inkl. Bewertung nicht übernommen wurde.Auch ein nachträgliches Einlesen der Metadaten über (Metadaten / Metadaten aus Datei lesen) hat nicht weitergeholfen.Ich wäre froh, wenn man dieses Problem lösen könnte. Ansonsten habe ich seit 2022 all meine Bildbearbeitungen und Bewertungen verloren.

Still randomly receiving error messages when re-ordering a small batch of photos within a collection. LR tells me that it can’t (paraphrasing) move photos from disk in a collection...This has been an error I’ve encountered for many different versions of LR Classic over the years and have posted several times about it already.   Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Home Premium EditionVersion: 11.0.26200Application architecture: x64System architecture: x64Logical processor count: 24Processor speed: 3.4GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171CPU Utilisation: 2.0%Power Source: Plugged InBuilt-in memory: 65292.0 MBDedicated GPU memory used by Lightroom: 203.7MB / 15995.0MB (1%)Real memory available to Lightroom: 65292.0 MBReal memory used by Lightroom: 1364.7 MB (2.0%)Virtual memory used by Lightroom: 1633.4 MBGDI objects count: 787USER objects count: 2771Process handles count: 3129M

Hallo Forum und liebe Grüße, ich benötige nach langer Zeit eure Unterstützung. Ich bin jüngst von der A7IV auf die A7V umgestiegen. Ich nutze LrC über die Creative Cloud von Sony in der neuesten Version (V15.2). Meine Fotos erstelle ich als RAW-Dateien, in der V-er als RAW-komprimiert. Die Kamera ist auf die Version 1.01 upgated. Beim Einlesen in LrC erhalte ich die Meldung "Die Datei wird entweder nicht unterstützt oder ist beschädigt." Smartvorschauen können ebenfalls nicht erstellt werden. Zuerst dachte ich, die RAW-Version würde dies verursachen. Blöd das Ganze, weil ich morgen nach London will und die Kamera soll dort zum Einsatz kommen. Nun sieht es so aus, als müsse ich ohne die Kamera reisen, weil es keinen Sinn macht. Oder ich fotografiere in jpg. Hat jemand eine Ahnung, was der Grund sein kann?Beste Grüße, Uwe

I’m using macbook pro, Sequoia 15.3.1. I'm seeing many bugs since the LrC 15.2 release. This is one of them: when I set the profile in Print module, and then move to say, develop, and back to Print the profile is no longer selected (none is.)Another bug, may or may not be related, is that I can’t turn off mouse-hovering over History states showing the change. I have this unselected in preferences, reset preferences (very painful loss), but problem remains.

Blur toepassen met een model loopt niet lekker. Het model wordt niet herkent als de persoon die de focus moet krijgen maar objecten voor haar krijgen die. Alles wat zich voor het model bevindt is loei scherp terwijl het model de blur ontvangt. Ga je dan met de focus en blur button corrigeren dan is de verwerktijd echt heel lang en veranderd de muis keer op keer op een zandloper en kan je minuten lang niks doen, vaak omdat je een kleine correctie uitvoert. In een aantal gevallen ga je met de cursor over het gebied om iets scherp te maken of omgekeerd en dan hangrt de laptop (i9, 64GB RAM) en gebeurd er niks maar wordt er wel een item aan de geschiedenis toegevoegd. Kortom: blur zit VOL BUGS, IS SUPER TRAAG en verdient jullie aandacht om het wel werkend te krijgen. Met photoshop en layers kan het allemaal wel en Lightroom Classic blijft gewoon achteraan de lijst hangen voor updates. 

Running latest LRC on Windows 11 laptop.  I don’t sync from LR, which I rarely use, and haven’t synced anything for a long time from LR mobile. (LRmobile photos are synced into a “From LR mobile” folder in Collections, none of which shows any obvious issue or activity.)  I’m not aware of other sync activity, Once or twice before, when sync has gotten stuck on a photo, I remember being able to fix this in the Preferences sync settings.  There’s nothing there now showing any sync activity at all, so nothing to delete. No help or search suggestions are useful; they involve different kinds of sync problems and mostly give only Apple and/or LR instructions.)  I’d like to get rid of the error message that appears every time I close LRC, and eventually I’ll have other mobile photos to add to some collection.  If any more info is needed, please let me know.  I’m sure I’m missing something obvious and easy.Many thanks.   

Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Enterprise EditionVersion: 11.0.26200Application architecture: x64System architecture: x64Logical processor count: 32Processor speed: 2.9GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171CPU Utilisation: 0.0%Power Source: Plugged InBuilt-in memory: 65241.4 MBDedicated GPU memory used by Lightroom: 1969.2MB / 12110.0MB (16%)Real memory available to Lightroom: 65241.4 MBReal memory used by Lightroom: 7285.3 MB (11.1%)Virtual memory used by Lightroom: 10360.7 MBGDI objects count: 1088USER objects count: 3663Process handles count: 8272Memory cache size: 0.0MBInternal Camera Raw version: 18.2 [ 2482 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2,AVX,AVX2Camera Raw virtual memory: 89MB / 32620MB (0%)Camera Raw real memory: 98MB / 65241MB (0%)Cache1: NT- RAM:0.0MB, VRAM:0.0MB, Combined:0.0MBCache2: m:0.0MB, n:0.0MBU-main: 194.0MB

When using Lightroom CC on my M3 MacBook Pro, I occasionally get the  "This file does not contain a supported format (or might be damaged)" message when trying to import from either an SD or CFExpress cards containing .CR3 files. Sometimes it works as it should, allowing me import straight from the card, other, usually after I have just imported some files, it shows me this error and I have to first move the files from the card to my Mac before Lightroom allows me to import them - so there's nothing wrong with the files themselves. I don't know what triggers this, I do not know how to get rid of it - it just happens. It's been happening to me for approximately 2 years now on different machines and different versions of macOS, different versions of Lightroom.  

Recently I bought a Mac Mini to be able to work on Adobe applications. I have an external SSD that I used on my old MacBook M1. I uninstalled the Adobe applications on the SSD. Then, I downloaded Creative Cloud on my Mini, but when selecting the installation path of my SSD in Creative Cloud, for some reason Creative Cloud continues to install its apps on my Mac's internal storage.Yes, my SSD is in APFS format

There is a one-way sync issue between Lightroom (cloud) and Lightroom Classic. Sync works correctly from Classic → Cloud:If I create a collection in Lightroom Classic and enable sync, it appears in Lightroom (cloud) with all photos. However, Cloud → Classic does not work:If I create an album in Lightroom (cloud) and upload photos, the album and its photos do not appear in Lightroom Classic in the Collections list. Both apps are logged into the same Adobe account. Only one catalog is syncing in Classic. I have already tried pausing/resuming sync and restarting Classic.System info:macOS Tahoe 26.3Lightroom 9.2Lightroom Classic 15.2

When I try to import photos from my iPhone 14 Max to Lightroom Classic, it is always SUPER SLOW and ow it won’t download all of the,. Currently, I’m trying to import all 1633 photos but am only able to get 776 and then it just stops. I have tried again and again. Not sure what to do. 

ProductAdobe Lightroom ClassicVersion: 15.2OS: Windows 11Camera RAW Format: Canon CR3GPU: NVIDIA GeForce RTX 3050 Laptop GPU (4GB)Graphics Processor Setting: Custom GPU for image processing: Enabled GPU for export: Enabled GPU for preview generation: On Full graphics acceleration enabled  Summary When “Use Smart Previews instead of Originals for image editing” is enabled, exposure adjustments made before the full-resolution original is loaded are reverted once the original file loads (triggered by zooming to 100% or any other zoom).Both the Exposure slider value and the visual rendering reset to their previous state.This issue is 100% reproducible under the configuration described above. Expected Behavior Develop adjustments applied while editing via Smart Previews should persist. Switching from Smart Preview to the full-resolution RAW should not override committed develop parameters. Slider state and render output should remain consistent across rendering pipeline transition

Is there any downside to applying “remove chromatic aberrations" to all files? Normally only certain images show chromatic aberration, such as wide-angle images of buildings or trees against a sky.Is there any reason not to simply apply the correction to an entire folder, even though many of the images don’t show any aberration? Looking at the files in Lightroom Classic I can't see any effect on those without any chromatic aberration.I am working on a project involving thousands of 20-year-old canon files. Back then, both lenses and sensors produced more chromatic aberration than they do today.Any thoughts?

Ich verwalte in LR Classic eine umfangreiche Stichwortliste.Immer wieder passiert es, dass ein Stichwort in einer anderen Gruppe, oft in der obersten Ebene vergeben werden, ohne dass ich sie dort eingetragen hätte.Hier ein Beispiel:Ich habe eine Gruppe "Familie" erstellt, in der verschiedene Namen als Gruppe der nächsten Ebene von mir angelegt wurden.  Dann erscheint an anderer Stelle entweder noch einmal unter der obersten Ebene die Gruppe "Familie" mit einer Untergruppe mit einem Namen und einer geringen Anzahl von Bildern, die ich dort nie hinzugefügt habe.Hat jemand eine Idee, wie das zustande kommen kann?Und wichtig wäre mir eine Lösung, wie ich die Eintragungen, die in einer nicht gewollten Gruppe auftauchen, der richtigen Person in der richtigen Gruppe zugeordnet werden können.Bisher habe ich tausende Bilder nacheinander markiert und geprüft, ob ein Bild in der falschern Gruppe auftaucht. Dann habe ich das Bild in der falschen Stichwortgruppe entfernt und der richtigen zuge

Greetings!I updated LR Classic to 15.2 a few days ago and am unable to import “new” panoramic photos that I create in a new subfolder within the folder structure. Additionally, I started a new batch/project that I imported after the upgrade. To start my project in LR, I first import the folder(s) and files and then start my editing tasks.My workflow is to choose my series of photos in LR with which I want to create a panoramic photo in PS. I then pass them to PS using LR: Edit In> Merge to Panorama in Photoshop. The files are passed to PS and merged/edited/flattened to my satisfaction. I save the panorama in PS, but within the folder structure I create a new subfolder titled “Panoramas” with the very first panorama that I create for this new batch of photos/project in the PS save image dialogue box. I then create additional panoramic photos as I wish and store them in this Panoramas subfolder. This is the workflow that I’ve been using for years.When I return to Lightroom, this time,

Modal progress Scopes created by SDK stay visible EVEN when they are done.The modal scope can’t be cancelled, it stays there unless I restart LrCI see this with my own plug-ins but also ​@johnrellis (that I use for the video example) Usually the task running within/under the scope is completed safely BUT still the bug is problematic. 

When i start LRC or LR there is just coming up a message box"The code execution cannot continue because mfc140u.dll cannot be found. Try reinstalling the application.”Have tried reinstalling without success,This message applies only to LRC and LR.PS works. What to do? BRHåkan

Na ferramenta “Cortar” quando escolhemos a opção “Personalizar”, podia dar a hipótese de personalizarmos por escrito o tamanho que queremos realmente cortar a fotografia. Desta forma não teria que trabalhar as fotos no Lr do iPad e depois ter de passar para o Lr do computador para poder realmente personalizar o corte como quero. Isto facilitava imenso na questão de corte para redes sociais como Instagram (corte de foto para paisagem por ex.).

I’ve tried the ‘autosync’ reply and can’t get it to work.   Any other ideas.  Would *really* be a time saver?   And WHY was the code changed from the previous working version.   I have v 15.1.1

I have recently run into an issue where very dark shadows are being clipped in Lightroom Classic and Adobe Camera Raw. No issue in Photoshop. MacBook Pro M3 MaxmacOS 15.6.1Photoshop 26.10.0Lightroom Classic 14.5.1 I noticed this issue with macOS 15.5.0 and the previous releases of PS and LRC. I updated everything to the latest as of this morning, rebooted multiple times, and the issue still exists. The issue happens when:Using the built-in display of my MacBook and the stock Apple XDR profiles or custom profiles I created with my Calibrite Display Plus HL.Using my external 24" LG 4K display with custom profiles created with my Calibrate Display Plus HL. The issue DOES NOT happen when I set the display to use a generic profile like Display P3. Disabling GPU acceleration in LRC improves the problem (less clipping) but doesn't completely get rid of it. The issue also happens when using Adobe Camera Raw in Photoshop as filter on a layer. I updated Calibra

Hallo, ich habe mit LRC gestartet und die ersten Bilder importiert und ausprobiert. dabei is galube ich so einiges durcheinander geraten. Am liebsten würde ich alle von LRC installiert Ordnder wieder löschen und von vorn beginne. Wie kann ich das machen? Danke für Hinweise. Beste GrüßeWPetersen

How can I add additional aspect ratios as a saved preset to my crop tool? I’m tired of entering them manually each time and would like to save them for future use.