New AI DeNoise breaks my Publish Service workflow

Forum|Forum|2 years ago
April 29, 2023
2 replies
589 views

I'm looking for suggestions on how to proceed, if there are any. I hope I am overlooking something simple here. The fact that AI Denoise in Lightroom Classic 12.3 creates a brand new file, with a different file name, breaks how I use Publish Services.

In the past, whenever I made editing changes to a photo, any Publish Service that the photo was in would overwrite the existing photo with the photo that had the new edits when I told the Publish Service to actually Publish.

Now, with the AI Denoise creating a brand new file, while leaving the original (edited) file unchanged, means that this new AI Denoise version of the image is seen as a new image that needs to be published, but it doesn't remove the previous (non AI Denoise) version of the image. I think all of the above applies to any Publish Service. It's even worse with my Flickr publish service (using Jeffrey Friedl's plugin) because all the views and favorites and comments on Flickr stay with the original image, and the AI Denoise version shows up with zero views, zero favorites, zero comments. Not what I would like to happen. Yes, for Flickr I can manually make all these corrections so that the AI Denoise version retains all the views, favorites and comments, but I don't want to do this manually, I'm hoping there is some smarter and automated method that I haven't figured out.

This topic has been closed for replies.

GoldingD

Legend

The Enhanced Denoise photo is a new separate photo. Adding it to a publish service is easy. Not any different from adding say a imaged sent to a third party editor, or to PS. Just add it to the service, and publish.

J

Jao vdL

Community Expert

OP wants to apply the denoise to long published images and replace the image that is already on the sharing site (e.g. flickr) with the newly denoised imageand not lose all the comments and likes to it in the process. Just publishing the newly created image and unpublishing the other will make you lose all of that. I have wished this was possible for many years. All it needs is for the publish service to be able to associate another image with an already published image and then mark it as out-of-date so you can publish the updated image to the same location and not lose likes and comments or to need to create another link to the image if you're sharing it from your website on social media for example.

J

Jao vdL

Community Expert

You need to simply only publish the image after you have edited it completely including denoise, not before. What you see here is true for any edit that creates a new file such as editing in photoshop, editing in Topaz tools, doing a denoise, etc. The new file will not be published but it will still be publishing the old image.

That said, I would love to be able to point already published images to new source images but that is not possible in Lightroom currently. Could be a good feature request.

dj_paigeAuthor

Legend

Thanks. I guess I didn't make it clear that my question was mostly about already published images, for which there is now a new AI Denoise version. I will make a feature request (or can this be moved to "Ideas"?)

J

Jao vdL

Community Expert

Yeah would need to be a feature request. A forum administrator can change the type of the post but it is probably better to write this as a feature request. This is a very old problem all the way from the beginning of publish services and I am sure there are already requests for this around. I've certainly run into this for many years and have wished (and asked for) there was a way. Any time you do an edit that creates a new file, the publish service keeps referring to the non-edited image. It should be possible to design a GUI that allows you to connect a new image to a published image.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded