Hi all …
not sure if there is an answer to my question , regarding the missing color matrix within a DNG created with RawForge plugin created by Ayeda Okambawa .
The plugin works just fine giving me better results than the NIND AI denoise , well at least after some testing from my side … but this might be just me .
Once the DNG is created and appears in the LT , a warning pops up … " Canon EOS R5 II color matrix not found . When opened in the DR … the same happens every time when i do change settings in various modules .
Does DT not support the RawForge DNG´s , or could there be another issue somewhere in workflow .
As far as I know, basic darktable doesn’t export to or write DNG. So that would mean the plugin does the exporting, and doesn’t include the color matrix (or not correctly)…
You may have to discuss that with the author of the plugin.
It is of course possible that your version of darktable doesn’t accept a (newer) DNG version written by a plugin. But I wouldn’t expect that to give the result you see.
Anoher point: does darktable now support third-party plugins? or is it a matter of darktable calling an external program? With a “real” plugin, I wouldn’t expect to go through a DNG to get the plugin’s result into darktable…
I was able to replicate the issue and found a workaround:
In darktable, open the DNG, go to the input color profile module, and change the setting to Embedded color matrix. This should resolve the color matrix not found warning.
Hi Ayeda …
thx for your reply .
It does work partly , as the warning disappears in the LT .
As soon as i open the file in the DR , it does pop up again .
Every time you try to edit a module , it does pop up again … with every additional module again ?!
So something is wrong with the created DNG on that front .
If want to copy the settings or edits i made to the original … to the DNG , nothing is happening . Like i can do with DNG´s created by Pure Raw 6 ?!
THX for your reply …
Latest nightly build … no issue with the camera , as it is fully supported .
As said above … it is only effecting the RawForge DNG !!!
MacOS M1 Tahoe 26.4 .
Something else is " funny " … as the created DNG is not supported by my Asset manager which is the Fast Raw Viewer … so it seems not a DT only issue !!!
I think I fix it. It’s more like a patch/workaround since the root issue seems to be in the DNG generated by RawForge. Now in the script, I add one missing DNG metadata field so darktable knows how to interpret the camera colors. If you want to try it, here is what you have to do:
In the terminal, do cd .config/darktable/lua/<folder_name>/. In my case the folder is named Custom, but you may have named it differently when you installed RawForge.
Thx Ayeda … for your feedback , much appreciated.
Would like to try …. It .
Maybe a dumb question , but what git pull should I perform ?
Your lua script ?
Hey ho … i´m not too dumb , thanx for the update .
Now it works …
Glad you that you changed something else , one get now the messages what is going on with the plugin … very nice !!!
Still a interesting fact with the DNG , I do not see a thumbnail of a RF DNG in Fast Raw Viewer … but I do see the DNG in the viewer , for whatever reason .
But this is just a minor issue .
Hi Ayeda …
I did find two more " bugs " or small " issues " in the created DNG .
Not sure if you could fix this as well …
First the exif data is not complete or some weird data is transferred .
1st … the f stop is showing 0.0
2nd … white balance is missing
3rd … focus distance is missing
If a shot in portrait orientation is processed … it shows up in landscape orientation , so no auto rotation is working
Would be really cool , if there would be a solution for it
