Connect with fellow editors in our Lr Classic community.
Recently active
Version: Lightroom Classic 11.0 OS: Windows 10 Home 21H1 In the new masking tool, the shortcut SHIFT-O to cycle the overlay color does not work. Nothing happens. In the new masking tool, the shortcut ALT-O to cycle the overlay mode works, but produces an annoying "system beep" each time it is applied.
Nella pagina https://helpx.adobe.com/it/lightroom-classic/help/keyboard-shortcuts.html questa scelta rapida per Mac OS X è sbagliata Modulo sviluppo Aumentare o ridurre dimensioni pennello LrC su Mac OS X si comporta come su Windows e vanno utilizzati i tasti < e + per aumentare o ridurre la dimensione del pennello nel modulo sviluppo e non ]/[ come indicato nella pagina. Please note: the Mac OS X keybord shortcut help page suggest the ]/] keys to increase or decrease brush size in develop module. The italian localized LrC version shortcut is </+ and not ]/[ as indicated in the Italian help page. PLS see link above.
Checking just Upright Mode, Straighten Angle, or Aspect Ratio doesn't work in Copy/Sync Settings or when creating a preset. The workaround for Upright Mode is to first check Transform and then uncheck the undesired sub-settings. This doesn't work for the Crop sub-settings though. To reproduce: 1. Edit photo A, and in the Transform panel, select Auto. 2. Select photos A and B with A most-selected, and do Sync Settings, click Check None and then Transform > Upright Mode. 3. Observe that B has the Transform mode set to Off. 4. Select photo A, do Copy Settings, click Check None and then Transform > Upright Mode. Select B and do Paste Settings. 5. Observe that B has the Transform mode set to Off. 6. Edit photo A. 7. Create a preset, click Check None and then just Transform > Upright Mode checked. 8. Observe that the preset doesn't appear in the Presets panel. But in the presets folder, there is an appropriate
I installed updates to LRC and PS. Now I have LRC 11 and PS 23. My workflow involves creating different snapshots in LRC, export the file as smart object to PS. "Edit In -> Open as Smart Object in Photoshop". When I am in Photoshop, I used make duplicate layers with 'New Smart Object via Copy' and double click on the smart object layers to go to ACR and select the required snapshots in different layers. After the upgrade, LRC is not retaining the snapshots in the smart object. Is this an intentional change or a bug? I was hoping someday Adobe will introduce a feature where snapshots in will automatically go as layers into PS. Now even the existing functionality is gone. 😞
MAC OS 11.6 - LR 11 (French) In the last "GREAT" release of LRC I notice a little bug. The command shift+Q is no longer assigned to image rotation (counterclockwise) it's now for editing masks... OK, however a BUG appear in the Photo Menu because the shift+Q shortcut still appear.
I've just installed Lightroom Classic 11.0 (on Windows 10) and took a look at the new masks, but have found 2 strange behaviors. In both cases, the overlay for a mask that is not selected stays visible, although it shouldn't. Here's how to replicate: Behavior 1: - create 2 masks - with Mask 1 selected, press and hold S to display the pins of all the masks - while holding S, hover with the mouse over the Mask 2 pin to display the overlay - with the overlay still visible (i.e. the cursor on the pin), stop pressing S - the Mask 2 overlay stays visible, although it has not been selected. - hovering the cursor on the pin of the (still selected) Mask 1 will temporarily hide Mask 2 overlay and show Mask 1 overlay, but when the cursor is moved away from the Mask 1 pin, the Mask 2 overlay reappears Here's how it looks: The active Mask 1 contains only the visible radial filter, while the overlay that is shown is from Mask 2, after following the steps explained above. Behavior 2: -
“The catalog could not be opened due to an unexpected error.” Not just my main catalog. Every catalog, recent and older, and every backup. This is what I'm looking for urgent help with. It's far from the only problem. InDesign crashed hard on first launch of the update. Fonts spun in Adobe Fonts and wouldn't load. What an utter disaster you are lately Adobe.
A nested viewFactory:group_box doesn't display its title on Windows but does on Mac: To reproduce, run this script: local LrColor = import "LrColor" local LrDialogs = import "LrDialogs" local LrView = import "LrView" local f = LrView.osFactory() LrDialogs.presentModalDialog {title = "Test", contents = f:column { f:group_box {title = "Outer group box", f:checkbox {title = "Outer checkbox"}, f:group_box {title = "Inner group box", show_title = true, f:checkbox {title = "Inner checkbox"}}}}} Tested on LR 11.0.1 / Windows 10 and Mac OS 11.6.
I am running Lr Classic. "8.4 Release". My catalog that has all of my pictures, and that I have always used on a daily basis, will not open. What is the issue?!
Hi, There are various articles on smart collections that check if the "Title" field is filled or not. Because the "Title" field doesn't have an "is empty" like function, the sugested solution is to use: Title doesn't contain a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z But there is a bug in this rule. I found that the letter 't' is causing a problem. The letter 't' seems to include all characters. Situation: Four images that have a their Title field as follows: Image 1: Image 2: 2014-01 - Street Photography.dng Image 3: 2014-01 Image 4: Some Image (Image 1 has an empty title) Four smart collections with the following rules: Collection 1: Title doesn't contain a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z Collection 2: Title doesn't contain 0,1,2,3,4,5,6,7,8,9 Collection 3: Title doesn't contain a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,u,v,w,x,y,z Collection 4: Title doesn't contain t My expected result of the smart collection is: Collection 1: Image 1 and Image 3 Collection 2
I have taken out the subscription for Lightroom and I can not import my videos. I have tried reinstalling the program and nothing works. The videos will play with Quicktime and they can be imported to Photos on my iMac.Please help as I am very frustrated.
Not sure if this is new behaviour or if LR6 has always done this and I've never noticed.I am currently cropping all my images to 2x3 / 4x6 to upload to a school site (outputting with longest edge as 5400 to make 12x18 prints).When I cycle between images and go back to one already cropped the aspect name is reset to say original each time rather than 2x3/4x6.This is extremely confusing as I have no way of seeing if the image has actually been cropped or if I have just forgotten to do it! I'm sure in the past the behaviour has been to keep the chosen crop aspect visible in the panel.
There is a small but annoying bug if you try to apply the same profile to 2 or more images in the Develop module.Say that you have 4 images: Images A & B in Profile 1, Images C & D in Profile 2. If you select all images in the Develop module (with Auto Sync on), and you choose the same profile for all 4 images, the profile will be changed only if this changes the profile for the most selected image. For instance, if image A or B is the most selected, and you choose Profile 1, then images C & D will not be changed. However, if image C or D is the most selected, then the new profile will be applied to all the images.Lightroom seems to use the (incorrect) rule -- if the most selected image is already in the chosen profile, then there is nothing to change, but if the most selected image would be changed, then apply the change all the selected images.This is an annoying bug because changes in color profile can be subtle, and it isn't always apparent that no change was made.The w
In the following case, a photo is permanently deleted from disk unintendedly:1. In the Library view, right click on a photo and select "Remove Photo"2. In the following Pop-Up "Confirm" select "Delete from disk"3. Abort the following Pop-Up "Delete Permanently" by pressing ESC=> The photo is falsely deleted from diskReproduced with Lightroom 5.5, Windows 7, 64 Bit
I noticed that LR clone and brush tool on my XEON E5-1650 0 3.20GHz (Attention: E5-1650 0 and not E5-1650 v4) can not stress my CPU and after x minutes of working LR slow down, until I have to restart it.Please see the full diskussion with the problem here: https://forums.adobe.com/thread/2210245 (test with different Lightroom versions, confrontation with a weak laptop, that works fine, tests wit other graphic grafic card, test with other bios settings etc. No results. Only restart LR or minor display resolution helps.)Can anyone with an XEON E5-1650 0 3.2Ghz confirm this?
Lightroom Classic CC for Windows (7.0.1)The shortcut keys "Ctrl +," are doubly assigned.1. Preferences2. Zoom outIf you press the key, the environment setting opens.In addition, the operation of the zoom in key "Ctrl +." Is also strange.The result is different from Lightroom Classic (2015).
Yes. This problem was fixed in some earlier versions of Lightroom, but appears to have resurfaced in Lightroom Classic. I just reproduced it in Lightroom Classic CC 7.0.1 on MacOS X 10.12.6 (Sierra).Adobe's support team on Twitter have denied that the problem exists, but I can reproduce it reliably on my system.Note: This conversation was created from a reply on: Lightroom: Deleting rejected photos while in Develop doesn't work.Lightroom reports "Error changing modules" after rejected photos are deleted while in the Develop. STEPS TO REPRODUCE1. Launch Lightroom.2. Switch to Develop.3. Flag 1 or more photos as Rejected.4. Choose "Delete Rejected Photos" from "Photo" menu.5. Switch to Library.EXPECTED BEHAVIORSwitch to Library should work correctly.ACTUAL BEHAVIORLightroom displays a dialog reading "Error changing modules". Thereafter, the app is in an inconsistent state; no photographs are displayed in the Library module, and choosing "Quit" causes the app to exit without the normal pr
Lightroom 9.1 doesn't start at all for me on Windows 10. I updated my video drivers to the latest versions (with a clean reinstall), I reinstalled my CC Apps (also using Adobe Creative Cloud Cleaner tool). I event used an older version of LR (8.4) but still doesn't work. I found the error in the Windows Event Viewer and it says Faulting application name: Lightroom.exe, version: 9.1.0.10, time stamp: 0x5de0bfe8Faulting module name: DirectML.dll, version: 10.0.18362.267, time stamp: 0xd1d24d33Exception code: 0xc0000409 Now, I checked the official requirements: I am using a supported version of Windows 10 (1903) and my video drivers are DirectX 12 compatible (I also have DirectX 12 installed and I have no problems with it, checked with dxdiag).I have opened a support ticket but it seems to me that even the support team is clueless. I had to drop the conversation with them today but I'll resume it tomorrow. This upsets me, especially since LR used to work very well on my PC, but it seems t
I have been coalescing my mini travel catalogs in to my main catalog. They import fine, but they show up in the folder panel not in the correct spot in the directory tree. When I do show parent folder it gives me An internal error has occurred: Database "E:\lightroom\lightroom.lrcat": UNIQUE constraint failed: AgLibraryFolder.rootFolder, AgLibraryFolder.pathFromRoot Statement: UPDATE AgLibraryFolder SET rootFolder = ?,pathFromRoot = ? WHEREand an ok button. I tried doing update folder location My folder tree looks like this:2018 trip 12019 trip 2Z 2018 january 2019 january februarywhere the actual hard drive is:Z 2018 trip 1 january 2019 trip 2 january februaryIn future I'll make sure to do show parent folder in the mini trip catalog before I import it, bu
When attempting to import photos from my Nikon D850, Lightroom Classic states it is importing photos but status bar is not progressing and no photos are being imported. Restarted system and program along with camera and still has issue. This is all been occurring with macOS Catalina 10.15.
Like title says, the screen of my MacBook 16" turns black for 2-3 secs while (fresh) opening PS. Sometimes the same in LR when switching from Grid View to Develope Module. This happens only on battery mode with Automatic Graphics Switching ON (MacOS settings)Turning Automatic Graphics Switching OFF solves the issue. Turning OFF graphics processor in PS solves the issueBut that's not a solution for me.Anyone experiencing the same?
Lightroom Classic 9.3 Library Preview Zoom interpolation type has been changed to nearest neighbor. Nearest neighbor interpolation uses a simpler and faster algorithm that can create "jaggies" and other artifacts in the image. Presumably this was done to reduce preview building time, but don't know. I checked LR Classic 8.4 and Camera Raw 12.3 (most current) and they both appear to use bicubic or bilinear interpolation, which does not exhibit the artifacts seen with nearest neighbor interpolation.What this means is that the ALL of the Library Zoom view settings less than 1:1 may exhibit artifacts with certain image files that appear as edge "jaggies' or moire' patterns. This makes them less useful for evaluating the image detail at Zoom settings of resized export and print output. Here are examples using Lightroom Classic 9.3 showing PS Image Size panel with 33.33% (1:3 Zoom) image resizing using Nearest Neighbor (top screenshot) and Bicubic Sharper (bottom screenshot) Resample a
When I check "Remove chromatic aberration" checkbox I get artefacts on the left border of the image. Artefacts looks like 1-pixel vertical straight green and/or purple lines of random length.Images where I noticed this problem - are panoramic 360ox180o DNGs (6080x3040px) exported from Insta360 Studio app. I see this lines very clearly in VR-viewers later.I see this artefacts not only in preview inside Lightroom but also in exported TIFFs. Inside Lightroom I see mostly green, and in exported TIFFs I see purple. See attached video for examples.I don't see this lines with unchecked "Remove chromatic aberration" chackbox and I don't see them in other apps, like Apple Preview.I don't see this artefacts on other my files (JPEG, HEIC and DNG from iPhones).I Use Lightroom Classic on MacBook Pro 2018 15" with Radeon 560X 4 GB. I tried to turn On and Off using of Radeon in Lightroom - no difference.DNG with the problem:https://yadi.sk/i/EUC6Ztr-GjKXvw
When you import a .heic containing a face name saved to the photo's metadata, LR doesn't import the face name. But this works correctly with .jpgs. To reproduce: 1. Make a new catalog. 2. Import a .heic photo containing a face, export it as a .jpg, and import the .jpg into the catalog. 2. In Loupe, label the face in both photos with "John". 3. Select both photos and do Metadata > Save Metadata To File. 4. Remove both photos from the catalog. 5. Reimport both photos into the catalog. 6. In Loupe, observe that the .jpg's face is still labeled with "John" but the .heic's face has "?". Observe that both photos have keyword "John". See the attached screen recording. Tested with LR 11.0.1 / Mac OS 11.6.
Ever since Lightroom CC 2015.7 there has been a performance issue with Lightroom and Sony ARW files. When working in the develop module, when you first move to an image, the sliders will operate, but have no effect for several seconds. On non-sony images this does not seem to be a problem. This issue only started with 2015.7 and has not been resolved by subsequent updates. In some cases it can take up to 10 seconds after an image loads in the develop module before the sliders become responsive. I have tried using a new catalogue with no other images in it, to see if it was my catalogue, but to no effect. Others have reported this too, but as they are not using other cameras, they did not realise it was specific to sony ARW files. One user posted a video on YOu-Tube showing the problem. https://www.youtube.com/watch?v=XPFujo_tNY8 This is not my video, but the person is having the exact same problem that I am having. My setup is a MacPro 12 Core with 20GB ram. I've also tried it on
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.