In the 2.0.1 update due out on Thursday, will you also fix the conflict between Gigapixel and AI photo in Photoshop’s file/automation tab?
Because I and others have observed that Gigapixel as a Photoshop plugin no longer works since the Photo AI 2.0 update.
2 Likes
Thank you. My point seems to be highlight. Why was this fix not influenced in the release of the program advertised as general release version? Instead as I’ve pointed out, a week or two later, after people tested it, bug fix comes out. Meaning we are all beta testers. There is no final stable version. Its perpetual beta. No fun when you cannot rely on the program, you have to install and download bunch of new versions all the time and knowing that if you are buying this application, you are applying for beta program. That’s not cool.
5 Likes
Sadly, Topaz have spent more than a year developing this inadequate product and asking us all to be beta testers. I am finished with it but will probably continue to use Topaz Sharpen AI if and when I need it. For denoising there are now other products that are just as good or better.
Over and out.
2 Likes
I want to say huge thanks to Topaz team for massively speeding up Photo Ai!
1.5 version was much slower than Gigapixel, which drove me nuts. Every shift of preview window resulted in re-enhancing entire image, the resutls of previous enhancement wasn’t cached.
Now in 2.0 everything changed and working as expected.
I have the option to update, but the program has never updated without me specifically clicking the button to do so.
I can stick with a version that’s stable on my system and just ignore the updates. Or, if the update button is just too tempting, I would recommend creating a restore point, trying the new version, and using the system restore point if you don’t like it.
I might be wrong here, but this one does not make sense to me.
I think most people who update software do it with the hopes of on the one hand solving whatever issue they might be dealing with in their current version and on the other hand because they also want to enjoy new functions or improvments as advertised in the changelog.
It’s not like anyone update their software hoping to run into regressions or new errors.
1 Like
For me personally, I’m seeing a speed improvement when I’m using only the core models, standard, low rez, etc. But, as soon as I turn on any of the other sliders for noise and sharpen, then it’s about like it was, slow, or at least seems that way.
If someone doesn’t want to be a “beta tester” they can just wait.
If Topaz labs were to just make us wait, it would protect us from the possible inconvenience of getting a bad release. But is that really necessary when updating is optional, there’s an active forum that discusses the success or failure of each realease, and rolling back is not that complicated?
“Just wait until there’s no bugs.” Seems to be the argument, but I like that I have a choice in the matter. I can choose to “Just wait until there’s no bugs” myself (or at least no ‘game-breaking’ bugs) or I can try new stuff when it’s released.
It’s my choice and I like that.
Newsflash - other companies such as Adobe, Microsoft, makers of Malcrium Reflect and … release “buggy” software at times. That’s why many people wait a week or 2 before updating. Really if you don’t like PAI don’t use and go elsewhere. Why they didn’t catch this “bug” before releasing I can’t say. For me, the features I like about PAI are that it processes raws for noise and sharpening including selection. I disabled face recognition, so this issues doesn’t effect me.
1 Like
Lot’s of good ideas from @devenpsc here but this one stands out for my use cases too. STABILITY is a core component of any successful workflow and some time could be spent on nailing down bug fixes and when things go wrong… failing gracefully.
1 Like
Macrium reflect has always been very reliable for me, and updates good too. Have used it for years now.
1 Like
They have had some “buggy” updates
The Sharpening Standard v2 is definitely lightening the image.
I just compared the histograms of Sharpening Standard V2 to Sharpening to the original RAW file. The histograms of the 2 versions of sharpening were the same. Both of them moved very slightly to the left (darker) as compare to the RAW. Truthfully looking the images I couldn’t see any difference. But maybe some images with different histograms will behave differently.
No issues here with Affinity Photo 2 and Photo AI 2.0
1 Like
Testing the Photo AI 2.0 initial release with today’s new Photoshop 2024 Generative Fill (starting with an empty canvas and using a text prompt). Enlarging 4x.
If that is true then it will be interesting to see how many smartphone snappers will go out and buy a rather high end computer (PC or Mac) with a strong GPU and NPU (Neural Engine) and then spend a couple hundred dollars for Photo AI, learn to use it all, export photos, and then upload to their social media accounts/online storage to view on their smartphones. I have my doubts that enough will buy to swamp the Mac/PC using photographers with traditional cameras.
3 Likes
Gee, this is like deja vu! I just mentioned that as a great app for PAI (& GAI, ahem) File > Automate scaling as a Ps Plugin (for low res Firefly assets) in the past day or two. It’s almost as if I knew. 
1 Like
Topaz Photo AI 2.0 is fantastic! BUT just an update (released today) to Photoshop 2024, and Topaz Photo AI 2.0 wasn’t there under FILTERS as usual. I just copied the Topaz Photo AI 2.0 plugin from earlier PS, pasted into the PS Plugins folder, and all is good. So ya know, Adobe’s messing with ya!
Well, that’s interesting. That your filter wasn’t in the Filters list (and that they released Ps 2024 before Adobe MAX…?). Did you have any prior Topaz filters (like the ‘classic’ ones)? If so, did they transfer to the Ps 25.0 rel.? And, were you using the Ps beta before updating to the latest commercial release?
I’d hope that the PAI installer installs into the Adobe Ps Common Programs folder - which was always the one that ensured filters carried forward from one annual release of Ps to the next.
Unless Adobe changed that for this year.
