ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
pounce has quit [Remote host closed the connection]
pounce has joined #wayland
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
ahartmetz has quit [Quit: Konversation terminated!]
pounce has quit [Remote host closed the connection]
pounce has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
carbonfiber has joined #wayland
Brainium has joined #wayland
i509vcb has joined #wayland
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
Brainium has quit [Quit: Konversation terminated!]
Company has quit [Quit: Leaving]
carlos_ has quit [Ping timeout: 480 seconds]
agd5f has joined #wayland
agd5f_ has quit [Ping timeout: 480 seconds]
Company has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
Guest5442 has quit [Remote host closed the connection]
cool110 has joined #wayland
cool110 is now known as Guest5519
Sally[m]123 has left #wayland [#wayland]
gallo has quit [Remote host closed the connection]
gallo has joined #wayland
parbosa has joined #wayland
Company has quit [Quit: Leaving]
sima has joined #wayland
tzimmermann has joined #wayland
parbosa has quit []
i509vcb has quit [Quit: Connection closed for inactivity]
junaid has joined #wayland
junaid has quit [Remote host closed the connection]
___nick___ has joined #wayland
ahartmetz has joined #wayland
Hypfer is now known as Guest5539
Hypfer has joined #wayland
Hypfer is now known as Guest5540
Guest5540 has quit [Read error: Connection reset by peer]
Hypfer has joined #wayland
manuels has quit [Quit: Ping timeout (120 seconds)]
Guest5539 has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
junaid has joined #wayland
junaid has quit [Remote host closed the connection]
jmdaemon has quit [Ping timeout: 480 seconds]
sima has quit [Ping timeout: 480 seconds]
carlos_ has joined #wayland
kts has joined #wayland
kts has quit []
cmichael has joined #wayland
nerdopolis has joined #wayland
kts has joined #wayland
kts has quit [Ping timeout: 480 seconds]
<pq>
EDID base block has gamma value. CTA-861-H says that for the default RGB colorimetry (i.e. nothing else indicated) use BT.709 Item 1.2, which is essentially the home of the footnote saying displays use BT.1886 which says gamma=2.4. Who to believe and when?
<pq>
or is this again the secret contract to achieve system gamma 1.1 if base block says 2.2?
<pq>
FWIW, linuxhw/EDID.git has 96k samples with gamma=2.2, and less than 2.5k samples with other values.
<emersion>
FWIW, edid-decode has a warning when gamma ≠ 2.2
<emersion>
when "Default (sRGB) color space is primary color space" is printed
<emersion>
it checks gamma = 2.2 ("sRGB is signaled, but the gamma != 2.2.")
<emersion>
and also chromaticities match sRGB ("sRGB is signaled, but the chromaticities do not match.")
<pq>
oh, naturally yes, because sRGB is approximately gamma 2.2. Saying otherwise would be inconsistent indeed.
<pq>
but default RGB colorimetry can also be not sRGB AFAIU
<emersion>
i see
<pq>
then gamma does not need to be 2.2 either, I guess
<pq>
there is an explicit bit in base EDID saying that the default RGB colorimetry is sRGB, and if the bit is set, then primaries and gamma *must* be according to sRGB.
<pq>
..."If display is sRGB compliant"
<pq>
whatever sRGB compliant means
<emersion>
"does not blow up the whole building when sRGB data is sent"
<pq>
I'm fairly sure not blowing up depend on timings and not colorimetry.
<pq>
While reading all this, I've come to the conclusion that the base block primaries might not be be physical primaries.
fmuellner has quit [Ping timeout: 480 seconds]
<pq>
base block primaries apply only when using the default RGB colorimetry *with an IT video mode*
<pq>
I wonder if one could find out the practical primaries of a consumer HDR display by looking at primary gradients; when the gradient goes flat as saturation increases, the cut-off point is the primary.
<drakulix[m]>
Hmm, the state of the next wayland meeting doodle is unfortunate. d_ed and bl4ckb0ne have no overlap. Are any of you fine with skipping this one or should we delay the topics till next week?
<d_ed[m]>
next week is a big kde conference
<d_ed[m]>
as in, from the 15th for a week
<d_ed[m]>
but you can meet without me, Vlad is on the same page as me for most things
<bl4ckb0ne>
im fine reading the notes
<drakulix[m]>
Thanks you two. I'll roll a dice then. 😂
<pq>
"Monochrome displays shall indicate the appropriate white point x, y coordinates regardless of the actual color" - curious, wonder what that means. White point is arbitrary? Or matches the monochrome color?
junaid has quit [Remote host closed the connection]
gspbirel56873408 has quit []
gspbirel56873408 has joined #wayland
cmichael has quit [Quit: Leaving]
junaid has joined #wayland
nerdopolis has joined #wayland
tzimmermann has quit [Quit: Leaving]
junaid has quit [Read error: Connection reset by peer]
i509vcb has joined #wayland
bodicceaII has quit [Remote host closed the connection]
bodicceaII has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
jmdaemon has joined #wayland
fmuellner has joined #wayland
ciara has quit [Ping timeout: 480 seconds]
ciara has joined #wayland
keir- has quit []
keir has joined #wayland
DynamiteDan has quit []
DynamiteDan has joined #wayland
junaid has joined #wayland
___nick___ has quit []
___nick___ has joined #wayland
Narrat has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
___nick___ has quit [Ping timeout: 480 seconds]
DodoGTA has quit [Quit: DodoGTA]
DodoGTA has joined #wayland
Moprius has joined #wayland
Moprius has quit [Remote host closed the connection]
sima has quit [Ping timeout: 480 seconds]
alatiera has quit [Quit: Ping timeout (120 seconds)]
alatiera has joined #wayland
fmuellner has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
columbarius has joined #wayland
junaid has quit [Ping timeout: 480 seconds]
rederick29 has quit [Remote host closed the connection]
gilvbp has joined #wayland
Ishq has joined #wayland
<Ishq>
Hello, Is it possible for you to know what screen you are hovering over? Something like xwininfo for wayland? It seems this might have to be compisitor specific?
<Ishq>
(Sorry, by screen, I mean application window)
ahartmetz has quit [Remote host closed the connection]