I forgot to mention that this workaround is slow -- about 0.25 seconds per photo on my computer. ... View more

"a field set with the photo:setPropertyForPlugin() function will be viewable by other plugins, but cannot be accessed or modified by other plugins."   Correct.   "This being in contrast to the photo:setRawMetadata() function which would be viewable and editable by other plugins?"   Correct. ... View more

@Astonished_Penguin5ED0,   There are two workarounds that may help with your symptoms:   1. Try deleting the Helper.lrdata folder: a) Do Catalog Settings > General > Show to open Finder / File Explorer on the current catalog folder. b) Exit LR. c) In that folder, delete the folder "<catalog> Helper.lrdata". d) Restart LR, and it will rebuild the folder. The Helper.lrdata folder caches information about metadata, keywords, folders, collections, and other things to speed the performance of LR and it can sometimes get corrupted. In recent versions, LR has used it more heavily to improve the speed of displaying metadata, and there have been a fair number of bugs with it.   2. For others in this thread, and especially if you see a spinning wheel, deleting the Helper.lrdata doesn't help, but rolling back to LR 14.0.1 does help. ... View more

@coryp21354218: The three non-generative-AI modes usually do very well with small spots. It would be interesting to see an example where it's failing -- attach a full-resolution JPEG exported from the unmodified original photo (not a screenshot). ... View more

Use the Clone or Heal mode for dust spots -- much faster, doesn't use Adobe severs. And just as good. ... View more

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   @Rikk Flohr: Photography, if the Web module isn't adjusting XMP face regions for cropped or rotated exported photos, that is a "bug" according to Adobe's definition -- LR isn't obeying the designed behavior publicly announced for Camera Raw 6.4 and LR 3.4.    In March 2011, Adobe employee David Franzen announced that Camera Raw 6.4 and LR 3.4 would be obeying the Metadata Working Group Guidance: https://www.lightroomqueen.com/community/threads/camera-raw-6-4-and-lightroom-3-4-public-betas-add-metadata-working-group-support.11522/      (See also his post below.)   The MWG spec defines how face regions are recorded in XMP metadata, and the spec requires that the regions should be adjusted when photos are cropped or rotated: https://web.archive.org/web/20180919181934/http://www.metadataworkinggroup.org/pdf/mwg_guidance.pdf    @MarkCulp  says the Web module adjusting face regions in exported photos, though the Export module does. Thus, the Web module wouldn't be obeying the MWG spec. By declaring the Web module's behavior "as designed" and not a bug, are the developers now withdrawing the public commitment to the MWG spec made in 2011, to keep their bug counts low?   --------------------------------------------     ... View more

@Rikk Flohr: Photography: If the Web module isn't adjusting the face regions in the exported photos' metadata, that is a clear bug according to Adobe's definition of "bug" -- LR isn't obeying the as-designed behavior publicly announced years ago.   Adobe employee David Franzen announced in March 2011 that Camera Raw 6.4 and Lightroom 3.4 now followed the Metadata Working Group Guidelines: https://www.lightroomqueen.com/community/threads/camera-raw-6-4-and-lightroom-3-4-public-betas-add-metadata-working-group-support.11522/    The MWG spec defines the XMP metadata fields for face regions and requires that the regions be adjusted when the image is cropped or rotated: https://web.archive.org/web/20180919181934/http://www.metadataworkinggroup.org/pdf/mwg_guidance.pdf   The Web module isn't obeying the MWG spec to which Adobe committed, though the Export module does obey it. Has the LR team withdrawn their announced commitment to that spec?   ------------------------------------------------------------------------------------------------------------------ From: Photoshop Family <noreply.photoshop_family@getsatisfaction.com> Sent: Wednesday, April 27, 2011 12:50 PM To: Photoshop Family <noreply.photoshop_family@getsatisfaction.com> Subject: New reply: "Lightroom 3.4RC not exporting XMP EXIF schema properties?"   David Franzen replied to Lightroom 3.4RC not exporting XMP EXIF schema properties?, a problem about Photoshop Family.   Lightroom 3.4 and Camera Raw 6.4 now follow the guidance provided by the Metadata Working Group for recording metadata in files that contain both native Exif and XMP packets. Photoshop CS5 was the first Adobe app to ship with MWG support, so Camera Raw and Lightroom are just catching up in this respect. A specific example germaiin to this thread is that most Exif properties are now only written once, in the native Exif block, and not duplicated as XMP tags in the exif: and tiff: namespaces. Where Exif properties are mapped to XMP properties outside the tiff: and exif: nameapsaces--for example the TIFF Artist tag is mapped to the dc:creator XMP property--the property values are kept in sync in both the native Exif and XMP (and native IPTC IIM for that matter). You can find the complete MWG specifications here: http://www.metadataworkinggroup.org/ WRT some of the other topics in this thread (like multi-byte text, and date-time handling)... well, the MWG specification really describes these issues better than I can, so I refer the technically curious to start there. A good, Adobe-hosted, place to ask follow-up questions WRT the MWG and metadata handling might be the Adobe XMP developers forum: http://forums.adobe.com/community/des.... There may be other relevant, non-Adobe forums as well. Go look at this reply This solves the problem! | Comment | Stop following this problem jsed   This message sent from Get Satisfaction. To unsubscribe or change your email settings, click here.   ... View more

