Wayland Color Management Protocol Might Finally Be Close To Merging

[emblemparade]

It won't be ready until there's a shared common implementation that everyone uses.

This color management protocol? Yeah, great, maybe KWin and Mutter will implement it in the next 12-36 months or so, in five more years it will be in other 70% of Wayland implementations. The rest 30% or so will never get it. That's madness that no other modern widespread OS has.

The "madness" always existed. There are several X implementations out there, and it took some time until Linux-based operating systems settled on the X.Org server. The primary reason they picked it is that the others weren't good enough. It's immensely difficult to implement an X11 server, especially if you want it to be complete: with decades-worth of barely-used but massively complicated features.

Nobody is stopping non-GNOME desktops from using Mutter or non-KDE desktops from using KWin. Thing is, you do need a lot more than just a display server to implement a desktop, so both Mutter and KWin have different ecosystems around them to provide other services. Both are also quite good and comprehensive. I consider this to be a massively better situation than having only one choice, of X.Org. And I'm not even mentioning other Wayland servers out there, each with their own unique ecosystems.

For all those frustrated with progress on Wayland: all major Linux-based operating systems still ship X11, so just use it! For all those frustrated that no developers want to work on X.Org anymore, well, I suggest listening to what these developers have to say about working on the X.Org codebase. They are very, very burnt out and done with it.

[ezst036]

Once this gets merged, what is the current state of x/wayland and missing items?

[ezst036]

I just don't understand why Linux fans try to make it personal all the time.

I always defer back to the actual developer talent. You should be sober and make this your starting point instead of what you normally do.

Since everybody runs for the hills while yanking their hair out from the x.org server code base, Wayland is what we have to work with.

It simply is what it is.

[ezst036]

I suggest listening to what these developers have to say about working on the X.Org codebase. They are very, very burnt out and done with it.

This.

Far too many people labor under a denial that we can magically dig up new x.org developers to keep it going.

[Damnshock]

For the love of God... don't you get tired of trolling?

It was fat sarcasm. It won't be ready until there's a shared common implementation that everyone uses.

One and only implementation is almost antagonistic with the wayland design. Just read the comments https://gitlab.freedesktop.org/wayla...3#note_1186503 and https://gitlab.freedesktop.org/wayla...3#note_1186531

In short: if you want one and only thing to rule them all... it will not be wayland.

This color management protocol? Yeah, great, maybe KWin and Mutter will implement it in the next 12-36 months or so, in five more years it will be in other 70% of Wayland implementations. The rest 30% or so will never get it. That's madness that no other modern widespread OS has.

Stop embarrassing yourself...

There are already three compositors implementing this RIGHT NOW.

[caligula]

It was fat sarcasm. It won't be ready until there's a shared common implementation that everyone uses.

This color management protocol? Yeah, great, maybe KWin and Mutter will implement it in the next 12-36 months or so, in five more years it will be in other 70% of Wayland implementations. The rest 30% or so will never get it. That's madness that no other modern widespread OS has.

Well FWIW only a minority of people need color management. You basically need to calibrate your monitor. The colorimeters's sensors wear out even if you don't use them. I don't think this is that common practice among suckless and other small WM developers. Basically Gnome and KDE cover 99% of the relevant users.

[Damnshock]

Almost everything that I've been requesting over the past 25 years has been implemented one way or another.

• Common init system? SystemD. Done!
• Common audio server? PulseAudio/PipeWire. Done!
• OOM daemon? systemd-oomd. Done!

There's a lot more to be done unfortunately.

Get out of your head that what you "requested" was what people want and they developed.

What you are pointing at are only *one* of several things that are implemented right now in their respective domains. They just happen to be very popular, nothing else.

And, to add insult to injury, PulseAudio and PipeWire ARE TWO DIFFERENT audio daemons! (pipewire does more but... you get the point)

Stop trolling, please, I beg you, just stop.

[caligula]

How did you come to that conclusion?

Like, try googling how to set things up. You'll only find dated instructions for Xorg. Some even explain that you need to edit xorg.conf. On X you only need to set up udev. I did a search and also noticed that there are several bug reports for Wayland.

[MorrisS.]

weston is always ready before the other compositors. So the news is when the others will be provided of this improvement.

[Quackdoc]

This protocol actually doesn't suck???? you all can read the protocol itself here https://gitlab.freedesktop.org/wayla...agement-v1.xml

It doesn't tell compositors to make dumb assumptions about srgb vs a pure 2.2 transfer function, it sticks to the specs in regards to "reference nits" It seems to support everything that is needed for hdr10 info, they do let you set powers for transfer, and set custom gamut values etc.

This should be adequate information to have a good initial color management system,

I would like to remind everyone that while this extension does not include display response measuring and calibration, they will come later.

all in all, decent protocol stuff for an initial release I suppose.