@johnrellis  Here's a video of my code in action. It is theoretically possible to keep more than 3 variations per each Generative Remove but I had problems In the example 4 out of 5 variations work, 1 is bad. I don't know how to fix this, I am using what Camera Raw gives us. With the SDK I was hitting a wall. I should revisit this code, I kinda abandoned it. ... View more

@johnrellis  "I had to go through about 20 variations to find some good ones. Tip: When you're looking at variations, if you see a good one, create a snapshot to save it. You can then easily go back and review the saved snapshots to find the best one." It is possible to keep more than 3 variations. I have a code that does it BUT I found there's a table limit of max 5 variations (or I am just stupid and can't store more) So we could have the following: 1. User refreshes selected Gen Remove. 2. After refresh the previously selected variation is carried over. 3. The previously non selected variations (supposedly the bad ones discarded) are lost. Result : 4 variations  1 old best + 3 new. Frankly IMO any user that needs results with Generative Remove should just use Photoshop that: is two clicks away form LrC AND allows to keep 40+ variations AND allows type instructions AND erase the layer without generating more variations AND allows to generate similar AND etc...  Downside: user has a second file with the Gen Removes. .   ... View more

Thanks @johnrellis   Funny thing : I had actually considered a "make all upper case" code for all CorrectionName or or MaskName.         Guess it will  ... View more

Content Aware (renamed as Remove) is also good for spots or hot pixels. For small stuff it works.         ... View more

Many users speak there has been an update. Did we really get a new Model for remove? Because I see the same Model version for my old files and for those edited  now. i.e Before : 1.0.5-beta.1-1.2_1.2-8c2cea4-0.1.27.1r16.2, Now:     1.0.5-beta.1-1.2_1.2-8c2cea4-0.1.27.1r16.2  Some images have :  1.0.5-beta.1-1.2_1.2-8c2cea4-a6 Which rarely happened also with LrC 13 And this brings me to my complain: why is never possible to chose the Model version NOR is even mentions which one is in place? Midjourney show the version used for the Generative Content Adobe doens't. We can never tell which MV was used. We have ProcessVersion in LrC visible and selectable but not ModelVersion for Remove or even AI Masking. The only two users here that can tell which MV is in used by each Remove Ai are @johnrellis and me. .     ... View more

No, I can't By @ccullen22 Then you must restart the app. I can re-select the main window and make the modal window stay in background...but I can't dismiss it without quitting LrC ... View more

@Riju241992 what were you trying to remove ?       ... View more

@ccullen22  Check the attached video. You can't dismiss the shadow/empty modal window clicking the UI, like I do? . ... View more

Simply click elsewhere in the Ui. The ghost/empty window will stay in background.   Restart LrC if it's unbearable to work with the ghost/empty window(s).   DO NOT reset the preferences.   ... View more

@SJ_Pettit I recommended you to use Any Shortcut Plug-in by @johnrellis     Download it here : https://johnrellis.com/lightroom/anyshortcut.htm   .While we wait for Adobe you can have it today. ... View more

@Per Berntsen Yes I experience rhe same as @David ART   LRc still palys a sound when deketing Masks and Remove AND when an operation is non valid OR kbsc is doing nothing.   I believe at some point it was asked to mute any sound via a Preference.   @CMass I think you could pitch the option to the LrC team. Something like "Mute All Sounds" in the Preferences > General    I think that option should also affect Plug-ins. ... View more

That "swoosh" sound when deleting a heal or remove mark/point is infuriating! By @David ART That I fear can't be turned off...and neither the error sound. . ... View more

@ZimFromIRK if you disable the "Auto Save into XMP" then it will not appear in the Status and Acrivitity bar, that's normal...but perhaps it should appear but as "Dsisabled"   Anyway good to see you problem is solved.   I recommend doing a manual save of all your catalog as LrC does not detect photos with metadata-status "Has Been Changed" unless you view them in library. You might have photos not up to date. LrC will save ONLY the photos that actually need saving and skip the others .   . ... View more

It's in the Status and Activity Bar, click your Identify Plate   In the top left corner where the ID plate is do right click and show the "Auto save into XMP"   ... View more

@ZimFromIRK  Maybe a stupid thing to say on my part but check if you have paused "Auto Save into XMP" in the main catalog. ... View more

The shadow/empty modal windows can be dismissed by clicking the Ui. They come back BUT restarting is not strictly necessary to keep working.   So for instance I restart ONLY when it becomes unbearable to have multiple shadow/empty windows, like 4 of them.   I live with this bug a bit.         ... View more