@LightroomStatistics, recently while learning how LR builds previews, I discovered a workaround for this bug: Increment the photo's exposure by 0.01, request the photo's thumbnail, decrement the exposure by 0.01, request the thumbnail again. After doing this, the value of Temperature will be non-nil.   Here's a script demonstrating the workaround: local catalog = import "LrApplication".activeCatalog () local currentTime = import "LrDate".currentTime local message = import "LrDialogs".message local sleep = import "LrTasks".sleep local size = 50 local poke local function fix (photo) poke (photo, 0.01) poke (photo, -0.01) return photo:getDevelopSettings ().Temperature end function poke (photo, delta) local exp = photo:getDevelopSettings ().Exposure2012 catalog:withWriteAccessDo ("Poke " .. delta, function () photo:applyDevelopSettings {Exposure2012 = exp + delta} end, {timeout = 30}) local done = false local handle = photo:requestJpegThumbnail (size, size, function (data, err) if err then assert (err) end done = true end) while not done do sleep (0.05) end end local t = currentTime () local nNil, nFixed = 0, 0 for _, photo in ipairs (catalog:getMultipleSelectedOrAllPhotos ()) do if not photo:getDevelopSettings ().Temperature then nNil = nNil + 1 if fix (photo) then nFixed = nFixed + 1 end end end t = currentTime () - t message ("Test results", string.format ("size: %d, nil: %d, fixed: %d, time/photo: %f", size, nNil, nFixed, t / nNil)) ... View more

@Pinner Photographer: "the user interface is all over the place. I get half a box showing me the optional results that tries to display before the replace is complete. There is then some screen redrawing on the right panel and focus seems to come and go."   First troubleshooting steps:   1. Restart your computer.   2. Update your graphics driver by going directly to the manufacturer's web site: https://helpx.adobe.com/lightroom-classic/kb/troubleshoot-gpu.html#solution-4   3. Reset 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.   4. 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

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   LR does a good job of removing the wire from your screenshot:   Most likely you've applied Remove on top of a Sky mask. Do Settings > Update AI Settings to recompute the Sky mask. See this short article for Adobe's recommended order in which to apply editing operations: https://www.lightroomqueen.com/generative-remove-replace/   ... View more

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   Hmm, I'm not seeing that incorrect behavior. I took this photo with an identified face:   and cropped it:   and exported it with all metadata and then imported it back into the catalog. That newly imported photo shows the same location of the face rectangle.  Exiftool shows that the XMP description of the region in the original photo: [XMP] Region Rotation : 0.00000 [XMP] Region Name : Jamie [XMP] Region Type : Face [XMP] Region Area H : 0.16211 [XMP] Region Area W : 0.24340 [XMP] Region Area X : 0.52639 [XMP] Region Area Y : 0.21680   has been adjusted in the exported photo: [XMP] Region Rotation : 0.00000 [XMP] Region Name : Jamie [XMP] Region Type : Face [XMP] Region Area H : 0.31174 [XMP] Region Area W : 0.35340 [XMP] Region Area X : 0.31236 [XMP] Region Area Y : 0.41690   To make progress on understanding what you're seeing, select the original, cropped photo and do Metadata > Save Metadata To File, and then export it. Upload the original photo (and it's .xmp sidecar if it's raw) and the exported photo to Wetransfer, Dropbox, Google Drive or similar free service and post the sharing links here.     ... View more

