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

Tone Curve and WB problems.


Recommended Posts

Since posting the problem I've realised that changing the RAW tone curve/take no action setting in Affinity 1 (which is still on my Computer), dictates the setting in Affinity 2. Changing the status in Affinity 2 does not make any difference. The WB problem remains.

Link to comment
Share on other sites

37 minutes ago, Callaghan said:

changing the RAW tone curve/take no action setting in Affinity 1 (which is still on my Computer), dictates the setting in Affinity 2.

No it does not. They are not connected in any way. I just tested this and changing the settings in V1 has no effect on V2.

The WB issue is not related to the Develop Preferences.

Affinity Photo 2.3..; Affinity Designer 2.3..; Affinity Publisher 2.3..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD

Link to comment
Share on other sites

2 hours ago, Callaghan said:

it does appear that in V2, changing the setting in the Assistant does not take effect until you close and re-open the RAW file.

I don't know if that's intentional (by design) or a bug. I do know Serif is aware of it.  In V1, changing those settings are dynamic, instant.

Affinity Photo 2.3..; Affinity Designer 2.3..; Affinity Publisher 2.3..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD

Link to comment
Share on other sites

  • 1 month later...
  • Staff

The issue "Unable to scroll or use the arrows on the White Balance field in Develop Persona" (REF: AFP-5659) has been fixed by the developers in internal build "2.1.0.1720".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release (this build is not yet available).
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.

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • 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.