This week has a few more fixes for various camera profiles as well as some tweaks to how Autopilot recommends values. Autopilot will now try to minimize the extra denoising option in Sharpen models if a Denoise model was recommended as well and vice versa. This should help in cases where Autopilot was trying to fix the same noise/sharpeness issues with both models which led to some over-sharpened or over-denoised results.
As always the full change log is below!
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.
We’ve recently added the ability to post RAW files under 65MB in the forum. If you are okay with your image being posted in this thread publicly you are free to do so. You are also free to go through our dropbox if you do not want to post publicly.
These pages are just the beginning for making Topaz Photo AI an easy and engaging experience users. We welcome any feedback and suggestions on how to improve this new section of our webpage, and we will be keeping our users and beta testers involved in future updates.
I’m using Capture One 22, and was also wondering why the “Respect Crop” option in the Photo AI plugin was not respecting the crop when it goes to DNG and in to PhotoAI.
I noticed someone ( [john.robertson-1219]) posted about this issue in January, but the only suggestion was that RAW processing did not support crop.
DNG must support crop because we can crop in PhotoAI and send a DNG file back to Capture One, but Capture one does not seem to export cropped images to DNG, so I was wondering if this is a Capture One issues.
Right now, I’m using uncompressed 16 Bit Tiff instead. It seems like this is supposed to be the best alternative, but still I feel like the RAW/DNG processing result looks cleaner than the Tiff processing result. That could be my imagination though.
This is a known preview issue. I may be able to resolve it in the upcoming months but I’m currently working on other things.
The issue is that the original preview image draws the full image at full resolution, but the preview downscales the output to match the window size. This causes some artifacts in the preview that do not show up in the output. This is also the cause of slight pixel shifting as well. I plan on working on this soon.
Are you saying that sending a cropped DNG from Capture One into Photo AI does not actually crop in Photo AI? If that’s the case it may be Capture One putting crop metadata in a weird place or that Capture One does not put crop info in by default and our plugin has to handle it manually. If you send me a DNG file I can check if it’s the metadata case. Might be worth verifying that the DNG also doesn’t crop correctly in standalone mode too.
The Topaz Photo AI advertising material gives the impression that it probably does support it. It says “Get better image quality without changing your workflow. You can use Topaz Photo AI either as standalone software, or directly from most photo editors.” I’ve asked Topaz to clarify - and hopefully produce a fix? Many people who don’t like Photoshop’s subscription-based service still use Photoshop CS5.
I often have to Refine the Subject selection. I would love to have a keyboard toggle between Add and Subtract so that I do not have to keep taking my eyes of what I am working on to go to the Add and Subtract buttons and then back to my subject…it would be much faster with a keyboard toggle, like A and S. If this already exists, please tell me what it is!
Absolutely right. I have to turn noise reduction off entirely because it loses details even at the lowest setting. My current workflow is to layer the Topaz result on top of the original file and then lower its opacity or mask it to show up only where I need it, but it would be nice to have better control in Topaz to begin with.
The Adobe CS software reached end-of-life 9 years ago…
Whether we like the subscription or not, Adobe has moved on and other developers such as Topaz have no obligation to try to shoehorn their current cutting-edge apps to support such old technology. It probably wouldn’t work anyway. And if it does, it’s probably not going to for long.
When dealing with computers and software, the direction of the technological flow is always forward, not backwards.
When Topaz says “most photo editors”, they are speaking of the present offerings, not those from the distant past.