@francesco_g: "I also have a problem with the teeth mask, it is almost unusable because it doesn't select all the teeth of the single person neither all the teeth if I have more people in the picture."   Without sample photos, Adobe is unlikely to pay much attention to the issue. Please attach here full-resolution JPEGs exported from the unmodified original photos (not screenshots). ... View more

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   @Yvou73: "I cannot modify opacity in the remove menu any longer (IA or not). Cursor has disappeared."   Do you see the Opacity slider after clicking Remove? In LR 14, the slider appears only after you click Remove:   If you're seeing the slider but you're unable to move it,  try resetting LR's preferences: https://www.lightroomqueen.com/articles-page/how-do-i-reset-lightrooms-preferences/ LR sometimes soils its preferences file, and resetting it can fix all sorts of wonky behavior. That article explains how to restore the old preferences if resetting doesn't help. ... View more

"Why don't we see artifacts in the 1:1 preview of a pano DNG?, I take it 1:1 previews are not lossy JPEG XL."   A panorama DNG created by Photo Merge is a "linear raw" with the raw pixels represented as three channels (RGB) in the color space of the camera's sensor. The pixels are normally compressed using JPEG XL compression, but their color space is that of the camera.    When you view such a DNG in Library, it is converted to Adobe RGB, which is used for all Library previews. When you view the DNG in Develop, it is displayed in the working color space of Develop, Melissa RGB, which has the same color primaries as Prophoto RGB except with a linear curve instead of Prophoto's gamma curve.   So viewing Library is different than exporting:   Raw photos to panorama to Library preview: Camera color space > JPEG XL compression in camera color space > JPEG XL decompression > Adobe RGB.   Exporting raws to JPEG XL format in Prophoto: Camera color space > JPEG XL compression in Prophoto       ... View more

@Ozzyyz: "it creates variations to similar what is there, e.g., if there is a face it creates another face, if there is a ball it creates another ball. It simply does not remove!"   See this short article for how to remove objects more reliably: https://www.lightroomqueen.com/generative-remove-replace/ Most complaints about Remove are addressed in the article. But if it doesn't help, please attach a full-resolution JPEG exported from the unmodified original photo (not a screenshot). With nearly every one of the many dozen problem photos posted here, we've been able to show how to quickly remove the desired objects. ... View more

"Library Path: C:\Users\amber\OneDrive\Pictures\Lightroom\Lightroom Catalog.lrcat"   Your catalog folder is being synced with OneDrive, and there are many reports here of that causing all sorts of problems for LR. Try moving the catalog folder to somewhere not synced with OneDrive, e.g. as a top-level folder under C:.  ... View more

First, restart your computer. If the problem persists, try resetting LR's preferences: https://www.lightroomqueen.com/articles-page/how-do-i-reset-lightrooms-preferences/ LR sometimes soils its preferences file, and resetting it can fix all sorts of wonky behavior. That article explains how to restore the old preferences if resetting doesn't help. ... View more

Most problems with LR's AI commands are caused by older, buggy graphics drivers. Try updating your graphics driver by going directly to the manufacturer's web site: https://helpx.adobe.com/lightroom-classic/kb/troubleshoot-gpu.html#solution-4 If that doesn't help, please copy/paste here the entire contents of the LR menu command Help > System Info -- that will let us see exactly which versions of hardware and software LR thinks you're running. ... View more

"DirectX: NVIDIA GeForce RTX 4060 Laptop GPU (32.0.15.6103)"   That driver is five months old. Update to the latest Studio driver: https://www.nvidia.com/en-us/drivers/details/240529/  ... View more

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   "I want to send a print to a lab: 24x36", 300 dpi, image placed on the page as I wish, with a border"   If you don't have an installed printer whose driver supports custom page sizes, you've got a couple of options:   1. With your current printer, in the Print Job panel, select Print To: JPEG File and enter the custom page dimensions in the Custom File dimensions:     At least in my LR, it was a little glitchy displaying what I just entered (showing 0.00 in), but the sizes "took", as shown in the screenshot.   2. If your Creative Cloud subscription includes Acrobat, you can set LR Print to use the Adobe PDF printer installed along with Acrobat; it lets you define a custom page size. Then you can either print to a PDF or save the print to JPEG.   I found I had to restart LR after defining the page size in the Adobe PDF driver:     ... View more

