Copy link to clipboard
Copied
Posted by:
Update (Dec 2024): With the new release, it is no longer necessary to perform Generative Remove Operations prior to Cropping.
Copy link to clipboard
Copied
Trovo l'ultimo aggiornamento molto peggiorativo rispetto alla versione precedente che reputavo ottima. Rimozione generativa lentissima e a scatti. Ad ogni operazione di rimozione lasci fastidiosissimi aloni chiari. Diventa tutto molto complesso. Urge patch di correzione.
Copy link to clipboard
Copied
@vincenzo_6388: "With each removal operation you leave annoying light halos."
Please attach full-resolution screenshots (not phone pics) of the ENTIRE LR window showing the photo after you've made your selection of the object and then after you've clicked Remove. We'll then see exactly what's going on and can likely provide an easy solution.
Copy link to clipboard
Copied
Generative removal has to be done again for ALL masks in the catalog and this causes errors in already finished images and also means that all newly created masks are deducted from the monthly available credits? WHY?
Copy link to clipboard
Copied
Tried to remove a tree trunk but it simply replaced it with a smaller section . I also tried extending the selection quite a way into the background but got a similar result. Went into PS and removed it with the remove tool.
Copy link to clipboard
Copied
Hello,
since today i have the problem, that a few minutes after removingan object an exclamation mark appears a few minutes later to indicate that it needs to be updated. The removed object is then back and I can start again from the beginning. What is the problem?
Copy link to clipboard
Copied
Next problem: I updated the masks in Lightroom Classic and then Lightroom Mobile tells me on the same image that I need to update the masks AGAIN. Each update reduces the monthly credits...REALLY?
Copy link to clipboard
Copied
Please make the remove properties mantained from one picture to others. I have to "update settings" after each use to remove some spots or areas. It's nonsense... if i don't want to use, I don't copy "remove" properties. It's a lot of time wasted.... in previous version it works like a charm this option. Now I have to wait 10-15 sec for every picture even it's not used generative AI. Apart from this inconvenience, generative AI works fine in Lightroom.
Copy link to clipboard
Copied
What do you mean by "Please make the remove properties mantained from one picture to others."
.
Copy link to clipboard
Copied
Warum muss ich, wenn ich ein unerwünschtes Objekt entfernt habe beim nächsten Öffnen von Lightroom das bereits entfernte Objekt nochmal mit "Aktualisieren" erneut entfernen? Das macht doch - ausse mehr Arbeit - keinen Sinn, oder?
Copy link to clipboard
Copied
To all users having with Remove (i.e Gen Remve doing a poor job OR replacing object with another object) then use the "Report Variation" menu.
You can send the images to Adobe so that eventually can train the Ai.
Unfortunately you must add a description of the problem because there are no checkboxes for "Quality issue" or "Replaced instead of Removed"...the two common case of Generative Content failure that so many of you are experiencing, that we all experience daily.
Adobe will hopefully issue Firefly credits refunds.
.
Copy link to clipboard
Copied
So far the results I got were much better than with the old tool, but in my case, changing the tool/circle size is extremely slow. There's a huge delay when I turn the mouse wheel or use the square brackets, doesn't matter. Did not have the same issue with the old version.
Copy link to clipboard
Copied
I am using the latest version of Lightroom Classic. When removing objects on a DNG file everything goes well. Later on, when reviewing my photos before exporting them, I realise that the objects I had removed in some of my photos are still visible. Going to the Develop Module I realise there is a red dot under the remove tool and a message saying ''Some Remove settings need to be updated''. I update them and minutes later I have to go over this process another time. It doesn't seem to keep the changes. Am I the only person having this problem? Is it a bug in the software? Am I doing something wrong?
Copy link to clipboard
Copied
I just experienced exatly the same issue. Except that there was no indication of an issue before exporting. I exported and saw that the removed objects were still visible in the JPEGs. After performing the update all looked good. Still very annoying.
Copy link to clipboard
Copied
I have been doing this over and over and over adn over again all day. The only work around i am finding is ediitng and exporting each photo one by one because the moment i move to the next photo the AI edits are gone on the previous. GIGANTIC waste of time!
if anyone has a fix please let me know!
Copy link to clipboard
Copied
I am not a fan of the new AI generative features in lightroom classic. It casues continual issues of having to update the masks. I edit one photo, and a few previous ones need to be updated. I edit another, and a few other masks fail. It is a HUGE time waster.
Copy link to clipboard
Copied
This facility simply doesn't work. Do we have to go to anoher product to get rid of unwanted items? How do I get back to a previous version of the product . It worked!!!
Copy link to clipboard
Copied
None of the remove/heal/clone options in Lightroom Classic are working for me in the new update. What am I doing wrong?
Copy link to clipboard
Copied
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
@marklSanDiego: "None of the remove/heal/clone options in Lightroom Classic are working for me in the new update."
As a first step, make sure the Opacity slider is set to 100:
If that doesn't help, please describe in detail the steps you're taking and what you observe.
Copy link to clipboard
Copied
There is no opacity slider:
Copy link to clipboard
Copied
In LR 14, the Opacity slider only appears after you make some brush strokes.
There have been a number of reports in the past year of LR setting the slider to 0 by itself.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
@marklSanDiego: "the opacity was down to 40%"
Glad it was fairly easy to resolve. These random changes to Opacity don't strike the overwhelming majority of users, but it's occurred enough times in reports here that it's become an FAQ.
Copy link to clipboard
Copied
@John R Ellis Opacity slider was available whenever we created a new stroke.
It was removed for the Ui for LrC 14 so now the user must first paint then change Opacity.
This leads a problem.
If one sets an existing Remove to Opacity X then even the next new one will be at Opacity X.
1. So set an existing Remove/Clone/Heal at Opacity 0.
2. Create a new one.
Result: The new one will start at Opacity 0 because we can't set it before painting anymore.
We complained.
Copy link to clipboard
Copied
absolute garbage. whatever you did makes lightroom impossible to use. if I use AI to remove say hair from one photo and them remove background components from another photos, and then something from another, every single photo i used Ai on gets Red dot and a message that says "some remove settings need to be updated" and i have to go through every single photo and hit update, and by the time i get to the end and update all my photos they all have the same red dot and message.
it is literally like, the AI wants the same exact edits on every single photo.
Lightroom is no completly unusable and of course becuase it updated my library i can't go back to the old version.
You have literally cost me days of work to have to now do all editing in photoshop or export every single photo out of RAW to JPG as i edit them so that the edits i make don't go away.
FIX THIS NOW. THIS IS COMPLETELY UNACCEPTABLE
[abuse removed by moderator]
Copy link to clipboard
Copied
so telling you that your update is garbage is abuse? WOW. if not for having a backup, you wold have cost me literally tens of thousands of dollars in lost work.