Hello! We released a hotfix for 3.6.1 to fix quick preview in Super Focus. These patches also include support for new cameras, a major fix for preview on Mac, and other bug fixes.
We will continue to update Photo AI with additional bug fixes as needed to improve performance, stability, and the overall user experience in the coming releases.
You can find the installer links and the full changelog below for this version of Photo AI. For any issues, make sure to send us an email to support@topazlabs.com
I just now tried 3.6.1. Unfortunately, this still does not fix my bug report about Super Focus 2 just producing a very blurry preview and result. I reported this to support about 3.6.0 about 2 weeks ago. Super Focus 2 is totally broken for me. In our several back and forth emails Alexandre has been very nice, but she does not have any idea when or if Topaz will fix this. She said I am not the only one though. Do you know? Thank you.
The issue with Super Focus v2 on which Alexandre added your contact info currently has 14 users on it that have reported this issue. It is being looked into and only affect M2 Pro computers - As Dakota mentioned on the Gigapixel thread replies with you, this is being discussed with Apple and is related to the issue you are also experiencing with Gigapixel. As Dakota also mentioned, because they are actively talking to Apple to resolve this, there is no timeline we can give. We hope to resolve this as soon as possible!
We have your contact info on these open development team tickets and will circle back once those issues are resolved
We are working on a model update that should hopefully reduce these artifacts. For now, I would recommend deselecting areas of the image that have artifacts in Super Focus v2.
From reading the Super Focus 2 info when 3.6.0 was released it talks about being much faster than Super Focus 1 and also that it is more flexible because you can make some changes without re-rendering. What is not clear is if the results are exactly the same for 1 and 2. Are the results the same, but 1 is slower and less flexible?
@Lingyu@Ange.topazlabs
I don’t remember… Is the Panasonic DC-G9M2 already supported by the program officially? Are its 16-bit RAW files read in the correct way? (The GH7 should also have the same sensor and thus the same “files”)
One more user who detected a “secret code” in a .HEIC image. It seems, this kind of artifact appears mainly in otherwise unstructured areas of a photo.
upscale 4x, export, import, sharpening (things we were able to do before! Because it is how it should work, with sharpening, denoising, anything… you don’t sharpen or denoise tiny resolution image before upscaling anything. And you never, ever sharpen something at the beginning of a photo edit, you always, always do it at the end. You don’t see any photographers doing sharpening first. It makes no sense and it destroys images!)
and here, upscale 4x, save, import again (things we didn’'t have to do in the past, because Photo AI was an all in one tool), then sharpening.
@michael-3397 - Adding to Lingyu’s message, can you confirm if the artifacts occur if you use Super Focus before it’s sized up? Seeing it’s already 14000 pixels. Can you test Super Focus on the original, then once Super Focus done Upscale? Let us know if same results and I can relay to the development team!
@Tostanica-fezanamu - They are both different AI Models and that is why they are different version numbers. They will produce different results as they are different AI models. The development team will continue to work on v2 as it has reports of being too cartoonish on some processed files, etc. This is why there was a added “send your image and feedback box” to make sure to get as much feedback as possible. There is also no “less flexibility in v2”, it was always the same behavior in v1 (where it renders the while image and allows change of selection after the process to avoid rerendering). The difference is a different AI model, that is much faster. In your Case, since you are on a M2 Pro, there is an issue with the blur, for which the development team is looking into!
@JakSpoon - The G9M2, even is same sensor as the GH7 will be detected by Photo AI as an unsupported model and can give out wither wrong colors or an error on export. To test! If it does, you can write to support@topazlabs.com and send an original RAW file from this camera and we can open a ticket with the development team to look into it’s support. In the meantime, instead of using the native RAW file, test converting that native RAW file to DNG and see if it works in Photo AI. If you have LrC, can do this on Import with the “Copy as DNG” option or use the Adobe DNG converter.
@Richard.J - it’s actively in the works - saw it with my own eyes. It’s a drastic change and still being developed but it will come! Thanks for your examples
Hi all,
any idea, why Photo AI is failing after upgrading my graphic card to RTX 5070? Windows 10 updated, drivers from nVidia updated, Photo AI latest version… Problem is only in Sharpen module, denoise works fine. Does not matter if jpg, tif, raw, standalone or called from Lightroom. After export the picture looks exactly the same like in preview (whole object, not just the part like here in screenshot).
Then I will send an email soon to send a sample of the RAW file, even if it is a “famous” camera and well spread in the market (released in fact before the GH7, it seems strange to me that the support in the program has not arrived already)!
I sincerely hope that official support will be added soon, in the future!
For sure! I’ll keep an eye out for your email and open a ticket for its support Let us know as well if the DNG workaround works until it is! It would still be the RAW file, just the conversion needed till its supported.
I reported this to support about 3.6.0 about 2 weeks ago. Super Focus 2 is totally broken for me. In our several back and forth emails Alexandre has been very nice, but she does not have any idea when or if Topaz will fix this. She said I am not the only one though. Do you know? Thank you.
Let us know as well if the DNG workaround works until it is! It would still be the RAW file, just the conversion needed till its supported.