Camera Support #9968
Canon PowerShot S120 support
This is my first time trying Darktable and it's quite confusing to see that all my photos have an extreme magenta tint. Presumably this is a problem with recreating the Canon white balance adjustments. I've attached an example photo plus a screenshot (which shows the rendered image vs. the embedded JPEG).
I'm using a Canon S120, so maybe this issue is related to #9476.
#3 Updated by Pascal de Bruijn about 6 years ago
- % Done changed from 0 to 50
- Target version set to Candidate for next major release
- Status changed from New to In Progress
- Category set to Darkroom
- Subject changed from Incorrect "camera white balance" for Canon S120 raws to Canon PowerShot S120 support
- Tracker changed from Bug to Feature
We never supported the S120, so it's not a bug at all. So I converted to ticket into the feature request.
Of course yesterday's unsupported camera, can be todays supported camera :)
I just committed preliminary support for the S120 to our development branch (git master).
That said, it may however still not work well with high ISOs.
When running the development branch keep in mind that your image database will be upgraded and will no longer function with version 1.4.2. Also when using the development branch keep regular backups just to be on the safe side.
To check you should shoot a similar generic image in RAW mode for every ISO the camera supports. Then convert those CR2s to DNG (Adobe's DNG Converter generally runs in Wine), and load them in darktable's development branch to check if there are significant differences. Let me know how it turns out.
#4 Updated by Dan Cecile about 6 years ago
Oh, that makes more sense that this is just a feature. Maybe the list of supported cameras could be linked to from the darktable homepage?
:) Anyways, thanks for the speedy turnaround. I've taken the full series of RAWs, converted them to DNGs, and compared the results in the darktable GUI (May 26 git master).Some observations:
- Adobe has more aggressive RAW clipping
- Adobe white balance is warmer (see ISO 1600+)
- When zoomed in, the dominant colours in the noise don't seem to match (but the intensity of the noise matches) (see ISO 1250+)
So that you can see the results yourself, you can download the files (680 MB) from my Google Drive.
There are also two error messages that kept repeating:
[colorin] could not find requested profile `ematrix'! [exiv2] Directory Canon with 25665 entries considered invalid;3not read.
Is the lens info for important for a compact camera? In darktable, it shows as "(65535)".
And one last thing, the base curve looks good but it doesn't quite match the camera's. (Does the camera only have one base curve? Or does it use multiple depending on the image contents?) I've attached the RAW+JPG to my comment here.
I took a look at your blog post about new camera support, but I'm not sure what else needs to be set up now. Just let me know if you need more samples/etc.
#5 Updated by Pascal de Bruijn almost 6 years ago
Our processing is of course not identical to anybody elses. So small different are expected.
Lens identification doesn't work for compact cameras, because the library (Exiv2) we use, doesn't handle them specially. It just displays whatever the vendor puts into EXIF, which essentially is just a dummy value. In theory one could construct a virtual lens name by taking the make/model and min/max focal, min/max aperture (if present at all) and concatenating them, but that's fragile at best. So handling this would quickly become brand specific. You're free to see if the Exiv2 project already has a feature requests about this, and if not, file feature request, but be aware that it's fairly non-trivial to do well.
The basecurves exist to get a ballpark tonality match with camera output, it's rarely exact. And you're free to tweak the basecurve to your own pleasing of course.
One thing that could be added for convenience are the white balance presets, for which we'd require a single shot per white balance preset, as documented on that page.
#8 Updated by Dan Cecile over 5 years ago
- File canon_powershot_s120_white_balance_20140928_184246.cr2.txt canon_powershot_s120_white_balance_20140928_184246.cr2.txt added
- File canon_powershot_s120_white_balance_20140928_184241.cr2.txt canon_powershot_s120_white_balance_20140928_184241.cr2.txt added
- File canon_powershot_s120_white_balance_20140928_184237.cr2.txt canon_powershot_s120_white_balance_20140928_184237.cr2.txt added
- File canon_powershot_s120_white_balance_20140928_184233.cr2.txt canon_powershot_s120_white_balance_20140928_184233.cr2.txt added
- File canon_powershot_s120_white_balance_20140928_184229.cr2.txt canon_powershot_s120_white_balance_20140928_184229.cr2.txt added
- File canon_powershot_s120_white_balance_20140928_184225.cr2.txt canon_powershot_s120_white_balance_20140928_184225.cr2.txt added
- File canon_powershot_s120_white_balance_20140928_184222.cr2.txt canon_powershot_s120_white_balance_20140928_184222.cr2.txt added
- File canon_powershot_s120_white_balance_20140928_184218.cr2.txt canon_powershot_s120_white_balance_20140928_184218.cr2.txt added
Hi Pascal, I've attached the Perl output for each of my camera's 8 white balance presets. (Each preset can have 19 different blue-amber settings, but I just left everything at defaults and only did 8 shots.) Let me know if there's any problem with these files.
#12 Updated by Dan Cecile about 5 years ago
OK, here's a link to the 8 raw files (84 MB total size):
#13 Updated by Pedro Côrte-Real over 4 years ago
- % Done changed from 20 to 100
- Status changed from Incomplete to Fixed
Thanks for submitting these,
The presets have been added in this commit: