LibRaw is limited to whatever raw data is. Processing of raw data (white balance, colour space conversion, gamma) is out of the scope of main LibRaw functionality, we keep such processing for testing purposes only. LibRaw is not a raw converter and isn't meant to be one ;)
Btw, I'm wondering how useful (or harmful?) is it to have that huge ACES AP0 output color space when LibRaw is limited to uint16 representation...
Sounds like an AP1-based ACEScg D65 adapted option would be good to have as well?
One should perhaps clarify in the docs that AP0 based "ACES2065-1 adapted to D65" is meant by the existing "ACES" enum?
> My apologies if I offended or annoyed you.
Not in the least.
> I was under the mistaken impression that the ICC profiles are simply assigned on output
They are not, but even if they were, what good is it to assign one profile while converting to a different one?
I checked, and yes, Coffin's aces_rgb matrix isn't adapted to D65.
Fixed in master now (the changes are in src/tables/colorconst.cpp) https://github.com/LibRaw/LibRaw/commit/1974214acf47ef260853d74006765746...
My apologies if I offended or annoyed you. I was under the mistaken impression that the ICC profiles are simply assigned on output
I think I made it clear what I'm referring to, and so did you. We can't fix what is not there. Your proposal is technically impossible (and in any case, the starting point is the matrix in the standard), and I explained what we are going to do. Let's return to the topic only when there will be anything new to discuss.
To which matrices are you referring? The cam2rgb matrices? I am talking about what's in the actual icc profiles embedded in the images, to be clear.
I'm saying that matrices in Coffin's workflow are of a different nature (his workflow doesn't use "forward matrix for ACES", or "ACES colour profile", so no place to change it), and that we will check aces_rgb matrix to see if the chromatic adaptation from ACES "D60-like" white point to D65 necessary for Coffin's workflow is missing.
I checked the ProPhoto and sRGB XYZ values, and when arranged in a matrix the rows sum to the expected D50 values. The ACES one was the only one that was abberant.
The D65 part comes in the MediaWhitePoint tag in the ICC profiles. There's no issue with that, I'm aware of that aspect of Coffin's color profiles and they have correct values in the MediaWhitePoint tag.
The XYZ values in the ICC profile which form the RGB to XYZ matrix ('forward matrix') though should sum to the connection space illuminant however, which is D50 regardless of the media white point. This is because these values take it from the connection space, which is CIE D50 2 degree observer XYZ space, to RGB, and chromatic adaptation to the media white point is done from there. See section 18.104.22.168 of https://www.color.org/specification/ICC1v43_2010-12.pdf
In any case, the sums of the XYZ values found in the ACES profile I extracted are 0.97056 1.00145 0.76492 respectively. Looks like it's almost the correct set of values, but somewhere along the way there was probably a typo. I'm not sure if this is exclusive to libraw or if this was also present in the original dcraw since I don't have the original dcraw currently.
Thanks for getting back to me!
> Note that even if the white point is D65 or D60, the rows of the forward matrix should sum to the D50 values.
Not in Coffin's workflow, he uses D65 to avoid an extra step of chromatic adaptation (check his ProPhoto RGB, for example).
Also, aces_rgb is not a forward matrix, it's sRGB to ACES matrix (see identity matrix rgb_rgb for sRGB).
We will check the aces_rgb matrix to make sure it follows the same logic as other matrices.
Seems ECW Demosaicing looks similar to the one Capture One uses 2021.
Without coding, just using a simple script with calls to: dcraw.exe, exitfool and dng_validate from Adobe, I have managed to create some synthetic valid DNG files:
- Linear light decomposition to balance different colour temperatures in RAW
- Mean stacking to mimic ultra low ISO/ND filter
- Median stacking to remove moving subjects
- HDR RAW
Thank you. Now I use command line tool to decode. Alexa LF plus W is the camera of the ARI file that I exported with other software.
We use Adobe DNG SDK to create DNG.
Last LibRaw public snapshot supports some Arri models if compiled with LIBRAW_OLD_VIDEO_SUPPORT defined. Not sure that LibRaw support this specific camera (Alexa LF listed as supported, do not know what is pus W)
We plan to continue Arri support up to release 0.21, than drop this support: LibRaw is not about video.
Please consider use of other API (e.g. Arri SDK)
Please advise the author of the program in question to check https://www.libraw.org/blog and to use the current LibRaw version.
I Have a question about .cr3 format by canon.
When I add .cr3 files and start stacking the program is not creating stacked file.
Could you help me with this issue?
right you are, now that is shameful.
Yeah, I barely ever develop/compile any code on windows. I wouldn't try and use 'rm' in the Win CMD but I thought the Makefile.MinGW will be fully Win-compatible.... I guess not, didn't think straight, this lack of movement due to COVID is eating away on my braincells.
Good find and lazy me, great community here!
You are running mingw32-make from cmd.exe shell, and rm command does not exist in DOS. Even if you have the MSYS bin directory in your PATH where MSYS rm.exe lives, its behavior is probably strange/undefined under cmd.exe...
I prefer to use the MINGW (bash) shell from the start menu and traditional make (installed under MSYS) instead of ming32-make, the behavior is much more consistent with all other *nix platforms and build scripts.
right... so I removed line 134: rm -f lib/libraw.a
from the Makefile.mingw and it finished as expected. Not sure why the rm throws an error. Running it again throws no error even with the rm sinc the 'lib/libraw.a' then exists. Windows... :-/
thanks for the help. Now I'm working on windows defender accepting the compiled *.exe and NOT starting thread alerts everytime they run. Only happens to compiled ones. I'll get it done.
thanks again. Any usage questions I'll post elsewhere.
'normal' rm should not raise return error code if rm -f [nonexistent-file] is used
Because your rm is not 'normal', you may try to remove rm -f lib/libraw.a statement from makefile
this is the error message:
rm -f lib/libraw.a
process_begin: CreateProcess(NULL, rm -f lib/libraw.a, ...) failed.
make (e=2): The system cannot find the file specified.
mingw32-make: *** [Makefile.mingw:134: lib/libraw.a] Error 2
here's the entire console output:
never stumbled upon this error, but I suppose it must be my setups then. Tried on two machines one with msys, one with mingw freshly installed.
I don't compile a lot for windows, but I need it running on there since I'd implement it for automation. I wish github would just offer some virtual machines for compiling binaries for whatever platform one needs, still seems a hassle on Win-machines.
Thanks for your comments and help.