Questions

lightroom new folder create short cut key not working ctrl+shift+n please help i am using windows and this is most important for me

I am an amateur photographer and subscriber to the Adobe Photography plan.I usually organize and develop my photos on my desktop computer.I am also in a photography association and a couple of times a week I meet with other members to look at our photos and exchange all kinds of knowledge. For these meetings I use a laptop.Since I didn't want to move my photos from one place to another, I came up with a great (disastrous) idea. I bought a USB docking station with a slot for an M.2 disk. It is an Orico docking station 10 in1. I connected a Crucial P3 Plus 4TB drive to it. I put the last five years of photos on this disk along with the Lightroom Classic catalog. The hub connects to the computers via a 10Gbps USB-C port. I have assigned the letter T to the Crucial drive on both computers. My idea was that anything I do to the photos in the desktop would be available in the laptop because I was using the same catalog.On the desktop, the difference in speed between having the catalog on an

While importing photos from disk I'm struggling to stack these photos with existing photos in the Lightroom catalog. My use case:In my Lightroom catalog I have 2 imagesOn my disk I have 2 other images, noy yet loaded into Lightroom.Their file name makes it clear which image on disk belongs to which image in the databaseI'm using:catalog:addPhoto( filePath, photo, 'above')What works well?The images are loaded into Lightroom.What works not?They are not stacked.Question: what am I missing? Steps to reproduceSee the attached imagesImport the two photos without "_nbg" into LightroomPut the other two, without "_nbg" in the file name, into some directory.Change in my sample code below my directory name with the directory name you used above. I downloaded the images from Unsplash.com local LrApplication = import "LrApplication" local LrDialogs = import "LrDialogs" local LrFileUtils = import "LrFileUtils" local LrFunctionContext = import "LrFunctionContext" local LrPathUtils

Adding a keyword not currently in the Keyword List to a photo and then doing Undo correctly removes the keyword from the photo but incorrectly leaves the keyword in the Keyword List.  This is important to users maintaining a carefully controlled vocabulary. If they mistype a new keyword and then Undo, leaving it in the Keyword List will make it likely that auto suggest will cause them to add the mistyped keyword to a future photo. Back in LR 9.2, LR's product managers recognized that it was important that Undo remove the newly added keyword from the Keyword List as well as the photo. Previous versions would remove the keyword from the Keyword List but not the auto-suggest list, and LR 9.2 fixed that, also removing the undone keyword from the auto-suggest list:https://community.adobe.com/t5/lightroom-classic-bugs/p-deleting-a-keyword-from-the-keyword-list-doesn-t-remove-it-from-auto-complete/idi-p/12249083 From version 9.2 through version 12.1, Undo would remove the

Hola,  Por favor, alguien sabe como se puede instalar la última versión (Lightroom Classic 9.x) compatible con Mac OS High Sierra?  Gracias

Hello. I recently changed my system, here are the specs:   CPU Amd Ryzen 7800 X3D GPU Amd Rx 7900XTX Asrock 64 gigs of ram ddr5 6400 mhz Windows 11 64 bit   My current version of lightroom is 7.2   Whenever i open the mask/correction section, the system slow down a lot. Sometimes i am able to apply the mask but most of the time Lightroom freeze (white screen). I also have issues in the visualization of images (inverted luminosity and colours). Sometimes i get th message "the acces to the graphic accelerator was disabled. Obviously I tried to disable the acces in the option of lightroom but the problem came back again.   I uninstalled the Amd drivers with amd clean utility and installed them again with the latest version of adrenalin control wich is the 24.5.1   Here's the report from lightroom:   <?xml version="1.0"?><!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd"><crashreport serviceVersion="13.2.0.202308091502_65b8636" clientVer

Adobe Lightroom Classic por es mas lento que en todo Capture One no entiendo por que.Tengo un I7 12700, una Tarjeta grafía rtx3600, 32 de ram ddr5 y un ssd para programas y sistema operativo de un tera .Capture One todo es prácticamente instantáneo y adobe todo tiene Lightroom pasar de galería a edición , cambiar de foto en edición 3 o 4 segundos pasar a al galería otro tantos segundos , llevo muchos años en Capture One era una maravilla y me pasa adobe por el tema de IA que esta bien muy bien ahora que hay capas Lightroom por IA me encantan .Porque el programa haciendo cosas normales esta siempre con retados no lo soporto . Hay forma de solucionar estoy haciendo algo mal. Hay poner las foto también el disco ssd porque en Capture One no hacia falta. O hay que poner la base de datos de Lightroom en el ssd . Hay una alguna forma de que Lightroom sea igual de fluido que Capture One. Tengo activado la aceleración por hardware

