So far, it’s working well in most respects. DNG export works if lighting and colour effects are not applied. I have not been doing large batch processing, so have not experienced the memory leak issue.
What still does not work is Preserve Text. I have tested it with several images of varying initial quality. Here is one of the worst – very low-res and noisy original:
I would not expect a readable result, but at least one that does not distract form the overall image from which this was cropped. Version 2.3.2 gave this:
In the background, it is inoffencive.
Without Preserve Text, or with it, on 3.0.2 makes no difference. You get this:
Even in the background it no longer even looks like a calendar in any known occidental language!
Oddly, it takes about the right amount of time to process and then does nothing. Please fix this. It worked before, so the code module is already somewhere at Topaz to do it right.
The quality of denoise hasn’t been addressed still - large color blotches are still there.
When will this issue be fixed? I reported this issue a very long time ago, this is core function of software and it is in a poor state.
so why am I paying for something that hasn’t worked for 3 versions? When will you fix it? and will you fix the missing meta data issue at the same time?
Win 11 Pro desktop PC. Using Ps 2024 Plugins. PAI 3.0.2. Processor = AMD RX6800 XT. Intel i9 12th gen.
Tried both the Filter menu plugin and the File > Automate plugin in Photoshop 2024. Both opened my test (.jpg) image from my Ps ‘launch’ layer and processed image using manual settings I applied.
When I save/export back to Ps - the Filter menu implementation overwrites the Ps launch layer when returning the processed image to my Ps layer stack. The File > Automate implementation creates a new layer and labels it with the PAI enhancements I applied.
I prefer the File > Automate approach to exporting b/c no possibility for users to accidentally overwrite original content with processed content (if they forget to duplicate the launching/sending layer). This 3.0.2 release didn’t exhibit the same image mutilation bhvr as 3.0.1 when using the Ps plugin on the 1st image I tested. Thanks Anthony!!!
Unfortunately, there’s still a status label plunked overlaying on the image content in my PAI workspaces - covering image content at bottom center of the image workspace. Would love for that to be in a highly visible locale off image in the grey horizontal bar above the image workspace:
Also, there’s still no initial image dimension to scaled image dimension functionality in the File > Automate implementation of the Ps Plugin (I assume it’s not there in the Standalone either - and should be there also). It’s something that’s been requested for a while & seems important to a product with scaling functionality - to have both the original dimensions and the user-specified scaled dimensions (up or down/scaled) in the righthand settings panel. It’s a frame of reference that I, at least, believe is important to have.
Aesthetically, the TPAI logo can be removed from the Msg Box in the Ps plugin (launch & export). It screws up the text formatting and overwrites it to make it unreadable and the logo is really unnecessary there. But if messing with it might impact the functioning of the plugin transport in some way, it’s not something I will lose sleep over…
Why do we have to waitf or 3 versions to to have these issue fixed. Why was the software released in the first place. Where are your beta testers? Maybe it’s time to get testers that actually know what they are doing. Maybe you only release updates monthly in order to make sure they are fully working.
All’s well That ends well. After waiting a little longer than we are used to, the annoying problem of TIFFs, instead of DNG, in Lightroom Classic has finally been resolved. Now it works perfectly.
Can we have this fully supported in a future release? As it is now, it is recognized by Windows and other apps so it can be located within the various predefined window position sets, but you cannot select a predefined window size and position using PhotoAI’s window sizing widget itself.
That’s an honest review. The quality issues in TPAI are perplexing. Who should care about window snapping on Windows vs image quality? The prioritization of issues being fixed is at fault. I I would suggest Topaz to start examining what allowed the known issues to even exist. Take, for example, an awful color shift when processing Nikon Z8 images. Has anyone at Topaz even bothered to look at the images when compatibility with Z8 was added?
Not really sure what’s really been fixed with regards to memory usage/leak…
Just ran a 105 photo batch autopilot doing denoise, face recovery and the occasional sharpen. This took about 42 minutes which is a tad slower than the batch I ran a couple of days ago in 3.0.1 (170 photos in one hour vs calculated 150 photos this batch) but I write that off as today’s batch was shot late afternoon and with a bit more noise (otherwise same motive - castellers performing) while the batch I shot the other day was shot mid-day and at less noise.
Anyway… RAM usage doesn’t seem to have changed much, and now - a bit over 10 minutes after writing the last file PAI still hasn’t released any of the RAM claimed even after closing all loaded photos.
It’s more than that unfortunately. There is some foundational work required for us to be able to handle this item, but we are getting closer! It’s an item I am tracking and hopeful on. I will let you all know when I have an update here.
Thanks samb - yes this is very much on our radar as well. Right now we see good results with Gigapixel’s Text and Shapes model, so I’m hopeful here we can bring that good AI energy to TPAI too!
It’s just one more example of a small usability improvement, that resulted in a partiatial implementation effort, which may never get finished properly. I care that all the things they decide to start actually get finished. It’s called holding them accountable to their customers.
