Yes, I have the same issue when cropping with Photoshop.
The latest version is crashing multiple times. Never had this problem before.
Same here. A lot of crashes.
Alpha/Beta users mentioned many of the issues expressed in this version. So, I was surprised to wake up and find a new BETA version labeled as a final version! Plus, there seem to be more bugs than most of us saw in Beta. I’m not sure why there’s an alpha/beta version if Topaz isn’t going to listen to its users.
I’ve rolled back to the previous version.
I have 50K YouTube views per month that are now obsolete with this update (thanks Topaz). It will be interesting to see how many of my affiliate sales are rejected due to refunds. I’ve also instructed thousands of my students to upgrade with caution and how to roll back.
Not sure why the fundamental change from the previous version with “stacking” was necessary. The results are worse than before.
Also, I like the idea of applying Denoise to the background vs the subject and vice versa. However, all you had to do was introduce masking (to Denoise) like we had for Sharpening. And if you want to introduce “stacking,” Lightroom provides a simple solution by including a new panel to manage Masks. Why reinvent the wheel?
I tested PAI 2.4.0 earlier on my 2023 M2 Mac Mini (Ventura). Today I installed PAI on a 2020 M1 MacBook Pro running Sonoma 14.4 (latest beta). No installation, activation or saving issues during my quick test.
I did learn a couple of things with this random web image (an example of my daughter’s digital art being stolen and included in one of those large sticker packs you can buy online…).
Autopilot was adding Remove Noise and every Upscale model was giving bad results. I was concerned at first until I turned RN off and just used Upscale, in which case different models looked great. So this is an example of failed auto-pilot.
Here are a few different Upscale models at 4X with Remove Noise on (you can’t tell what models I used because there is no static right-side panel that we are all asking for, and the Enhancement buttons in the stack are simplified to the point where you don’t know the settings you are using):
A couple more examples with RN off:
I also discovered what “Done” means in the pop-out dialog! It means “close this panel after making adjustments so you can see your image again”…
Yes, ditto.
Yes, agree.
And, users then write in and say, “Isn’t anyone testing these things before release?” Some of us spend many hours testing, reporting, commenting on actual & perceived issues (wrt our own use & potentially for our compatriots who will be users of any tested design(s)).
That’s right. But even then I have an empty sidebar and have to call up the desired functions in a complicated way. This is totally disappointing. The previous versions showed how to do it better.
The Preserve Text tool does a very poor job in the new stacking workflow:
Compare this with the same enhancements in V2.3:
Has the Preserve Text tool has been correctly integrated into the stacking workflow?
I agree with you. The new layout makes users have to click more times to complete while there’s plenty of space in the interface.
Topaz should put more effort to introduce 4 comparison view to UI .
The performance of version 2.4.0 is terrible. It cannot be used in my batch workflow. It takes ages to load and process 2K files for processing. I’m going back to the previous version where processing took a few hours. The new version at the same time as the old one did not process 10% of the files!
Guys from Topaz - do you test it before you announce a new version or do you treat all users as beta testers? Where can I send you an invoice for testing?
Totaly wrong, the message that a raw file has been added has been removed.
The message here is to inform you that the software has new functions.
I can confirm that the OM1-Mark II files are not importing back to LR as noted above. I have same camera and also get the "Error: DNG Write Error Message. My older Olympus EM1X files are working fine.
Brutal what a piece of junk On1 RAW is, I haven’t even edited the images yet, everything at “0”, and they’ve already been denoised.
Due to the compression on this website, you may not be able to see the differences as clearly as they really are.
On1 RAW, all settings a “0” - all colors are mixed together.
Adobe, all settings a “0”
Capture One, all settings a “0”
The new UI - while appealing - appears to have broken Photo AI somehow.
I haven’t experienced outright crashes, but when batch processing (over 1000 files, for example), Photo AI simply stops processing the queued files (appears to lock up). There also appears to be a noticeable slowdown in processing of queued files until it finally stops processing. The only way to exit Photo AI is to go into Task Manager and kill the task.
This is the first time I’ve experienced Photo AI being delivered non-functional upon a new release, which is disappointing. Back to 2.3.2 until it 2.4 fixed. . .
OS : Win 11 Pro 23H2
CPU : Threadripper 3970X
GPU : Nvidia 2080 TI
RAM : 32 GB
I want to offer a suggestion… Topaz, please stop releasing new versions on a Friday!
You’re now gone for the weekend, and TPAI is currently useless. Those who have been using it for a while and are aware of these forums know how to downgrade.
Please release new versions on Monday so you can troubleshoot and fix them ASAP.
In this case, though, I’d suggest something more drastic… like, put this version back in BETA and ask for more participants… AND listen this time.
The UI doesn’t bother me and the stacking is a nice option, personally I like it. The selection tool works well and the preview and new images load incredibly fast.
My issue is the scaling of the image when importing into 2.4, smaller images come into the app @ 141% and can’t be reduced to 100% or below. It doesn’t appear that sharpening has taken place but it is difficult to assess with the image over 100% and no way to view it @ 100%. That being said it looks like nothing occurred. 111% is the lowest I could reduce the image, this selection should allow you to reduce below 100% if you desire.
All of the AI features are to heavy handed! I would at times be pleased with the results in 2.3.2, it would come close but 2.4 the results always to drastic. That being said, I frequently tweaked the settings but the starting point in 2.4 takes longer because the settings are way off.
Moving back to 2.3.2
Microsoft Windows 11 Home
Version: 10.0.22631 Build 22631
Processor: AMD Ryzen 7 5700G with Radeon Graphics, 3800 Mhz, 8 Core(s), 16 Logical Processor(s)
Installed Physical Memory (RAM): 32.0 GB
Total Physical Memory 31.3 GB
Fully agreed. Especially with the upscaling.