mpv
mpv copied to clipboard
DOCS: document P3-D65 primaries and two missed in format
display-p3 was undocumented and EVERYONE somehow uses dci-p3 with funny DCI whitepoint, that no one should target and no iPhone photo uses! Oogh.
as https://github.com/mpv-player/mpv/issues/9620#issuecomment-1021971768.
--target-prim is primary only, doesn't matter what tfc, wp, cct it is.
rather than call it display p3, i'd like to call it dci-p3-d65
https://en.wikipedia.org/wiki/DCI-P3#System_colorimetry
Commits should be squashed
rather than call it display p3, i'd like to call it dci-p3-d65
We cannot: this is part of public API now. What is done is done. See https://github.com/mpv-player/mpv/pull/5236#issuecomment-351904328
Anyway, squashed and addressed comments. I WILL ADD white points to those two places, sorry. BTW, is there a way to give any white point and primaries to it??? Like Little CMS should not care, does it not??
Also WTF is that??
https://github.com/mpv-player/mpv/blob/6265724f3331e3dee8d9ec2b6639def5004a5fa2/video/csputils.c#L942-L946
Change seems fine to me
BTW, I did check that bt.470m/s-gamut/display-p3 all work for vf format. And no, they are not the same with others in format and yes they do have a perfect roundtrip when format is the same as target. gpu only, gpu-next is not really working with format at least.
@jeeb Please merge.
Any update on this? I'm interested in having the display-p3 option.
Any update on this? I'm interested in having the
display-p3option.
The option already exists. This patch just adds the manpage entry for it.
I will probably merge it eventually. Some day. I think @ValZapod is pushy enough with his comments that he can learn to wait.
Oh okay, I thought it wasn't being passed to VOs. Thanks.
comments that he can learn to wait.
I cannot see your comment. looks like you forgot you blocked. Hilarious.