Lightroom Classic

I am using the latest version of LRC and it has always been set to backup on exit. This has worked perfectly up until now. When exiting it asks to backup as per normal, I start the backup and it appears to be working. Once Lightroom closes after backup is complete the backup files are then deleted. If I point the backup to a new location it performs the backup and then on subsequent backups the files are then deleted. Is this a bug with the latest update from Adobe or has something changed in the configuration that I cannot see?More information: backup size is 1.2 GB available space for backup on any drive ranges from 4 TB to 48 TB, so hard drive space is not an issue. It occurs on all drive types from spinning disk to SSD, and it does not matter if it is the primary disk or not the same issue happens. There is no error messages, backups appear to run as per normal then Lightroom exits and then the backups just disappear. Any help would be appreciated.

Hi everyone,I have an heating issue in my macbook pro which has i9 processor and 32 gb of ram and 2 tb of storage. It heats up in using of 30 min. Its gpu if full acccelerated too. Apple care center are telling that you are using a high end sofware so it is heating. Any help what to do.

Hi, since a while now I can't seem to see or adjust the edit pins on masks when a mask is bigger than the photo/crop. I have a radial gradient for example and cant adjust the size without placing the border in the frame of the picture....

I have a library with processed images. Unfortunately the file names have changed. Is there a way to link the files without having to do this file by file (more then 1000 images)

Bonjour, j'ai à chaque fois ce message d'erreur lorsque je veux ouvrir une photo de LrC vers Ps 2024, cela fonctionnait avant correctement.  Si je réinstalle Adobe Photoshop 2024, vais-je perdre tout ce que j'avais dedans (brushes, actions enregistrées,....)?  Merci d'avance pour votre aide 🤗 

Hi, Lightroom Classic v13.5.1 on Mac Sonoma 14.6.1   I'm trying to publish a collection to Flickr and I get an error message:-   Can't update this collection. An internal error has occurred: Error Domain=NSXMLParserErrorDomain Code=76 "Line 4: Opening and ending tag mismatch: META line 2 and HEAD Userinfo={NSLocalizedDescription=Line 4: Opening and ending tag mismatch: META line 2 and HEAD   Anyone else getting this message?   Si  

I'm doing a rather large import (3000 images) and the processing gets stuck at the Build Smart Previews step.  The images are successfully imported to the catalog and destination folders - it's the previews step that stalls.  Lightroom is gobbling memory until the system becomes unresponsive.  I tried manually requesting smart previews on the folders of images and had the same result.  After 20+hrs it finally just stalled and I had to kill Lightroom. I've successfully imported large groups of images like this before with no issues, and the import and preview build takes < 2hr.    Below is a snapshot of the "system info" while it's bogged down creating previews. Lightroom Classic version: 13.5.1 [ 202408271704-d15d09cd ]License: Creative CloudLanguage setting: enOperating system: Windows 10 - Home Premium EditionVersion: 10.0.19045Application architecture: x64System architecture: x64Logical processor count: 4Processor speed: 2.9GHzSqLite V

I have a Windows 11 computer.  Since updating to lightroom 13.5, when importing images into lightroom I have been getting low memory on C: drive warnings. My question is: does lightroom have a command similar to the ctrl+alt command in Photoshop that the user to define the drive space that the app uses to do ith thing.

https://www.veed.io/view/7f2805ea-0c44-4f07-adcd-7ecd3ead0be4?panel= Help, my lightroom now always crash like this whenever I try to edit or apply the presetsanyone have similiar experience?

Lightroom Classic  13.5 update installed recently and programme will not respond. Have tried to delete and install an earlier version but am frustrated at not being allowed to do this. Unable to process any of my photos 

Lightroom Classic on PC opens now to import page and when I close or press "Done" it cucles from "Develop" automatically back to import page. I cannot access myphotos or download new ones.

Hello,    I am a long time user of LR Classic. Recently application become unusable due to the following problem. When I launch the application, within 2-3 minutes all 32GB of ram are being consumed, my SSD tops at 100% and CPU utilisation rises. It is not clear if there are some background processes that are running or if it is related to the latest update.    I have tried to let it run over night (in hope that LR will complete whatever it might be doing) unfortunately it didn't helped.    Could you please help in investigating of what could be the problem. Attaching a log below. Thanks you.    Lightroom Classic version: 13.5 [ 202408062022-6258095b ] License: Creative Cloud Language setting: en Operating system: Windows 11 - Business Edition Version: 11.0.22631 Application architecture: x64 System architecture: x64 Logical processor count: 16 Processor speed: 3.7GHz SqLite Version: 3.36.0 CPU Utilisation: 1.0% Power Source: Plugged In Built-in

