Denoise wasn’t slow at all. My circled areas were showing examples of the positive results I noted in the pink, annotated comments…. 
It was Wonder that was slow and the time quoted was entirely for Wonder2. I noted it in the Wonder processing feedback…
Great thanks for the clarification! I’ve relayed to Lingyu and the development team as positive feedback, let us know if any unwanted results do occur. I’ll leave the workflow reply as it could help anyone getting artifacts with PS/RAW files to avoid them.
Interesting. What OS do you use? I’m Win 11.
I just downloaded to give it a run.
Remove v. 2 in Phot 1.2.0 output:
Remove Tool in Photoshop:
Because it’s a blurry image and there’s bleed I had to cover the area where the bleed was with my Remove overlay.
The image was just a screengrab of a video to show the (known and aknowledged) issue, no real sense in removing that horn there. But all other real images I had on the PC at that moment were of persons that I didn’t want to upload in a public forum.
It’s a general issue on quite some systems (see those many similar reports) with NVidia GPUs with the Remove V2 tool. On the affected Systems it occurs every time regardless of the image or area you want to remove.
What is Phot 1.2.0? Can’t find this software, it’s so ambiguous name.
Here’s a clue what’s the name of this Category
If you look at the top left panel of this forum, it’s the current generation of this Topaz product. It’s in large bold letters. I abbreviate them as Phot (and Giga) to save time…
But that really looks strange - and typing Photo isn’t taking really any longer than Phot?
Thx! I use NVIDIA processors (4090 & 5090 - which I’m reading in the news are now fairly rare…). But know that sometimes certain systems behave more quirkily than others. So it made me wonder if that’s what was happening.
The thing that gets me is that the Removed objects keep coming back with subsequent processing steps.
When the processing for those steps complete, it goes away again. But those things should not reappear at all once removed. They shouldn’t be stubborn ghosts. IMO.
You don’t recog phot as photo? I test, so I’m always typing vers. #s & GPU #s too. To keep moving, I abbreviate. And, I used to have a beta forum to rpt sys issues. And, no more. So force of habit! My comments are for the devs (which means, developers).
@Fotomaker the Remove grey blob issue jo.vo flagged with Windows is specific to some RTX cards, but not all (example I have a RTX 4050 and can’t reproduce). We have in the development team ticket all the flagged cards and they are looking into a fix. The workaround fr users that experience this is to force CPU in the AI Processor if need to use Remove 2, which would bypass the card for now.
For the Remove showing the parts again when adding other enhancements, can you confirm what enhancements on your side? I want to make sure we are tracking the specific enhancement you are having issues with, if not already. We have an item opened already for Preserve Text and Recover Faces, showing up removed parts when used after Remove.
For shortening words internally, we use shortened TP vX.X.X (for the new app) vs TPAI vX.X.X (for the legacy app). If that can help, if you use those terms, we would know what you are referencing. TGAI, TG too.
I am puzzled. The release notes say Remove2 is not available locally for Mac Tahoe users, implying that cloud rendering is. However, I am seeing it greyed out completely. Is that intentional and when can we expect a fix?
The Releases mention Remove 2 is a cloud only model until further optimized with a warning it is not compatible for Win ARM or MAC OS 26 machines.
It sounds like there is some confusion happening between Remove v2 and Recover v3. There is no cloud processing for Remove v2, at least not that is accessible within the app.
I have email you the video of the screenshot. Email subject title is : “Adust Lightning” comes on Auto
Previous version is not like this behavior.
Please help. Thank you.
Hello Ange, you can add the rtx A6000 Pro Blackwell to the list, I got the grey blobs as well. Thanks !
ah yes, my message fixed thanks for flagging!
@olivier.martin - thanks! Added it and added your contact information to the development team ticket as well.
@mrtoyota03 - great seeing John received your file and has added you to the development team ticket for the Remove blob issue. Make sure to see his email for link to revert to v1.1.1 or to force the AI Processor CPU in Edit > Preferences to stay on v1.2.0!
