This is our largest release since… well, releasing the app itself! We have two new models and a major rewrite of our preview panel. There’s also significant improvements to our AI Brush, and of course your usual set of bug fixes and stability/performance improvements.
Please give us any feedback or report issues with this release. We’ll be updating TPAI regularly to address those pieces of feedback and issue reports. If there’s a specific image you’d like us to see, you can send it us at this dropbox link.
New AI model for noise detection (used in Autopilot)
Complete rewrite of the preview panel, for improved performance
AI Brush performance improvements
AI Brush now has a set of brush sizes to choose from
Added undo and redo shortcuts for AI Brush
Full images are no longer cached to save CPU/Memory
Fixed RAW images opened in external editor mode overwrite checks being wrong
Fixed old installation being removed if upgrading app fails
Fixed issue where GPUs that didn’t support Vulkan couldn’t run the application
Updated Qt to 6.4.1
The new preview panel may act unexpectedly sometimes
The new preview panel may have a slight pixel shift that will NOT appear in the exported image
We’re working on many more exciting improvements! Instead of a couple bullet points at the end of the changelog, we’re transitioning to regular roadmap updates that go more in detail on what’s coming up next, where people can give feedback on the direction we’re going. Check out the first of these here:
Currently the Auto-Scaling > Set Output Size menu only contains Scale, Width, Height options.
Perhaps the list could be expanded to include common target display resolutions with slide shows in mind (1080p, 1440p, 4K 2160p, 8K 4320p).
An option to smart-rotate preset dimensions (and the current width/height options) would be handy, as some may want all photos to be the same resolution regardless (portrait as 3840x2160 and landscape as 2160x3840, rather than force all photos into landscape 2160x3840).
This is a bug that has continued from previous versions.
When upscaling specifies height instead of magnification
When multiple images are specified, the magnification is sometimes output as 1x.
Also, .bmp is not displayed in the image selection dialog.
Can you add AI model for video snapshots upscale please ? The current models work really bad with video snapshots ! And unfortunately current versions of Video AI dont handle .png or .jpeg video snapshots files too for some reason … ?! Thank you in advance !
I just did a fresh install of 1.1.0 on Win10. Now my Denoise AI, Sharpen AI, and Gigapixel AI no longer run. They look like they are starting, but I just get a white screen with the app title bar at the top for about 1 second and then it is gone. I am very unhappy.
Feature Request - I use Lightroom, so use Edit In Topaz Photo AI. When there’s an update available, I get the pop-up, but once the image is processed the program auto closes. Why? Why not allow the program to keep running, so that after I process the image, I can then do the update. Instead of having to manually re-launch the app and update it. I’m on a powerful Mac and don’t mind having Photo AI open all the time, I have no need for it to close after every use.
Best update so far! Worth waiting 2 weeks for. AI brush now works as expected even after resizing the preview which now updates much faster. The denoise function seems to be less aggressive maintaining detail in stonework for example. I would still like the ability to use a non-AI brush but the size selection etc makes it much more useful. Thanks for this update.
What has happened to Face Recovery since Version 1.0.5?
I bought Topaz Photo AI after trying out the first release…I was amazed by the quality of images created by the software…It seemed almost magical to me what the AI could achieve. I have been downloading the updates with great anticipation each week since then, but after release 1.0.5. the face recovery seemed to simply cease to function. I have a large library of older digital photographs from the early days of mobile phone photography and it was the improvement of these images that thrilled me so much when I saw Topaz PAI. Many of the images I have are around VGA size with pixel dimensions like postage stamps in comparison with recent digital images…but up until release 1.0.6. I had astonishing improvements in both quality and scale.
These two screen grabs illustrate the results from release 1.0.5 and 1.1.0. Comparison of both releases provides quite noticeable differences though both were created using default Autopilot settings and scaled to 200% in the preview window to show the difference between the original image and the new PAI creation. Whilst both AI images are far from perfect, with odd artifacts popping up in the image, the image from 1.0.5. is far superior to it’s later version. So for the last 6 weeks, I have been rather disappointedly having to uninstall the latest update and reinstall version 1.0.5.
Can one of the Devs please shed some light on why this is happening?
The second set of comparison photos also illustrates the common, box of enhancement, result around the face, which outlines the enhancement area…in a lot of my images it’s not too noticeable, but in some cases it can ruin an otherwise beautiful photo. Feature request… Can a face area selection tool be made available to manually scale the size of the area of enhancement to include long hair etc…I have had many cases where the enhancement area has stopped below the mouth and left a very pixellated chin with an otherwise perfectly enhanced face.
Answers to my questions and future correction to these issues would be great…This software has the ability to create some stunning imagery and banning the huge pixels from my older photos…delights my eyes and enhances my memory…Keep up the good work guys!
There is a major problem with Photo AI when the system has multiple identical GPU cards. If I run an image using the CPU, then Photo AI works fine. If I attempt to use one of my two Nvidia GTX 1080ti graphics cards, I get a model loading error. Needs fixed ASAP
Bug - Unfortunately it is still impossible to use PhotoAI from Capture One if the filename contains any local characters like German Umlaute (üöä) sind the encoding of the filename which is given to PhotoAI is not correct. I have reported that quite a while ago and these things should be an easy fix. So I hope it will get fixed soon!
Preview is missing while processing… but in overall first impression is highly positive!
I can even minimize window in middle of processing now, and default settings aren’t so hugely over sharpening image. Also some skin artifacts are gone now.
I know how everything in code can mess up something else, so I really apprechiate your effort.