Questions
Recently active
After installing LR Classic the app is now so slow that it is unusable. Windows 11, strong PC.
Ich habe LR mit LRc gekauft und wie erhalte ich die Oberfläche von LRc auf meinem Desktop?
# Environment- Mac: MacBook Pro 14" 2026, M5 Pro (18-core) (identifier: Mac17,9)- RAM: 64 GB- macOS: 26.5.1 (build 25F80)- Lightroom Classic: 15.4.1 (latest)- Power: AC connected, High Power Mode enabled (powermode 2)- Catalog: freshly created; source files and export destination both on internal SSD- Previous machine for comparison: MacBook Pro (M1 Pro) # SymptomDuring export, total CPU utilization plateaus around 50% and exports are much slowerthan expected. Using powermetrics, I confirmed that while exporting, the P-cores(P0 cluster) are ~100% active but locked at roughly 2.4 GHz (2304-2652 MHz),never boosting above 3 GHz. The P1 cluster stays mostly idle.Measured comparison against M1 Pro (same photos, same export settings):- Export: 92 s on M1 Pro -> 70 s on M5 Pro (only ~24% faster)- AI Denoise: 9.5 s on M1 Pro -> 4.5 s on M5 Pro (~2.1x faster)GPU/Neural Engine-bound tasks like Denoise scale as expected with the new chip,while the CPU-bound export barely improves. Also, on
when going to camera profile only the acros film options are shown. the raw files are from a fuji x100VI
Summary: Lightroom Classic throws a generic "unknown error" when importing HEVC video files tagged as hvc1, which is the default output format for DJI cameras (tested with DJI Osmo Action 6). The same file remuxed to use the hev1 codec tag imports without issues. No re-encoding is performed — the video bitstream is identical.Steps to reproduce:Record video on a DJI Osmo Action 6 (or likely any DJI camera outputting HEVC). Or use attached input file. Attempt to import the resulting .MP4 file into Lightroom Classic via File → Import LrC throws "unknown error" and fails to importWorkaround: Remux the file using ffmpeg with no quality loss:ffmpeg -i input.mp4 -c copy -tag:v hev1 -map 0:v:0 -map 0:a:0 output.mp4The resulting file (attached) imports correctly.File properties (ffprobe):Codec: HEVC / H.265 Profile: Main 10 Resolution: 3840×2160 Codec tag (original, failing): hvc1 Codec tag (remuxed, working): hev1 Color: yuv420p10le, bt709Expected behavior: Both hvc1 and hev1 are valid, spec-c
I just updated both Lightroom Classic and Photoshop today. I selected two images in Lightroom Classic. I went to edit them as a stacked layer in photoshop. Instead I get this error message in photoshop, "load layers need at least two files selected.” Device name OriginLaptopProcessor 11th Gen Intel(R) Core(TM) i7-11700K @ 3.60GHz (3.60 GHz)Installed RAM 64.0 GB (63.9 GB usable)Graphics card NVIDIA GeForce RTX 3060 Laptop GPU (6 GB)Storage 852 GB of 2.73 TB usedDevice ID 66FE5495-1690-41A9-A517-02EF8DBEBC18Product ID 00330-80000-00000-AA768System type 64-bit operating system, x64-based processorPen and touch Pen supportEdition Windows 11 ProVersion 25H2Installed on 7/21/2025OS build 26200.9974Experience Windows Feature Experience Pack 1000.26100.385.0
In Lightroom Classic 16.0, the Loupe Info overlay text (top-left, over the photo) now has a heavier drop shadow that makes it hard to read, especially over white/bright areas of the photo — white letters plus a soft gray shadow on white is nearly unreadable. Affects: Loupe view in Library and Develop.Does not affect: Grid view (text sits on the gray interface there, no shadow).The shadow is a single, clean, consistent offset behind every letter — not smeared or doubled — so it does not look like a GPU rendering glitch.There is no setting I can find to change the overlay font, color, or shadow; View Options only controls when it shows.Workaround for now: View > View Options > Show Briefly When Photo Changes (set separately in Library and Develop), or press I to cycle it off. System: Lightroom Classic 16.0, Mac Mini M5 Pro, macOS. Is anyone else seeing this in 16.0, and is the heavier shadow intentional?
Come procedere in sicurezza per trasferire il mio Catalogo principale da un Hard Disak ad un altro Hard Disk?
JPEG XL files with the ProPhoro RGB color space exported from Lightroom contain color compression artifacts. They appear in quality 100% and lower. Other color spaces do not have this problem. Lightroom version 13.3.1 Windows 11 23H2 version 22631.3593
This thread is for Camera Raw & Lightroom Classic feedback on the (Early Access) Content Authenticity Initiative (CAI)For the Lightroom Ecosystem feedback, click here. The Lightroom team is dedicated to building capabilities that foster trust and transparency in the age of AI. Our latest release, as part of the Content Authenticity Initiative (https://contentauthenticity.org/), allows you to add content credentials to your work when exporting in Lightroom to ensure provenance and preserve authenticity. New content credential capabilities are available across the Lightroom ecosystem (Lightroom, Lightroom Classic, Lightroom for mobile (iOS & Android), Lightroom for web), and Adobe Camera Raw in Early Access. When exporting a JPEG from Lightroom, you can attach your name, social media handle, and a list of edits via a digital signature. You can find the option to apply Content Credentials while exporting a JPEG in the export panel. It is, by default, turned OFF
I am experiencing a reproducible and severe performance/unresponsiveness issue in Lightroom Classic 15.6 on Apple Silicon.Environment:- Lightroom Classic 15.6- Apple Silicon Mac- M2 Max- 64 GB unified memory- Lightroom Classic running natively as ARM64- Large Lightroom catalogProblem:Lightroom Classic becomes severely unresponsive when Cloud Sync is running at the same time as a large number of Develop Copy/Paste operations.The issue is highly reproducible.Reproduction steps:1. Open Lightroom Classic.2. Start syncing approximately 450 photos to Lightroom Cloud.3. While the sync is running, perform a large number of Develop Copy/Paste operations on photos in the catalog.4. Continue performing these operations while Cloud Sync is active.5. Lightroom Classic CPU usage increases dramatically, reaching several hundred percent and, in the latest reproduction, exceeding 1000%.6. At the same time, Lightroom Classic becomes extremely sluggish and stops responding normally to user input.7. Opera
Subject: Lightroom Classic 16.0 – Severe HDR/Panorama merge slowdown on MacBook Pro M5, resolved by disabling GPU accelerationHello,I would like to report a significant performance issue with Lightroom Classic 16.0 on a MacBook Pro with an Apple M5 chip and 24 GB of unified memory.System configuration: MacBook Pro, Apple M5, 24 GB unified memory Lightroom Classic 16.0 macOS: Tahoe 26.6.2 RAW files: 45 MP Nikon NEF files, stored on a fast external SSD Camera Raw cache: 30 GB, located on the internal SSD Issue:Since upgrading from Lightroom Classic 15.x to 16.0, I have experienced severe performance degradation when performing HDR merges (typically 5 RAW files) and HDR panorama merges (15–25 RAW files of 45 MP each).Performance becomes progressively worse after processing several images or merges, sometimes resulting in extremely long processing times or apparent freezes.Memory usage reaches approximately 19–20 GB out of 24 GB, but macOS memory pressure generally remains green, o
I have noticed a reproducible issue with the new Vectorscope in Lightroom Classic 16.When I right-click on the left side of the Vectorscope, the context menu opens normally and remains visible, allowing me to select its options.However, when I right-click on the right side of the Vectorscope, the context menu briefly appears and immediately disappears, making it impossible to interact with.Steps to reproduce: Open Lightroom Classic 16 and switch to the Develop module. Display the Vectorscope in the right-hand panel. Right-click on the left side of the Vectorscope: the context menu works normally. Right-click on the right side of the Vectorscope: the menu appears and immediately closes. Expected behavior:The context menu should remain open and usable regardless of where the user right-clicks within the Vectorscope.Actual behavior:The context menu immediately disappears when opened from the right side of the Vectorscope.Environment: Application: Adobe Lightroom Classic 16 Operati
Windows v16.0, all drivers, etc. are up to date.Hard to describe with a single line but the following steps will reproduce it.With a range of images selected turn on an attribute such as the pick flag or a colour.Now enable a filter that shows only those imagesSelect one image and go into DevelopChoose any mode apart from Edit, eg, Crop, Remove, etc.Remove the chosen attribute from the selected image so it’s no longer part of the filtered selection, this forces the image to be deselected and the next one selected instead.The Develop editing mode reverts to the default set closing Crop, Remove, etc.In earlier versions the forced change of selection did not change the editing mode.Note that simply changing images does force close the Crop, Remove, etc., it only happens when the filtering requires a change in active image.
I just updated Lightroom classic to v16.0 I can no longer edit a photo in an external editor, ON1 Photo RAW 2024, error message: Lightroom was unable to prepare the selected file at S:\Photos downloaded here\Canon\2026_11_10\5D_45606.CR2 for editing. It will not be opened. **** It does work in opening in photoshop. In the upper left corner it stopped at Preparing file for editing with progression bar at end next to x.Hundred of gigs of free space on the Solid State drive. Windows 11 Home, Alienware Laptop fully loaded, fast, powerful, latest updates all around. Bug in the new version?
This behavior is systematic and reproducible. I have been experiencing it for at least two Lightroom Classic versions, including the current version 16.0.Lightroom Classic VersionLightroom Classic 16.0Build: 202611041403-7ac14c66Operating SystemmacOS Golden Gate 27.2.1Camera ModelNikon Z6IIFile FormatDNG converted from Nikon Z6II NEF files using Lightroom Classic's "Copy as DNG" import option.Steps to Reproduce Select at least one DNG file (a single file is sufficient to reproduce the issue) whose metadata status is "Up to Date". The DNG file has no develop adjustments applied (if any, the behavior is the same anyway) Create a new, empty collection. Add the DNG file to the collection. Enable synchronization for the collection. Wait until Lightroom Classic indicates that cloud synchronization is complete (green checkmark). Check the DNG file's metadata status. Notice that the status has changed to "Changed", with a downward-pointing arrow indicating that the metadata is out
My Macbook died while culling a gallery. Now all my collections (and images) are gone, I checked and its the only catalog I have on my computer. The most recent back-up I have is months old and isn't any help in this case. I am able to import photos and I checked to make sure the catalog was corrupted. Does any one have any suggestions? I recently culled some galleries and have a finished gallery that I had exported yet (hours and hours worth of work) that I would rather not have to re-do.
Hi everyone,First, ChatGPT helped writing this post since i have been talking with it about this question yesterday the whole day. now the question below:I'm having a really weird problem with Lightroom Classic and I'm running out of things to try.When I switch Lightroom Classic to Chinese, most of the UI becomes garbled/unreadable. The really strange part is that the top menu bar displays Chinese normally, while most of the rest of the Lightroom interface is messed up.Even stranger: Photoshop on the same PC displays Chinese perfectly.So I'm starting to think this might be something specific to Lightroom's UI/text rendering rather than a general Windows Chinese-font problem.SystemWindows 11 Build: 10.0.26200.8875 Lightroom Classic 15.5 Windows display language: English (United States) Display scaling: 150% Lightroom scaling: Auto Chinese fonts: Microsoft YaHei installedThings I've already triedI've gone pretty far down the troubleshooting rabbit hole:Uninstalled and reinstalled Lightr
I decided today to delete some of my old Lightroom backups, to make space on my drive. I deleted them all except for the two most recent backups.When I then tried to open Lightroom, I got a screen saying that it could not find the catalog. Looking in the default catalog location (C:/user/pictures etc, there is an .lrcat file dated today, but it is only a couple of megabytes, and just opens an empty catalog.How can I find the missing catalog?Thanks Peter Windows 11 pc, Lightroom 16.
When trying to apply one of my presets (which includes some masking) to about 50 images, LR stalled after about 10 images. It didn’t show an error, but did not advance to next image for over 5 minutes. I had to quit the program, then force quit the program from running in the background. After reopening LR, the 10 images were correctly done, but not the rests. I did them in batches of about 10 moving forward without incident. Prior versions, I would do this same thing often to batches in the 100’s without issue. I then exported the images and LR made the directory, but just sat there and did nothing. No exports, the progress bar didn’t move, nothing else happened. I had to restart LR again (again killing the Running in Background process) this time it exported the images, in literal seconds. Mac Version, latest OS. Mac Studio with 64gigs of RAM.
@Anshul_Saini I am still experiencing this on 15.6.I have Assisted Culling enabled on my library, there are ~120k images left to process. Memory is not being released, and Lightroom will keep eating it until it crashes. There is no reason why it would need in excess of 20GB to process a queue.
Lightroom redémarre automatiquement après la fermeture. Ce problème ne se produit que sur la tour, pas sur le portable. Le problème est le même, avec ou sans sauvegarde. J'ai fermé manuellement le module Excire Search avant la fermeture de LR, il n'y a pas de changement.
Need Advice: Upgrading from 1050 Ti 4GB for Lightroom AI (45MP RAWs) on a budgetHi everyone,I’m looking for some real-world feedback from Lightroom Classic users regarding a much-needed GPU upgrade.My Current Setup & Workflow:System: Windows 11, X370 chipset motherboard, 4K display. Current GPU: 1050 Ti 4GB (Experiencing severe slowdowns on modern AI tasks, creating a massive editing backlog). Files: 45-megapixel High Efficiency RAW files. Workflow: Heavy batch processing, lots of AI Denoise, and frequent local AI masking. I also do some lightweight video editing for travel vlogs using mobile footage, but photography is the priority.The Dilemma: I am on a budget, so price-to-performance is critical. I've been looking at the latest generation of GPUs to take advantage of faster AI processing, but I am torn between VRAM capacity and cost. I want to keep my options open, but I am generally weighing two paths:Option A: A modern 8GB GPU (e.g., 4060 8GB class) - This fits my budget perfe
I did some photo editing in Lightroom classic (15.6 version with Camera raw 18.7).It was a difficult shoot in very dark conditions but I managed to salvage a few photos.I edited in the develop module so this photo was acceptable but when exported, the photo had horrible “blotches” that were not visible in the develop module… I opened the file in the Library module and the same problem is shown on the same RAW file but not in the Develop Module?! I have tried to do a screen record to show what I mean.Here are also two static screenshots - however the difference is actually more noticeable than it appears on these.Even if I EXPORT the image as a jpeg file directly from the develop module, it saves it quite differently to the edits I have saved… How are the edits I am making in the develop module not showing the same when viewing in the Library or exporting?
Description of IssueI have noticed inconsistent behavior in how Adobe Lightroom Classic and Adobe Content Authenticity handle creator identity verification.My identity has already been verified through LinkedIn and is correctly recognized by Adobe Content Authenticity.However, when I export a JPEG from Lightroom Classic with Content Credentials enabled, my name appears as "Not verified" when the file is inspected.To demonstrate this inconsistency, I have attached three screenshots: Test 1, Test 2A, and Test 2B.System Information Application: Adobe Lightroom Classic 16.0 Build: 202611041403-7ac14c66 Operating System: macOS Golden Gate 27.2.1 Camera: Nikon Z6II Original File Format: DNG converted from Nikon NEF using Lightroom Classic's "Copy as DNG" import option. Test 1 – Content Credentials Exported from Lightroom ClassicI exported a JPEG from Lightroom Classic using the following settings: Content Credentials enabled. Storage method: Attach to Files. Creator name include
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.