"I'm now thinking its during the conversion from the native space to the non-native space some of the maths/rounding doesn't allow for a number bigger than 1  or smaller than 0 and you get a blown or clipping artifact in one or more of the channels."   This doesn't explain why the "cjxl" program from the reference implementation "libjxl" doesn't have this problem.   ... View more

On Windows, you define custom paper sizes in the print drivers: https://www.google.com/search?q=create+custom+paper+size+printer+windows+11&rlz=1C5CHFA_enUS1064US1064&oq=create+custom+paper+size+printer+windows+11&gs_lcrp=EgZjaHJvbWUyBggAEEUYOTIGCAEQRRg80gEINzU1NWowajSoAgCwAgE&sourceid=chrome&ie=UTF-8   For example: https://epson.com/faq/SPT_C11CG43201~faq-00004f4-xp15000 ... View more

"Are you sure?"   See the 13.2 version here: https://community.adobe.com/t5/lightroom-classic-discussions/p-color-artifacts-in-jpeg-xl-prophoto-rgb/m-p/15127726#M395383   which has green artifacts around the light bulbs not present in the original or the version created by "cjxl": https://community.adobe.com/t5/lightroom-classic-discussions/p-color-artifacts-in-jpeg-xl-prophoto-rgb/m-p/15111170#M394182 ... View more

As a first troubleshooting step, do the LR menu command Help > System Info and copy/paste the entire contents here so we can see exactly which versions of hardware and software LR thinks you're running and important LR options that are set. ... View more

"I added [Folder] [starts with] [Folder 1] AND [Folder] [ends with] [Folder 1] to ensure that it matches only "Folder 1", not "Folder 12"."   Note that the operators Starts With and Ends With have been broken since LR 13.3: https://community.adobe.com/t5/lightroom-classic-bugs/p-starts-with-text-filter-on-captions-or-filename-incorrectly-matches-words/idi-p/14729614 ... View more

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   With the same test photo I used above, I see artifacts in LR 13.2 too (below). Unfortunately, the Adobe engineering team has already decided this is a limitation of the JPEG XL format when used with Prophoto, not a bug, and it's unusual for them to change their minds in such cases. In my example above, the "cjxl" program distributed with the reference implementation "libjxl" doesn't produce such artifacts, so I'm highly skeptical about the engineers' claim.     ... View more

As a first troubleshooting step, do the LR menu command Help > System Info and copy/paste the entire contents here so we can see exactly which versions of hardware and software LR thinks you're running and important LR options that are set. ... View more

Many have observed here that the replacements made by Generative Remove sometimes don't match the photo's tone or noise. To get better matches, these techniques sometimes help: 1. Adobe recommends applying Denoise before Remove. This can reduce the noise, making it more likely the replacement will match. 2. The replacement patch supplied by Adobe Firefly has a maximum size of 2048 x 2048 pixels. If the selected area in the photo is larger than that, then the replacement patch gets upscaled (and blurry). Try removing smaller selections if possible. 3. Make a larger selection, even including the entire background. Upscaling of the replacement sometimes won't be noticeble then. 4. Sometimes there's a distinctly visible boundary where the tone or noise don't match. You can often use the heal tool around the boundary to get better feathering and make it less noticeable -- apply Heal in small brush strokes. Sometimes, making a very raggedy selection around the object makes the boundary less noticeable. 5. For grain/noise in particular, see this post for how to ameliorate the problem by adding the grain back or reducing the grain: https://community.adobe.com/t5/lightroom-classic-discussions/p-generative-remove-feedback-lr-classic-amp-lr-eco/m-p/14917497#M382464 ... View more

If you're referring to the Any Comment plugin, yes, it has been retired. But you can search for comments and likes using the Any Filter plugin. ... View more

Nearly all problems with sorting by capture date reported here are caused by the photos missing a capture date in their EXIF metadata. This can occur with very old digital cameras, scanned photos, editing software that doesn't preserve metadata, and social-media services that strip all metadata.   "In september I changed the location of my catalog and image folder.  ... a decent number of images have that September date as the "capture date" for files that are much older (and no original date exists in that field)."   When a photo is missing capture date in its metadata, LR behaves very badly, using the photo file's date-modified (as shown in Finder / File Explorer) as the capture date displayed in the Metadata panel, under thumbnails, and used for sorting. When the file is modified for whatever reason (e.g. doing a LR Metadata > Save Metadata To File), LR will soon after start using the new data-modified as the capture date!  This appear to be what's happened with the "September" photos.   The only way to stop LR from doing this is to ensure that each photo has a consistent internal capture date in the catalog:   1. Select all the desired photos.   2. Do Metadata > Edit Capture Time. 3. Immediately click Change All. This does not, repeat DOES NOT, repeat DOES NOT, change the photos to have the same date. Rather it consistently records the date shown for each photo in the Metadata panel and under the thumbnail as the internal capture date in the catalog.   I don't know if this is the procedure you used on the previous photos you mention. If after applying this procedure, you're still having issues, the only way to troubleshoot is to start with a specific photo.   ... View more

