"This where the SDK and the Programmers Guide is so misleading and confusing."   Agreed. Though the original bug report was marked as "fixed", the API Reference was never updated.  And the Guide has all sorts of little errors like this. ... View more

Your post has already been merged with the existing feature request in the forum's Ideas section, for 4K slideshow video. It's one of the more popular feature requests, with 41 upvotes. (Unfortunately, it's also eight years old.) Make sure you click the upvote button at the very top of the thread if you haven't already. ... View more

This script is setting the "bind_to_object" property of the various controls to strings rather than property tables: bind_to_object = 'p.group' bind_to_object = 'p'  When I change those to: bind_to_object = p.group bind_to_object = p your first script appears to work as intended. ... View more

Moderators, @Rikk Flohr: Photography, please merge with this existing Idea: https://community.adobe.com/t5/lightroom-classic-ideas/p-ability-to-export-4k-video/idi-p/12248648 ... View more

@Richie Vitale: "my belief that Lightroom has dropped the ability to bulk denoise files."   You can apply Denoise to a batch of photos in both LR Classic and LR Desktop. See this pinned reply at the top of this thread from Adobe employee Rikk Flohr: https://community.adobe.com/t5/lightroom-classic-discussions/p-how-do-i-batch-edit-denoise-june-update-lrc-14-4-amp-lrd-8-4/m-p/15374288#M406636 ... View more

"how these all got stacked? Does stacking occur when selected photos get ratings or color tags?"   Applying tags or ratings won't stack photos.  Perhaps you accidentally typed the keyboard shortcut for Photo > Stacking > Group Into Stack (Ctrl G) when the photos were selected. ... View more

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   Unfortunately, Adobe developers won't pay much attention unless this can be replicated by others (especially them). Your screen recording suggests that there were other edits applied to the problem photos, which might help trigger the problem.   I observed two screwy things in your screenshot and screen recording, to which you alluded:   1. The position of the slider doesn't correspond with the numeric value:   Often when the user interface is acting up, resetting LR's preferences fixes it: 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.   2. The AI Edit Status button is yellow, but when you click on it, it doesn't show any other settings that might affect Denoise:   Then nothing happens when you click on Update.     There are many reports here of AI settings needing constant updating and updates not taking effect. The catalog's .lrcat-data file stores the results of AI settings, and if it gets corrupted for some reason, or if there is a permissions issue, that could cause these symptoms.  When the file gets corrupted, the only remedy is to delete it and let LR rebuild it, as described here: https://community.adobe.com/t5/lightroom-classic-discussions/p-ai-masks-require-updating-and-or-disappear/m-p/15514958#M414181   While most of the AI commands will be correctly recomputed, there will be new variations computed for Generative AI Remove, which you'll have to review and adjust individually, if necessary.   Alternatively, you could create a new catalog (which will create a new .lrcat-data file) and see if the issue occurs again.   3. Have you used the Imagen AI service at some point? It had a nasty bug that permanently corrupted the .lrcat-data file.     ... View more

With your 12 sample pics, I too observed that syncing Denoise from the first to the succeeding 11 worked correctly. I then changed the Denoise slider of the first pic and synced that to the rest, and that worked correctly too.  To actually see the noise, I applied a Tone Curve. Take a look at the attached screen recording to see if you consider those results correct (I edited out most of the two minutes of Denoise being synced initially to the the other 11 pics.)           ... View more

"All the Macs in our studio are connected to the same network, so it can't be a firewall issue."   Not necessarily -- firewalls can look at both where packets are coming from as well as to where they're going, and they look at the content of the packets as well (which differ among your computers). And it may not be the firewall on your local router but somewhere deeper along the path from the computer to Adobe's servers.   As a diagnostic step, try connecting a problem Mac to another network, e.g. the hotspot on a cell phone or a neighbor's Wifi. ... View more

@Espen Frivold: "Graphics Processor Info: DirectX: NVIDIA GeForce RTX 3070 Ti (32.0.15.7700) - 8 GB"   Before reposting in the correct forum, make sure you update to the latest Nvidia Studio driver: https://www.nvidia.com/en-us/drivers/details/254262/    (Your current driver two months old.) ... View more

"value = bind(  'a', 'p.group' )"   I don't see a two-argument form for LrView.bind() documented in the AP Reference or the SDK Guide, and it doesn't work in my testing either. However, I did observe that these other three methods did work for referencing a second property table in an LrView control hierarchy:   - bind {key = "key", bind_to_object = prop2}   - bind "prop2.key"   - Setting the property "bind_to_object = prop2" in a nested part of the control hierarchy.   This script illustrates all three methods: local LrBinding = import "LrBinding" local LrDialogs = import "LrDialogs" local LrFunctionContext = import "LrFunctionContext" local LrView = import "LrView" local bind = LrView.bind local f = LrView.osFactory() LrFunctionContext.callWithContext ("main", function (context) local prop1 = LrBinding.makePropertyTable (context) prop1.prop2 = LrBinding.makePropertyTable (context) prop1.value, prop1.prop2.value = "prop1 value", "prop2 value" LrDialogs.presentModalDialog {title = "Bind", contents = f:column {bind_to_object = prop1, spacing = f:control_spacing (), f:static_text {title = bind "value"}, f:static_text {title = bind "prop2.value"}, f:static_text {title = bind "value", bind_to_object = prop1.prop2}, f:column {bind_to_object = prop1.prop2, f:static_text {title = bind "value"}}, f:static_text {title = bind {key = "value", bind_to_object = prop1.prop2}}}} end) ... View more

Moderators, @Rikk Flohr: Photography, please merge with the main thread on this topic: https://community.adobe.com/t5/lightroom-classic-discussions/p-how-do-i-batch-edit-denoise-june-update-lrc-14-4-amp-lrd-8-4/m-p/15374288 ... View more

You can copy the Denoise setting to a batch of photos in the same way you copy any other Develop setting (e.g. Exposure): Copy/Paste Settings, Sync Settings, via presets, or Auto Sync (that last option is dangerous, beware).  For example, see: https://community.adobe.com/t5/lightroom-classic-discussions/p-how-do-i-batch-edit-denoise-june-update-lrc-14-4-amp-lrd-8-4/m-p/15385170#M407384 ... View more

@denise_0053: "how do i create a modules folder?"   1. In LR, do Preferences > Presets > Show All Other Lightroom Presets. That will open Windows File Explorer or Mac Finder in the "Lightroom" settings folder.   2. Navigate into that "Lightroom" folder.   3. Create the folder "Modules" if it doesn't already exist. ... View more

"Edit one image, including the face mask. Copy everything to all the other images, including the mask. I manually stamp out small pimples on each image, and then I always get a message asking me to update the mask."    That's the way LR is intended to work, though many find it confusing. If you apply the Remove tool on top of an AI mask, then LR wants to recompute the AI mask, since the Remove tool might have changed what the mask selected.      Note that you can update a batch of photos at once by going to Library Grid view, selecting all the photos, and doing the menu command Photo > Develop Settings > Update AI Settings.    ... View more

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   @desono5000000: "Shouldn't LR sort them like: MAY_1034.NEF, MAY_1035.NEF, MAY_1035-Edit.JPG, MAY_1036.NEF....?"   Windows LR normally sorts the file names in that order:     This is the same order as in Windows File Explorer:        (Note that Mac LR and Mac Finder put MAY_1035-Edit.JPG before MAY_1035.NEF.)   If you're seeing something different, then:   1. Do View > Options > Grid View and change Compact Cell Extras to show File Name on top of the thumbnail. Then change Show Grid Extras to Compact Cells:   2. Post a full-resolution screenshot of the entire LR window in Grid view, including the left column showing the currently selected Collection or Folder.         ... View more

@Uday32183416ueoc: "Any idea when Adobe might release all the profiles for RAW (DNG) photos taken using Pixel 10?"   The Pixel 10 is not yet supported by the LR ecosystem: https://helpx.adobe.com/camera-raw/kb/camera-raw-plug-supported-cameras.html Support for a new camera from a leading manufacturer typically comes in the LR release following the release of the camera or, less frequently, the second following release. A new version of the LR ecosystem comes out about every 8 weeks, so we might expect to see LR 15 the end of October (the week of Adobe Max). (I have no inside information on this, and Adobe never announces such things ahead of time.) ... View more

@Andrew34581870op5p: "Just recently got a new phone [Iphone 17]. Now whenever I go to edit photos there's an error message: Adobe standard is not available on this device"   The Iphone  17 is not yet supported by the LR ecosystem: https://helpx.adobe.com/camera-raw/kb/camera-raw-plug-supported-cameras.html Support for a new camera from a leading manufacturer typically comes in the LR release following the release of the camera or, less frequently, the second following release. A new version of the LR ecosystem comes out about every 8 weeks, so we might expect to see LR 15 the end of October (the week of Adobe Max). (I have no inside information on this, and Adobe never announces such things ahead of time.) ... View more

Moderators, @Rikk Flohr: Photography, please merge with this thread discussing the same topic: https://community.adobe.com/t5/lightroom-classic-bugs/p-sdk-lrview-bind-key-fails-when-quot-key-quot-contains-a-period/idi-p/12684846  ... View more

I had to dig up my notes from several years ago, when I filed a bug report on the then-undocumented behavior of hierarchical dot notation in LrView.bind(). Adobe's response to that bug report was to modify the description on page 98 of the Lightroom Classic SDK Guide, but they never updated the API reference for LrView.bind(). The Guide now reads:   "The required argument of LrView.bind() is the key name; by default, this is in the table that is already bound to the UI element; that is, the value of bind_to_object in the same UI element. This is inherited in the view hierarchy, but can be overridden at any level. The keys in the table are treated as “.” (dot/period) separated hierarchical key-value pairs, e.g. a key such as x.y would bind with the key y in the table bound to key x."   Note that only LrView.bind() understands the hierarchical dot notation for keys.  Indexing property tables and the addObserver() method do not recognize it.  And if you want nested properties recognized by addObserver(), the subtables also have to be property tables constructed by LrBinding.makePropertyTable().   With this in mind, I've attached a script "bind-nested.txt" that shows how to use nested property tables with the "value", "enabled", and "visible" properties of checkboxes and the corresponding observer functions. Save the script to the Scripts subfolder and restart LR; then run the script from the Scripts menu.   See the attached screen recording of the script in action.         ... View more

"the binding to my properties table p is placed at the very start"   Your code is setting the "bind_to_object" property in a section entry (as described on page 34 or the SDK Guide).  But it must instead be set within a view object, e.g. f:row() or f:checkbox (), and it appies to all hierarchically contained view objects. ... View more

@Rikk Flohr: Photography, please consider moving this to Camera Raw bugs. Denoise isn't working on high-ISO DNGs from the DJI Mavic 4 Pro Hasselblad camera.  Perhaps it has a similar cause as this acknowledged bug with the Ricoh GR-III X: https://community.adobe.com/t5/camera-raw-bugs/p-denoise-on-dng-from-ricoh-gr-iii-x-is-missing-luminance-denoise/idi-p/13736622 ... View more

I see the same problem with your sample photo.   I wonder if this is related to another bug acknowledged by Adobe, where Denoise doesn't work on DNGs from the Ricoh GR-III X: https://community.adobe.com/t5/camera-raw-bugs/p-denoise-on-dng-from-ricoh-gr-iii-x-is-missing-luminance-denoise/idc-p/15412902   In that instance, Adobe says that Ricoh needs to make some changes to DNGs, implying that the DNGs were not conforming with the DNG spec.  A partial workaround in that case, converting the camera DNG to lossy compressed DNGs via the menu command Library > Convert Photo To DNG, doesn't have any effect on your sample photo.  (While one person in that thread claimed that the workaround lost detail, they didn't back up the claim with an example.) ... View more

In views returned by Info.LrPluginInfoProvider, you need to set the the property "bind_to_object" to the property table. (The SDK Guide is ambiguous about this.)  Here's the code snippet from my Any Vision plugin: sectionsForTopOfDialog = function (f, prop) return { {title = "Settings", f:row {bind_to_object = prop, f:checkbox {value = bind "smallDisplay", title = "Use Any Vision on small displays"}},   Also, see this thread: https://community.adobe.com/t5/lightroom-classic-discussions/trying-to-persist-a-dialog-value-using-lrprefs/m-p/15447097 ... View more

I downloaded a few sample 100 MP DJI Mavic 4 Pro DNGs into LR 14.5.1, and Denoise worked well:      If updating to LR 14.5.1 doesn't help, then definitely share a sample problem DNG, as @dj_paige  recommended. ... View more

Does the command Photo > Stacking > Auto-Stack By Capture Time not work well for this? ... View more

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   @ISTO_Photog: "Generative remove is leaving the area way too light and reflective"   Your screenshot suggests you've applied Remove on top of an AI mask, e.g. Background.  Look in the Develop tool bar -- is the AI Edit Status button yellow? If so, click it and you'll see:     Click Update to recompute the Background mask so the removed area matches the background. ... View more

I just posted a long message in the bug thread trying to disentangle the elements of the .lrcat-data mess: https://community.adobe.com/t5/lightroom-classic-bugs/p-automatically-write-changes-to-xmp-can-t-be-used-with-denoise-on-large-numbers-of-photos/idc-p/15521245#M63501   It starts, "The road to software hell is paved with little expediencies that seemed harmless to the developers at the time.  Here's my understanding of how LR got into the current mess.  The expedient paving stones are:.." ... View more

The road to software hell is paved with little expediencies that seemed harmless to the developers at the time.  For the current mess, the expedient paving stones are:   - Using the .lrcat-data file as both a store for the develop parameters and as a discardable cache of develop results for enhancing performance.   - Storing both develop parameters and cached results in .xmp sidecars, rather than separating them into .xmp and .acr sidecars as Camera Raw does.   - When LR saves metadata to disk, it first copies settings and cached results from .lrcat-data into the .lrcat file.   - LR stores no random seed for the random algorithms of Generative AI Remove, so its generated replacement patches must be considered as develop settings rather than as discardable computed results that are cached for performance.   I think all of these expedient paving stones have resulted in unncessary architectural compications making it harder for the developers to think clearly about the proper design and implementation of Denoise and other expensive AI commands.   DETAILED HISTORY   Originally, all develop settings were stored only in the SQL database (.lrcat file). The stored settings were all "parametric", describing the function to be applied to the image (e.g. slider settings or brush strokes), rather than containing the resulting pixels of the function.   LR 11.0 introduced the computed AI masks Subject and Sky.  It also introduced the .lrcat-data file for storing the computed pixels of these masks as well as LUTs (color lookup tables) from imported enhanced profiles.   The pre-version-11 code for saving metadata to disk found all the develop settings in the .lrcat file. But version 11 stored the subject/sky mask pixels as well as profile LUTs in the .lrcat file, with the express purpose of making the .lrcat file smaller and making it faster for the Camera Raw engine to access these relatively large binary objects ("blobs").   Rather than changing the save-metadata-to-disk code to read those settings and results from the .lrcat-file, the developers found it more expedient to copy them from the .lrcat-data file into the .lrcat file before invoking the existing save-metadata-to-disk code. This expediency didn't create huge issues, though, since the pixel masks and LUTs compress well and are relatively small.   Another architectural confusion introduced in LR 11.0: The .lrcat-data file and .xmp sidecars are used both as a cache for storing the computed results of the sky and subject masks and as a store of the develop parameters of enhanced-profile LUTs.    The pixels of the sky and subject masks are not develop parameters -- rather, they're computed from the parameters (the presence of the masks in the Masking panel). You can throw away the computed pixel masks and LR will recompute the masks, producing the same exact pixels.  This is exactly how all the previously introduced Develop settings work.   Thus, you can throw away the .lrcat-data file and .xmp sidecars and the sky and subject masks will produce the same exact results.  For these settings. the .lrcat-data file is simply a cache for accelerating performance.   But for the LUTs of enhanced profiles, the .lrcat-data is the store of the "truth", in the same way the .lrcat file stores the truth of all the other develop settings.  If you throw away the .lrcat-data file and the enhanced profiles' .xmp files, LR isn't able to recompute the effects of the enhanced profiles because the LUTs are missing (all the other parameters of the enhanced profiles are stored in the .lrcat file). This is unlike develop presets, where you can throw away the presets' .xmp files and LR will still be able to render cataloged images, because the presets' settings are stored in the .lrcat file.   LR 14.0 introduced Generative AI Remove. One might think that the parameters of AI Remove are simply the brush strokes applied by the user and the index number of the chosen variant, both of which are small and can be stored in the .lrcat file without huge impact (as the strokes of the brush mask are stored).    However, Generative AI Remove is not mathematically idempotent, like all other develop settings. That is, if you reapply the exact same brush strokes to an image, the Adobe Firefly server will return different results each time. The Firefly AI algorithms have randomness built in to them, as many image-processing algorithms do. In a better implementation, that randomness would have been controlled by a "seed" number provided by clients like LR, so they could recompute the exact same results later; but that's not how Firefly is implemented, or if it is, LR isn't using the seeds, another design flaw.   Thus, the computed replacement patches of AI Remove must be considered as parameters necessary to render the image the same way each time, not as cached results. And since those computed patches are stored in the .lrcat-data file and .xmp sidecars, the files serve as the only store for Remove parameters, rather than as a performance cache that can be discarded.   Users of the Imagen AI service discovered this the hard way when Imagen AI corrupted their .lrcat-data files. The only fix was to discard the corrupted .lrcat-data files, resulting in different Generative AI Remove results for existing cataloged photos. (This was primarily Imagen AI's fault for writing their results directly into the LR catalog rather than using the SDK APIs -- shame on them.)   And then LR 14.4 introduced the new implementation of Denoise, in which the computed whole-image results are stored in the .lrcat-data file. These results are huge, typically 5 to 50 MB per image, depending on the degree of detail in the image, two to three orders of magnitude larger than all the other develop settings and computed results.   But the Denoise results are not develop parameters -- they can be discarded and Denoise will recompute the same exact results. The only parameters are the checkbox and the slider. But because it takes so long to compute Denoise, it's crucial that its results get cached for performance.   Up until Denoise, it didn't matter much that saving metadata to disk copied develop settings from .lrcat-data into .lrcat before writing them to the .xmp sidecars.  The needlessly copied settings were relatively small. But the huge size of Denoise compiled with saving metadata to disk bloats the .lrcat file, negating the original purpose of the .lrcat-data file.   And if LR reserved .xmp sidecars for parameters and .acr sidecars for computed results, as Camera Raw does, the LR developers might have thought more clearly about the architectural principles sooner and implemented saving metadata to disk properly. ... View more