ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
psykose has quit [Ping timeout: 480 seconds]
RAOF has quit [Read error: Connection reset by peer]
RAOF has joined #wayland
anarsoul has quit [Ping timeout: 480 seconds]
glennk has quit [Ping timeout: 480 seconds]
yrlf has quit [Ping timeout: 480 seconds]
anarsoul has joined #wayland
abeltramo5895238271 has quit [Quit: Ping timeout (120 seconds)]
abeltramo5895238271 has joined #wayland
midgard has quit [Remote host closed the connection]
garnacho has quit [Ping timeout: 480 seconds]
psykose has joined #wayland
midgard has joined #wayland
anarsoul has quit [Read error: Connection reset by peer]
anarsoul has joined #wayland
f_ has quit [Ping timeout: 480 seconds]
f_ has joined #wayland
DodoGTA has quit [Ping timeout: 480 seconds]
yrlf has joined #wayland
<ezzieyguywuf>
whot: ah sounds good thanks for the clarification
anarsoul has quit [Read error: Connection reset by peer]
anarsoul has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
fmuellner has quit [Remote host closed the connection]
nerdopolis_ has joined #wayland
nerdopolis is now known as Guest8970
nerdopolis_ is now known as nerdopolis
Guest8970 has quit [Read error: Connection reset by peer]
nerdopolis has quit [Ping timeout: 480 seconds]
abeltramo5895238271 has quit [Quit: Ping timeout (120 seconds)]
<pq>
I want to keep swick as the patch author, will see how gitlab agrees. hmm... maybe I should do everything locally rather than try my luck with the gitlab UI.
<pq>
I'll update the history branch before squashing
<swick[m]>
mh, can you give me like half an hour to prepare for this occasion? :)
<emersion>
yeah, probably safer to do everything locally
<pq>
swick[m], my lunch takes like an hour, so sure :-D
<pq>
bbl
<swick[m]>
nice! I'll have to prepare something :D
Moprius has joined #wayland
saumon has quit [Quit: Leaving server]
<Drakulix>
now that is truly special occasion! how are we celebrating? :D
<daniels>
> Compared to that, I see your protocol adds the option for clients to provide a custom ICC profile to the server, and expects the server to process it properly.
<daniels>
> Is that a reasonable requirement for all compositors that support per-output ICC profiles?
<pq>
2012, eh. Huh. Not even the first full year at Collabora even, and I knew nothing of Wayland before joining.
<daniels>
> The protocol looks simple and clean, like it should be. I can't really comment on the deeper semantics on color management, though.
<swick[m]>
didn't yet have time to take a closer look
<pq>
daniels, maybe mentioning him in the protocol README file?
feaneron has quit []
<pq>
let's see what I can type up
<karolherbst>
just want to say big congrats to everybody involved with the protocol, glad to see it landing, hopefully when I buy my next display with proper HDR support I can make good use of it
<soreau>
so in the future, monitors are broken and they need software fixes? :P
<soreau>
at least something made it past the finish line, hopefully it works out 👍
<daniels>
*in the present and in fact always
<pq>
all printers and scanners and cameras have already needed them for as long as they have existed
<vsyrjala>
i don't think any non-broken monitors have existed since we gave up on crts
<pq>
only computer monitors specifically had an era when practically all of them were close enough to sRGB that the differences didn't matter, unless you worked in the print industry.
<DemiMarie>
pq: Is that because of the physics of CRTs?
<pq>
DemiMarie, I guess partly that, and partly the industry wanting to standardise around sRGB, because managing color was expensive.
<DemiMarie>
Expensive?
<pq>
CPU time, memory
<DemiMarie>
Are those still issues?
<pq>
they can be if you use high enough resolution and low enough hardware - but at least capable hardware exists
<pq>
unlike, say, in 1998
<pq>
AFAIU, sRGB was born from the desire to show images through the Internet.
<kennylevinsen>
huh, didn't know that NTSC is closer to P3 in volume than it is to sRGB - although I doubt many monitors existed that could get near that
pavlushka has joined #wayland
<JEEB>
I did laugh out loud as I noticed recently display companies instead of sRGB started talking about NTSC gamut capabilities
<JEEB>
NTSC... in <current_year>
<pq>
xvYCC next? or how does that compare?
<pq>
old is the new new
<JEEB>
oh right, xvYCC was the thing where they noticed that in video they were not utilizing all the value range in digital video
<JEEB>
so they allowed chroma to go 1-254 :D
<JEEB>
also this probably is from where the definition of full range chroma comes from in BT.2100
<JEEB>
although technically that maps to 1-255 in 8bit
<JEEB>
and yea, according to wikipedia it literally keeps the same primaries definition as BT.709
<JEEB>
so the only difference is that you flag the content as limited range, but actually expect chroma to be full range
<JEEB>
so BT.709 [0,1] map to limited range of 16-240
<JEEB>
and then 1-15 and 241-254 were utilized to widen the gamut
<pq>
the chroma breaks out of its old boundaries
<JEEB>
yea
<JEEB>
how on earth would you even signal such a coded signal according to H.273
<JEEB>
since apparently this stuff was put on disc media :D
<JEEB>
OK, so they gave it a transfer function value indeed
<pq>
yeah, it's obviously a TF thing, sure
<pq>
the TF table is more like a systems table
<JEEB>
not sure, I would have possibly put it into the full/limited range stuff. since the only difference is that you utilize a different range for chroma.
<JEEB>
but probably the range is a boolean in so many contexts
<JEEB>
and yes, the TF does affect f.ex. in which order steps should be done