HSL adjustment layer - Hue target range selection not working

[_Nox_]

Hello everybody,

the following error already occurs since version 1.x of Affinity Photo and was already described in the respective forum and declared as a bug.

When applying an HSL adjustment layer to a 32-bit RGB file, the hue selection does not work correctly. The bug can be reproduced.

I am running Affinity Photo 2.0.3 on Windows 10 Pro x64 22H2. Hardware acceleration is active, but the error occurs even if it is disabled.

The following step-by-step guide can be used to reproduce the bug and for details about it. The screenshots are from version 1.x of Affinity Photo, but the procedure is the same for version 2.x as well.

1. Start Affinity Photo.
2. Go to "File" --> "New...".
3. Create a new file with the following properties:
   
4. Place a new image (from file) by going to "File" --> "Place..." on the background.
5. Add a HSL layer. The work area should look like this:
   
6. Now open the HSL adjustment layer and pick one of the six predefined colors. Since I want to change the red and yellow colors I pick the red dot. Now decrease the saturation to 0 %. First of all, it seems everythings works fine:
   
7. Now drag the four color dots to another color like blue. The expected behaviour would be that the red colors get saturated again and the blue colors get gray. Since there are no blue colors in the picture the picture should look like the original again. But what is happing actually is, that the red colors are still unsaturated and although the outer ring of the color wheels shows gray "blue" colors nothing has happend in the picture:
   

8. It does not change anything if you try to use the "Pipette" instead of draging the four dots.

When working with an 8 or 16 bit RGB file, the HSL adjustment layer works just fine and as expected.

The original posted bug was found on MacOS. I guess the MacOS version is still affected.

Feel free to ask me for more information. I hope my findings provide some information on how to deal with this issue and find a solution to it for me, as well.

 

[EmT]

Hi @_Nox_

We are aware of this issue and I've passed your comments along to the devs to help with their investigation.