Lightroom Classic

I am addressing the problem of connecting the Sony A7R V camera to lightroom Classic (latest version). The camera is not detected by the program, and Live View and controls are not working.Laptop No. 1 ( Huawei MateBook X Pro 2024 )The Sony A7RV camera (firmware 3.0) does not connect to lightroom Classic (latest version 23...)Using a tether tools cable (USB-C → USB-A) with a USB-C 3.0 adapter in order to plug into a laptop.I tried another high-speed cable without an adapter (USB-C → USB-C) - and it doesn't connect either.At the same time, the fuji xt3 camera with the same cable is immediately detected on Huawei MateBook X Pro 2024.Sony's native Imaging Edge app sees everything and connects everything, everything is OK.Laptop No. 2 (my old one)I tried: on a new laptop, connect a Sony A7RV via a tether tools cable (USB-C → USB-A) and everything works without problems, the camera is displayed.All camera settings for "Remote shooting" are enabled.The camera is being sent to the Device Mana

In my AppData file on my laptop I found a file deep down inside named “Originals”. This file has a number of subfiles labelled 2001 to 2023 with my images for each year.  However, at this point they are consuming 500+ GB of my 1 terabit hard drive.  Can I delete these files without adversely affecting the performance of Lightroom Classic or Photoshop?

My camera internal naming has turned over recently without issue.  Suddenly LR Classic v15.01 sees majority of images as duplicates.  All images switched on everything switched off but most images are permanently6 and irretrievably greyed out.  The images in question are RAW images taken yesterday and indeed the names of those greyed out are in the catalog under different earlier dates (obviously) at least 4 times over!   Why has Lightroom suddenly altered its behaviour?  It is as if the introduction of the new (unwanted by me) culling features have upset the import coding?Even renaming the filename of the images fails to ungrey them out.   Following the 'show in explorer' option shows me the memory card file structure and the files present.  Confirmation with other softwares shows the files as present and without issue.   I have resynchronised all folders in the catalog and optimised LR, I have also reset all preferences via the alt click m

I am just reviewing and re-editing some old RAW photos taken on a Canon 60D with a Canon EF-S 17-85 f/4-5.6 IS USM lens.  The camera and lens are correctly identified in the metadata for these photos, but when I go to the lens correction tab it says the lens cannot be recognised. If I then enter Canon as the make it tells me my lens is a Canon 16 mm lens, so I then have to select the 17-85 from the long drop down list.  I don't mind having to do this for one or two photos, but I have many for which I need to make this correction.

I am SO INFURIATED! Half of my photos from 2021 have been deleted when I tried transferring the folder from one harddrive to the other through my Lightroom catalogue. I actually want to cry... it had wedding photos on there!! NEVER trusting Lightroom again when transferring files. 

Hello all, I'm using the Creative Cloud app (6.8.0.821) to download LrC 15.01 and Camera Raw 18.0 to my Mac (Mac Mini M4 Pro, Tahoe 26.1). I have LrC 15.0 installed but can't open the latest catalogs I generated with a different Mac because THAT Mac (also mine) runs LrC 15.01, and LrC 15.0 won't open a catalog that has been 'upgraded'. For both LrC and CR, the downloads are at literal snail-speed -- CR update hangs at 9% loaded, LrC update hangs at 19%. I can't work on my latest catalogs until this is fixed. Thoughts?

  Nach irgendeinem Windowsupdate im Sommer 2024 ging die Super Resolution und Entrauschen nicht mehr, egal ob arw oder raf , bis zum Sommer 2024 funktionierte das einwandfrei, habe seit einem Jahr alles mögliche probiert, es funktioniert nicht ??? siehe screenshots

Hopefully someone can help or point me in the right direction. I got a new MacBook Pro and loaded the current version of lightroom classic. The problem is when I import photos into Lightroom (either using a card reader or directly from the camera) - the photos are NEF in Lightroom but on the hard drive they have shown up as Topaz Denoise. I deleted that to see if that would make any difference. But when I imported again - Lightroom had NEF but the hard drive had NX this time. I’m not tech so I have no idea how to fix this. I'm importing  COPY with copies going to designated spot on my hard drive. Thanks for any help as I’m really frustrated. 

