Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'AFP-4444'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.3 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL



Member Title

Found 7 results

  1. 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. In normal contrast situations it cooperates brilliantly so I would like to use it more. I have asked DxO if this occurs with other photo processing software but had no reply to that question. It seems optimised for Lightwave.
  2. AP 1.10 (windows store edition) on Windows 10 Processing image in on1 nonoise ai as standalone and importing the resulting DNG files in AP causes images to look overexposed and/or with colorcast all the time. opening the same DNG files in PS elements 2020 works fine.
  3. The DNG files created by DXOPureRaw are incorrectly interpreted in Affinity Photo. This leads to a purple discoloration in the highlights. This problem also occurs in Luminar AI. Interestingly, this bug does not occur in Luminar 4, Photolemur, Aurora HDR and Photoshop CS6. So it's a bug that only occurs in Affinity Photo (and Luminar AI). See sample images. Why is that? Please help. I'm using the latest version of Affinity Photo and Windows 10.
  4. I got this photo I took with a Sony A6600, I process my ARW files with DxO PureRAW first and that gets me a DNG file, and I open the DNG file with Affinity. This usually works fine and my typical photos are more nature centric and I've never had a problem. But this particular file has this huge pink splotch that does not show up in Windows Photo viewer or DxO, I only see it in Affinity. I am in the Develop persona but have touched none of the adjustments. (white balance does say there's a 25% pink tint but adjusting it to zero does not help) I have uploaded screenshots and the actual DNG file. Is this a bug with Affinity? Or with DxO PureRAW? Or is something not configured right? DSC02092-ARW_DxO_DeepPRIME.dng
  5. Recently I started using DXO Deep Prime to reduce noise in my RAW files (when shot at high ISO). The software of DXO opens the RAW file (in my case Canon CR2 files), does a fantastic job in reducing noise and primary sharpening and saves the file in DNG format. When I open this DNG file in Affinity Photo the Develop Persona allows me to reduce hightlights as well as other RAW adjustments. However reducing the highlights will change all blown out parts of the DNG image into magenta. After opening the image in the main Photo Persona these blown out parts of the image remain magenta. As the highlights can not be reduced without the magenta colorisation of the blown out part, the resulting image in the main Photo Persona is useless. However it should be noted that opening the original CR2 file in the Develop Persona and reducing the highlights does not result in magenta colorisation. I checked of this bug is typical for Affinity Photo by repeating the above process in Adobe Photoshop. When I open the DNG file in Adobe Camera RAW the highlights in the image can be reduced (to -100%) and the blown out parts of the image remain white. They do not turn magenta. Based on this comparison it seams there is a bug in the RAW processing in the Develop Persona in Affinity Photo resulting in the unwanted magenta colorisation of blown out parts is a bug in the DNG file. To illustrate the above I have included my CR2 file as well as the DNG file (resulting from processing in DXO Deep Prime) and some screen shots from the RAW conversion and highlight reduction in both Affinity Photo and in Photoshop. Can someone please look into this bug in the RAW conversion persona of Affinity because apart from this bug I prefer using Affinity Photo and not using Photoshop. DRCStaut_20200905_IMG_4348-CR2_DxO_DeepPRIME.dng DRCStaut_20200905_IMG_4348.CR2
  6. I'm not sure if this is a bug, but when I open DNG files that have near blown highlights I'm getting a pinkish magenta cast in the brightest areas. If I try to correct by reducing the highlights in the develop persona the magenta color gets more intense. The DNG file was created in the new DXO PureRAW program and imported into Affinty Photo, I have contacted DXO also to investigate. This was taken with an Olympus E-M1 MkII with a 7-14mm 2.8 Pro lens 1/6400 ISO 200 f/2.8
  7. EHello, I use DxO PureRaw to improve my RAW photos before post production in Affinity Photo. The jpeg image I get from PureRaw is ok. But the DNG is badly interpreted by Affinity Photo that transforms blank color into pink Does somebody know how to prevent or fix it in Affinity? Thank you
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.