Questions

I am making a photobook using double-sided panoramic paper, and need to leave a blank page- whats the best /easiest way to achieve this? Each sheet will be folded and the whole case-bound.

No sure why I was unable to report a bug, and so I have to create this post. I have beent trying to import H.264 video and it consistently fails - tried with latest 15.6 and also 15.4.1 and 15.3.1 (just in case). The details are as follows… H.264 video import consistently fails with Dynamic Link server error on Apple Silicon MacSummaryLightroom Classic 15.6 on an Apple Silicon Mac cannot import H.264/AVC video.The import causes dynamiclinkmediaserver to consume approximately 100% CPU. After approximately one minute, Lightroom reports:An unknown error has occurred while reading the video file. Connecting to Dynamic Link server failed. (1)The same H.264 file can be successfully processed by Apple's avconvert, demonstrating that the file itself is readable by the macOS media framework.A Dynamic Link process sample captured during the failure shows the server spending its time in Adobe's mc_dec_avc AVC/H.264 decoder path.System informationLightroom Classic: 15.6 [202609251514-f839cde9]Lice

I recently come across the following Issue:   I have a bunch of jpg files I have post-processed in Photoshop that I want to add geo locations to using the Lightroom Classic map module. After adding the locations I mark all images and do right click - metadata - save metadata to file. For some jpg files the data is written into the jpg file (desired behavior and how I know it from LR Classic for the past 6 years), while for others LR creates a seperate xml file (same location same name as the jpg) containing all metadata including the location.   Since this is a recent thing for me I suspected LR 14 to be the issue so I downgraded back to 13 but the issue persists. I already cleared out my complete LR catalog and only importet a hand full of jpg files to test but the issues persists. The issue can be reproduced, it is always the same jpgs causing the issue. When I open one of the not functioning jpg files in Photoshop and save it again in a new location the issue persists. Whe

SystemLightroom Classic 15.5.1 macOS 26.6.2 (build 25G83) MacBook Air, Apple M4, 24 GB memory Apple M4 GPU, 10 cores; Metal supportedSteps to reproduceMerge source images using Lightroom Classic’s Photo Merge → Panorama. Open the resulting DNG, approximately 13,000 × 4,000 pixels, in Develop. Create a mask using Select Sky. Enable the overlay and try changing the mask’s adjustment sliders.Actual resultSelect Sky appears to run, but no mask overlay is visible and adjustments have no effect.Expected resultSelect Sky creates an editable mask covering the sky.Comparative testsLinear-gradient masks work correctly on the same merged DNG. Select Sky works on the individual source images. Select Sky works in Lightroom Classic on a full-resolution TIFF version of the panorama. Photoshop’s Select Sky also succeeds on the panorama.These results suggest an issue with Select Sky processing this merged DNG, rather than a general masking failure or image dimensions alone.WorkaroundExport the merged p

Title: Lightroom Classic 15.6 – Photoshop 27.11 interoperability warning when editing any photoSince updating Photoshop to version 27.11, Lightroom Classic 15.6 displays the following warning whenever I try to edit a photo in Photoshop:“Lightroom Classic has detected interoperability issues with Adobe Photoshop 2026, limiting advanced functionalities. Reinstalling Adobe Photoshop 2026 is recommended.”This happens with every photo I have tested, including recent and older images, both RAW files with and without AI Denoise applied.My Camera Raw version is 18.7. I have tried quitting and restarting both applications and launching Photoshop directly before reopening Lightroom Classic, but the issue persists.This problem appeared after the recent Photoshop update. Could Adobe please investigate and clarify whether this is a known compatibility issue with these versions?

