I’m not planning on going beyond 4.0.1 unless something so big and amazing is released that not trying it would cause my physical pain. At my age, I don’t need to be plagued by anything else. Topaz Photo AV 4.0.1 gives me all that I can reasonably hope for. I’m staying with it.
Yes, I also still use 4.0.1 on my M2 Pro Mac. From what I have read 4.0.2 introduced some new bugs.
I tried it one more time today, turning off all my extensions and Bitdefender, and then did a clean installation of 4.0.2. I was sure to remove any vestige of 4.0.1. Ran every disk check, cleaned out every cache. The result? The same as before, one crash after the other when pressed into batch processing. There’s no lack of RAM, the GPU function remained optimal, but 4.0.2 still bombed. I went through the previous procedure and installed 4.0.1, and it works without a flaw.
I have no idea why this is, other than I believe that without an engineer’s tools, the inclusion of the NVIDIA fix is at the root of it. After all, tech support insists nothing else was changed.
As I mentioned earlier, I’ll need extensive proof of function before subscribing to the next major upgrade, which would likely be version 4.5. 
We will see what happened.
1 Like
Hello @john.turner-2678 - Checked with Tabitha and v4.5 was a typo. We are planning to fix the batch processing issues in the next upcoming patch if all goes well. next patch will be v4.0.3. To make sure to stay on v4.0.1 for now!
3 Likes
Looking forward to it! Thanks for the clarification!
1 Like
Today I used the Upscale function for the first time on a .DNG file.
I was satisfied with the result except for a few minor details.
But after I saved the upscaled image (already as a DNG) I see that all EXIF datas were gone.
Is this normal, do I something wrong or it’s a bug?
I send the image from Lightroom Classic to PhotoAI as the plugin.
How was that DNG created that you imported in TPAI? Can you test with the original out of camera RAW file and not a converted DNG or not changed in any way (included LrC renaming)?
The DNG file was a original file from a DJI mini 4 pro and wasn’t converted in any way.
I’ll check it outside from Lightroom.
I’ve done some further test. If I open and upscale the original file in PhotoAI all EXIF are contains in the exported file (exported as .DNG)
If I using the PhotoAI plug-in in Lightroom (via menu “File - Plug in Extra”) the upscaled image doesn’t include the EXIF data.
As far as I see this is a bug that has been known for a long time.
See here:
Photo AI issue writing EXIF data - Topaz Photo AI / Bugs and Issues - Topaz Community
Update 3.1 of Topaz Photo AI - exported files STILL missing metadata (EXIF, GPS, original date taken, etc.) - Topaz Photo AI / Bugs and Issues - Topaz Community
I think it’s time to finally fix this bug.
Instead of constantly implementing new features, you should first address the known issues and bugs and solve these.
2 Likes
@axel.matthies The link you posted is different, and they have a workaround. On that link that user was changing the file to a DNG format in LrC before sending to Photo AI (by either choosing Copy as DNG and or renaming the file) and that causes issues with Lrplugin. It is a supported camera, however if they use the original format of the file without DNG conversion or file remane there will not be any issues with the metadata. Thanks for flagging these threads, the users reached out to Support by email and were given the solutions already. We added replies on the links now if other users experience this.
In your case DJI will shoot only in DNG, not in any other format and that will cause issues with the metadata when used as a plugin from LrC. Keep in mind DJI mini Pro 4 is not a supported camera model either. The root of the issue will be similar and it’s an issue with DNG files in plugin for LrC when the starting file is a DNG. I added your contact information on the development team tickets for 1. The DJI support of that model and 2. The metadata loss on DNG files and we can contact if we find a fix. You can send the file to Photo AI using Edit in to get back a TIFF that will have the metadata.
1 Like
I already let my subscription lapse for this exact reason.
1 Like
OK. Thank you for forwarding to the development team. I’ll hope there’s a fix in the near future.
I’ll check if the workaround with using the Edit in… is a possible way for me and matches with my workflow.
What I don’t understand is why the DJI’s mini4 pro isn’t still supported by PhotoAI.
The drone has been released for almost two years.
The development team works on camera support by order of popularity and we have not gotten any requests for this model specifically yet. I added your contact information and request on a ticket for this. The file does work in standalone and for the LrC issue, a lot of users won’t need the metadata so it must be why we haven’t received any requests or reports on that model specifically. The links posted for forum threads were users on camera models we support, that were converting the native RAW file to DNG, by skipping that conversion, they won’t have the problem anymore. But in your current workflow, using the non-supported camera model and your metadata needs, then you have the underlying issue of the DNG metadata loss as DJI can only shoot in DNG. Using standalone, or LrC Edit in plugin are the only workarounds in your case. We will contact you if a fix is found for the DNG part!
1 Like
Almost. a month and no updates. What is happening, topaz team?
2 Likes
@michaelezra - There is no set frequency on when we release updates, and while we like to release as many updates as possible, the amount of fixes in a month/year will not always be consistent. There are very important batch issues and plugin issues that are being tested and aim to be fixed on the next upcoming patch (v4.0.3 this month). The development team is also aiming for another version in near future (September) with some new features/changes and more fixes, and so on. Stay tuned!
I’ll just put this right here.
Each update cycle will consist of one major upgrade and two patch updates. We estimate 6-7 weeks for each cycle
3 Likes
@vincentabel42 - Thanks for flagging that older post, it’s a 2024 Roadmap! As Jacob mentioned, the cycles are always an estimate and since we are working on bigger fixes at the moment the timeline will be longer. I will archive this post thanks for flagging it.
A patch is set for this month and aiming for v4.1.0 in September and so on!
1 Like
Of course my subscription is due to run out in September…
… We will contact you if a fix is found for the DNG part!
Ok. I’ll hope the best and wait.
1 Like
