Connect with fellow editors in our Lr Classic community.
Recently active
Hello my friendsI have Intel 17-14700kf, AMD RX 7800-XT, 64GB DDR5, but Lightroom is so slow, I tried everything but nothing is working, when I try to add a mask it takes about 10sec to get ready, I have the latest windows update + latest lightroom update + driver + etc.can anyone help me please?
macOS Catalina 10.15.7Lightroom Classic 10.1.1Camera Raw 13.1Fujifilm GFX 50s Hello. Whenever I do a tethered shoot, I am able to establish a connection. (Taking a photo on the camera automatically appears in Lightroom as intended.) However, the Tethered Capture Window is nowhere to be found. I've tried clicking "Show Tether Capture Window" and "Hide Tether Capture Window" - as well as the keyboard shortcut - but the tether window is nowhere to be found. I've double checked to make sure its not nowhere on the edges of the screen, and have tried resetting the preferences in Lightroom.
THe above two images show the difference in the export. the Left is my edit and the Right is the image that was exported.i am editing in Adobe RGB and exporting to sRGB. the settings i have tried are, with LR version 8.4.1, 8.4.0, 8.3.0 . i have viewed the image in the native windows 10 viewer, google drive viewer, and iphone image viewer. i have never had this happen to my exports before, nor have i had an issue with colours. the image above is a screen grab which shows that it is not the result of my vision on the screen or the calibration of the screen. this is the output raw from the machine. EDIT:Ive added more information via screen shots. the far left images are from a proper image viewer that sees the colour calibration, the middle is windows viewer, and the right is lightroom. you can still see a difference between each image.
I recently upgraded my 2021 MacBook Pro M1 Pro (10-core CPU, 16-core GPU, 16GB RAM, and 1TB SSD) to a 2023 MacBook Pro M2 Max (12-core CPU, 30-core GPU, 32GB RAM, and 1TB SSD). The MacBook Pro 16-inch was a significant improvement over my 2016 model and handled my R5 files with ease. However, as my editing demands grew, I began experiencing more frequent slowdowns. I decided to move to a brand new 14-inch MacBook Pro M2 Max for its portability and expected performance boost for my workflow (So I thought). After migrating my files and selling the 16-inch model, I was excited about the upgrade. However, I have noticed that even on this newer machine, I sometimes encounter jerky performance, leading to increased fan noise and heat buildup, which is frustrating. While many praise the MacBook Pro M2 Max for its fast file importing and exporting capabilities, few discuss or measure its performance during high-volume editing sessions. I have the latest Lightroom Classic installed
I use a lot of custom print profiles in my workflow. I just noticed that the Profile settings in the Print Module have now reverted to "Managed By Printer" in every one of my custom profiles. The ICC profiles are still there, and the media format settings haven't changed in the Print Properties dialog. Only the saved ICC setting in the Print module itself has changed. Relatedly, all of the ICC profiles have also gone missing from the drop down color management setting menu in the Print module, which typically saves the last 10 or so profiles used. Again, the ICC profiles are still installed and recognized by LR; it has just forgotten which ones to apply to which print profile, and tells them all to be managed by the printer (Canon Pro-1000). It is easy enough to change the color management setting before printing (if I remember to look!) and then update the profile with current settings, but with dozens of custom profiles that is a major PIA.&nbs
One question for the SDK veterans or the team.In one of my codes I want to append a unicode character, I use it in "MaskName"U+26A1 High VoltageIn General are unicode characters safe or best to avoid them?.
Lightroom classic ne peut pas importerun fichier jpg de 30000 pixels de long et 120 Mo alors qu'il indique une limite de 65000 pixels et 590 Mo. Est-ce que cette limite ne s'applique qu'aux fichiers raw ?
I updated my LRC to 14.2 today.When I open LRC it immediately gets stuck in "not responding" mode.I tried also to use a back up catalog, but unfortunately with the same result.I have forced app shut down and rebooted my PC.I have loaded the latest GPU driver and OS.OS: Win11 24H2GPU: Nvidia GeForce GTx 1080Ti Studio ver. 572.60RAM 32GbAnyone else had same problem? Any help would be highly appreciatedBR Ritu
Hello, I have updated Lightroom to version 14.2 where you say that it already supports the Sony a6400 when tethering. But when connecting LR it says that this firmware is not supported, even though it is the latest version 2.0.macOS Sequoia 15.3.1LR 14.2
In Lightroom Classic , the syncing of images to the cloud has stopped due to some corrupted images. How can I identify the corrupted images, and secondly, how can I then delete them so syncing can continue?
When using the remove tool, it auto selects the option "heal" verses "remove" which I would love for lightroom to give me the option to have it auto select the last used tool instead of having to keep going into the drop down "Fill:" tab each time I want to use "remove". Remove does a way better job verses using the auto selected "heal" option.
Over the past few months, I have been extremely frustrated with my cloud edits not syncing back to LRC. Here's my basic workflow: 1. Import photos to LRC on an external SSD (I store all photos on my external) and add those images to a collection to sync with the cloud.2. Once all previews are done and syncing is complete, I edit on my mobile devices (iPhone 13 Pro Max and iPad Pro 2020). My edits will show as fully synced on either mobile device and show edits made on the other mobile device within minutes.3. When I return to my LRC on my desktop (my external SSD stays attached this entire time), the edits I have made via mobile do not sync back and update in LRC. When I look at my sync status, it shows the green check. I have tried pausing and restarting sync to see if it recognizes updates that need to be downloaded from the cloud. I have tried the pause and restart both with the app open and pausing, rebooting LRC, and then restar
Beim Importieren erhalte ich seit dem neuesten update den Hinweis "Datei konnte nicht in den Zieloedner kopiert werden, da er schreibgeschützt ist". Wie kann das wieder auf einem Macbook hergestellt werden
Upgraded to classic 12.3 on mac M1 and will not open reverted back to 12.2.1 which runs ok - any ideas
I am trying to use custom plugin-specific metadata on a per-photo basis. In the API reference for "setPropertyForPlugin" it states that metadata set using this function does not need to be declared anywhere. However, when I attempt to run a script I get an error that reads "attempt to access property that's not declared in Info.lua". Currently I do not have a metadata scheme defined nor a LrMetadataProvider file specified in my Info.lua file. I would like this metadata to only be viewable and editable from within the scope of my plugin. Did I misread the API reference stating that these metadata fields don't need to be declared? Do I need to specify my metadata id in an LrMetadataProvider file?
Some Canon EOS R5 M2 raws imported into a LR 14.1.1 catalog acquire a pink cast when the catalog is opened in 14.2, and the default As Shot Tint changes in 14.2. To reproduce with LR 14.1.1 and 14.2 / Mac OS 15.2: 0. In LR 14.1.1, verify that Preferences > Presets > Raw Defaults is set to Global: Adobe Default and there are no camera overrides. 1. Download and open this catalog in LR 14.1.1. It contains two raws from a Canon EOS R5 M2: https://www.dropbox.com/scl/fi/li67cc9uswth22wyitsox/tint.14.1.1.2025-02-19.zip?rlkey=037kh2wf6sdatm4ccadij5xjc&dl=0 2. Open _U6A4519.CR3 in Develop. Observe that it has WB: As Shot, Temp: 5,950 Tint: +29. 3. Click Reset and observe no change to the photo or the WB settings: 4. Exit LR and re-open that catalog in LR 14.2. Observe that the buildings now have a pink cast, but the WB settings remain unchanged: 5. Click Reset and observe that the pink cast has disappeared and that Tint has changed fr
There are many threads about this topic like this one for example. I purchased an Eizo CS2400S along with an EX4 calibrator and encountered an issue in Lightroom's Develop module: The Navigator image and filmstrip thumbnails display incorrect colors after clicking on an image. Initially, the colors appear correct, but after a brief loading period, they shift and remain incorrect until Lightroom is restarted. The Library module is unaffected. After researching similar cases, I found that most discussions attribute this problem to a corrupted monitor profile. A common troubleshooting step is to temporarily switch to the default sRGB profile, restart Lightroom, and check if the colors display correctly. In my case, this confirmed the issue—Lightroom displayed correct colors with the sRGB profile. The recommended solution is to recalibrate the monitor to generate a new, uncorrupted profile. However, after multiple calibration attempts with different settings in ColorNavigator 7, every prof
Problem: The Keyword List has a number to the right of each keyword for the number of photos that have this keyword. To the right of the number there is an arrow that one can click, which results in displaying the catalog 'All Photographs' filtered for those photos that have this keyword. However, if photos are part of closed stacks, this method will not find the photos. Therefore, the smoothest solution to this problem is to make the catalog 'All Photographs' always show all photos as unstacked. The problem is slightly related to the discussion in https://community.adobe.com/t5/lightroom-classic-discussions/lightroom-classic-not-finding-photos-in-closed-stacks/m-p/14770539. There are workarounds, such as https://www.danhartfordphoto.com/blog/2022/4/lr014-lrc-tip01-all-photos-really, but none are as obvious and smooth as if it was possible to simply click on the arrow to the right of the keyword in the Keyword List, directly listing those photos.
After a corrupt catalog issue, everything is again up and running but: - when I close Lr Classic I get the message Lr is still synchronising photos Even after 12hrs, it is still synchronising ? Is this normal ? Catalog is about 2300Mb
After applying Develop Settings (either via SDK or via UI), sometimes photos are left in a state where photo:getDevelopSettings() will not give correct values for all sliders, especially Temperature and Tint. (and also the visual representation in the grid does not seem to be updated - when you scroll to the image, you see it visually update only after it has entered the viewport). Simple code snippet to try for yourself: local LrApplication = import "LrApplication" local LrTasks = import "LrTasks" local LrDialogs = import "LrDialogs" local LrFunctionContext = import "LrFunctionContext" LrTasks.startAsyncTask(function() local catalog = LrApplication.activeCatalog() local photos = catalog:getTargetPhotos() local badSettings = {} for i, photo in ipairs(photos) do local settings = photo:getDevelopSettings() local temperature = nil local tint = nil if settings.IncrementalTemperature ~= nil and settings.Increment
I'm giving a presentation to a group this weekend and want to show my images using the full frame/fill screen (F) command so they fill the screen. The images are of different sizes but all are above 1500x1000. If I zoom the image from the Grid and then hit F, it will always fill the entire screen. But if I do not first zoom the image from the Grid, some images do not fill the screen when I hit F. Problem is, I want to run the presentation manually entirely from Fill Screen/ Full Frame mode and not have to jump back and forth to the Grid at any point. Does anyone know how to accomplish this? You can see the grid view not zoomed and the image I get when I hit F for it as well as the images form the Grid zoomed and what I get in the Full screen view for it . I need them all to fill the screen when I hit F. Thanks for any help.
Hey all, I recently moved all of my files onto an external hard drive and have been trying to create a new library with them in Lightroom. This is an import where the already exist situation. It doesnt matter what I do, the import process hangs up. I see a few images show up in the imporrt screen and the progress meter stops. I cancel the process and start again, and get the same issue, just a few images at a time. In some instances, when I hit cancel, an error message shows up that indicates a file which is too big or corrupted, but most often not. I can select a single date folder with just a few images and it will not import them all. I have to stop and restart several times before getting all 20 or so images to sync. This is untennable. Anyone have any ideas? I want to simply set it and forget it to let the machine do its thing. I can do this file by file... I am using macOS Sequoia 15.3.1, Lightroom Classic 14.2 on a 2019 iMac 27inc
As stated, in Classic I periodically get a yellow alert message with ""Regenerate previews for HDR edited images to render HDR in Library Views" and a "Regenerate" button. If I click it, it can take hours to complete. The progress bar shows "Refining Previews for HDR." So far I've been too cautious to quit LrC while it's running. So it's a big annoyance. And note it has done this numerous times, so it must be "refining" images I've already imported unless it's very very very slow with new imports. I am using 14.1.1. Everything else works fine. I make extensive use of the HDR feature, and so quite a number of images are now imported with that setting in Develop enabled. I do it by default now. I want to know why it's happening and how to prevent it. And if I can dismiss the alert without consequences. And if I can quit LrC while it's running. Thanks, Rob
If an image containing face regions has been cropped and/or rotated/mirrored, the face regions in the exported image are not adjusted accordingly. Easy to reproduce. Take any image that has a face identified within it - to make this bug more obvious, have the face NOT in the center of the image (lets say it was on the right hard side of the pic at x~0.75). Crop the image so that the face is roughly centered (ie. x~0.5). Now export the image and look at the EXIF face region tags (RegionAreaX, RegionAreaY, etc). The values have not been adjusted for the crop. Ie. for my example, the RegionAreaX should be around 0.5 but will still be ~0.75. Similar issues occur for the y, width, and height values. Mirror flipping the image horizontally or vertically, or rotating 90, 180, 270 also result in wrong face region values in the exported image. I am using the latest Lightroom Classic 14.2 on Windows 10 x64 but the issue existed in previous versions as well. Lightroom Classic
Hi everyone, I have a problem with Lightroom Classic...I have passed after a long time in a forced way from OSX Mojave that had Lightroom blocked at version 10 (because these continuous updates in the end penalize you and are certainly not a help, something that I have already expressed several times to Adobe support)Now I have OS Sonoma with Lightroom Classic version 14 installed and also version 13.5 and both have a problem of not being able to open the Finder windows to search and update catalog folders not found, and not even doing "File > Open Catalog" opens any dialog box...I tried with the Adobe script found on this page and not even with the guide..."https://helpx.adobe.com/it/lightroom-classic/help/allow-permissions.html" All this is damn frustrating and is making me waste so much time that the new features are useless in comparison...Do you know what to do? I'm quite bitter... it seems to me that we are paying subscriptions as if we were Beta Testers and not as profes
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.