Adjustment - Curve settings not working (EOS R6, CR3 RAW)

[Stasi]

Info:
Camera: Canon EOS R6
OS: Windows 11 PRO
CPU: AMD Ryzen 7 7700
VGA: ATI RX 6600XT
RAM: 32GB
HW acceleration: on (disabling has no effect on the bug)

How to get the bug:
- develop RAW
- adjustment -> Curves
- move the bottom left point up

The procedure and result can be seen in the attachment.

It also shows up in the latest public beta (2.3.1.2217)

Maybe related to:

 

CurvesProblem.zip

[Dan C]

Thanks for your report @Stasi!

I can confirm I've been able to replicate this issue within 2.3.1 - it appears to only occur when developing to 32bit RGB output.

If you open Edit > Settings > Assistant > Develop Assistant and change this to 16bit, then redevelop the image, you should find it no longer appears:

24 minutes ago, Stasi said:

Maybe related to:

I agree this above issue is related, as I've also tested using your RAW file within our currently unreleased internal 2.4 beta and this appears to be fixed already, using either 16bit or 32bit developing.

Therefore once this 2.4 beta version is available, you should find this issue no longer occurs with any Develop Assistant settings!

I hope this helps

[Stasi]

23 hours ago, Dan C said:

Thanks for your report @Stasi!

I can confirm I've been able to replicate this issue within 2.3.1 - it appears to only occur when developing to 32bit RGB output.

If you open Edit > Settings > Assistant > Develop Assistant and change this to 16bit, then redevelop the image, you should find it no longer appears:

I agree this above issue is related, as I've also tested using your RAW file within our currently unreleased internal 2.4 beta and this appears to be fixed already, using either 16bit or 32bit developing.

Therefore once this 2.4 beta version is available, you should find this issue no longer occurs with any Develop Assistant settings!

I hope this helps

Hello,

today installed version 2.4.0.2222 still not working - on 32bit the same problem.

Petr

[Dan C]

On 1/9/2024 at 5:24 PM, Stasi said:

today installed version 2.4.0.2222 still not working - on 32bit the same problem.

My apologies, in further testing it appears as though this issue is dependant on the Tone Curve Develop Assistant setting - which I had not realised was different in my beta version compared to the retail version.

Setting the Tone Curve option to Take no action will stop this occurring when developing to 32bit, as shown below:

 

I'll be sure to update the development log with this information now, as clearly further improvements can be made by our team. Thanks for letting us know