Jump to content

Recommended Posts

Posted (edited)

Version: 1.10.0.1127

Platform: Windows10

 

Steps:

Adjust some settings and change the white balance in the "Develop Persona" and save it as a preset.

image.png.a5bda623dd817761d30c1c7b587845bf.png

Close the "Develop Persona" and reopen it and choose your saved preset, white balance is set as default = 0%

image.png.c768f74bfa36a2ff8e865dd4a1a7e8d7.png

Edited by dverleysen
Posted

I believe that once you Develop the picture, it's white balance is fixed, and if you re-enter the Develop Persona whatever you previously set it to is its default. You would need to start over with the RAW file again.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Posted
On 8/19/2021 at 1:47 PM, walt.farrell said:

I believe that once you Develop the picture, it's white balance is fixed, and if you re-enter the Develop Persona whatever you previously set it to is its default. You would need to start over with the RAW file again.

What good is a preset if that's the case? The OP created a preset so it can used for other images, but discovered the preset settings did not stick, were reset to 0

EDIT

Ok, I see what's happening. Even though when you reopen, or just attempting to develop another image, it shows your preset in the drop-down menu choice, you must click on it. Which opens the drop-down, showing all your presets you have saved there, you still need to click on the preset choice. Then it should change, in the OP's situation, the WB settings will be applied.

IMO, it should revert to Default, instead of the preset that hasn't been applied.

Affinity Photo 2.5..; Affinity Designer 2.5..; Affinity Publisher 2.5..; 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

Posted
16 minutes ago, Ron P. said:

What good is a preset if that's the case? The OP created a preset so it can used for other images,

But then he, I think, went back into the Develop Persona with an already Developed image. Even if the values in that Preset were preserved, I don't think they would work except for a RAW image. But I still need to do some testing.

 

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Posted
10 minutes ago, walt.farrell said:

But then he, I think, went back into the Develop Persona with an already Developed image. Even if the values in that Preset were preserved, I don't think they would work except for a RAW image. But I still need to do some testing.

 

I was adding to my post when you replied. I agree if you develop the RAW file, then go back into the Develop Persona, you're no longer dealing with a RAW, but a JPG file, and the WB is not going to reflect the Kelvin settings, but the percentage.

EDIT

Still something a little strange going on. I tested developing a RAW file, then going straight back into the Develop, and the WB section box was not and would not check automatically, as it does when using a preset with a RAW file.

I also tested using a JPG file, going straight into Develop, created a Preset, developed, then tried going back. Also trying a RAW file and applying the preset I saved from the JPG file. The WB section would not be selected, BUT, when I checked the box for WB, it opened with settings apparently being the Kelvin equivalent to the percentage I set it to.

Taking a JPG file into the Develop, and the WB not be selected after applying the preset, I checked the WB box to apply it, and found the settings for the preset to be correct.

So the behavior is different between RAW and JPG type files in the Develop Persona.

Affinity Photo 2.5..; Affinity Designer 2.5..; Affinity Publisher 2.5..; 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

Posted
10 minutes ago, walt.farrell said:

But then he, I think, went back into the Develop Persona with an already Developed image. Even if the values in that Preset were preserved, I don't think they would work except for a RAW image. But I still need to do some testing.

 

Maybe my first post was not so clear ;)

When using the preset with "another" image the white balance is not saved in the preset, so you have to redefine the white balance.

Posted
5 minutes ago, dverleysen said:

Maybe my first post was not so clear ;)

When using the preset with "another" image the white balance is not saved in the preset, so you have to redefine the white balance.

See my post above

Affinity Photo 2.5..; Affinity Designer 2.5..; Affinity Publisher 2.5..; 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

Posted

Well, well, well, now I get what dverleysen is getting. The preset settings are not preserved as they should be. I don't know why they were for me just a few minutes ago.

 

Affinity Photo 2.5..; Affinity Designer 2.5..; Affinity Publisher 2.5..; 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

Posted

White Balance is always set to 0%/0% for already-developed images (at least JPG), as far as I can see, if you take them into the Develop Persona.

If you have a RAW image in the Develop Persona, and save a Preset with a White Balance setting (in K/%), and then use that Preset on another RAW image, the K/% values are used. (Note that on that second image, you may need to switch from your preset to another one (such as Default) and back in order to see the values. I believe there's a known bug where the Preset name is shown but nothing from it is applied. You need to switch to the Preset for it to take effect.)

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Posted

For me the issue is nor bound to WB, but any adjustment. When creating a preset, it is "active" as chosen preset. Apply to develop the RAW to pixel layer. When re-entering Develop Persona, the last used preset is shown as selected, but it is not applied. To apply it, you need to select default (or another preset), and the select the saved preset again. It the becomes applied.

So at this time i see only the UI issue that the last used presets is shown as selected, but is not applied before getting re-selected.

So the best correction would be to always select "default" when re-entering Develop persona.

I may have missed other issues you are trying to explain.

Mac mini M1 A2348 | MBP M3 

Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.

 

Posted
15 minutes ago, NotMyFault said:

I may have missed other issues you are trying to explain.

The White Balance issue is that even after following the steps you suggest (select Default, then re-select the Preset you want) the White Balance values are always 0%/0% if you're working on an already-developed image (either a RAW that you developed, and then returned to the Develop Persona, or a JPG file that you're working on).

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Posted

To be honest, in my view the Develop Persona is overdue to an complete refactoring.

It is almost useless - except to get RAWs as fast as possible converted into pixel layers. There are so many unsolved UI issues, and except initial exposure and lens correction, all edits can be done better (non-destructive) in Photo Persona.

  • Want a crash? Select Blemish Removal Tool, set radius to 4096, click once. Photo is gone immediately. Yes, input is erratic, but apps must check for and clear erratic input instead of crashing.
  • Several UI actions temporary remove all edits (info panel, cross-hair usage) > 6 month.
  • Defringe quirks (on Windows), e.g. Remove opposite hue not working since >6 month.
  • Defringe UI: Affinity tried hard (and successful) to mix up every UI element vs. Photo Persona
  • Ignores most parts of Canon's "picture profiles"
  • Low-quality CA removal (vs. Canon OOC and DPP)
  • Destroying 3:2 aspect ratio by including 20-24 garbage edge pixels for 24 Mpx RAWs
  • Every time i'm bored and try something in Develop Persona i found old or new issues. More to be discovered
  • Missing ability to really create "recipes" (presets) and batch-apply to multiple RAWs.

Mac mini M1 A2348 | MBP M3 

Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.

 

Posted
15 hours ago, NotMyFault said:

It is almost useless - except to get RAWs as fast as possible converted into pixel layers.

Yep, I use it occasionally to view the odd raw file but never for raw developmet

I've just created a white balance preset (Temp 6000K, Tint 0) with a raw file in develop. It saved ok and works fine on any raw

I also created a white balance preset (Temp 100%, Tint 0) with a rgb file in develop. It saved something but nothing happens when subsequently used on anything, nuts

Microsoft Windows 11 Home, Intel i7-1360P 2.20 GHz, 32 GB RAM, 1TB SSD, Intel Iris Xe
Affinity Photo - 24/05/20, Affinity Publisher - 06/12/20, KTM Superduke - 27/09/10

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.