Lightroom Classic sur Mac reste bloqué sur “Synchronisation de 420 photos” avec le message “Problème de synchronisation”. Aucune collection n'est synchronisée et l'état de synchronisation sur le Web indique 0 photo. J'ai déjà supprimé Managed Catalog.mcat et Managed Catalog.wfindex ainsi que leurs fichiers auxiliaires, puis relancé Lightroom Classic, mais le problème persiste.Quelqu’un peut il m’aider ?

 When my long-established Lightroom Classic catalogue (~183,000 images) is opened with the drive containing the original photographs online, Lightroom automatically begins a large background image-analysis/culling operation. I am not deliberately starting Assisted Culling.During this operation Lightroom systematically reads original image files and its committed/private memory grows continuously. I have observed Lightroom reach approximately 148 GB Private Bytes, at which point Windows becomes extremely difficult to use.If the originals drive is disconnected, the same catalogue remains stable at approximately 2 GB PB.Clean Lightroom catalogues using photographs from the same physical drive and same original files behave normally: processing completes and memory stabilises. The problem reproduces in Lightroom Classic 15.4.1 and 15.5.1, and also with GPU acceleration disabled.SystemWindows 10 Pro 22H2Intel Core i9-1090064 GB RAMNVIDIA RTX 2060 6 GBCatalogue/previews on dedicated SSDOrigi

I am using Lightroom Classic 15.5.1 on an iMac. I have approximately 40,228 photographs already successfully synced over then years.I created a new synced collection containing 803 JPEG photographs. Syncing stopped with 364 photographs remaining and stayed there indefinitely.Lightroom Sync Activity shows the first affected photographs as “Uploading — [file path] — Image.”View Sync Status on Web reports no sync problems, and there is no “All Sync Errors” collection in Lightroom Classic.I tried removing individual photographs at the head of the stuck queue. This allowed syncing to progress temporarily from 364 to 362 and subsequently to 356, but it then stopped again on another photograph. A newly created synced collection also remains queued behind these photographs.I have generated the Lightroom Classic Sync Diagnostic Report.I have not used Rebuild Sync Data or reset the cloud library.Anyone out there having this problem?

I use Windows 11

When you paste only a few settings it changes the other values to 0 (default) really messed up my work flow and now cannot paste single setting when I have already edited the photo  

LrC is not working with its existing catalogue….. keeps saying corrupt, it makes copies, I delete.lock files and nothing changes…...im really sick of praying that LrC will work, its been like this for two days this week with tons of glitches and I can't access anything…. my clients are not happy!PLEASE HELP X

When I try to start lightroom classic I get the error message ?:0: attempt to index field'_nglController'  I cannot get it to start in any other way. Greg Hoglund 

Ok, so this is a small issue but it annoys me; Using the remove tool, I remove something and press “Enter” on my keyboard. The tool deselects and I can move on to the next photo in the queue. When I remove something with the Generative AI Removal tool, I remove something and press “Enter” on my keyboard...but nothing happens UNTIL I click the cursor in the empty border area surrounding a photo. Then, and only then, the removal tool becomes deselected after pressing “Enter”. This is especially aggravating when working on horizontally oriented photos where empty border area is extremely limited in size. I hope that was clear. Let me know if not, and I’ll do my best to explain more thoroughly.

I have catalog A with keywords and associated keyword tag options (ex. Export Containing Keywords) and export them as a .csv file using Metadata>Export keywords>Include keyword tag options  and then import that same file into catalog B with no keywords currently defined using Metadata>Import, will the keywords and associated keyword tag options get imported correctly to match catalog B?If catalog B has some keywords that don’t match any of the keywords from catalog A - same answer?If catalog B has some keywords that do match any any of the keywords from catalog A  - I belive the keyword tag options will not get updated, correct? Thanks. P.S. I may now regret having multiple catalogs if I have to update each keyword tag option in each one moving forward. 😁 

My lightroom classic is suddenly EXCRUCIATINGLY slow. Everything is running slowly, but especially when trying to copy and paste settings (even if there are no AI adjustments being copied). I have been waiting 15 minutes on my current image and it's not even a quarter of the way done processing.  It was working fine last week. Then one day I logged in and this started happening. I have not uploaded any images or anything in the meantime, so I know it's not a system problem ( I have a fairly good setup). This is causing me huge delays in my workflow and I've had to contact clients to extend their wait time for their galleries. 

Please add the “manual” remove setting to the camera presets you can save for specific cameras. like the sample below. No, in-camera pixel mapping does not fix this issue.  I have a couple of cameras with several of these black spots due to a sensor defect that I could just fix by using the remove tool (without generative AI) when importing.For some reason it is the only feature you have not added from the copy/parte settings to the camera presets settings. Just adding this feature would cut my workflow considerably since I would not have to hunt for those spots anymore.Thanks!D.  

