Project

General

Profile

Camera Support #9968

Canon PowerShot S120 support

Added by Dan Cecile over 3 years ago. Updated over 2 years ago.

Status:
Fixed
Priority:
Low
Assignee:
-
Category:
Darkroom
Start date:
05/22/2014
Due date:
% Done:

100%

Affected Version:
git development version

Description

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.

20140521_0001.CR2 - RAW from Canon S120 (14.1 MB) Dan Cecile, 05/22/2014 06:45 AM

2014-05-21-234817_1920x1080_scrot.png - Darktable 1.4.2 screenshot (1.91 MB) Dan Cecile, 05/22/2014 06:49 AM

20140601_0002.JPG - basecurve JPG (1.14 MB) Dan Cecile, 06/01/2014 01:33 PM

20140601_0001.CR2 - basecurve RAW (10.9 MB) Dan Cecile, 06/01/2014 01:33 PM

canon_powershot_s120_white_balance_20140928_184218.cr2.txt Magnifier (1.03 KB) Dan Cecile, 09/29/2014 03:38 AM

canon_powershot_s120_white_balance_20140928_184222.cr2.txt Magnifier (1.03 KB) Dan Cecile, 09/29/2014 03:38 AM

canon_powershot_s120_white_balance_20140928_184229.cr2.txt Magnifier (1.03 KB) Dan Cecile, 09/29/2014 03:38 AM

canon_powershot_s120_white_balance_20140928_184225.cr2.txt Magnifier (1.03 KB) Dan Cecile, 09/29/2014 03:38 AM

canon_powershot_s120_white_balance_20140928_184233.cr2.txt Magnifier (1.03 KB) Dan Cecile, 09/29/2014 03:38 AM

canon_powershot_s120_white_balance_20140928_184237.cr2.txt Magnifier (1.04 KB) Dan Cecile, 09/29/2014 03:38 AM

canon_powershot_s120_white_balance_20140928_184241.cr2.txt Magnifier (1.03 KB) Dan Cecile, 09/29/2014 03:38 AM

canon_powershot_s120_white_balance_20140928_184246.cr2.txt Magnifier (1.03 KB) Dan Cecile, 09/29/2014 03:38 AM

History

#1 Updated by Dan Cecile over 3 years ago

Actually, changing the "input color profile" from "standard color matrix" to "sRGB" seems to fix the problem, but I'm not sure if this is the correct thing to do and/or whether "sRGB" should have been selected automatically.

#2 Updated by Ulrich Pegelow over 3 years ago

  • Priority changed from Critical to Low

Seems that also the sensor cropping is off. Support for that camera model seems to be not good atm.

#3 Updated by Pascal de Bruijn over 3 years ago

  • Subject changed from Incorrect "camera white balance" for Canon S120 raws to Canon PowerShot S120 support
  • Category set to Darkroom
  • Status changed from New to In Progress
  • Target version set to Candidate for next major release
  • % Done changed from 0 to 50
  • 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 over 3 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?

ISO levels

:) 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.

Error messages

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.

Extras

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 over 3 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.

#6 Updated by Pascal de Bruijn over 3 years ago

  • bitness set to 64-bit
  • System set to all
  • Affected Version set to git development version
  • % Done changed from 50 to 20
  • Status changed from In Progress to Incomplete

Any chance you can provide us with the white balance presets for the S120?

#7 Updated by Dan Cecile over 3 years ago

OK, the WB presets sound easy to do; I'll try to grab it in the next couple days. (And thanks for the earlier explanations about lens identification and basecurves, it's interesting to hear about how these things work.)

#8 Updated by Dan Cecile over 3 years ago

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.

#9 Updated by Dan Cecile over 3 years ago

Oh yeah, I forgot to mention, this is with the original camera firmware, and no newer firmware has been released yet. Unfortunately, I can't figure out how to tell the exact firmware version.

#10 Updated by Roman Lebedev almost 3 years ago

  • Tracker changed from Feature to Camera Support

#11 Updated by Pedro Côrte-Real almost 3 years ago

These presets seem strange as each file has several when it should only really have one. Could you just attach the 8 raw files instead?

#12 Updated by Dan Cecile almost 3 years ago

OK, here's a link to the 8 raw files (84 MB total size):

https://drive.google.com/file/d/0B710_jA5wFt5T0tEZk5yUWlGTGM/view?usp=sharing

#13 Updated by Pedro Côrte-Real over 2 years ago

  • Status changed from Incomplete to Fixed
  • % Done changed from 20 to 100

Thanks for submitting these,

The presets have been added in this commit:

https://github.com/darktable-org/darktable/commit/77bc9e0f05e219a4bade71c392a9f6b3737ae9cd

Also available in: Atom PDF