Questions

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

I’ve had this problem for awhile now and haven’t been able to find a solution.  On the import tab when attempting to import pictures it takes Lightroom classic forever to generate the thumbnails. I’m not talking about the previews that get built based on my choice during the import. I talking about the grid view where you can select which files to actually import.  I just tried on a sample of 280 pictures and it took the better part of 3 or 4 minutes to generate the thumbnails. Which is about as long as it takes to do the actual import AND generate 1:1 previews…  I’m shooting primarily a fujifilm XT5 with and only shoot .RAFLightroom version 13-3 (but has been happening for the better part of the last 2 years) I’ve got a very good homebuilt computer Intel Core i7-13700k (liquid cooled)RTX 4070 (GPU acceleration turned on)64 gigs of RAMHarddrive in question is a 30% full M.2 NVME SSD I previously bought a high end card reader and usb 3.0 cabling hoping this would help. Which is doesn’t.

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’m done with this. With every single update, Lightroom becomes more of a mess. Now, out of nowhere, the brush tool and masking have completely stopped working. I can't get any work done.I have already tried all the standard "fixes":Toggling GPU acceleration on/off - no effect.Restarting macOS and Lightroom multiple times - no effect.Resetting preferences and clearing cache - still nothing.And don't even try to blame my hardware. I am running this on a Mac Studio M1 Max and a MacBook Pro 16 M1 Pro. The exact same issue occurs on both machines after working for a while. This isn't a hardware limitation; this is your buggy, unoptimized code.I posted about this exact problem months ago in this forum, and nothing has been fixed. You keep charging a monthly subscription fee, yet you fail to provide a stable environment for basic functions like masking. This is my last year with Adobe. I am officially looking for alternatives that actually work and don't waste my time and nerves.Fix your sof

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

Dear community, Today as often clickedon the LR shortcut towork on my photo but instead of launching normaly, I had the "Adobe Phtoshop Lightroom 6 Sign In " pop up. Than it directly goes to the Phtoshop Lightroom 6 Trial window. I click on License this software, put my Serial Number (bought in 2017) click on "Next" but instead of going to the next step, it reload the "Adobe Phtoshop Lightroom 6 Sign In " pop up. Did not try to uninstall the software as I am not sure it will help and not sure I won t loose my catalog. Any clue, on what happened? Thanks, Chris   {Moved from Lightroom Cloud to Lightroom Classic Forum by Moderator}

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.

The SDK call folder:getParent() raises the error "?:0: attempt to index field 'parent' (a nil value)" when called on the root folder of some catalogs on Windows -- it should return nil instead. To reproduce on LR 15.0.1 / Windows 11 ARM and Windows 11 Intel: 1. Download and uncompress this catalog folder:https://www.dropbox.com/scl/fi/t1gksh5hw2ov8g48tcca6/folder-getparent-bug.2025-11-20.zip?rlkey=kxqi5d5bx3tqcalrne14fyv2k&dl=0 2. Move the file "folder-getparent-bug.lua" from the catalog folder to the LR Scripts folder. 3. Start LR and open the catalog. 4. In the Scripts menu, invoke "folder-getparent-bug".  Observe this output: When tested on Mac OS 15.7.1, no error occurs:  Note that on Mac, the call to folder:getParent() returns 0 results rather than nil (though in most contexts, there's no difference).  

I’ve tried every twist possible. I have lots of details (pasted here) and will attach a diagnostic zip file.I’m having trouble with Lightroom Classic 15.x upon closing. The LrC window closes but LrC hangs as a very active background process. I’ve done a lot of testing and reinstalling and I’m looking for an under-the-hood solution to the problem. Please! Here is what I have, and the steps taken so far.System: Windows 11 ProLrC 15.1, 15.1.1 and 15.2, (have tested all three versions)NVIDIA GeForce RTX 3060, driver up to date, per Windows Update: 32.0.15.9144Primary LrC catalog on internal SSD (Drive X:)Problem: When LrC window closes and hangs as background process, Windows Process Monitor shows hits at a rate of 8-10 per sec toRegQueryValue onHKLM\System\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{6a90529f-eb48-11f0-9d67-806e6f6e6963}\EnableDhcpResult → "NAME NOT FOUND"Two Work Arounds – Neither is viable long term:In a new Windows 11 profile named “Test,” I launched and shu