It’s interesting that are a couple of attempts to add a gamma control to Wayland to support applications like redshift, and also allow adjusting the color temperature of the display - namely wlr-gamma-control-unstable-v1 protocol or by using the wlroots compositor toolkit.
wlr-gamma-control-unstable-v is actually a protocol to set the VideoLUTs rather than just a gamma value, so could be used to implement VideoLUT setting via XWayland, but it doesn’t appear to have much support amongst popular Wayland compositors at this time.
They are discussing your exact requirements in this extension.
2 Likes
you can help out by testing this if you want. not all devs have access to relevant hardware…
4 Likes
How can I set hyperland?
2 Likes
2 Likes
Thanks for the hint. Certainly not suitable for my level of knowledge.
1 Like
I didn’t mean it that way 
it’s the automatic preview of the page. I seriously shared in hopes of people installing it. IMO with window managers nobody knows it at first, the best way to increase your level of knowledge is to do it and play around with it.
It is still open PR. We’ll be able to test it no sooner then it gets merged. But kwin_wayland is ready for testing, indeed))
Yes you can indeed test before it’s merged 
3 Likes
You’re right, technically I can, but I don’t feel like deeping into this dev stuff, sorry. So I’m playing with kwin right now.
If they were interested in “my requirements”, they’d email me, rather than discussing it on some random website that I’m unlikely to stumble across.
[ Calls to mind Douglas Adams: “It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying 'Beware of the Leopard.” ]
And it’s not “my requirements”, it’s what is needed for contemporary color management.
It’s not some random website, it’s the hub where all the development for this specific issue(wayland development) is being made and discussed. If all other teams from every desktop environment and graphics developers will use it, why wouldn’t you, are you above them somehow? I agree they could’ve emailed you with a link so you were aware of it though.
It’s your requirements as in, they linked to your specific website where it says “requirements”. The list was created by you.
2 Likes
Easy now.
Some of the people involved on this thread were so combative that it seemed clear that they were not open to the input of experts we have in this community. Its obvious why he wouldn’t seek out their official space to try and provide more input: its clearly not welcome.
A real waste of mind share by the Wayland devs, and that was, what, six years ago?
2 Likes
As per the wayland section in the argyll cms website gwgill has tried to contact and give feedback in 2013. Read the wayland section where the list of requirement is linked - Argyll Color Management System Home Page
Starting in 2013 I attempted to engage the Wayland developers in discussing the challenges of adding proper support for display color management under Wayland, but in general received (and continue to receive) a very hostile response. NIH seems very strong, and there was little respect shown for the importance of color management or the wider experience of implementing it within other graphical environments such as X11, MSWindows and OS X. While there are certainly some in the Wayland developer community that are working on aspects related to color management, driven primarily by the reality of HDR displays, it doesn’t currently appear to me that there is much progress in addressing the wider and deeper challenge of fully supporting modern color management and its tools and applications.
Having spend a lot of patience and time over several years in the past, attempting to interest and explain modern color management to the dev’s on the wayland list, with an overall response of “we’re not going to listen to you”, you’ll have to forgive me if I haven’t gone searching for additional forums to engage wayland developers.
Bashing one’s head against a wall is only enjoyable for so long, both for oneself, and the wall.
See: Re: Setting the display calibration ramps using weston
https://wayland-devel.freedesktop.narkive.com/7tSjzow4/setting-the-display-calibration-ramps-using-weston# etc.
See Subject: Re: [RFC wayland-protocols] Color management protocol and associated
threads from 2016 thru 2017:
https://lists.freedesktop.org/archives/wayland-devel/2016-December/032049.html
https://lists.freedesktop.org/archives/wayland-devel/2017-January/032553.html
etc.
(Looking back on some of these threads still fills me with amazement. Daniel Stone telling me that under no circumstances would an application ever be able to know what display the pixels it is writing to is on, yet such a protocol was added later because (huge surprise!) it was technically necessary. etc.) Being told constantly that under no circumstances are users to be able to configure their systems, due to security. etc. etc.
As always, I’m more than happy to respond constructively if my expertise is solicited.
12 Likes
6 Likes
Also check this issue -
It is good to keep track of this too. Hope it gets finished so that we would have complete color managed workflow now that HDR is out of the way
4 Likes
GNOME 48 Mutter wp_color_management_v1 merged:
4 Likes
A blog post from one of the main authors of the protocol
And a quote from the article (I have emphasized the main point)
The color-management Wayland extension is enough for entertainment purposes like games and movies. However, it is not enough for professional color management needs including photo editing and print preview. The major missing piece is the ability to measure the display response. Every monitor is unique, and measuring is the only way to achieve reliably repeatable and accurate display behavior. If I get to it first, I will probably start by drafting a Weston-private Wayland extension to see what it will need. It is not certain it will be a Wayland extension in the end, it could also be a portal
2 Likes
Lovely to hear that the glaring omission being acknowledged and (in the words of the author) “probably” worked on. 
