Invoke PAI via Lightroom Module for raw workflow and do the processing in PAI
get a distorted image
Repeat this with standalone mode.
This is definitely a bug, not a user error. Sorry @AiDon for reporting this again, but I’ve got zero feedback from the dev and it is 4 updates since then. Please help, Topaz. In the logs you can see that lensfun is only applied in standalone mode. This is true for other cameras and lenses also. Just double -checked it with a Nikon Z7II with 14-30F4 Lens. Working in standalone mode, no correction via LRC-Plugin. I’ll add the logs, also.
No, that is not possible for embedded profiles. That was my starting point when I first posted about this problem, remember? Applying lens correction to the resulting dng works only without embedded profiles. For example: When I use the exact same Nikon Z7II with a Sigma Lens, I can apply the lens correction to the PAI DNG after the roundtrip. I think it might be possible to copy over the integrated lens correction data to the DNG, as that seems to happen when lightroom itself converts a raw with integrated profile to DNG. I’ve tried to do that quick an dirty, but with no luck.
So to sum up: There is no way around lens correction directly in PhotoAI for the Lightroom RAW Workflow as soon as you got a newer camera or camera/lens combination - as most of them work with integrated profiles. From your answer I assume the lack of PAI lens correction in the lightroom workflow is intentional. I do not understand why, as lens correction before for example sharpening or upscaling could be beneficial for edge resolution I think.
So can you confirm this behavior of PAI as intended?
If so, I want to request a feature.
I think you need to raise a support request at the main website as they still haven’t picked up on it. The only way around it at the time being is to use the Edit in option from LR and pass a TIFF for the best result.
When you raise the support request link the request to this thread also.
I’ve just uploaded 4 different camera samples for you. All of them have integrated lens profiles in the raws and it is not possible to correct them after or in lightroom raw plugin workflow for PAI (i checked all of them).
Nikon Z7ii with 14-30F4 (but the same with every Z native lens…if you need more lenses, drop me a line)
the lens Anthony uses in his video is actually supported as the cat photo he processes in the beginning is created with the Z 24-200 which is the 4th entry in the list you provided.
My 14-30 is the second entry and is supported also. Z16-50: 3rd entry from the bottom.
So I might just miss the point here (my little son does not allow me to sleep very much), but what do you want to point out? For me, your comment suggests this is a user error and just rtfm. But that is not the case. The lenses are supported and the correction works if the raw is processed with standalone PAI mode. Only in the lightroom module workflow it is not working. Ligyu has confirmed the issue, also.
So don’t get me wrong, I appreciate your valuable input all over this forum and you were the first one who responded to my problem report, asked the right questions and actually suggested a workaround which was great. What I want, however, is not to dilute the problem point and get a statement from topaz developers - even if that statement is “we see the problem and we’re working on it” or “support for your cameras and lenses is not a priority for us / not on our roadmap - please move on”.
I am not sure why they aren’t processed either but that may well be a problem with reading the DNGs from LR as they (DNG) are not RAW files.
Also I am not sure why there isn’t a response from support.
EDIT: Adobe noted there was a issue with exporting DNGs from Camera RAWs in LR Classic where the embedded profile was not being applied even if “enable profile corrections” was selected, it is supposed to apply the embedded corrections on export to DNG. Then if the DNG is imported back to LR the profile is NOT applied.
Note that I only have LR6 and it isnt a problem and I also use DxO PureRAW and it also does apply the embedded profile on export so there are no issues.
You recently added support for ARWs from the RX100VII camera. The problem is that I’ve converted many of those to DNG (using Adobe DNG Converter) and those can’t be opened properly in PhotoAI.
Hope you can add support for those DNG’s aswell.
this is not the same Problem, please open a new topic for it. Perhaps an adminstrator can help you move your post to a new topic.
I’ve analysed the lua scripts. I am not a lua expert, but as far as i can see there is no dng conversion via lightroom. The raw file path is passed to photo ai with a parameter telling it to run in plugin mode. So adobe bugs don’t play a role here.
The lensfun lens correction is simply not executed in PAIs Plugin mode and i assume they did it to enable users to enable/disable lens correction in lightroom for the PAI processed photos. This works only for specific lens/camera combinations with non-mandatory lens correction.
With mandatory lens correction (= camera manufacturer wants this correction active all the time in Lightroom - no matter what the user wants) this does not work.
I could reproduce this several times. So I also have to correct myself above: Problem is not existing with every Nikon Z-Lens, but with all Z-Lenses with mandatory lens correction (which are many, but not all).
I see three solutions to this problem:
the fast solution to make me and other users of these cameras happy: Just ask us to use PAI internal or lightroom lens correction in the presets und if enabled, just do lens correction in PAI.
intermediate: detect the mandatory lens correction in the raw somehow and correct these pictures via lensfun in PAI and leave the rest to lightroom.
The long path: Learn how to read and convert all manufacturer specific lens correction data in the raws and then integrate it in a standard-conform dng as opcodes.
Please dear topaz-developers, give me and all the RX100 Users the first solution.
@AiDon: I’ve looked for that - there isn’t. Also converting to DNG via lightroom before the roundtrip doesn’t help, because lightroom includes the proprietary lens correction information into the dng and it gets lost the same way in PAI processing.
I’ve build myself a very, very (!) dirty workaround via lua scripting and a shell script, but the process is not fully automatic and I hate it, hope they come up with a real solution soon.
All other ideas, like just copy OPCODE3 from a lightroom converted, temp DNG to the PAI exported DNG via exiftool or exiv2 did not work and I am missing time and knowledge to deeply analyze why (something to do with the makernotes - perhaps there is a solution with exiftool).
Additional suggestion for the developers (@Lingyu): You seem to just skip lens correction when photo ai is called via command line. I’d suggest to do that explicitly instead, as it is bad for half-automatic scripting. You could for example define a parameter “-lens correction = Off” instead…
If any questions, ask or contact me via email if you want.
I apologize for the delay in my reply. I am usually sorting by and answering the oldest threads. This one was active and ended up at the bottom so I never saw the additional responses.
@busse.oliver the built-in lens profiles in particular are a challenge as we are not aware of how to transfer this information into Topaz Photo AI. This has been a pain point for Raw processing since the start of Topaz Photo AI. Yes we are aware of this issue with lens correction and I have many tasks related to various built-in lens profiles that are lost during processing for the developers to look into.
I’m not sure when this will be worked on yet.
Lensfun is the best database we have, but it’s missing a lot of information. The issue with lens corrections when using command line (the LrC File > Plug-in Extras > Process with Topaz Photo AI method uses command line as well) is known as well.
I’ll look into the first solution that you are talking about. We can update lensfun and see if adding lens correction to the command line fixes this for some lenses.