Project

General

Profile

Feature #9711

Auto-apply basecurves camera model specific instead of maker specific, if availiable

Added by Jean-Pierre Verrue over 4 years ago. Updated over 4 years ago.

Status:
Confirmed
Priority:
Low
Assignee:
-
Category:
Lighttable
Start date:
12/06/2013
Due date:
% Done:

10%

Affected Version:
System:
bitness:
64-bit
hardware architecture:
amd64/x86

Description

Sorry for my poor english ... thank you google...

First a little explanation of my workflow. I manage my photos with digiKam. I do almost everything with digikam: importing, editing, tags, exports, except of course the processing of raw.
when I modify metadata - assign a tag, for example - Digikam creates a xmp file with many things inside whose tag. The XML namespace used is essentially the xmp namespace defined by Adobe.
The tests I've done show that when dt open a photo for the first time, if the xmp file exists (previously created by dk), it does not apply the D800 curve, but the "like Nikon." curve.
I guess the tests done during the raw opening must consider that the curve is already affected. Is it simply because the xmp file already exists?

I provided the following XMP files:
- Created by dt
- Created by dk
- Created by dk and modified by dt

JPV_3195.NEF.xmp.dt (5.15 KB) Jean-Pierre Verrue, 12/06/2013 08:43 PM

JPV_3195.NEF.xmp.dk (3.22 KB) Jean-Pierre Verrue, 12/06/2013 08:43 PM

JPV_3195.NEF.xmp.dk dt (7.52 KB) Jean-Pierre Verrue, 12/06/2013 08:43 PM

History

#1 Updated by Ulrich Pegelow over 4 years ago

  • Priority changed from Critical to Low

We would need the raw file to reproduce your issue.

#2 Updated by Jean-Pierre Verrue over 4 years ago

I have uploaded 2 Nikon D800E NEF files here http://moisson.free.fr/darktable/

#3 Updated by Ulrich Pegelow over 4 years ago

I would also need the corresponding XMP files for one of those RAWs - equivalent to the ones you attached already.

#4 Updated by Jean-Pierre Verrue over 4 years ago

I have uploaded the corresponding XMP files at the same place : http://moisson.free.fr/darktable/

files with dk extention : xmp created by digikam
files with dt extention : xmp created by darktable (good base curve)
files with dk+dt extention : xmp ceated by digikam and updated by darktable (bad base curve)

#5 Updated by Ulrich Pegelow over 4 years ago

  • Status changed from New to Confirmed
  • % Done changed from 0 to 10

I can confirm. darktable behaves differently in terms of the auto-applied basecurve depending on the presence of a digikam XMP.

#6 Updated by Christian Kanzian over 4 years ago

Ulrich Pegelow wrote:

I can confirm. darktable behaves differently in terms of the auto-applied basecurve depending on the presence of a digikam XMP.

I thought model specific basecurves are not auto-applied at the moment. If I open the .nef from above there is the 'like Nikon' curve. This also is true for my 'Pentax K-5' curve. I have injected my 'Pentax K-5ck' curve into the database before. So I can configured my personal curve to auto-apply via the config dialog, because the via darktable supplied basecurves are locked. Interesstingly both 'Pentax K-5' and 'Pentax K-5ck' appear in bold letters in the basecurve modul then.

Isn't it a feature request therefore? 'Auto-apply basecurves camera model specific instead of maker specific, if availiable'

#7 Updated by Simon Spannagel over 4 years ago

  • Subject changed from dt does not always use the preset base curve to Auto-apply basecurves camera model specific instead of maker specific, if availiable
  • Tracker changed from Bug to Feature

You are probably right... Renaming this.

Also available in: Atom PDF