Opening a DNG converted from a EOS 90D CR3 File Errors

[juststur]

Describe the bug

When opening a DNG file converted from an EOS 90D CR3 with Adobe Digital Negative Converter, the error "`Canon Canon EOS 90D' color matrix not found!" will display at the bottom middle of the screen as seen in this capture:

To Reproduce

Load DNGs converted by Adobe Digital Negative Converter. Double click image from Lighttable so it opens in darkroom, message "`Canon Canon EOS 90D' color matrix not found!" will display at bottom of screen.

Expected behavior

No error will display.

Screenshots

Platform (please complete the following information):

• Darktable Version:
• OS:

• Darktable 3.0, Windows 10 Intel HD Graphics 520

Additional context

https://we.tl/t-CHY8oGCTft

[juststur]

Test DNG https://we.tl/t-CHY8oGCTft

[guillaume1410]

Quite strange I don't have the issue on my side, even with your football dng. What versions are you using ? I use adobe digital negative converter 12.1.0.351 and darktable 3.0.0 (not a rc version)

[juststur]

I have the same software versions. Now that I think about it, the XMP was likely created initially by reading in a filename.XMP file created by another RAW editor (been playing around with others that handle CR3 files naively to see if I wanted to switch programs till darktable was updated). I don't recall which off hand...maybe ACDSee Photo Studio Ultimate. Attaching the non darktable XMP and the XMP from darktable.

xmpfiles.zip

[juststur]

I had to grab the non darktable XMP from backup...I had cleared the folder and the error still displays for the images. The non darktable XMP does contain additional metadata about the EOS 90D that darktable seems to ignore (I'd call that silently loosing data).

[jenshannoschwalm]

The message you see results from a color matrix not read/imported from the dng file. An xmp file can contain pretty much everything, so dt might bee "confused".

Please try:

1. re-read the exif data from within dt? (you find it under the metadata tab in selected image[s])
2. open the image in darkroom

After doing so, does the message still appear?

If it does, please

1. remove the image from dt database
2. delete the existing xmp file
3. reimport the image into dt

does the problem persist?

[ptilopteri]

I had to grab the non darktable XMP from backup...I had cleared the folder and the error still displays for the images. The non darktable XMP does contain additional metadata about the EOS 90D that darktable seems to ignore (I'd call that silently loosing data).

converting to DNG would definitely be called "silently loosing data".

[jenshannoschwalm]

I think i understand what is happening but i do not understand how to fix because i don't know that part of the code at all. I see two important things here and they are absolutely not related to the title of this issue.

1. When you have the "external" xmp file existing besides the image file it is "analysed" by dt_lightroom_import when a) importing or b) after discarding the history and reopening in darkroom. Somehow a wrong input color profile is added to the history, so in colorin commit_params looks for DT_COLORSPACE_STANDARD_MATRIX which is not available and thus the error message appears. Also the working profile is set to linearREC709 which also seems to be not correct.

2. Also try to load the given "external" sidecar file -- surprise, surprise -- i have the basecurve and again the wrong input color profile added to history. And - for me an even larger surprise - the console shows a history V1->V2 on the fly conversion!!!

@TurboGit i guess this is something for you when looking at the source history ... BTW this might be another origin of iop_order problems that as far as i remember have never been discussed yet. And, yes, it seems to be a real bug. And, the title of this issue seems to be very misleading.

[juststur]

I was able to clear the error. I believe the sequence of events that lead to the error message was as follows. 1) Use an app that supports CR3 RAW files and writes XMP sidecar files for the loaded RAW files 2) Use darktable to read in DNG files (converted from the CR3) whch are located in the same directory as the original CR3 files. 3) darktable loaded the XMPs in the directory of .xmp and merged the data from the two different RAW file types

I removed the DNGs from darktable, removed all the XMP sidecars, opened the DNG files and do not have the errors any longer.

[jenshannoschwalm]

Yes and sure. Thats of course the thing you observe and what i described in a more technical way. The point is how the second/wrong sidecar file is interpreted by the lightroom-importer.

[aurelienpierre]

Same here with DNG/TIFF from a scanner (with Vuescan or Silver Fast) on latest 3.1 master.

[github-actions[bot]]

This issue did not get any activity in the past 30 days and will be closed in 365 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

[daniel-lucio]

I don't have this problem using 3.2.1.