![]() I have already reported the problem to DXO (so far without feedback) and Skylum (Luminar). The RAW engines of Adobe Photoshop, Luminar 4, Photolemur, Aurora HDR 2019 and Apple Core Engine have no problems. This currently applies to the RAW Engine from Affinity Photo (Serif RAW Engine), Luminar AI, RawTherapee and Darktable. If you activate the Apple Core Engine in Affinity Photo on a MAC computer, the problem does not occur.Īll in all, I conclude from this that there are RAW converters that don't quite get along with the DNG file that DXO generates, because it deviates from the conventions of a DNG file. And that in turn leads me to conclude that there is also a problem with the serif RAW Engine there. This leads me to suspect that the RAW engine and the implementation of the recognition of a DNG file by Luminar AI is different from the RAW engine of Luminar 4. What puzzles me is that in the predecessor of Luminar AI, namely the Luminar 4, none of these problems occur with the DNG file generated by DXO. I conclude that the DNG file generated by DXO does not adhere to the DNG conventions and, depending on the RAW converter, problems then arise. And then when I open this DNG file in Affinity Photo (or Luminar AI, which I also use) there are no purple spots in the burned out lights. In this case only the Bayer interpolation is carried out. have not yet been changed and are fully available for editing.Īnd this is where the DNG file generated by DXO differs from a DNG file generated by the Adobe DNG Converter. The other areas such as brightness, colors, white balance etc. ![]() This is a linear DNG in which the Bayer interpolation, application of the lens profiles, noise reduction and sharpening have already been carried out and noted in the DNG file. ![]() ![]() I agree that there is a problem with the DNG file created by DXO. First of all, thank you very much for all the advice. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |