Skip to content

Panasonic LUMIX L10 noise profiles - #21528

Open
andriiryzhkov wants to merge 1 commit into
darktable-org:masterfrom
andriiryzhkov:np_dc_l10
Open

Panasonic LUMIX L10 noise profiles#21528
andriiryzhkov wants to merge 1 commit into
darktable-org:masterfrom
andriiryzhkov:np_dc_l10

Conversation

@andriiryzhkov

@andriiryzhkov andriiryzhkov commented Jul 11, 2026

Copy link
Copy Markdown
Collaborator

Adds a noise profile for the Panasonic DC-L10. Captured on 25 ISOs from 100 to 25600 with darktable-gen-noiseprofile.

The DC-L10 uses the same 25 MP MFT sensor as the DC-G9M2 (G9II) – Panasonic's L2-generation MFT sensor with on-chip PDAF and dual-conversion-gain readout. DC-G9M2 already has a profile from #17525; this fills the gap for the DC-L10.

Sanity check against DC-G9M2

Since it's the same sensor, the two profiles should be close. Averaged across all 25 ISOs the DC-L10 a values differ from DC-G9M2 by roughly +1% (R), +0.5% (G), and −3% (B). The R/G asymmetry ratio – the fingerprint of this sensor's noisier red channel – sits at 3.0–3.3 in both profiles.

noise_result.pdf
darktable-noiseprofile-20260710.tar.gz

PS: Just to be clear, to create noise profiles I used cameras.xml for Panasonic DC-L10 from the open PR darktable-org/rawspeed#976

@andriiryzhkov andriiryzhkov added the scope: noise profile adding noise profiles for new cameras label Jul 11, 2026
@andriiryzhkov
andriiryzhkov marked this pull request as draft July 11, 2026 10:14
@andriiryzhkov
andriiryzhkov marked this pull request as ready for review July 17, 2026 15:18
@TurboGit

Copy link
Copy Markdown
Member

@andriiryzhkov : The profile is not really good. Looking at the picture in the tarball I see that you are missing smooth transition from mid-tones to highlights.

@TurboGit TurboGit added this to the 5.8 milestone Jul 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

scope: noise profile adding noise profiles for new cameras

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants