HSL adjustment layer with CR2 files

[MarcGG]

Hi everyone,

The bug I'm going to mention takes place after opening a CR2 file in Affinity Photo 1.10.5.1342 in Windows 10, then developing the image (clicking on the "Develop" button) and creating a HSL adjustment layer.

The HSL parameters (Hue Shift, Saturation Shift, Luminosity Shift) work as expected, however, when modifying a color to which these parameters apply, it does not work properly.

For example, when selecting the first color slot (which is red by default), and changing it to a blue color, it is still the red color that is affected by the modifications. The same issue appears for the other color slots. It appears the HSL adjusment does not modify the color choice and keep, no matter what, the default color in each slot.

I tried it with, and without hardware acceleration. The problem was the same.

However, when opening a JPG, this issue is fixed (the color selection of HSL works properly).

So the bug comes possibly from opening a raw file (possibly only for CR2 files, I did not try other raw formats).

A workaround would be to export the file in PNG, JPG, or other and then open the exported file. Saving the file in afphoto format does not work (HSL still does not work properly after opening the afphoto file).

Let me know if you need other informations to reproduce the issue.

Best regards,

Marc.

Test sample.CR2

[Komatös]

Hi @MarcGG and welcome to the forums.

Use the colour wheel to set the range to be taken into account. You can change the colour by moving the slider of the colour band.
 

[MarcGG]

Hi @Komatös,

Indeed, but when changing the color and color range on the wheel, nothing changes, it is still the default color and color range of the slot that I changed that will get the modifications (see the 4th screenshot on the picture I gave. The over-saturation is still applied to the reds, while the blues did not change).

Did you try with the CR2 test sample I gave ? If it worked for you and not for me, then it must be an issue on my computer and not on Affinity Photo.

[Ron P.]

6 minutes ago, MarcGG said:

Did you try with the CR2 test sample I gave ?

Yes, as a matter of fact I did.

Moving the nodes on the color wheel, fine-tunes the range of shift within those. For example in your case, after selecting the Red Hue, and then moving the Saturation to 100%, moving those nodes only make subtle changes, since you have not actually done any shifting. You need to experiment, with moving each one of those, then using the Hue Shift slider see what changes they make or don't make.

 

[Komatös]

Hi @MarcGG 

See what happens when you move the beginning of the spectrum of effects into the green area. If you want the blue tones to be stronger, you should add another HSL adjustment layer and then select blue there.

 

[carl123]

30 minutes ago, MarcGG said:

Indeed, but when changing the color and color range on the wheel, nothing changes,

This is because your Assistant Manager setting for RAW Output Format is set to RGB/32

If you set this to RGB/16 it will work as you are expecting (you can also change this document setting after developing the image)

I don't know enough about RGB/32 to know if this is a bug or not

[MarcGG]

Hi everyone,

@carl123 Yes ! That's it ! That was the issue. The HSL adjustment works as it should now when I set the output raw format in RGB/16.

@carl123 @Komatös@Ron P. Thanks everyone for the time and effort you put in solving this issue. So the HSL adjustment does not work properly when setting the raw output format to RGB/32.

[MarcGG]

If it may help in some way for the dev team, it is the same issue as reported here : 

 

[NotMyFault]

HSL has a bug in RGB/32.

To my experiments, it works correct in RGB/16.

To make it easy to spot any potential flaw, you can load the file containing all 360 HUE values, and adjust the HSL settings.

In RGB32, when you choose one of the HSL color spots, changing of the source range (by mouse or color picker) has no effect at all.

It is independent form the type of image (jpeg or CR2). As the bug only affects RGB/32, jpegs are not affected as they only use RBG/8. If you convert them to RGB/32 manually after opening them, there are affected. Not because of jpeg format of the source file, but because of RGB/32 format of the document.

As the bug is already reported & acknowledged by Affinity, I can't see anything new in this report.

all HUES and HSL.afphoto