I’m getting a magenta hue when reducing highlights from the dng files created by PureRAW in Affinity Photo &/or Darktable using Olympus RAW files. Is anyone else experiencing this? This needs to be fixed or this software is useless to me, I had very high hopes for using this.
This is what I’m seeing. Any files that have near blown highlights produce this violet color when reducing the highlights. If I reduce highlights from the original RAW file it does not happen. I’ve tried this using several files on a few RAW converters, and the results are the same. I’ve even tried HQ, Prime, and Deep Prime all have the same results, Help!
I haven’t read of any one else having a similar issue so far. Perhaps the problem is specific to Olympus raw files or your particular model. DXO will probably want you to upload a DNG file when they respond to you. I hope you can get it resolved to your satisfaction.
Mark
1 Like
That magenta in the highlights it’s actually common, what is not normal, it’s the fact that it still shows after the raw has been debayer. I had the same issue in the past, less strong, with Canon 60D and Sony A6000. When I process my astrophotos, I use a dedicated app called Pixinsight, for that workflow, you work with raw before applying the dabayer, and the app has a specific function to limit that effect because at the true raw level, it’s common, with that said, even the programs you use after should be able to remove it in the background with no issues, is it some new camera that just got supported by the apps?
I did send a couple of photos with a blown sky through PhotoLab’s own version of PureRAW (export with only optical and denoising) and did notice pink hues creep into the highlights.
1 Like
I purchased PureRAW to try and speed up my workflow, I don’t want to have to add another step to clear up something that shouldn’t be there. This is the first time in 12+ years of working with RAW files that I see this, I’ve worked with a dozen or so RAW converters and this is the first that has caused this issue. The camera is not new and is in their data base so that shouldn’t be the cause.
It is a problem I have experienced (and reported to DxO) with blown out highlights on some smaller sensor cameras such as the Canon s95 and Sony RX100 M7. It seems to only be a problem when exporting the DNG to Affinity Photo. There are other cameras where the problem does not appear to occur.
It is not just a PureRaw issue; the same problem occurs with some DNG files created by PhotoLab if exported to Affinity.
I supplied example images to DxO and I think they are examining the issue but I have no idea if, or when, it may be resolved.
It’s not just with Affinity Photo, I’ve also experienced it using Darktable, Rawtherapee and Luminar
In which case I regret I am completely baffled. It does seem to be a problem with the DNG files produced by DxO and their compatibility (or lack of) with a number of programs. I did not experience any problems with the DNG’s when exporting to Adobe Elements but I know that is of absolutely no comfort to you.
I hope a member of the DxO team reads this thread and is able to be of rather more help.
Regards
Peter
1 Like
Thanks, hopefully it will get sorted out soon. If I can at least getting it working with Affinity Photo I will be happy as that is my go too editor! 
I’m going to experiment more with Affinity as there are a few settings that can be changed with opening RAW files.
This sounds a lot like the same problem that I ran into when the ability to “Export to DNG: NR and optical corrections only” was first introduced in PL4. This problem was fixed in V 4.1.0 so may not be the same problem. HERE is the link to the discussion that solved the problem.
1 Like
Looks very much like my problem! If they fixed in PL4 then they should be able to fix it in PureRAW. Thanks for your input.
1 Like
export with PL4
Out of curiosity I exported a NEF-file (D800) showing a gradually overexposed sky, which can be ‘fixed’ with PL’s SmartLighting (standard setting +25), as DNG “NR and optical corrections only”.
Reducing Exposure, Lights, White … in ON1 PhotoRaw 2020 as well LR5 worked as expected
– and in Affinity Photo (1.9.2.1035) in 32 bit mode/preview.
But with ‘normal’ Exposure, Brightness, Lights … it produced an increasingly pinkish colour gradiant
the more the sky was overblown.
While not very familiar with AP, I don’t know if it’s a persisting ‘problem’. – Checking the original NEF-file in AP didn’t show this pink …
Wolfgang
To countercheck, if it’s in DxO or Serif’s ‘ballpark’, maybe someone could try this in AP with an original DNG-file .
1 Like
I don’t believe this is an issue with PureRAW or PhotoLab. Someone recently reported the same problem with a DNG file they downloaded from my website. That DNG file was from a Fuji XT3 which was converted to a DNG using a product called Iridient XTransformer. When opening the DNG in Affinity you see this problem in areas of extreme highlight clipping. If I convert the file to a DNG with the latest version of Lightroom you don’t see the problem.
My best guess at what could be happening is that it possibly tied relates to the recent change in the DNG specifications. It’s more than likely a problem with the way Affinity is decoding the data in the DNG file for the clipped area. I don’t see this problem if I open the DNG file in Photoshop, Lightroom etc. It’s only when using Affinity Photo.
Try opening the problem DNG file with something other than Affinity to see if you still get the problem.
1 Like
I see the problem in Darktable and with some files with Rawtherapee (blown highlights), those are the only other RAW converters that I own, other than the Olympus Workspace but that doesn’t open DNG files.
I’m happy to take a look in Photoshop and other converters if you like. If you want me to take a look my email is robin@lenscraft.co.uk. Please use a file transfer like Google Drive, DropBox or WeTransfer rather than sending it directly by email though.
1 Like
Sure OK, I will send it this evening as I’m at work at the moment. I also have the guys from Affinity Photo looking into the issue, as that is my go too editor and I really want to be able to use PureRAW with it!
No problem. It may be Saturday before I can check them properly as I have a long drive to a shoot tomorrow and don’t expect to get back until late. Then again these things never go quite to plan.
1 Like
update to PureRAW Bug on Windows 10 - #13 by Wolfgang
@Lenscraft & all,
completely forgot to run the aforesaid NEF-file (D800) through Adobe DNG Converter (11.2.0.135)
- in AP the same result as with the original NEF-file
- in AP pinkish again when ‘re-processed’ in PL4 (DNG NR + optical corrections only)
Wolfgang
1 Like
I can confirm the problem. I use a Canon 6 D Mark 2 and for RAW development I use Luminar AI and Affinity Photo. Incidentally, I have never (even when I was using Photoshop) had problems with the DNG images created by the Adobe DNG Converter. But I always had problems with the DNG’s from DXO. I actually don’t think the program is bad. It applies the correct lens profile, provides excellent noise reduction from the image and subtly sharpens it. I saw a significant improvement in all problematic images with image noise. But the eroding of the extreme lights and the purple coloring destroy the entire utility of the program. It’s just not usable like that. I would also have liked to be able to influence the strength of the noise reduction and sharpening in the program in several stages. Unfortunately, that doesn’t work either.
1 Like