Connect with fellow editors in our Lr Classic community.
Recently active
필름스트립에서 일정 이상 가운데를 벗어난 위치에 있는 사진을 선택 했을 때 멋대로 스크롤되어 가운데로 옮겨지면서 사진 선택을 상당히 힘들게 합니다.설정 옵션이 있다면 끄고 싶네요.
I have seen posts from as far back as 2011 asking this same question and it is astounding to me that LrC doesn’t have the ability to batch re-name files using string substitution. So it appears my options are: create a naming template that will overwrite the part of the filename that I want to keep, or rename them in Bridge the way I want and then re-import them into LrC. Anyone else have a way to accomplish a batch rename that allows for a simple find and replace?
*deleted*
non riesco a creare nuove raccolte o a rinominare una raccolta esistente
I recently transferred Mac’s. My light room pictures transfer but not my light room classes. None of the pictures or presets. I need those presets for my business. They should have been stored in your cloud but have not. Do better.
I cannot get my lightroom to open.I first noticed an issue when Lightroom Classic was not resuming at the previous pictures but returned to a picture edited some days ago, however in other respects everything seemed to be working. This may have started after the last update.It first failed to load after I had done a backup. I tried loading this backup and then a previous one but kept getting corupt catalogue message.I eventually got a backup from June 5th to load, though the catalouge had to be updated to the new format before appearing to open and operate correctly. However on closing the program it would not open again.Since then I have reset preferences and reinstalled lightroom from the adobe creative cloud app, all without any change.Today I launched the reinstalled Lightroom with a new empty catalogue and imported an old catalogue (over 500000 pictures). It took some hours but after it loaded photos and then loaded masks it did open and appeared to function correctly.However,
When the same HDR AVIF or HDR JPEG is viewed on macOS, Apple Photos, Quick Look and Flow Vision adapt the highlight rendering as display brightness changes, while Lightroom Classic and Camera Raw keep rendering highlights much more directly. Is Lightroom intentionally bypassing Apple's system HDR photo rendering (EDR/tone mapping), or is there a preference to use the macOS HDR rendering pipeline?
Description of IssueAfter Assist Culling (and Face Detection) analysis for a catalog reaches100% complete, quitting Lightroom Classic normally (File > Quit, not acrash/force-quit) and relaunching causes the "remaining photos toanalyze" counter to jump back up — i.e. photos that were alreadyanalyzed are treated as unanalyzed again. This is reproducible acrosstwo different machines (Windows and macOS) and multiple catalogs,including catalogs rebuilt from scratch via "Export as Catalog".Lightroom Classic Version Number (Help > System Info)Lightroom Classic version: 15.3.1 [202605261338-e36f8566]License: Creative CloudOS Version Number- Machine A (macOS): Mac OS 26, version 26.5.2 [25F84], arm64- Machine B (Windows): Windows (native, catalog originally migrated from Mac to this Windows machine)Camera ModelN/A (issue is not camera/file-specific; reproduced on catalogs with56,000+ mixed JPEG/RAW files)Step-by-step Reproduction Instructions1. Open a catalog where Assist Culling / Face
Hi, I’m using macOS 12.7.6 (Monterey) and the latest Lightroom Classic isn’t supported on my system.I have an active Adobe account and I’m also a student.Could you please help me access or provide a download link for Lightroom Classic 11, which is compatible with Monterey?Thank you very much!
Metadata fields provide an opportunity to liberate us from the difficulties of using the file system (filenames and directories) for sorting and searching. The Lightroom sort options should take advantage of this. I would particularly like to sort on the Title and Caption fields, and to use multiple sort criteria, as in Sort by Title and then by Capture Time.
Hoping someone can help! I have used Lightroom for 7+ years and this has never happened until yesterday… After I imported a session into Lightroom, I realized all the photos are extremely overexposed from how I shot them. When I open the RAW file outside of Lightroom, it is exposed the way I shot it (Pictures for reference). I shot these with the same Camera I’ve used for years (6D Mark ii) and use Lightroom all the time and have never had this happen to me until yesterday. I have googled, YouTubed, and attempted everything I could find, but nothing has fixed it. So I’m hoping someone here can help!! Also for reference I have tried rolling back to an older version of Lightroom… I have tried purging my cache… I have made sure I don’t have a preset turned on when importing… I have looked under preferences at camera defaults… Desperately trying to finish sessions, so all help and suggestions are appreciated!
I was using Lightroom Classic, hovered over the Adaptive:Sky drop down menu and it crashed.When I re opened it had reset itself to Default, every menu had to be reopened and it will not allow me to save an image as a jpg, I only get jpeg2000 and jpeg XL in the menu, I do not have any unflattened layers.
I store all of my images in a LR catalog. That’s how I was taught to do it. I can access certain years of photos based on my hard drives, labeled LR1, LR2 and so on. My first catalog is from 2010. However, when LR says it cannot open my catalog unless I update I have been doing so. Now, when I go to open catalogs on older hard drives, I can’t! Please help. I just need access to my photos. TIA!
Hi I have recently migrated my catalogue from a very old version of lightroom to the most recent but even though the program knows where the files are located it is not showing any previews of my images, just greyed out boxes. I have tried deleting the preview files held but that hasn’t worked. I have also tried changing the colour space but that hasn’t worked either. Please help! Lightroom Classic version: 15.4.1 [ 202606201310-b9f148a4 ]License: Creative CloudLanguage setting: en-GBOperating system: Mac OS 26Version: 26.5.2 [25F84]Application architecture: arm64Logical processor count: 14Processor speed: NASqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.213Built-in memory: 49,152.0 MBDedicated GPU memory used by Lightroom: 60.3MB / 38,338.5MB (0%)Real memory available to Lightroom: 49,152.0 MBReal memory used by Lightroom: 979.3 MB (1.9%)Virtual memory used by Lightroom: 427,402.0 MBMemory cache size: 0.0MBInternal Camera Raw version: 18.4 [ 2608 ]Maximum thread count used by Camera
Bonjour après avoir été dans Préférences/Lightroom synchronisation/supprimer les données synchronisées/Lr web puis supprimer la bibiliothèque Lightroom, impossible de supprimer la bibliothèque. Après avoir recopié la phase, "supprimer" reste en grisé. Une idée du problème?
Lightroom Classic should allow a virtual copy to be assigned to a different folder from the original photo.For example, one group photograph may belong in several separate folders. It should be possible to create virtual copies and place each virtual copy into the relevant folder, while all copies continue to reference the same original file.At present, virtual copies remain tied to the original photo’s folder, which makes this kind of organisation unnecessarily difficult. Collections are not a substitute when the workflow specifically requires folder-based organisation.This would allow one photo to appear in multiple folders without duplicating the original file.
Add High level logging, with timestamps, to a text file to record key events such as -Launched LrC version xxxLog core elements from System InfoOpening Catalog X:\parh\name.lrdataDetecting GPU, Initialising GPU, GPU Driver version, GPU settingsMajor catalog activities - compressing, checking, Edit in application (log the app, the filename)Import/Sync summaryALL failures and warningsUser launching/pausing backgroud tasksUser switching between modes (Library, Develop, Map etc)If possible - Last activity before application becomes unresponsive.Memory limitationsI am sure there are many more.I appreciate it is difficult to find a balance between too much and too little.Maybe record the number of times that certain faults re-occur.If possible, use this count to increase logging levels of certain components so that future logs can concentrate on the issue.And then :Rolling logs, so keep the last N logs, or last X days of logs.Tool to view any log.Cut-n-paste to sent to AI tool to review. or
Lightroom Classic 11.2 on MacOS Catalina 10.15.7. In the batch file renaming feature accessed through the hamburger icon to the right of the File Name field in the Library module, I often need to search and replace particular text. I don't see a way to, for example, replace "Jan1969-" with "1969-01-", which I wanted to do this week because I had improved my file naming system and wanted to update my old files' names. Even better would be to support entering an arbitrarily long list of replacements to make in one pass, with a "+" or "Add" button to add more "From" and "To", or "Old" and "New", boxes. For example, Old: Jan1969 New: 1969-01 Old: Feb1969 New: 1969-02 Old: Mar1969 New: 1969-03 A further enhancement to that feature would be to give either the whole list or each entry a pulldown like in the Library module Text Filter, specifying Contains, Starts With, or Ends With. I could actually benefit from a full-blown regular expression matcher,
I upgraded to 15.4.1 about 10 days ago and have been experiencing LRC crashes ever since. It’s mostly OK in the Library Mode but if I go into Develop, it usually crashes after a few minutes. If I also have Chrome open, it sometimes freezes as well and gives me a ‘low memory’ reason.I run LRC on an LG Gram 16” laptop which uses an Intel Iris Xe Graphics card with 128 MB of dedicated video memory and 8 GB of shared system memory. I suspect those numbers may be low to support LRC, but none of this happened before upgrading to 15.4.1. LRC ran quite well before the upgrade.Any ideas on how to fix this before I reluctantly buy a new laptop?
I have encountered an instance where a wide gamut orange colour appears desaturated in HDR editing mode. I have the uploaded output PQ HDR AVIF files to https://andrewkeyanzhe.github.io/posts/Lightroom_vs_darktable/ for comparison. My website serves the uncompressed HDR AVIF files, so you should be able to see the difference on an HDR capable device and browser (e.g. Macbook Pro with XDR display with Google Chrome) The camera used is the Panasonic Lumix S5ii Details: Version of the app - Lightroom 14.2 (Camera Raw 17.2), Lightroom mobile v. 10.3.1 71F6C8/202 Platform and OS version - Macbook Pro 16 M1 Pro, macOS Sequoia, iPhone 14 Pro Max, iOS 17.5.1 Basic steps to reproduce the problem - Download the raw file https://drive.google.com/drive/u/0/folders/1YIhkxHvp77HHTaanyFJ5LXX28jH74Rau , open in Lightroom, turn on HDR editing mode, increase the exposure by 3.4 stops so it matches https://youtu.be/0FYjApop7Mk?si=S-cXCX-0hyAvsT
It would be great if there was a way to search/filter images for those that need their AI edit status updated? I, often, use Adaptive Color, then, of selective images, decide I need AI Denoise. Sometimes I forget to update the AI. When dealing with a lot of images, it is difficult to go back and check that all the updates have been done.
After the updated 15.4 my images have degraded quality using the same editing workflow and editing process as before. When boosting the exposure the noise profile has changed to a more pixelated versions and artificial look. After applying Denoise AI the shadows and mid tones have a posterisation look, especially around high contrast edges, that did not appear before 15.4No matter what amount of Denoise AI level I put the image quality looks horrible, where before using 50-100 looked great now it looks very bad and I can’t use more then 5-15 and have to accept noise in the images.I have tried the same files on a Windows 11 with i7 9750H,16GB DDR4 and RTX 2060 6GB and Mac mini M1 base model with 16GB RAM with the same issue being presented. Both machines are OS and Drivers updated to Jul 2026. This problem has persisted for almost 3 weeks since the Lightroom Classic 15.4 and 15.4.1 was introduced. Both software have been installed via Adobe Creative Cloud with updated Adobe Camera RAW t
Individual photos in develop have an indicator whether the AI needs to be updated. There is an option to batch update photos to batch AI update required. The batch does not allow to review individual results of the AI update in case unwanted changes have occurred. I would like to suggest adding a Filter attribute for 'AI Update Required' that would allow a manual selection of those photos needing the update. This would allow makers to individually walk through the selection to apply the 'AI Update' and review the results.
I have been working an an Imac 5K for 8 years and since the introduction of the face recognition mask in Lightroom classic, it has worked flawlessly even finding and masking people and faces which were pretty small in a picture.However, I very recently switched to a MAC Ultra M1 and did a clean install of all my adobe suite apps (No Migration but proper installation). Since installation, Lightroom classic is working lightning fast with very fluid navigation, ultra fast process of images, noise etc... BUT, unfortunately, most of the times, Lightroom does not find people, even on portrait where people are looking at the camera with a open and clean face.The only time it works i would say, it's when the faces are about a quarter of the size of the photo. If faces are smaller like in a full body group photo, Lightroom does not find faces.Why is that? Is there a fix to that? Is it. bug or is it due to the M1 ultra chip or GPU?Thanks for anyone's help.
Please update Lightroom Classic to include “Head Detection”While I appreciate the ability to select individual aspects of a person face and body to edit, it would save me a tremendous amount of time if Lightroom was able to detect just a persons head and all facial features found within. Often I do not wish to edit a person’s entire body as their attire does not require adjustments. It takes too much time selecting all of the facial features in the selection panel. The other workaround is to select an entire person and then removing the mask for a person’s clothes and body skin afterward. Which again, takes up time when doing this hundreds of times for a particular gallery or event. It would increase my productivity tremendously by having a face and/or head option that limits the mask to a person’s head and/or face.Also appreciated if there was an option where I did not have to manually remove the background after creating a mask for a person. If I do not remove the background fr
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.