Bonjour, Lorsque je selectionne un sujet celui-ci devient fuchsia au lieu de rouge comme d'habitude et reste fuchsia lors des modifications ce qui m'empeche de travailler correctement. Avez-vous déjà rencontré ce problème et trouvé la solution ?  merci de vos réponses 

Hi to everybody!  I think I'm doing something wrong so I beg your help! I shoot with nikon z6II at the highest level. I impost the file in LR Classic 13.2 and then I export it in Photoshop 2024.  The  .psd file coming out from Photoshop 2024 is 458 MB.Then I save it as .jpeg (save as) and the result is 3 MB!!!!! What's happening? I'm upset. I want to deliver to my costumers High definitions file but 3 MB are my my idea of HD files! The picture is 7087 x 4714 pixels (300 dpi).I tried to check our all export preferences but maybe I forgot something. Thank you to the person who can help me! Cinzia 

Plugins for correcting, erasing and repairing photos in LR classic do not work

Can somebody help me? I'm experiencing this kind of error where the files are broken when i was editing them. I tried reinstalling the app and even downgrade the version but the same thing still happened. When i migrated the file into Photoshop the file became normal again. But yesterday the same error occured in Camera Raw as well. And the problem with my Lightroom Classic has turned even worse now. It's always force closed everytime i migrated the file to Photoshop  

Just downloaded some Lightroom preset brushes, however according to instructions there is suppose to be a brush icon on the far right.  Mine does not....anyone have any thoughts?  Photo attached.  

Hi.My lightroom classic v.13.2 sometimes at the start was doing reset to factory settings, delete all my presets & show tips as the program was only installed. The only thing that doesn't fit is the graphics card, which the program shows is incompatible. do I need to change the graphics card? or is the problem somewhere else?The program works normally except for the graphics card incompatibility.

The Adobe support web site states the LrC 9.3 and later support HEVC video.  I am shooting HEVC video with my Sony A1.  The files play well on the VLC media player.  In LrC v13.2 which I am using the video shows still frames in the video clips if I drag the small button but if I click the play arrowhead it shows a bizzare greenish mess.  Here is the file info from Sony Catalyst Browse (with incidently plays the video without any issues): I thought I might need the addional codecs that Microsoft sells, but the Microsoft site says they are already installed.  Here is a list of the video codecs on my system:I find it strange that other apps play the videos without issue, but LR fails.Any suggestions?? System info:Edition Windows 10 HomeVersion 22H2Installed on ‎9/‎30/‎2021OS build 19045.4412Experience Windows Feature Experience Pack 1000.19056.1000.0 I have an Nvidia 3090 with 24GB of memory with the latest Studio driver. 

It’s a 13” M2 MacBook Pro with 24 GB of RAM, and the files are from a Fuji GFX100s. I have always used Lightroom Classic and never had a problem unless I was editing a lot of photos without restarting Lightroom, which would solve the problem (the problem being running out of RAM). Recently, it seems to be using way more hardware than it ever did before. The CPU usage hovers around 70% and the RAM usage is over 100% while I am idling in the development window, and when I try to do anything, the CPU jumps to 100%, and everything freezes up until the CPU usage drops back down. This is all while only having one file in my catalog.I took the same file and edited it in Lightroom CC, and the CPU usage never got over 35% and hovered around 17%, and the RAM never went over 21 GB used. Nothing was laggy, and it worked fine. I also edited the same file in Capture One 23, and it used even less hardware.I prefer to use Lightroom Classic for most of my work, but as of late, it’s been straight u

I am still experiencing crashes and off behaviour while editing captions and, to a lesser extent, titles in Lightroom Classic.   The attached screen recording shows characters at the end of a caption disappearing in edit mode but reappearing when leaving edit mode. Finally, I select-all and paste the correct text to clear the characters. This occurred in the default metadata display. I moved to Large Caption display mode to better see all the text.   Another failure mode is when clicking in the caption box to edit an existing caption, the box goes all white, the existing text disappears, and any new typing is not shown. When this happens, a crash is imminent. See my recent crash logs over the last two days.   System Info Lightroom Classic version: 13.2 [ 202402141005-bf1aeb84 ]License: Creative CloudLanguage setting: en-AUOperating system: Mac OS 14Version: 14.4.1 [23E224]Application architecture: arm64Logical processor count: 10Processor speed: NASqLite Version: 3.36.0B