LRC seems to have severe GPU memory leaks, at least v.13.3. It keeps growing till consuming 80-90% of 12GB VRAM (*), at which point all GPU-intense operations such as AI noise reduction become unberably slow, so I have to restart every 20 minutes or so. It does not contribute to a smooth workflow.Does anyone know a simpler workaround than just restarting the entire thing (that does not involve disabling GPU acceleration of course)? -----*) 80-90% is per Windows Task Manager when no op is running in LRC. Lightroom itelf says litreraly the following in System Info: "Dedicated GPU memory used by Lightroom: 13884.1MB / 12107.0MB (114%)" 

Regardless of how I try and open LR Classic on my MBP M1 Max 64GB memory Ventura 13.2.1, I rcecive the same error report : "Adobe Lightroom Classic Quit Unexpectedly" It occurs with Lightroon CC as well.I HAVE SHUT DOWN AND RESTARTED, BUT TO NO EFFECT.Any thoughts?Cath Here's a selection of the report sent to Apple:Process: Adobe Lightroom Classic [2163]Path: /Applications/Adobe Lightroom Classic/Adobe Lightroom Classic.app/Contents/MacOS/Adobe Lightroom ClassicIdentifier: com.adobe.LightroomClassicCC7Version: 12.4 (12.4)Code Type: ARM-64 (Native)Parent Process: launchd [1]OS Version: macOS 13.2.1 (22D68)Exception Type: EXC_CRASH (SIGABRT)

When I Delete photo from disk while in Develop panel, after deleting next photo is not selected and I have to take mouse and select it. When I try to use arrow keys to jump to next photo, it jumps to the end or beginning of stripe. It is annoying and slowing workflow.

LRC is not importing pictures. When I open the import window, I see the files, but the thumbnails are grey. When I press the import button nothing happens. When I stop the importing I get a message that that no videos or photos were found to import. I have already uninstalled and reinstalledLRC.Lightroom Classic version: 14.0.1 [ 202410161356-30922cfc ]License: Creative CloudLanguage setting: enOperating system: Windows 10 - Home Premium EditionVersion: 10.0.19045Application architecture: x64System architecture: x64Logical processor count: 8Processor speed: 3,2GHzSqLite Version: 3.36.0CPU Utilisation: 0,0%Power Source: Plugged InBuilt-in memory: 32723,5 MBDedicated GPU memory used by Lightroom: 2557,2MB / 5966,0MB (42%)Real memory available to Lightroom: 32723,5 MBReal memory used by Lightroom: 6970,6 MB (21,3%)Virtual memory used by Lightroom: 11544,1 MBGDI objects count: 1263USER objects count: 3777Process handles count: 7392Memory cache size: 305,8MBInternal Camera Raw version: 17.0

Hey y'all, For the last few months I've been encountering an irritating bug that I would love some help solving.  I have a catalog of around 90,000 images--a mix of digital camera files as well as film scans. Running Mac OSX Sonoma 14.4.1 with Lightroom Classic 13.2 (CC, updating automatically). The issue: In Library grid view, I see my edited images, but when I select an image, after a few seconds of "thinking", the edit dissapears and the image shows as if it just came straight from camera (unedited). This remains the same when I move into the Develop module. The edit history is still intact, so I simply have to navigate to the most recent (top line) of the edit history and select it to reload the edit. Almost like I'm reminding it that it's been edited.  This bug only affects images from before a certain date. So if I import new images and edit them, they hold their edits just fine. But the majority of my libary is affected by this issue. It's not the e

I am having issues with LR (15.0.1) behavior when applying auto profile lens corrections (via copy/pasting, "paste from previous," or creating/applying a preset).   As soon as I reduce the "amount" of distortion or vignetting, the profile setup gets changed to "Custom" and as such copy/pasting applies the exact lens profile (the model & profile of the copied image) to the next image regardless of whether it used that lens or not.   My usage case is something like the following: 1) I have pictures taken on a Canon EF16-35mm f2.8, as well as pictures taken on a Canon EF35mm f1.4 and a Canon EF50mm f1.4. 2) Often when I click "Enable Profile Corrections," I like to turn the distortion correction to "0", and reduce the vignetting correction to 50. 3) When I proceed to the next image and paste from previous, LR also applies the Lens corrections with the lens profile & model of the previous image. The can be quite frustrating, as any change of lens means I have to avoid cop

I just installed 15.0.1 and the 2nd monitor no longer shows or toggles the info display with the press of the 'I' key.  OS is Win11.

On my imac importing mp4 or mov files in my library has n problem.On my New windows 11 laptop it is impossible to import both file types.Does anybody have a solution for thuis problem. / I