@kumard30512702,  Apple released buggy graphics drivers for the AMD Radeon 5000-series GPUs, causing problems for many LR users. Many have reported that upgrading to Mac OS 15 solves the problem, but some have reported that it doesn't. If upgrading doesn't solve the issue, you can work around issues displaying photos in Develop and Library and exporting them by setting Preferences > Performance > Use Graphics Processor to Off. ... View more

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   @jakobv90966696: "also the generative fill seems to have a transparency"   Two possibilities:   1. After clicking Remove, make sure the Opacity slider is set to 100:   2. If you applied Remove on top of an AI mask (e.g. Sky or Subject mask), do the menu command Settings > Update AI Settings to recompute the mask.   If this 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

@Michael_Bues6754: "I always have issues with objects against the sky (cranes, power lines...)"   1. Uncheck Detect Objects -- it doesn't work well, especially with skinny objects and along the edges of photos.    2. If you applied Remove on top of an AI mask (e.g. Sky or Subject mask), do the menu command Settings > Update AI Settings to recompute the mask.   3. 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

My understanding is similar: Excire uses an external app to display it's UI, and that app communicates with LR via a plugin.  The UI displayed in the Youtube video in that linked article can't be implemented using the documented methods of the SDK. ... View more

 "I already saw some closed source plugins, which use similar widgets"   I've never seen that -- can you provide links to an example?   The SDK doesn't provide enough hooks to do such widgets. ... View more

"If I import, with an Adaptive Color (only) preset and 'Standard previews', the previews are built but the Adaptive profile needs to be updated.  After updating, the previews are not updated until the image(s) are then viewed/selected in subsequent processing."   Others have complained here that when you apply a setting or command to a batch of photos, previews aren't updated until their thumbnails become visible: https://community.adobe.com/t5/lightroom-classic-ideas/p-build-library-previews-in-the-background-regardless-of-their-having-been-visible/idi-p/15044055   See here for a plugin that corrects that: https://community.adobe.com/t5/lightroom-classic-ideas/p-build-library-previews-in-the-background-regardless-of-their-having-been-visible/idc-p/15138131#M23643 ... View more

@Brandon_Soto3638: "DirectX: NVIDIA GeForce RTX 2050 (32.0.15.7247)"   That's the latest Game Ready driver, but Adobe and Nvidia recommend using Studio drivers for Lightroom. You can download the latest driver here: https://www.nvidia.com/en-us/drivers/details/240529/    However, if you're seeing an error message when you try to use Generative AI Remove, installing the correct driver may not help. Please post a full-resolution screenshot (not a phone pic) of the entire error message. ... View more

Do these steps:   1. Go to the Library module. 2. Exit LR. 3. Start LR. 4. Go to Map.   Is the map visible? ... View more

@hanna_2225: "Generative Remove Failed. We've encountered an issue and can't complete your request at this time. Please try again later."   That badly written error message indicates that the Generative Remove command was unable to contact the Adobe Firefly servers to do the removal. Sometimes firewalls and anti-malware / anti-virus utilities incorrectly block some network requests from LR. Try these troubleshooting steps: - Temporarily disable all the firewall / anti-malware on your computer. If that solves the problem, then add a specific exclusion for LR to the firewall's rules. - Connect to another network, preferably one serviced by a different ISP. E.g. a Wifi connection of a neighbor, a coffee shop, work, or your phone's hotspot. Sometimes the routers in these networks block LR's requests, especially in authoritarian countries like China. To help others, please let us know which of these work and which don't. ... View more

