"re-installing the pic-time external uploader ... a faulty pic-time plugin"   There's clearly a conflict between the two plugins, but you can't conclude from this that the Pic-Time plugin is at fault. It may be simply that reinstalling the Pic-Time plugin changed the order in which LR loaded the two plugins, and that there is some issue inside LR with respect to TCP sockets. ... View more

Re the Loupedeck error messsages, the evidence strongly indicates that the Tourbox developer copied the Loupedeck plugin code and forgot to change one instance of "Loupedeck" to "TourBox" in an error message. Oops,   Details   The Tourbox and Loupedeck error messages are both coming from the Tourbox plugin's file InitPlugin.lua:     $ strings Tourbox.lrplugin/InitPlugin.lua | grep "needs access" Loupedeck needs access to tcp ports, but failed to make a connection. TourBox needs access to tcp ports, but failed to make a connection.     The Loupedeck plugin (now called "logiplugin" after their acquisition by Logitech) has very similar error messagew for its InitPlugin.lua:     $ grep "needs access" logiplugin.lrplugin/InitPlugin.lua LrDialogs.showError("Logi Plugin needs access to tcp ports, but failed to make a connection.") LrDialogs.showError("Logi Plugin needs access to tcp ports, but failed to make a connection.")       The Loupedeck plugin doesn't compile its source-code files, so it's easy for another developer to copy the source code. Tourbox compiles its code, making it harder for another developer to copy the source code.   It sure looks like the Tourbox developer copied the Loupedeck code and neglected to change "Loupedeck" to "TourBox" in one of the error messages. ... View more

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   @valentinosh: "i do it to remove a face and in the place it generates new faces...lots of time those stuf doesnt work, creating lots more of work"   If you select a face but leave parts of the body unselected, even parts that are disconnected, Remove will generate a replacement that tries to match that body. Select all of the body along with the face.    See this short article for 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.   "why not put a tab , with the old options ? like cloning and stuff"   The older Clone, Heal, and Content-Aware modes are still available:       ... View more

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   Often, Remove doesn't match tones well in flat tonal areas, as in your example. Sometimes you can fix that by selecting a larger area:    (You can get rid of the newly added wall outlet with a second application of Remove.)   Other techniques for ameliorating a tone mismatch: make the selection more raggedy; use short strokes with the Heal tool around the boundary to get better feathering; use the Brush mask and set Texture, Clarity, and Sharpness low to blur the area.   ... View more

According to the Exiftool utility, it looks like you have a new camera model, the Sony RX100M7A, not the RX100M7: [EXIF] Camera Model Name : DSC-RX100M7A   This model is not yet supported by Camera Raw / Lightroom.  You can submit a request for the camera model to be supported here: https://community.adobe.com/t5/camera-raw-discussions/p-new-camera-raw-file-support-requests-amp-information/m-p/12354770   I wouldn't assume that Adobe will automatically learn about the new camera model, so be sure to submit the request. Even Sony's web site lacks useful information. I can find very little about the RX100M7A there, other than a help guide and accessories that support the model:   Help Guide: https://helpguide.sony.net/dsc/2410/v1/en/index.html   Google search: https://www.google.com/search?q=%22rx100m7a%22+site:sony.com&sca_esv=f4ec9ff83705f9fe&rlz=1C5CHFA_enUS1064US1064&sxsrf=AHTn8zqfo-uxS2FI8TbPCNzV2KKEsgh0HA:1740844110877&ei=TizDZ4aeNZWy0PEP3JfouQw&start=10&sa=N&sstk=Af40H4VCuwucPQU_prKrUXYbOfiZFB62CzCl-b2zoJ8HCtjXXF2dLL4ovBc9ELrjexp9g39OCdKxxuwt3xKItJk7DnMmvfeA4E9VJA&ved=2ahUKEwiG_dnWnemLAxUVGTQIHdwLOscQ8NMDegQILBAW&biw=1562&bih=906&dpr=2    Sony's web sites are notoriously bad. ... View more

