UweN Posted April 26, 2021 Share Posted April 26, 2021 Hello, I am testing the workflow: DxO PureRAW and AP. Since the lens correction is already done in PureRAW, I have created another preset ("Without_Correction") in the Develop Persona. This preset is displayed as selected. But you have to click on the preset again and again to use it, because it seems that the preset "Standard" is always active, which you can also see in the settings that belong to "Standard" and not to the new preset. Only after clicking on the "Without_Correction" template its settings (all deselected) are used. regards, Uwe Quote Link to comment Share on other sites More sharing options...
Old Bruce Posted April 26, 2021 Share Posted April 26, 2021 8 minutes ago, UweN said: This preset is displayed as selected. But you have to click on the preset again and again to use it, This has been driving me up the wall for years. Quote Mac Pro (Late 2013) Mac OS 12.7.4 Affinity Designer 2.4.1 | Affinity Photo 2.4.1 | Affinity Publisher 2.4.1 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that. Link to comment Share on other sites More sharing options...
phil_k Posted April 27, 2021 Share Posted April 27, 2021 Since I use a Canon camera with Canon lens the lens correction is applied by the camera. I have turned off lens correction in Affinity Photos develop persona assistant and then apply it only when I have a raw file requiring correction. Quote Link to comment Share on other sites More sharing options...
Staff Chris B Posted April 27, 2021 Staff Share Posted April 27, 2021 This is a known issue and I will give it another bump - sorry everyone. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted July 28, 2023 Staff Share Posted July 28, 2023 The issue "Develop Persona - Last used preset shown in list but not applied" (REF: AFP-522) has been fixed by the developers in internal build "2.2.0.1925". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.