More > JRiver Media Center 31 for Windows
JRVR Feature request - Native colorspace playback option
karmat63:
So, just trying to understand, if I profile a display that has a full DCI.P3 coverage, then I create a 3DLUT in 2020 color gamut.
I'm wrong or this is not optimal as the display is far from 2020 coverage? I've tried, and on verification, there are significant errors in color reproduction (DE > 4 in some patches)...
mattkhan:
--- Quote from: karmat63 on May 27, 2023, 06:26:57 am ---So if a 3DLUT is built in DCI.P3, the correct setting would be DCI.P3?
--- End quote ---
If this outputs dcip3 but your pj expects 2020 then I would expect it's going to be wrong
karmat63:
I've corrected my answer, sorry...
I think you'right, but what is the solution?
mattkhan:
You are correct in that creating such a lut can lead to errors
You need a way to let the lut not define the output colourspace basically or you need a way to transform your lut with another one that essentially fits it into bt2020. I am not aware of displaycal being able to do this. I think colourspace can (but that is ££££), probably Argyll can at the cli but I have no idea how to do that.
Hendrik:
In general it is assumed that the LUT outputs pixel values that are designed for your monitor to display, so no further color processing is performed on them by JRVR. This allows you to actually create rather complex 3DLUTs, eg. some that not only correct, but also transform.
It would be possible to do further processing after, but I fear that might introduce a lot of complexity for very niche scenarios, when in reality the 3DLUT should probably be designed to just output the expected values.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version