Project

General

Profile

Camera Support #10907

Sony DSC-RX100 Mark 1, wrong white balance read from RAW files

Added by Gregor Müllegger over 3 years ago. Updated over 3 years ago.

Status:
Incomplete
Priority:
Low
Assignee:
-
Category:
Darkroom
Target version:
-
Start date:
02/08/2016
Due date:
% Done:

20%

Estimated time:
Affected Version:
2.0.0

Description

I'm shooting quite a while with the RX100. Darktable 1 was not able to read the white balance correctly from the ARW raw files that the camera created. The image was always very greenish. As a workaround I converted the ARW into DNG files, using digiKam. Darktable 1 read the white balance correctly from the DNGs.

After upgrading to Darktable 2, the white balance doesn't work anymore for DNGs. The DNGs are when opened in Darktable 2 completely pink, the temperature slider is set to 25000K by default. The ARWs are still very greenish as with Darktable 1.

Is there any more information I can provide to fix this issue?

My camera is set to auto white balance. I'm running Arch Linux with Darktable 2.0.0. The DNG file is attached.

History

#1 Updated by Pedro Côrte-Real over 3 years ago

  • % Done changed from 0 to 20
  • Status changed from New to Incomplete

I have access to one of those cameras and the files seem to work fine. So does the sample that's available in rawsamples.ch:

http://rawsamples.ch/raws/sony/RAW_SONY_RX100.ARW

As for the digikam DNG it seems to encode a broken whitebalance (all zeroes):

Exif.Image.AsShotNeutral Rational 3 0/1000000 0/1000000 0/1000000

The image still loads fine here by falling back to camera neutral whitebalance, and displays 6500K as color temperature (as that's what camera neutral is).

If I had to guess I'd say you're either changing some other module or have a screen calibration issue. It's hard to know though.

#2 Updated by Gregor Müllegger over 3 years ago

Ok I see that the broken all zero whitebalance might be part of the issue. You can see here in this screen how the DNG looks for me (beeing a screenshot rules calibration issues out, and I'm quite confident that my screen is kind of ok calibrated).

http://i.imgur.com/tdtu8Dh.png

The strange thing is that I also tried a DNG file that I know has worked with Darktable 1.x but now shows to be as pink as the first example. You can find the file attached.

Canon RAWs and DNGs converted from those Canon RAWs work find for me.

I upgraded Darktable to 2.1.0 now and the issue persists with the DNG files. The sample file from rawsamples.ch gives me the warning you mentioned that it's unable to read the camera white balance. However the green tint is gone and color temperature is set to 5994K. See the screen below for the error message (it's german, translated it says "Cannot read camera's white balance data")

http://i.imgur.com/64sJuhg.png

I will try to get Darktable 1.x back on my machine and if the issue is there right now with the posted DNG. Thanks for the response so far though! :)

#3 Updated by Gregor Müllegger over 3 years ago

I can confirm that the initially posted DNG (2016-02-07_17-23-13 Snowboardtour Windegg (Gregor) 0015.dng) does work with Darktabel 1.6.9.

See this screenshot:

(I deleted the .xmp files between tests)

#4 Updated by Pedro Côrte-Real over 3 years ago

Deleting XMP files doesn't delete the history from the database. Have you tried discarding the history stacks for these images? Because the DNG works fine for me in the current master (darktable 2.1.x).

Also available in: Atom PDF

Go to top