Connect with fellow editors in our Lr Classic community.
Recently active
LRC update to 14.0.1 this morning and since hasn't been usable. It did complete its catalog update, however while using it the CPU is constantly busy and the RAM usage keeps climbing. I've tried restarting my computer as well and still it just climbs and runs slowly. I had it build standard previews (took hours - much longer than expected) hoping it would speed up after those were in place.However, even after a reboot, if I open lightroom to a folder that has all previews already built with the latest version the issues persists.It starts at about 1.2GB of RAM. Over the next several minutes of just sitting there doing nothing, it rises at about 100MB / Sec until it uses all the RAM on my computer.Those no tasks shown as running - address lookup and face detection are paused. Lightroom Classic version: 14.0.1 [ 202410161356-30922cfc ]License: Creative CloudLanguage setting: enOperating system: Windows 10 - Business EditionVersion: 10.0.19045Application archi
Looking for some help. I am having a major Lightroom issue in LCR. I can move around from module to module but I not able to edit in the develop and I have lost the ability export and my backup in running in what appears to be a endless loop same for optomization. I was running verion 14.01 now I went back 14..0 it made not difference any.Followup contiuing to have Lightroom unresponcivemenss issues. I have isolated the problem to just lightroom. I wondering the catalog could be corupt. I have moved from 14.01 to 14.0 and now back 13.5 and Im considering a complete uninstall but worry about what I might lose thoughts? the Catolog updates would not allow going back the 13.5Syptoms:cannot back up goes to endless loopCannot use any functions in the deveplop modCannot export or publuishCannot create or remove synced folder flags.Optomizing Catolog endless loopWhile the Catolog seems to be intact Lightroom tell cannot if I have Previously imported. [Moved from ‘Bugs’ to ‘Discussions’
Using windows 11. Updates to both LRC and PS (cloud) seem to have issues that get worse on every update. ie, LRC won't retain in preferences anything I put in, all goes back to default. When going from LRC to PS via editing under photo tab, will not transfer, unless I completely power down and restart, also still says PS2024 no matter how many times I've reset prefferences in LRC. Also, tools goes blank, reset to photo instead of paint, it does NOT retain this. WHY???????Have been using this for years, seems you just screw it up more on every update.Also, this fearure to post, gets more and more tedious, WHY?????
Hi All,I just upgraded my 2021 Macbook Pro from Catalina to Ventura 13.7.1. When I go to use my Lightroom Classic catalog it comes up with an error. While it says my catalog is too new I know it is the other way around - my OS is too new for the older catalog version - I went through this before. However... How can I download the right version of Lightroom Classic to my laptop without exceeding my OS? The only version I see in Adobe Creative Cloud is 14.1. I am concerned that I will overshoot my current OS and have more problems. What do I do?? And, my clock is ticking on deadlines... many thanks!
When the M4 Max processor came out, I read in a few places that LRC did not take advantage of all the power the M4 Max had, especially when exporting. I've read the Release Notes for the December update (14.1) and they don't say anything about that. Can someone confirm that this was fixed?
LR 13.4 fixed most problems with the keyboard shortcuts shown in LR's built-in Help, but it introduced many new ones, most associated with the newly added Remove shortcuts. The most common problem is using the incorrect localization of key modifiers ("incorrect" meaning different than used in the rest of the Help): EN: Ctrl instead of Control FR: Ctrl instead of Contrôle IT: Ctrl instead of Control NB: Ctrl instead of Control NL: Ctrl instead of Control PL: \\ instead of \ PT: Ctrl instead of Control SV: Alternativ instead of Alt There are still some Help shortcuts with inconsistent case or spacing: EN: Command + Shift+ J EN: Command + Option+ Up Arrow RU: Shift+F SV: Ta bort instead of Ta Bort zh_TW: Alt+^U+2192 zh_TW: Option+^U+2192 zh_TW: Alt+^U+2190 zh_TW: Option+^U+2190 zh_TW: Command + Shift + J Full details are in the file "errors.txt" generated by the Any Shortcut plugin: ht
In LR 14, some of the in-program help entries for keyboard shortcuts in TranslatedStrings have extra spaces around the shortcuts, causing unaligned display in the help windows. For example, see below for what the Remove help looks like and what it should look like. Obviously not a significant impact on usability, but it looks sloppy, like the team doesn't take pride in its work, especially considering that it's so easy to run the Any Shortcut plugin to find these issues. (Note that the forum is removing extra spaces when I copy/paste the output from the plugin here.) es_ES: original: corrected: * (*, *): 290 Develop Module > Brush > Increase Brush Feather ($$
LR 13.5 incorrectly changed the TranslatedStrings keyboard shortcuts for Secondary Display > Loupe - Live to use invalid syntax for shortcut definitions. The shortcuts, defined by these ZString keys: $$$/MultiMonitor/LiveLoupeShortcut/Win $$$/MultiMonitor/LiveLoupeShortcut/Mac should be "Shift+Z" (no spaces). But instead they have these values: Note that the keyboard shortcut for Loupe - Live doesn't work on Mac but it does on Windows: https://community.adobe.com/t5/lightroom-classic-bugs/p-shortcut-shift-z-loupe-live-doesn-t-work-on-mac/idi-p/13201806
In LR 14.0, the in-program help for Remove on Mac incorrectly shows Backspace as the shortcut for Delete. On Mac, the key is called "Delete": For example, the Mac Library Shortcuts shows the correct name of that key (Delete): The offending line in TranslatedStrings is: "$$$/AgDevelop/Menu/Photo/DeleteSpot/Key=Backspace" It should be: "$$$/AgDevelop/Menu/Photo/DeleteSpot/Key=Delete" LR's convention is that occurrences of "Delete" in the help shortcuts in TranslatedStrings get translated to "Backspace" on Windows. For example: "$$$/AgLibrary/Help/Shortcuts/Remove_from_Library/Key=Delete" Windows LR help translates that Delete to Backspace before displaying it. But it appears for the Remove > Delete help, even after you change "Backspace" to "Delete", LR isn't calling the code to do that translation. So two mistakes: 1) TranslatedStrings has "Backspace" instead of "Delete", and 2) The code
In EN and ZH_TW, LR 14 uses "Ctrl" in the help for Cycle Upright Mode, though in those languages "Control" is used everywhere else in the program shortcut help. Screenshots of Help > Develop Module Shortcuts:
Command + Option + O doesn't toggle Remove > Detect Objects on Mac, though Control + Alt + O works on Windows. Tested on LR 14.0 / Mac OS 14.6.1, Windows 11. To reproduce: 1. In Develop, open the Remove panel and click on Mode: Remove. 2. Type Command + Option + O and observe that instead of toggling Detect Objects, it invokes View > Loupe Overlay > Show (incorrect). 3. Hover the mouse over Detect Objects and observe that Command + Option + O is advertised as its keyboard shortcut: 4. Click the "?" icon in the Remove panel and observe that Command + Option + O is advertised as the shortcut for Toggle Detect Objects: 4. Close the Remove panel and observe that Command + Option + O invokes View > Loupe Overlay > Show (correct)
Hello, the right side of my lightroom filmstrip has gone off the edge of the screen, please see attached screenshot where you can see half of the scroll bar is missing and last 2 photos are cut off. Using Mac Sequoia 15.1.1, LR version 14.1. I have: restarted application, restarted laptop, updated LR to latest version, hid and unhid the filmstrip in window settings. No change...
I have some photos that Lightroom will not import. I have previously had these photos imported, but my Lightroom catalog corrupted, and I've spent the past month putting everything back together (and creating a good backup).I suspect it is thinking they are duplicates, but even when I uncheck the button to not import duplicates, it will not allow them to be imported. I tried searching for the full file names without any filters on, and I get results (older photos), but nothing of these photos I'm trying to import. Any ideas how I can get these to import? The folder location shows up in the "folders" drop-down menu, but they show up as containing zero photos (not accurate), while other folders on the same hard drive are having no issues showing correctly.
Can you add the Display Focus Point back???
All of a sudden I can't import photos destination folder is not writable. I haven't changed anything.
The SDK method exportRendition:waitForRender() returns incorrect results for videos. The documentation says: For photos, it works correctly. But for videos, it returns "false, nil" even when the video is correctly exported. To reproduce: 1. Download and unzip this catalog: https://www.dropbox.com/scl/fi/g9ihjg69c85v8ets6h6kj/export-video-bug.2024-10-19.zip?rlkey=20fnn83lz8aao1bmii6pr4wlk&dl=0 2. Copy the file "export-video-bug.lua" from the catalog folder to the Scripts subfolder in the Lightroom settings folder. 3. Open the catalog in LR. 4. Do File > Export, right-click the preset folder User Presets, do Import..., and select the file "Video Test.lrtemplate" in the catalog folder. That is an export preset that will export video files to the Desktop. 5. Select one of the videos in the catalog and do File > Export With Preset > Video Test. Observe that the video is correctly exported to the Desktop. 6. Wi
Hi all. I'm having a strange behavior here and dunno if this is related with the latest Lightroom Classic updates. I have my catalog with a lot of photo and sometimes I find photos from my computer and just to check if they are imported on my catalago, I select the folder to import and if the phots are not highlighted, they are on my catalog. I always worked like this.These days, I tried to do the same thing with some photos and Lightroom Classic shows all the photo as not part of my catalog, but I check on the photos folder and all are there and on the catalog too on lightroom. Dunno why this is happening now, but there is a way to "validate" all the photos on the catalogo to avoid duplicated imported photos? Checked the metadata of the photos that are "duplicated" and are the same of the original imported on the catalog.Thanks.
Version of the app Platform and OS version Basic steps to reproduce the problemNot sure what this means exactly but here goes nothing:When I insert the SD Card into the machine directly or an attached card reader the drive becomes navigatable on the desktop / finder. (working as expected)When I open LR Classic then navigate to the import screen the cards are selectable and in that left most pane the sub folders available and selectable however the photo previews do not appear so I am not able to select and import my photos from SD Cards.LR Classic has access to all files in privacy Expected result and actual resultWhen I insert the SD Card into the machine directly or an attached card reader the drive becomes navigatable on the desktop / finder. (working as expected)When I open LR Classic then navigate to the import screen the cards are selectable and in that left most pane the sub folders available and selectable however the photo previews do not appear so I am not able to
Hello! I'm trying to import photos into Lightroom and I can't. I have no warning of any errors, it just doesn't matter. I already tried in another catalogue, I changed the folder and it didn't work.https://drive.google.com/file/d/1S3dt0p5qamFvFCF-IBS8MOgxuZFg-rOL/view?usp=sharing
I haven't had problems with my primary LR Classic catalogue for years, however recently encounterted an odd bug: Clicking to different collections didn't yield the proper photo count (below the toolbar), even though the correct images were shown. No menu options could be selected and attempting to quit out didn't register anything. Strangly, there was no "not responding" note in the force-quit menu when I'd inevitiably have to do that. Just a note, the mouse doesn't freeze, I can click around to different collections, however most actions are not occuring. Other cats works fine but going back to this one, the same problem recurs. I updated LR Classic, which updated the catalogue. That along with restarting the computer didn't fix the problem. LR .cat backups only occur monthly, though I can possibly nab a much more recent one on time machine, I hope that'll have to be a last resort. Any suggestions greatly appreciated by me AND my deadlines! ԅ
I updated to LRc 14.1 this morning since when the software is unusable. When I open LRc it will force close immediately I try to work on an image; even if I do nothing an error will occur and the system will close. It was working perfectly before the update but is now unusable. After submitting an error report the Adobe software ran a diagnostic for compatability issues but found no problems. I'm running Windows 10 24H2 (OS Build 26.100.2605) with a core i9 14900K CPU, ASUS TUF Gaming B760-Plus WiFi and Zotac GeForce RTX 4060 Ti 16GB Twin Edge - which was perfectly capable of running LRc before the update.
if a dng file is created from pre-processing app (e.g. Topaz Photo AI), the returned DNG will show up correctly in Lightroom with all metadata intact. However, if this file is exported as jpg (all metadata included), the resulting jpg does not contain any exif data (no aperture, no exposure time, no lens info, no model ect). The original DNG can be found in this link (the file is too large to be attached): DNG The exported JPG is attached to this post.
I usually rate images in Camera itself after the shoot.I then import the entire set of captured photos into Lightroom Classic (ALL captured - Rated+Unrated)Post import, I sort the images by Rating and then delete the Unrated images (Remove from Lightroom)Followed by editing the rated images in Lightroom Is there any workaround to import only the Rated Photos into Lightroom?
When Export's Image Format is set to JPEG XL, the Export window doesn't remember that the previous setting of Bit Depth was 16 bits. Tested on LR 13.5.1 / Windows 11, Mac OS 14.6.1: 1. Reset LR's preferences. 2. Select a raw file and do File > Export. 3. In File Settings, set Image Format to JPEG XL and Bit Depth to 16 bits: 4. Click Done. 5. Do File > Export, and observe that Bit Depth has been reset to 8 bits/component (incorrect): 6. Change Bit Depth to 16 bits/component and click Export. 7. Do File > Export and observe that Bit Depth has again been reset to 8 bits/component (incorrect). 8. Change Bit Depth to 16 and click Export. 9. Do File > Export With Previous and observe that file size of the export from step 8 is quite a bit larger than that from this step. Use the "jxlinfo" command (on Mac, "sudo port install libjxl") to observe that the step 8 .jxl is 16-bi
Our agency recently upgraded our server and all computers. I wasn't involved firsthand in that, and now I've found several issues in Lightroom.Our photo library currently holds more than 293,000 photos. Those files were copied to the new server with the same folder structure (year --> date --> file). No one involved knew how to relink everything in one click, so one person started linking one collection at a time. I was asked to get involved and figured out how to do a batch relink.However, several things aren't right as seen in the attached photos which I'll explain.Many photos indicate "file not found". If you right-click and select "Show in Finder", it will point to the photo, so the software knows where it is.Many photos also indicate via the right-click menu that they are not in a collection. However, the thumbnail badge shows it is in a collection.Conversely, some photos say they are in a collection, but there's no thumbnail badge.Edits do not immediately show up in History
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.