Lightroom ecosystem (Cloud-based)

Product: Adobe Lightroom Desktop (Cloud-Based), Version 9.6Operating System: Windows 11Camera Equipment: Nikon Z8 and Nikon Z6 IIIIssue: AI-related C2PA metadata remains embedded in exported JPEG photographs despite disabling Apply Content Credentials.Description of the ProblemI am reporting an issue with Adobe Lightroom Desktop 9.6 involving the automatic inclusion of C2PA Content Credentials in exported JPEG photographs.My original images are authentic photographs captured using Nikon digital cameras. During normal post-processing, I occasionally use Lightroom's Generative Remove tool to eliminate minor distractions, such as unwanted shadows, lines, or small objects.These are genuine camera-captured photographs, not images created entirely using generative AI.Despite explicitly disabling Apply Content Credentials during export, Lightroom continues to include C2PA metadata identifying AI involvement in the resulting JPEG files.This behavior creates problems when photographs are publis

Hi All, tl;dr need gallery that clients can use to choose photos for editing. The more automation, the better. I am quoting to shoot 160 headshots for a company, and I want to streamline the photo-choice process. I'd like to upload 3-5 unedited photos per person into an online gallery (password-protected), and allow them to tick a box on their favourite, and then have that list of favourites automatically come back to me so I can edit the right ones. Ideally, it'd be great if Lightroom Classic (my database of choice) could import those choices automatically (and marking them with a flag, colour, or star rating). I have the vague notion that Lightroom CC may be the way to go, but I've never used it and am not sure if the niche need I have can be done or not. Can the Adobe Cloud ecosystem give me this functionality? (I am a subscriber to the entire suite). You see, I normally shoot 20 or fewer people at a time (I usually work with much smaller companies), so for

Somehow I managed to hide the letter “I” info and ratings. This was located beside the Lr logo in the top left side of Lr mobile. I’m running the latest Lightroom mobile version. This was a shortcut that I use frequently. Now it’s gone. Any idea how to turn this back on?   

I usually pay for my Lightroom subscription monthly, I changed that last month to a yearly subscription and since then, I’ve not be able to use the pro version. I’m getting notifications that I have to subscribe for the pro version even after it shows on my App Store that I have successfully paid for a year’s subscription 

Description of Issue- While culling in Detail view with the arrow keys, every photo step starts a Camera Raw task named "find transparent" on 6 worker threads. In three Time Profiler recordings it used 39%, 46% and 54% of all of Lightroom's CPU: more than decoding, demosaicing and rendering the photos put together.- It happens with the Crop tool closed and no editing. In two of the recordings only D and the Left/Right arrow keys were pressed.- It's specific to Detail view: moving through the same photos in Grid view with the same keys runs no check at all, and Lightroom uses 0.18 cores instead of 5.2- It runs for every photo, whatever the camera, lens, file type or crop, and it found nothing: all 79 checks over 55 photos from a Sony A7R III, a Panasonic GH5 and four iPhones (ARW, RW2, HEIC and JPEG; three cropped, one of them also straightened 4.9°) left hasVisibleTransparentAreas false. Each check cost about the same, 1.5–2.2 CPU-seconds, for 12 MP and 42 MP photos alike.- Its result

Lightroom displays HDR photos on the iPhone Duo's outer screen, but not the inner screen. HDR becomes unavailable when unfolded and works again when folded.

Description of Issue- While culling in Detail view with the Edit panel hidden, each photo step spends about 0.3 s of main-thread CPU recomputing the Optics panel's lens-profile properties (lensProfileName, lensProfileMakes, lensProfileLensNames, lensProfileNames in AgCameraRawControllerLensCorrection.lua). In a 60-second recording that was 14.9 of the main thread's 26.3 CPU-seconds (57%).- The expensive one is negative:getLensProfileName (the lensProfileName getter): about 94 ms per call (up to 115 ms), 3–4 calls per photo. Lightroom can't respond to input during each call. - Why each call is slow: to name the photo's profile, Camera Raw classifies every lens profile by maker. For each profile it searches up to three name fields for each of 50 maker names ("Canon", "Nikon", "Sony", ... "REEFLEX") with a byte-by-byte case-insensitive substring search, after a series of mount tests ("Leica R", "Sony FE", "Zeiss ZE", ...). Lightroom ships 3,633 lens profile files. The classification never

Description of Issue- Lightroom's live AgTimerMac objects (AgSubstrate) keep accumulating: 226 just after launch, 224,705 after 34 minutes of culling, 950,048 after 8 more days idle in the background. Some are released (44,000 within 2 minutes of leaving Detail view), but far fewer than are created.- Memory grows with them. Left open in the background with no interaction, the same process grew steadily by ~0.25 GB per hour (~6 GB per day) whenever the Mac was awake: 6 GB → 29 GB over 8 days, during 3½ of which the Mac was asleep.- Most of the growth is small allocations made through the Lua VM. The churn also leaves the small-allocation zone heavily fragmented: 20.9 GB dirty against 8.1 GB of live allocations.- For long stretches, the main thread runs a timer loop: an NSTimer fires, calls into Lua (AgSubstrate → lua_pcall), and the callback invalidates and re-creates a run-loop timer (CFRunLoopTimerInvalidate → __CFArmNextTimerInMode), ~6,400 times per second at a flat rate, independen

Description of Issue- When culling in Detail view, moving to the next photo makes Lightroom download that photo's full original raw (~59 MB for a Canon R5 II CR3) from the cloud, even though a local smart preview (2560 px proxy) exists for every photo (all proxies are stored locally) and Detail view is at fit-to-screen.- Culling a large shoot therefore downloads hundreds of GB. macOS flagged Lightroom for writing 137 GB in 13 minutes (173 MB/s) during one culling session.- The writer is the libcurl write callback inside WichitaFoundation: the heaviest stack in the macOS disk-write reports ends in WichitaFoundation → fwrite. That function multiplies size × nmemb and only writes when the HTTP status is below 400, and WichitaFoundation contains a statically linked libcurl (CURLOPT_* and Content-Range strings). Step-by-step Reproduction Instructions1. Use a cloud library where originals are not all stored locally (Preferences → Local Storage: "Store a copy of all originals" off) but all sm

Lightroom Classic wont open. Says application not responding. I uninstalled and reinstalled. Still doesn't open.

Very upset as I got Charged credits for using AI Sharpen, yet the system didn’t complete sharpening the photo?? It glitched and wanted me to try again?? This sucks...take us back to manual please no failure AI…..and pls give me back my credits you falsely took!

When I view my filmstrip, there is no way that I can see what number photo I am on, such as #135 out of 300. I can only see how many images I have selected, but not what number an individual image is. This is very frustrating because when I share an album for someone to view in a browser or on their phone, it clearly displays the images with their sequential matching numbers. When people tell me the like “#6, #100, #200, etc.” I have no way to reference this in my lightroom app. I do not think requesting that my friends make adobe accounts in order to use your cloud features is reasonable, as they only want a few images and sending me the numbers should be all that needs to happen. I find it incredibly frustrating that something as simple as numbering photos is so poorly implemented into this app, yet you keep pushing ai features that I wish I could remove entirely.

When I open a photo and AI sharpen it, then export it immediately, it tries to export as an MP4 instead of a JPEG. I have to quit Lightroom and reopen it before I can export to a JPEG.