Suddenly i am receiving a 2nd prompt screen when Exporting a photo to disk. As far as i know i have not changed any settings. The first screen has "Export To: Hard Drive" and "Export To: Specific Folder" with a valid folder selected. When i click Export a Windows File Explorer window appears with the proper folder already selected and i simply need to hit "Select Folder" to continue. Anyone know why this is happening?Thanks in advance. Windows 10Most current version of Lightroom Classic

Hello,I need a download link for Lightroom Classic 12.5.2 - I know I was given one a few months ago, but can't seem to find the download anymore. Life was very hectic the last months, please forgive the redundancy of my request…Thank you !T.

I have configured Lightroom Classic to use the GPU,  all settings are checked in Preferences.   Yet when I check System Info GPU is clearly NOT enabled.   V15.01 takes minutes to load evern with an empty catalog and subject masking amongst others takes forever.   I have been working on this for days and have now run out of ideas.   Please check my System Info : Lightroom Classic version: 15.0.1 [ 202511041508-dddee541 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Home Premium EditionVersion: 11.0.26200Application architecture: x64System architecture: x64Logical processor count: 28Processor speed: 2.1GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171CPU Utilisation: 0.0%Power Source: Plugged InBuilt-in memory: 32536.5 MBDedicated GPU memory used by Lightroom: 2760.1MB / 15907.0MB (17%)Real memory available to Lightroom: 32536.5 MBReal memory used by Lightroom: 3144.6 MB (9.6%)Virtual memory used by Lightr

I have run into a problem after upgrading to the latest version of Lightroom Classic. I keep having an exclamation mark on my ultimate parent folder, but there is no exclamation mark on any of the subfolders. Hence, I can see if there are any missing photos. Everything seems to work fine but I’d like to get rid of the exclamation mark. I have tried to make a new catalog with the same photos. This works and the exclamation mark disappears but I am loosing all my collections. Is this a bug or am I missing something?

I'm using Lightroom Classic version 15.0.1 on a MacBook Pro, Sequoia 15.7.1.I understand that you may get an icon showing that folders have missing subfolders in them. My main folder, Pictures, shows the icon. I have gone through every folder & subfolders within that parent folder, and none of them have the icon.I have no idea how to get rid of that icon without starting a new catalog and reimporting all my images (26K+).Is this a bug as was suggested by a Lightroom Classic guru, or am I missing something?Thanks! 

Running LrC 15.01 on Mac mini M4 Pro with 64GB of memory and Tahoe 26.1. Catalog is on the main drive with over 300GB free. I have already tried uninstalling and reinstalling LrC. I also tried factory reseting the preferences on LrC.Certain things are not responsive. The most recent example is exporting. I selected 10 photos to export and hit the export button. It took over a minute for the export dialog to come up. I selected the options I needed (nothing exotic and nothing that has not worked quickly before) and it has been several minutes already and there is no sign of the export happening. Another example is marking a photo as rejected. I hit the X and it says the photo is rejected but it is not marked with an X nor grayed out in the grid view until minutes later.I observe that LrC is often running at around 100% in the background regardless of whether I am doing anything or not. I left it overnight and it was still doing 102% CPU usage in the morning. I have paused sync, AI culli

I recently had the external hard drive containing all of my images fail. Today the 4 TB WD SSD from Backblaze arrived. My Macbook Pro shows this new drive in Finder but LrC is not seeing it. I've used multiple SSDs in the past as I travel quite a bit and never had a problem with it recognizing any of the Samsung T7s that I use. I am using LrC version 15.0.1. Apple M2 Pro  Sonoma 14.6.1. 

Problem: If I made a mistake in a face assignment to a named person, I cannot fix it. Steps to reproduce: Double-click the face of any named person to open up the collection of faces assigned to that person ("Confirmed" panel). Right-click any face - no menu available. This means that if I made a mistake in the assignment, I cannot fix it. I'm pretty sure that this worked before the latest LRC update.Expected result: Go to the People panel, right-click on any of the named people and you'll get a menu including the option to "Move to unnamed people".Version of the app: 13.2Platform and OS version: Windows 11 Pro - 23H2Thanks, Adriaan Sachtler

Hola, En Lihgtroom 15, cuando se importa un preset despues no sale en la lista de la izquierda. y si se crea uno, no aparece en las demás carpetas. Aunque esta instalado y no se le puede llamar. Es decir que creas un peset y no lo puedes usar en otras carpetas o catálogos. El preset solo lo puedes usar en una carpeta.