Lightroom Classic

I shoot both in RAW and Jpeg on my Fujifilm camera. When I import the RAW files into Lightroom Classic or CC the files retain their Jpeg look, they don’t look like RAW files at all. This happens not just in the grid preview but in the Develop mode as well and with all the sliders set to 0, which makes it very difficult to edit a photo accurately since the colours etc. are all wrong. I’ve checked the RAW default setting in the Presets tab in Preferences and it is set to Adobe Default as it should be. In the Develop mode the profile is set to one of the Adobe profiles. Where am I going wrong? Thanks for any advice.Left is from Camera Roll, right is in Lightroom develop mode.  

I am working with the latest version of LR on an Acer desktop. When moving my target catalog to an external hard drive, I seem to have created a situation in which my exported catalog is nested within another exported catalog of the same name. In the process however  a years worth of work can’t be found in target catalog (which is the one I use and import to and which appears in last of the screen shots as Catalog 13.3This became an issue when I tried to locate the files in the catalog, found that they bore the telltale Photo missing icon but then I located them in folders did not have the telltale question mark. Here is the first screen shot showing the Exported Catalog which conspicuously does not include the year 2021:Notice how 2021 is missing both in Explorer and in the left hand folder listThe next image comes from Explorer where I have clicked on the folder in the screen shot above:Notice that there are three folders for 2021 imagesAnd by clicking on the folder entitled LRC Cata

After updating to 15.5, I noticed during the last editing cession of a dozen of landscape pictures with various masks that the histogram disappeared from its window. The RGB values were still changing when the cursor moved over the picture, proving the window was still active. The histogram returned only after entering and exiting the masking tool. But scanning through the photos make it disapeared again later in the develop module for some pictures.I had to relaunch LRC to have the histogram window working again as it is supposed to be.Unfortunately this bug seems to happen randomly and cannot be repeated on purpose.My config is Apple MacBook Pro M1 Max 24Mo Ram OSX latest version of Tahoe, LRC 15.5.I must say this is the third strange behaviours since the update to 15.5. The first was the uncontrollable scrolling with the arrow key in the film strip, the second being the loss of the zoom ratio in Full view returning automatically to 33.3%. Restarting LRC solved apparently both issues

I am trying to print one of my images which contains a good bit of orange.  The image was converted to LAB and the a and b channels made a bit more vertical to bring out the colors.  Yet the image prints in a manner which ignores the adjustments made in LAB. I am using current versions of LR and PS with an Epson 9570 printer along with a custom profile for Hahnemuhle Fine Art Baryata paper. Three images are attached.  One printed with Pro-foto color space, another LAB, and the 3rd being a photo of the screen.  The latter shows the colors I am trying to achieve (although over-saturated in the cell phone photo).  When soft-proofing the orange colors and just about everything else (except for some very deep greens) are all within gamut. I look forward to your advice.Bob Greenbergrsg.photo.1@gmail.com 

Lightroom Classic now adds AI content credentials to image exports automatically (just started last week, without warning).  For tools such as Remove, for dust spots, etc.  This appears not possible to be turned off ?The export options show that Content Credentials are off, but it is still appliedMy use of such tools is for image refinement, not creation of distortions (which is where the content credentials are more appropriate)For minor refinements I do not want my images to be tagged in this way, misconstruing and giving he wrong message about the final image Please let me know how I can stop the CC being tagged, as it appears in Bridge (and beyond)

System information Adobe Lightroom Classic 15.6 Adobe Camera Raw 18.7 Windows 11 Home (Build 26200) 32 GB RAM 16 GB GPU memory Problem descriptionSince updating to Lightroom Classic 15.6, I am unable to apply any Develop Presets.Whenever I click on a preset, Lightroom attempts to download AI models. The download consistently stops at exactly 68% and never progresses. Eventually, Lightroom displays the following error message:"Some AI models could not be downloaded. Please try again later."The issue affects all presets, including Adobe presets, existing custom presets, and newly created presets.Interestingly, the preset preview works correctly when hovering over a preset with the mouse. However, clicking on the preset does not apply any adjustments.Reproduction testTo eliminate the possibility of an AI-related preset causing the problem, I performed the following test: Selected a photograph in the Develop module. Changed Exposure to +1.00. Created a new preset containing onl

dkSimple question which makes me feel an amateur.I need to remove custom metadata fields associated to a Plug-in from my catalogs.I am thinking to set them all as nil, then disable and remove the plug-in rather than migrate. Any know problem that could arise from this approach? I can't think of any but maybe I am missing something.The fields can be regenerated easy as they originate from catalog metadata.  

Welcome to Lightroom Classic Community Hey there! Welcome to the Lightroom Classic Adobe Support Community, where you can get answers to all your how-to questions and learn how to troubleshoot issues you are experiencing. If you're new to the Adobe Support Community, check out Using Community, which provides helpful information about the Adobe Support Community and our Community Guidelines. Let's get started! Where To Post There are a few areas within this community where you can post depending on your question. Still trying to figure out where to post; check out the descriptions below. Have a question or need help troubleshooting an issue? Create a post here. Do you feel like you've run into a bug in the app? Learn how to report a bug. Have a great idea you want to share? Learn to request a new feature. Who You'll Meet in the community Our community is a diverse group of cultures, experiences, backgrounds, and knowledge that share a common interest in Lightroom Classic a

Als ik een serie foto,s hebt gemaakt is het wel handig als je het zelfde stof deeltje op alle foto,s tegelijk weg kunt krijgen met synchroniseren. 

I have 20k images keworded painstakingly by plant and animal species as I am a wildlife and nature photographer and blogger. Being able to view my folder structure (location) and heirarchical keywords to find species x are critical. Till now have been using desktop with a supported keyword heirachy. Just attempted to use cloud for first time an had a shock when no folder or keywords apparead in my test. It didn;t i nthe slightest occur to me these might not be there!Please tell me reintroducing these feature to the cloud option is on the product roadmap! otherwise What on earth am I paying my subscription for exactly? There are plenty of good raw editors out there. Its the keywording that provides the product value.And believe me the answer is not AI...

System configuration Lightroom Classic 15.6 (Creative Cloud subscription) Camera Raw 18.7 Windows 10 Business Edition (Build 19045, 64-bit) GPU: AMD Radeon RX 6800, 16 GB VRAM CPU: 12 logical processors, 3.9 GHz RAM: 16 GB Camera: Canon 5D Mark IV RAW format: CR2 Problem descriptionAfter updating to Lightroom Classic 15.6, the AI Denoise feature became extremely slow, taking approximately 15–20 minutes per RAW image.Lightroom was detecting the AMD Radeon RX 6800, but it was not using GPU acceleration.The Performance preferences panel displayed the following warning:"GPU acceleration is not supported by your system."The Lightroom system information report showed: Initial GPU status: Unsupported GPU GPUDeviceEnabled: false Dedicated GPU memory used by Lightroom: 0 MB GPU renderer: AMD Radeon RX 6800 GPU memory: 16,338 MB Direct2DEnabled: false Troubleshooting steps performedI tried the following: Updated the AMD Radeon RX 6800 graphics drivers. Restarted the com

I primarily use Lightroom Classic for organizing my photo and video library. I have diligently assigned keywords to categorize and manage my media efficiently.My intention is to share my media with others through Lightroom (cloud) while ensuring that the keywords are synced along with the files. This is crucial for facilitating easy search and retrieval of specific photos or videos.But the keywords are not syncing from Lightroom Classic to Lightroom (cloud) automatically. also:Videos require manual importation into Lightroom (cloud), as automatic syncing doesn't include them.   

Ich möchte im Drucken-Modul eine JPG-Datei erstellen. Früher konnte man über die Benutzerdefinierte Dateiabmessungen die Pixelgröße der JPG-Datei festlegen. Der Wert für die Dateiauflösung hatte keinen Einfluss.In der aktuellen Version (und wahrscheinlich schon viele davor) hat der ppi-Wert einen (unbekannten) Einfluss auf die Pixelmaße der JPG-Datei. Die eingegebenen Dateiabmessungen werden ignoriert.Bei dem Beispiel im Screenshot wird aus den 1.200 pt x 415 pt eine JPG-Datei mit 5000 x 1729 Pixel! Warum wurde der Prozess geändert? Das macht doch bei einer Bilddatei keinen Sinn.

This post applies to Camera Raw and Lightroom Classic. Dust Removal is no longer in Early Access status and can be found in the Remove edit panel for Camera Raw & Lightroom Classic. Dust Removal helps remove distracting spots in an image that may be caused by dust on a camera's sensor and is also effective on dust on the rear lens element. Once enabled, your image will be scanned, and any detected dust spots will be automatically removed using Content-Aware Remove. For refinement, you can select one or multiple spots to delete or refresh. Batch removal is also supported; simply select the "Dust" checkbox under "Remove" in the copy settings dialog.Please note that scanned negatives are not in the scope of this feature at this time.  Dust spots on scans tend to be located in the focal plane, with the negative and very sharp, while sensor dust is typically positioned out of the focal plane and therefore not in focus. Scanned negative dust typically appears as white spots on a darker b

This post applies to Lightroom Classic and the Lightroom Ecosystem products. Camera Raw feedback can be found here.   Generative Remove makes it easier to remove unwanted objects and distractions with a simple gesture, even on complex backgrounds. For more accurate results, be sure to include the object's shadow in your selection and/or expand its size.    Detect Objects uses AI to find the objects underneath a brushed area. The masked areas will now appear larger than the Early Access version of this feature. You can also circle objects for quicker selection now.    We have also updated the spot selection experience to make it easier to manage variations, switch the fill type, refine the selection area, or re-generate as needed.    Batch updating is also now supported for Generative Remove spots.    Try out the latest updates and share your feedback with us here. Please also include the following details in your post:  App versi

Version: Lightroom Classic 15.4.1, macOSSteps:Export a JPEG with Content Credentials set to “Attach to files”, with only “Producer” ticked (“Connected accounts” and “Edits and activity” unticked).Export the same photo again with “Edits and activity” also ticked.Inspect the C2PA manifest in both files.Expected: with “Edits and activity” off, no edit information is included. With it on, edit information is included.Actual: both exports contain the full develop settings verbatim inside the ingredient metadata. That’s around 158 crs: fields, including white balance, tone, the full HSL panel and colour grading, plus spot-removal (RetouchAreas) positions. Ticking “Edits and activity” only adds a generic c2pa.actions list (opened, edited, color_adjustments, drawing) with no values. So the checkbox doesn’t control the detailed edit data; it’s always included.Regression: exports from Lightroom Classic 14.4 and 14.5.1 with the same settings do not contain develop settings in the ingredient metad

when trying to use presets I'm getting the error saying some AI models are downloading please try again later.   This is making the program unusable. 

This thread is for Camera Raw & Lightroom Classic feedback on the (Early Access) Content Authenticity Initiative (CAI)For the Lightroom Ecosystem feedback, click here.  The Lightroom team is dedicated to building capabilities that foster trust and transparency in the age of AI. Our latest release, as part of the Content Authenticity Initiative (https://contentauthenticity.org/), allows you to add content credentials to your work when exporting in Lightroom to ensure provenance and preserve authenticity.   New content credential capabilities are available across the Lightroom ecosystem (Lightroom, Lightroom Classic, Lightroom for mobile (iOS & Android), Lightroom for web), and Adobe Camera Raw in Early Access. When exporting a JPEG from Lightroom, you can attach your name, social media handle, and a list of edits via a digital signature.   You can find the option to apply Content Credentials while exporting a JPEG in the export panel. It is, by default, turned OFF

In Lightroom Classic 15.5 with SDK 15.3, suppose mask A is selected when a plug-in calls LrDevelopController.setValue for local exposure. If the user selects mask B immediately after the call returns, is the edit guaranteed to apply to A? At what point does Lightroom bind the edit to its target?Is there a supported API or callback that lets the plug-in confirm that this particular edit completed on mask A, even if B is now selected?