I find it very hard to believe that the original product manager would have considered this behavior "as designed".   When you first open a new catalog and import a photo, you'll be asked, "Enable address lookup? ... Note: this operation can be paused/resumed at any time." The user's initial choice takes effect immediately.  But all subsequent changes don't take effect until after a restart, and the user isn't informed of that.  That's not really fulfilling the promise to the user that the operation can be paused/resumed any time. It's confused a number of users posting here.   If a product manager had designed the option to require a restart, surely she would have required the user to be informed. There is only one other option that requires a restart, Preferences > Interface > Font Size, and the user is warned, "Changes take effect after a restart".  Changes to all the other background processing options -- face indexing, automatically writing changes to xmp, replacing emedded previews -- take effect immediately. It's very straightforward engineering to implement immediate changes to address lookup, just as it was implemented for the other three background options. It's trivial to pop a warning when she changes the option that a restart is required.   Responses like this from the engineering team led me long ago to conclude they're more interested in keeping their bug count low. ... View more

@Leandro_Barreto: " I had better results and much more efficiency using Photoshop."   Note that Generative AI Remove in LR uses the same Firefly service as Generative AI Remove in Photoshop.  LR does have the Detect Objects option, on by default, which doesn't work well. That leads people to think PS's Generative Remove is superior to LR's, but if you turn off Detect Objects, you should get the same results in both apps. ... View more

@Leandro_Barreto, without example photos, your feedback won't carry that much weight with Adobe. There are dozens of "problem" photos posted in this thread, and with nearly all of them, we've been able to show how to quickly remove objects. ... View more

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   @ABkc4here: "I want to remove an object not add one."   Your screenshot is a good example of what happens when you don't select all the parts of an object (the red thread on the right) and the shadows cast by the object.   Here's what happens when I select the hallucinated object but not the thread or the shadows:   Selecting the dangling thread still generates a snowball, as Remove tries to match the unselected shadow:   Adding the shadow to the selection completely "removes" the object:   Note that I always uncheck Detect Objects -- it doesn't work well, especially with skinny objects and along the edges of photos.    See this short article for more details on how to remove objects 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

@Leandro_Barreto: "Learning my work in LR perhaps?! And if that is the case, this is dangerous, if not at least unethical. I felt like I was Adobe's little slave, unwittingly training its AI while it messed up my work and learned from my techniques."   Adobe Firefly (the service used by LR's Generative AI Remove) doesn't train on user content: https://helpx.adobe.com/firefly/get-set-up/learn-the-basics/adobe-firefly-faq.html Last year, there was a big brouhaha with many claiming that Adobe was training on Creative Cloud users' content. The brouhaha was caused by poorly written cover-their-legal-buttocks terms of service, but Adobe reacted quickly and significantly clarified theirs terms of service and their FAQs and help.       ... View more

@Leandro_Barreto: "I noticed that using AI removal in LR was CHANGING ALL THE LIGHTING IN MY IMAGE."   Many of LR's settings, such as Shadows and Highlights, are computed based on the current contents of the image (users have been quite satisfied with that adaptive behavior for many years). This is why Adobe recommends apply Remove very early in the workflow.   "but the original HDR image is sometimes too dark and needs to be worked on before using AI."   If you're having problems seeing the object to be removed, bump up Exposure, apply Remove, then reset Exposure.   ... View more

@Leandro_Barreto: "However, sometimes the worst possible result, such as replacing a vase with a HUMAN HEAD, or a pair of sneakers that turned into a child on a shelf. "   Let's tease apart the various issues you've described.  When LR "replaces" an object rather than "removes" it (by replacing it with innocuous background objects), that's usually because you haven't selected all of the object (even disconnected parts), its reflections, or its shadow. In that case, LR tries to generate a replacement matching what's unselected.   See this short article for details on 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

@Barry36212844cdld: "It happens only in the Develop module."   That's often a sign of an incompatible or corrupted display profile, not uncommon on Windows. Did you try the quick test described in the link that dj_paige posted above? ... View more