Topaz Photo AI v3.0.4

Still the same problems in 3.0.4 as in the previous versions.

I thought I saw this one addressed in here before, but when I process a dng image and get a tiff output, I still get a significant color shift.


Sending images from Lightroom to Photo AI using Lightroom export is back to not working. It was/is fixed in 2.3.2, but it’s back to NOT returning a DNG when it’s sent an exported DNG. Yes, I CAN use the plug-in, but it creates more work, and it WAS WORKING FINE IN 2.3.2.

Feathering still defaultS to 100%. Is it intended that we use 100% feathering all the time, or can we have a persistent setting for feathering so it can be set to 20% or some other value as the default?

Subject selection, when set to “Subject” does not work as well as in 2.3.2. I frequently have to do more cleanup in 3.0.X than in 2.3.2. I thought the specific types of subject selection would improve the quality of the default selection, but it doesn’t appear to consistently be the case.

1 Like

I often use Photo AI to enhance the decades old analogue photos I digitize from negatives. The process however introduces some color artifacts to the black & white original and the new TIFF file is recognized by Lr as a color photo. Could you address this? A B/W mode would be welcome. Ewen more a model for analogue photos because there is always some level of noise reduction and it “washes out” the grainness of the films. I might not be the only one who enhances B/W photos as well.

3 Likes

Since 3.0 was released, I’ve noticed that the tiling is back. Didn’t report before since I’ve been using 2.3.2. until the UI and other bugs are fixed.

I’ve noticed tiling (in 3.0+) for my Nikon d500, z6, and z8 files. I’m not using the RAW workflow since it still doesn’t work properly (going back a year+).

First, I do all my edits in Lightroom, initiate the PAI plugin, and create TIFF files with a ProPhoto RGB color profile at 16 bits.


Off to re-install 2.3.2.

2 Likes

Any idea whether C1 sends a .dng if one uses open with instead of edit with? I’m sitting on 2.4.2 and starting to wonder whether to re-up my license when it expires or take a hard look at PureRaw.

Updated right now. I have though an issue with objects removal. It works fine for the first 2 iterations, then crashes the whole program. All changes lost.

Are you telling us that you once again holding back an important bug fix for a feature release? Ok, I will have to reconsider if I’m really willing to renew my subscription.

5 Likes

And the bug where Adjust Lighting is not not applied to recovered faces is not fixed. When is it going to be fixed? It seems it should be easy - just apply lighting changes on the final full image, like the final upscale, not its components. The bug has been there since 2.4.2. One thread is marked “Resolved” but it’s far from resolved.

Relevant threads:

1 Like

Program crashes when using the object selection brush and remove object. If I click and drag instead of just clicking on the object to select the object it crashes immediately. It happens in both the latest release and beta.

I use both … even PhotoLab 7 bc PureRaw is like … eh!

Denoise the output of Pure Raw or Photolab via TPAI looks great.


btw.

1 Like

Adobe, especially CC, is getting sort of interesting regarding its new terms of use, as well. Definitely laying some groundwork.

Has sharpening and upscaling modules been improved, in v3.0.4 compared to v2.3.2?

Or are the modules exactly the same in both versions?

1 Like

Parker,

Are you attempting to use this method from Lightroom or Photoshop? I can do the multiple versions in Lightroom pretty easily (edit a little lua), but in Photoshop I haven’t found a way to get the Filter to bring up the right version of Photo AI.

Is there some other Photo AI forum where questions are more likely to actually get answers? Small-ish things like the feathering defaulting to 100% and color shifts and stuff that gets posted in here with each new release, and doesn’t appear to get any attention…

2 Likes

Have you fixed the select brush yet?
It’s to the point where I need to set up one machine with 2.3.2 as a fallback.

1 Like

Lightroom

In the current Beta, lag has been removed, and it’s now lightning-fast!

The newest update does not function. The last version was perfect, now i cant even open a picture or even open preferences without it becoming non responsive.

Yes. Bug fixes should be applied to all versions it is present in, even if it has to be done retrospectively because new versions have been released. If that causes the developers more work, tough - that can be largely solved by slowing down the frequency of feature updates.

People who choose to delay upgrades or stop upgrading should not be left in the lurch with unfixed bugs when their current subscription expires. " Buy once, own forever" should mean what it says - and though it shouldn’t include feature improvements, it should include free bug fixes. Reasonable consumer expectation and normal industry practice is for no extra cost when bugs need fixing.

15 Likes

Die Angaben für Blitz verschwinden auch.

Maybe they don’t have this code anymore?
It’s implemented in 2.x versions and can’t be transferred to 3.x?

1 Like