I have a Classic catalog of 43,000+ photos (version 15.6 on Windows 11) that has been syncing with Lightroom online however something has gone astray recently and I get Sync Error showing maybe after a handful of photos have loaded. I think it’s overloaded and clogged and ticking Sync Keywords a few days ago probably did not help.Sync Activity always shows the same approx 70 photos, all marked “Uploading”. Online there is no folder for Sync errors (or similar). I have unticked sync on all my collections and selected Rebuild Sync Data. I am told to that it’s recommended to Generate Diagnostics Report and contact customer care.Trying here to load that diagnostics report I get “Sorry, we couldn’t upload your file because it's too big. Maximum file size: 50 MB”. It’s 321MB…Advice on how to proceed appreciated!Thanks, Scott

Currently, selecting Custom Name in the Rename Photo dialog does not display the filename of the selected photo.Instead, Lightroom Classic reuses the last custom name entered, even when a different photo is selected.This behavior is confusing for users performing single-photo renaming because the command behaves more like a persistent naming preset than a traditional rename operation.For single-file renaming, the expected behavior would be to display the current filename of the selected photo in an editable text field, allowing quick modifications without retyping the entire name.Instead, when selecting Custom Name, Lightroom initially presents an empty field rather than the current filename.What makes this behavior particularly confusing is that Lightroom remembers and automatically reuses the last value entered in the Custom Name field, even when a completely different file is selected.For example, after renaming:IMG_20260920_123456.CR3to:IMG_20260920_123456.CR3_modselecting another

AI sky masks often must be feathered entirely within the sky, without bleeding into the background below.  With the current Feather/Edge sliders, Feather can go to 100, but Edge can only go to -50.  Therefore, the practical maximum is Feather 50 and Edge -50, so that the feather remains within the sky.  The Edge slider should go to -100, so that the full feather can be applied within the sky.

 "Custom Name" or "Edit": Please populate with current name. Allow direct editing. e.g. current name “Alaska_1034.nef”  “Show Alaska_1034.nef” and let me delete “Alaska_” or change it to “Yukon_”And: include button <Copy File to New Name [same folder]> which leaves old file with old name untouched

I’m trying to detect the background/subject while editing pictures, but I keep getting the message “no background detected. couldn’t find background to select” on all images. This is a recent issue that I’ve been having and can’t figure out why. I’ve updated my Mac and Photoshop software, reset my computer, and made sure my GPU settings were set to auto. How do I fix this?

Note the original Hierarchy is under “All Photos Digital, by year…. since the new MacOS it started putting them above and in some cases put them in 2026 under “pictures” which I removed because I don’t want them there - it’s like it moved them instead of added them.  I have always used add and now it’s not working correctly since I upgraded to the new OS. Also, you should know I have the photos stored in DropBox and so are the backups.  The catalog is in: What can I do to make the 2026 folders on top, be under the 2026 folder under All Photos Digital? Confusing?  Thanks, Lorinda 

I often work on a single image and then on export find I am exporting dozens - if the currently selected image could be made way more obvious on the film strip that would be day-to-day useful

Over the last few years, I set Lightroom cloud on my phone to automatically import my phone photos to the cloud. Basically as a first stage backup.I was trying to set up Lightroom cloud app on Windows to pull down the original files into a folder that I can then import into Lightroom Classic. So that I have them on MY hard drives and can back them up.That proved basically impossible, in some part because LR Classic was also downloading all the images. And they can’t be in the same sub folders as each other. Fair enough.So I am taking the step of importing the photos from my phone as properly imported images into LR Classic. Thats fine. But now I find that I cannot stop LR Classic from downloading ALL the images in the LR cloud (in my case 35GB) to somewhere on my machine. I do NOT need them downloaded. But I cannot STOP them being downloaded. And no I can’t just pause that sync for ever, because then the collections that I WANT to be synced up to Lightroom cloud won’t ever be synced up

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