How to manage the iso of a sensor that has noise differences between the electronic shutter and the mechanical shutter

[AprentiUnity]

Is your feature request related to a problem? Please describe.
Some cameras, such as the Canon R6 Mark II, have more noise at the same iso value between mechanical and electronic shutter. So I don't think that correction profiles designed for the mechanical shutter are suitable for correcting photos taken with the electronic shutter.

Describe the solution you'd like
Would it be possible to add electronic shutter correction profiles to darktable in addition to the mechanical shutter profile? And if the information in the exifs allows it, let darktable choose one of the two profiles automatically.

Alternatives
Display the corrections for the electronic shutter in the drop-down menu of the module and let the user choose by himself.

[github-actions]

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

[AprentiUnity]

Hello,
I see that my idea interests other people. Could someone take a closer look at it and perhaps plan to integrate it into Darktable ? Thanks in advance.

[wpferguson]

It would help if there were a set of electronic shutter noise profiles and images taken with electronic shutter so that we would have something to work with.

[akapitany]

Thank you very much to take care of this question, I also use the ES a lot...

I created the profile according to this guide:
https://pixls.us/articles/how-to-create-camera-noise-profiles-for-darktable/

I'm not sure I did everything properly, but it definitely handles the chroma noise well. To remove the luma completely, I also need to use the contrast equalizer module, I don't know how good that is.

If you give some advise I'm open to redo the profiling.
darktable-noiseprofile-20250102.tar.gz

I will send some high and low ISO samples soon...

[github-actions]

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.