With GPU disabled, Lightroom uses about 6GB.  With GPU enabled LRC consumes all available memory in a 32GB system and eventually stops responding and then crashes.  When LRC stops responding, Process Explorer shows the process "suspended"... after a few minutes in this state, LRC crashes.   System Information, containing O/S, hardware and driver info     Lightroom Classic version: 13.2 [ 202402141005-bf1aeb84 ] 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.9GHz SqLite Version: 3.36.0 CPU Utilisation: 3.0% Built-in memory: 30436.7 MB Dedicated GPU memory used by Lightroom: 21.0MB / 1946.0MB (1%) Real memory available to Lightroom: 30436.7 MB Real memory used by Lightroom: 5924.3 MB (19.4%) Virtual memory used by Lightroom: 6617.7 MB GDI objects count: 944 USER objects count: 2713 Process handles

Am I missing a way to splice together sections of two DNG files and then run Lightroom Noise Reduction and Lightroom Presets on the combined DNG? I tried masking in open eyes from one DNG over blinking eyes in another DNG in Photoshop in 32 bit mode and saving to a TIFF file, but the TIFF file has already lost a lot of detail when opened again in Lightroom. Thanks!

So.   I have a laptop MacBook Air to edit my photos in Lightroom Classic. I have an external monitor from Benq model  BL2420PT so I can see the photos in more datails while I.m editing. I edit the photos, I export them in sRGB to my samsung S22 Ultra smartphone and it looks like desaturated. Am I doing something wrong? How should I color mach on each devices to have the same look? What color profiles on devices should I use so the final images will look the same on every devices screen.   Regards.

Lightroom is only opening a copy with Lightroom adjustments in Photoshop and not giving me any options. I need Open Original in Photoshop. It's something I use a lot. How do I fix this? Thanks.  

Issue: Lightroom freezes and quits in a few minutes by itselfVersion: 13.2.0.202308091502_65b8636 and all versions 13.x and 12.xWindows 11 22631.3593 step 1: Open Lightroomstep 2: Do nothing for a minute or two or select an image in the Library Expected result: browse in images in Library or edit the images in developping mode Actual result: Lightroom Classic freezes. Adobe Crash report takes a high run on scanning SSD and reports EXCEPTION_IN_PAGE_ERROR', '0xc0000006' '0x00007FFE2203AC72'. Start in V12 gives the same result. Also after disabling GPU.

Ich habe auf einen Mac Studio M2 mit Sonoma V14.5 von einem IMac umgestellt. Jetzt gibt es diverse Probleme mit dem Ligthroom V13.2. - LrC  bleibt hängen- Bilder laden dauert sehr lange wenn überhaupt.- Metadatei kann nicht geschrieben werdenDie Bilder sind auf eine externer NAS drobo Box mit USB2 Anschluss. hat jemand eine Idee? 

The Camera Calibration Panel in the Develop Module is missing. My Lightroom CC is up to date. I have been using Lightroom for about ten years and have never seen this panel. I wouldn't know it's supposed to be there if I hadn't just read an article about it. I'm a Mac user. Does anyone know why this panel is missing and what I can do to get it?

I have been using LR Classic for several years.  I back up catalot on a regular basis.  I bought a new laptop this week that runs Windows 11.  I have never had to restore a catalog before, so this is all new to me.  It seemed relatively simple.However,  for some reason I keep getting an error message : "Lightroom cannot use the catalog named "XXXXX" because it is not writable and cannot be opened." I have searched for answers and can't find an answer that works.  I have unchecked the "read only" box on all the files, but it keeps going back to "read only."  This sounds like a permission thing, but I don't know where to look to change that. Can someone help??

Bonjour, J'ai un problème quand j'enregistre dans Lightroom mes photos dans une collection simple (depuis la collection rapide), l'ordre des photos est différent (il ne respecte pas l'ordre des photos que j'ai choisi mais applique un ordre chronologique). Le problème est assez récent. Je suis sous Mac OS Sonoma 14-4-1. Une idée pour résoudre ce problème ?