Given the dozens of reports, I think there's a bug, perhaps in the upgrade process, that is setting Opacity to 0 in the preferences. By @johnrellis Very possible: The preference is this one: <key>AgDevelop_dustSpotOpacity</key> <real>1</real> The minimum allowed value is 0.01 I suggested to always set it to 1 for any new Remove but even this suggestion never was considered. . ... View more

Per Desing any new remove uses the last set Opacity in the preferences. e.g Set the Opacity for an existing Remove to 0 Crete new one The new one will have Opacity at 0 The team has decided to remove the Opacity slider upon creation from the UI (the slider was there in LrC 13) so we can't immediately crete a Remove at 100% opacity. I have been thinking about a plug-in taht notifies users at the Opacity is not at 100% BUT it would suffice to instead return that slider to the Ui as before, Many users had problems due to this ill fated UI redesign. The issue has been reported by me "in primis" nearly 6 months ago internally, but also publicly by other users: https://community.adobe.com/t5/lightroom-classic-discussions/p-remove-opacity-slider-has-changed-locations-in-workflow/m-p/14932300#M383618 . ... View more

Tool overlay and icon gets on the way when visualizing the different variations of the remove tool. Needs a toggle to hide it so you can better see the final results. By @juliaanastazja It's already doable. See screenshot Use "H" to hide or show the overaly...same KBSC also des it for masking. . ... View more

@Luz Photography  Opacity is set at 54 Set it at 100 ... View more

@richs61807160   A fix:   1. Do "Show in Finder". 2. Back in LrC do "Remove the selected photo form the catalog" instead of deleting it. 3. Using the finder/OS move the photo to Bin.    Now back in LrC all photos in that folder can be moved to  trash ... View more

I suggest to go back in history one step prior to the creation of the new Remove and do "Clear History Above This step". Quick way to do this to hold the Alt/Option modifier and clik on the step (above which you want to clear). Deleting the unwated Remove after having created it will only add more useless steps.   .   ... View more

Implementing Spots Extractions turned out to be very simple to do. See it in action in the video. . ... View more

The changes done in the current release DO NOT change the problematic situation with Remove. Yes we can now apply remove even if the image is cropped BUT it doesn't work well. Starting point. I paint the Gen Remove All works till now, I painted on the uncropped image. I then Crop the  image AND refresh the Gen Remove.   All seems good now as well...   Wrong!!! Look at the hidden reality: When the full uncropped image is revealed I can see the Gen Remove left an horrible blob on the tree outside the crop, something that didn't  happen when I painted on the uncropped image BUT because we can't do "Show Uncropped Image" I can't see the poor result of the refresh so I am led to believe all was ok (but it was not the case)   • The reality is that at all times we must always see AND paint the remove on the entire image otherwise we leave out parts necessary for the Remove to be usable in all situations...so we need the option "Show Uncropped Image" in LrC like in ACR to properly paint usable remove AND judge its quality when we refresh. Needless to say that painting a partial remove when the image is cropped delivers horrible partial results as the moment one changes the crop the remove must be redone/refined/completed.  ... View more

With the new API the SDK provided in the latest Update I have been able to implement  "Merge Spots" "Manage Spots" "Merge Spots" allows to combine any two spots into one, the same we can do when doing "Refine" but this is doable for all type of remove so also for Clone and Heal. Check the video. "Manage Spots" allows to delete specific spots within a "Spots Mask" E.g. An existing "Generative Remove" has a subtraction. At today we can''t get rid of the subtraction Masks alone (or the add mask) ...we must trash the entire Spot. With my code I can manage the existing Spot(s) properly and, like for masking, I can delete what I don't like selectively. Morale: a better workflow with Remove is doable. P.s. I will be evolving code and allow to "Extract Sub Spots" and even allow convert them to "add" or "subtract" within the same Spot (basically same conversion we can do for masking) P.P.S. I shows the plug-in in action with single spots but the plug-in obviously can merge complex/entire brush strokes. ... View more

This issue seems to be back. The Update Ai Modal Progress Window is not always disappearing EVEN if the update of Ai has finished. This happens when using the updateAiSettings argument in photo:applyDevelopPreset() I can't steadily reproduce it but it has happened when applying a preset (with Ai mask) on multiple images...attempting to stop the Modal progress Dialog didn't work and I had to restart the app. I am doing     LrTasks.startAsyncTask(function() catalog:withWriteAccessDo("Apply Preset and Create Snapshot", function() -- Step 1: Apply preset to each target photo for _, photo in ipairs(photos) do -- Apply the preset to the photo (virtual copy or original) photo:applyDevelopPreset(preset, nil, nil, true) -- Conditionally set the photo's copyName to the preset name if setCopyName then photo:setRawMetadata("copyName", presetName) end end etc...       ... View more