Files being saved as DNG (RAW) from DxO PureRaw/DeepPRIME technology do show magenta in highlights areas. Yes, you are describing the issue I was referring to. Sorry I failed to mention that this was a RAW issue but thought it unnecessary because Pure Raw will only accept RAW files! I produced some samples to send to DxO and will try to find them if that fails I can repeat the procedure and post them. In particular it makes rather inferior quality images from my Olympus TG6 (poor sensor?) more acceptable but it is sometimes also good with the Sony6300 ARW. It is the way Pure Raw handles noise and sharpness that attracts me. If I do the same with the original RAW files from my cameras in Photo without the intervention of DxO this is usually a successful procedure. The magenta occurs in the highlight zones when I operate the sliders for those. In Photo I either try to reduce exposure or to use the highlights/shadows dialogue to reduce highlights. The saved files are then opened in Photo.
These are then saved as RAW files to maintain flexibility. The files are first processed in DxO Pure Raw2. You will get a faster response from the DxO users there than from DxO Support.ģ) When you say, "optimised for Lightwave", do you mean the Nik plugins seem to work better in Adobe Lightroom? If you have not also posted about this problem on the DxO User Forum: It seems optimised for Lightwave.ġ) Do you actually mean "use the DxO Nik Collection of plugins within Affinity Photo", If so which Nik plugin is giving this colour shift? Or do they all do it?Ģ) When you say you've passed the problem on to DxO, do you mean you've submitted the problem direct to DxO Support via this page: I have asked DxO if this occurs with other photo processing software but had no reply to that question. In normal contrast situations it cooperates brilliantly so I would like to use it more. Does anyone else out there use DxO with Photo? If so do you know why, in high contrast situations, DxO converts whites to magenta? I have passed the problem on to DxO but so far there is no solution.
0 kommentar(er)
