anyway the second one looks “neutral”, i.e. right
Opened your DNG in RT final release versions 5.4 and 5.5.
Identical and like your second image above.
With Auto Levels only, both appeared as your first image.
I guess its related to this issue
@agriggio How do we solve this case. Is just a camconst.json entry needed?
if I were to do this “in the void”, I’d forget about backwards compatibility and try to stick with the dng specs. in the RT case, this is probably not what users expect, so it’s a tougher call… probably camcost is a good solution – but I haven’t actually tested this specific case
Can you try to change the entry for your camera in camconst.json from
{ // Quality C
"make_model": "Canon PowerShot SX150 IS",
"raw_crop": [ 26, 10, 4364, 3254 ] // cut 2pix left and right
},
to
{ // Quality C
"make_model": "Canon PowerShot SX150 IS",
"dcraw_matrix": [ 13481,-4867,-1063,-2074,9960,2472,-170,1474,3894 ],
"raw_crop": [ 26, 10, 4364, 3254 ] // cut 2pix left and right
},
please?
1 Like
Would it be possible to be more explicit when dng matrix is active. Manual override? Currently you can only really know if there’s a camconst but not really if adobe or dng matrix is active?
Sorry for asking, but where should i put then the file?
I have tried creating a file called camconst.json with the text below in the same dir of the option file (~/.config/RawTherapee) but nothing changes.
{ // Quality C "make_model": "Canon PowerShot SX150 IS", "dcraw_matrix": [ 13481,-4867,-1063,-2074,9960,2472,-170,1474,3894 ], "raw_crop": [ 26, 10, 4364, 3254 ] // cut 2pix left and right },
I’m using the 5.5 appimage. But now i can also try to compile from git.
Thank you.
I don’t know for appimage if it’s possible to change the camconst.json file at all. @Carmelo_DrRaw knows.
If you compile from git just look for the camconst.json in folder rtengine of your git source and change the entry as mentioned in my post. Then build and it should work.
If you want to test, you can extract the content of the AppImage:
./RawTherapee.appimage --appimage-extract
The content will go into an AppDir folder and you can change internal files.
2 Likes
imho they should be treated like an embedded profile, and applied only when selected explicitly, rather than being silently applied when “camera standard” is set. that would make things much more streamlined. however, it might break backwards compatibility…
I’m on Win7
Sorry I meant the royal you or you all, not you personally.
1 Like
Backwards compatibility should get less importance in future imho…
I agree 110% 
1 Like
Matrix committed (this model’s DNG file from Adobe DNG Converter 11.0 only has one illiuminant and one matrix, and it’s for daylight). The fix will be part of RawTherapee 5.6.
1 Like
Thank you a lot it works fine!
@ggc: @paperdigits has been quicker than me to give the answer, anywhay what he wrote is 100% correct.
Let me just add that once the AppImage is extracted (contents actually go into a squashfs-root folder instead of AppDir as far as I remember) and you have modified some files, you have to run RT by launching the AppRun script in the extracted AppImage. Runninf the RT executable directly will not work, as the AppRun script sets several environment variables in order to let the RT executable find the bundled libraries and configuration files.
2 Likes
Sorry for asking again, but i haven’t found out how to obtain the dcraw_matrix values…
I have the same problem with my phone dng, Honor 6a…
Here an “original” dng from opencamera, the jpeg, and the dng from dng converter (that btw fixes the exif that otherwise are not recognized, and this seems to happen with a lot of phones):
Thank you in advance.
Perhaps you can extract the DCP from the DNG with DNG Profile Editor then apply this DCP.
The HUAWEI DLI-L22 has swapped calibration illuminants, so ColorMatrix1 needs to be used:
{
"make_model": [ "HUAWEI DLI-L22" ],
"dcraw_matrix": [ 6984, -812, -975, -4792, 13481, 1381, -1056, 2355, 4873 ] // ColorMatrix1 (D65, wrong order) from Adobe DNG Converter 11.2.1
},
2 Likes