I'm not observing that problem.  While I've filed bug reports on other issues with photo orientation, I haven't see this problem before. The most efficient way to troubleshoot this is to upload one of the camera-rotated photos and one of the manually rotated photos to Wetransfer, Dropbox, Google Drive or similar free service and post the sharing link here. ... View more

Normally, the Remove mode (Clone, Heal, Remove with Generative AI, Remove with Content Aware) is sticky, as you can see in this screen recording: https://www.dropbox.com/scl/fi/xrbm0ic2i6czmug6ir66n/remove-mode-stick.2025-02-28.mp4?rlkey=30abnhcx69dt3bqxdvqvwvx4m&dl=0   If your LR isn't behaving that way, try resetting 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. ... View more

I have long used my RX100 VII with LR without problems. The most efficient way to troubleshoot this is to upload one of the problem .arws to Wetransfer, Dropbox, Google Drive, or similar and post the sharing link here. ... View more

"I’d like to think that the Lightroom Classic plug-in API wouldn’t allow for a conflict between two control surface plug-ins trying to talk to Lightroom Classic at the same time, but I don’t know enough about the Lightroom Classic plug-in API. Maybe @johnrellis would know if that’s even a possibility?"   There's a possibility for conflict if both plugins choose the same port number on which to listen for connections from their respective external apps.  So disabling one of the plugins is a good way to test for that.   It's also possible there's a bug in LrSocket, but that seems unlikely too.   Seeing the precise error message from Loupedeck could help clarify things.     Running pirated copies of software sometimes involves modifying the /etc/hosts file to prevent the software from phoning home, and depending on how the hosts file was modified, a side effect could be to disable the proper operation of "localhost", the loopback address LrSocket would use to connect to other apps' sockets on the computer. So seeing the contents of /etc/hosts could eliminite this possibility. ... View more

Moderators, @Rikk Flohr: Photography, please merge with this Bug: https://community.adobe.com/t5/lightroom-classic-bugs/p-photo-getdevelopsettings-does-not-always-return-all-valid-values/idi-p/14331997 ... View more

"For RAW originals: Unless you send the .xmp file associated with the Raw, the exported JPG does not contain the final edit instructions or presets."   Unfortunately, that's not necessarily correct. If the option Catalog Settings > Metadata > Include Develop Settings In Metadata Inside JPEG, TIFF, PNG, and PSD files is checked (the default), then the detailed develop settings will be included in the file and easily examined using a free utility like Exiftool. Uncheck that option to prevent the develop settings from being exported. ... View more

Another troubleshooting step:   1. In Finder, do the menu command Go > Go To Folder.   2. Type "/etc" and hit return.   3. Right-click the "hosts" file and do Open With > Textedit.   4. The file contents should be: ## # Host Database # # localhost is used to configure the loopback interface # when the system is booting. Do not change this entry. ## 127.0.0.1 localhost 255.255.255.255 broadcasthost ::1 localhost   5. If the contents are anything else, copy and paste it here. ... View more

If Conrad's good suggestions don't help, please post a full-resolution screenshot  of the Loupedeck error message. It may be similar to the Tourbox error message, but I'm skeptical it's identical. ... View more

Here's an example of how to change the controls displayed dynamically (see the attached screen recording):   local LrDialogs = import "LrDialogs" local LrView = import "LrView" local f = LrView.osFactory () local nRows = 1 while true do local rows = {spacing = f:control_spacing ()} for i = 1, nRows do table.insert (rows, f:static_text {title = "Row " .. i}) end table.insert (rows, f:push_button {title = "Add row", action = function (button) nRows = nRows + 1 LrDialogs.stopModalWithResult (button, "refresh") end}) local result = LrDialogs.presentModalDialog {title = "Test", contents = f:column (rows)} if result ~= "refresh" then break end end   ... View more

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