im having issues emailing images out of LR C ... i keep getting a message that states Validation Fail .. cannot establish a secure channe; with the outgoing email server ... ive tried serval email addresses ie outlook .. google,but still no joy ... 

Hi, I am using a MacBook with M2 Pro chip and Sequoia 15. I have also installed NX Thether 2.1.0. When I select Direct Acquisition, it requests me to restart in Rosetta Emulation mode. According to the Adobe manual, it should work in native mode without emulation. What shall I do to fix it? Thank you, 

Holding the Option key (Mac) while using the Basic tab sliders in Develop mode used to show Blacks and Whites peaks when editing. Now the screen still switches to black or white, but sliding doesn't reveal any peaks on either. Without the Option key, the sliders still work. Was there a change in this functionality? MacOS Sonoma 14.4.1 MBP 2023 M3 Pro Max

I have been scanning old negatives with VueScan, converting them from Negative to Positive in LR for nearly 4 years now.  The last step in my process is to convert the files to DNG in LR.  Since 13.x this step has slowed to a crawl and even crashed LR (sent a bug report to Adobe when it crashed).   I select a group of photos to convert (10-20) to DNG, I then watch high utilization and memory usage jump from about 10gig to 36gig or so. Converting 10 images in the past took maybe a minute.  Now it's at least a minute for 1 file.  I made an attempt to convert 22 files this morning, LR crashed after about 18. I have tested this with no other apps open, without GPU acceleration with the same results. Something has definitely changed in this version. Has anyone experienced this issue? The other bug I have is dual monitor zooming in Develop mode, something I use every day, now broken. This has been acknowledged in other posts here. Another bug

Message d'erreur "Echec de la suppression générative" dès le début du processus

J'ai créé une collection dans lightroom, grâce à une dossier photo de mon disque dur.J ai transféré mes photos de mon disque dur (que j'ai revendu) sur un autreMon problème c'est que ma collection ne trouve plus sa source et donc les retouches que j ai déjà faite de cette collection ne sont pas exportables Merci d'avance pour votre aide  Cam

How can I use Lightroom for my old Mac which runs on Catalina 10.15.x OS? Where can I download such installer that is compatible for my OS?

i use Nikon Zf and cannot tethering in Lightroom ?

Hey, so like so many here I have encountered an issue with my LR Classic. I opened it, synced my catalog since I just got a new PC and then in the final step wanted to paste my Presets into LR. Well during that time LR began using more and more RAM (up to 30 of my 32GB)...which I was confused about but just ignored. Well in the final Step I changed the App language since it was in German and I wanted it to be in English. Then I closed the app to restart it and that is where the issue began. IT. WILL. NOT. OPEN! I have tried everything: Delete LR, reinstall, Delete Preferences, Restart my PC, use the Cleaner Tool to remove it and also to clean the entire Suite...nothing. It just sits in my Task Manager using around 5GB of RAM...I have no clue what else I can do. Every other App works fine. Please someone help me 

There is a brown caste over the lower part of the tail and neck area of this hummingbird and I have made a couple of unsuccessful attempts are removing it in LR classic and Photoshop.Wondering if someone can help me with this image please. Tried to load the actual image however I keep getting a message that the file type is not correct or invalid. It is an Nikon NEF file. finno

Bonjour, je n'arrive pas à créer de diaporama. Au moment d'appuyer sur Lecture, ca mouline, mouline. Il apparait "création d'un aperçu de la photo X, et rien ne se passeJe n'ai pas désinstallé les anciennes versions de Lrc et Ps que j'utilisais avant de m'abonner à la suite Adobe ...Y aurait il incompatibilité ?    

Hi, I noticed that .arw raw files shot with lossless compressed (M) size are not supported with Denoise in Lightroom Classic. These are shot with my A7RV. The full size (L) files work fine, it just seems to be the medium size (or maybe small too...haven't tested those yet). Is this a bug? Are these not supported by denoise? Will they at some point?Thanks

I have been a loyal customer of Adobe for many years, however, I have been suffering crashes in Lightroom whilst import, editing, backing up and at random other toimes since March.  I have had Adobe Support Agents blame my system with not enough processor speed, its an I9, not enough memory I have 96gb, video card, SSDs et al, they have sone 3 clean installs then expect me to recreate the error instantly, one day I was able to do it and was told my copy of Windows was bad, I use Win 11 Pro and there is nothing wrong with it. So the challenge here is for an Adobe Support person on the forum to try and help resolve the issue before I cancel my plan and move to a different editor.  So the ball is in Adobes court, I await a response.