Quickly rule out problems with the GPU by temporarily setting Preferences > Performance > Use Graphics Processor to Off. ... View more

For stubborn issues like this, try doing a complete uninstall/reinstall of ALL installed Creative Cloud apps using the Creative Cloud Cleaner Tool: https://helpx.adobe.com/creative-cloud/kb/cc-cleaner-tool-installation-problems.html   I can't remember if the tool asks and then successfully removes Lightroom Classic preference files (despite what the help page says), but be sure to save a copy of your LR preferences file -- see here for its location: https://www.lightroomqueen.com/articles-page/how-do-i-reset-lightrooms-preferences/ ... View more

@GoldingD: "Can you take a photo with that lens on that camera."   You can download a sample raw with that camera and lens from dpreview.com: https://www.dpreview.com/sample-galleries/7568684162/canon-rf-24mm-f1-4-l-vcm-sample-gallery/4853359764 ... View more

Building on Johan's reply, Save New Lens Profile Defaults doesn't work with lens profiles that are embedded in the raw by the camera (which show up as Profile: Camera Settings in the Lens Corrections panel).  A bug report was filed about this last fall, but Adobe has never acknowledged the bug or marked the behavior "as-designed": https://community.adobe.com/t5/lightroom-classic-discussions/error-when-saving-changed-profile-corrections-in-combination-with-the-r5-mark-ii/m-p/14836446   It's hard to know what the "as-designed" behavior should be, since Adobe has never updated the documentation about lens corrections after LR 9.4 allowed embedded lens profiles that the user could disable: https://helpx.adobe.com/x-productkb/multi/lens-profile-support.html   ... View more

This help article provides a thorough explanation: https://helpx.adobe.com/lightroom-classic/help/enhance-details.html ... View more

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   Were those instructions from some AI bot or AI search results? Smart collections don't allow you to search the print history, and smart collections don't use the terminology "filter criteria".  You'll have to use the Any Filter plugin:       ... View more

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   "If I mark the images I want to edit and transfer them to Pure Raw using the "Export" function, they are edited correctly and transferred back to Lightroom as a new DNG file and saved in a stack together with the RAW as I requested. Unfortunately, the DNG file is always placed at the bottom of the stack. ... I had already contacted DxO support. As expected, the answer was that Lightroom alone determines this behavior and that it needs to be adjusted accordingly."   Not surpisingly, Dxo support, like most technical support much of the time, is wrong. It would be trivial for Dxo to modify their plugin to add the new DNGs to the top of the stacks rather than the bottom.   Details:   Looking at Dxo's documentation and the free trial I just downloaded, the Export option works via an Export preset provided by Dxo, which invokes an export service provided by the Dxo plugin, handing off the exported file to the Dxo program. It appears that both that export service and the alternative way of invoking Dxo via File > Plug-in Extras > Dxo Pureraw 4 use the plugin  DxOPureRawv4.import.lrplugin to import the DNGs back into the catalog.   Some quick examination verifies that plugin calls the LR SDK's method catalog:addPhoto() to import the DNG into the catalog. The addPhoto() method has a parameter "position" specifying whether the photo should be stacked on top or the bottom. See the documentation below.   Feel free to forward this to Dxo support. If you do, ask them to send me an address where I can mail my invoice for the free consulting 😆         ... View more

@AM34509514d7oj: "sometimes it tries to change it to another thing when actually you are wanting the selected objected to be removed."   See this short article for how to remove objects more reliably: https://www.lightroomqueen.com/generative-remove-replace/ Most complaints about Remove are addressed in the article. But if it doesn't help, please attach a full-resolution JPEG exported from the unmodified original photo (not a screenshot). With nearly every one of the many dozen problem photos posted here, we've been able to show how to quickly remove the desired objects. ... View more