Yes on that a screen needs to turn on HDR mode no in that the point is moot since we want to be able to do full color correction in HDR in the future (for example with Krita since it already has an HDR painting mode, it should also be relative easy to add to Blender and Natron). Complicating matter is that for the exception of the Freesync2 display modes[1] all others are designed to take the color management/tonemapping out of the hands of the software developers and put it in the hands of the HW developers who are not necessarily concerned with color accuracy but with making things look pretty on their screens (especially for consumer level screens, which also often donât give a lot of control).
[1] FreeSync2_scRGB and FreeSync2_Gamma22, for which the second one is the most interesting for us.
Sadly currently just gaming focused display due to this being marketed mostly as a latency reducing feature, at least speaking from a consumer oriented frame. There is probably also work being done for more professional screens but havenât been able to find much information (yet)
Probably not, most computer monitors seems to be HDR10(+) which is an âopenâ standard for HDR instead of the dolby one that requires a licensing fee. Dolby does have the (theoretical) advantage that it is 12 bit instead of 10 IIRC, still as far as I can tell HDR10(+) seems to be winning the race.
That said in either case for proper color management you still want to âdirectlyâ drive the display which neither format allows[1], at least as far as I can tell.
[1] Both send rec.2020-PQ to the screen which then gets tonemapped + color corrected by a system there instead of letting the SW do the tonemapping/color correcting itself
just a quick question - I think I never (at least consciously) tried wayland: does color management actually work with wayland? I mean with the gnome color manager and colord etc.? I mean fedora is supposed to use wayland as the default display-server?
apparently yes, at least manjaro 18 in a virtual machine, but I kind of cannot check if manjaro gnome really uses wayland
I am confusedâŚ
well⌠neither can I check if calibration data is really loaded since my screen is hardware calibrated⌠so the profile that was chosen in th gmc is just there for the apps that can not color management
edit: itâs x11
Not currently; gnome might set the calibration curves but currently not much beyond that is possible so in applications the color profile needs to be set manually, this is not too bad with normal gamut non-hdr systems (only slightly more hassle then currently on X11, especially if the display is only profiled) but will become a major problem when moving to wide gamut/HDR displays. The work currently done, here and on the wayland mailinglists is to make sure that in the future Wayland will work better then X11.
thanks for the clarification.
so, bottom line: if I want or need color management, I will have to stick to x11 for the next 5 years or so (actually I think cm works very well on x11, although I admit that sometimes it is a little bit complicated)
btw, I tried all kinds of distros that I had already downloaded and none of them is actually using wayland as the default display whatever
You could say, although you have to take into account that some of the issues we are trying to tackle here would be effectively impossible on X11 (e.g. full screen color management). In the wayland world the problems are just hard mostly because color management is a hard problem
More that itâs always going to make your life difficult if you set out to develop a whole new desktop graphics system in this century without architecting it for color management right from the beginning.
Didnât know about that one, consider me corrected. Still it requires a compositor which in the X11 world is neither mandatory and in some cases gets in the way (remember that compositing in X11 is kinda of a hack in and of itself, or at least something that has been bolted on very late)
True it should have been in the design from the start[1] but in my opinion bolting it on Wayland where compositing is mandatory anyway is I think still a bit easier then bolting it on X11 where such a bolt on would require a compositor.
So all in all I do think we have a better change to get it working (somewhat) right on Wayland then we would have had on X11
So, basically, Wayland color management is âvery buggyâ?
Well, I already heard many people say that Linux is going to the wrong directionâŚ
Well this is the way I (as a user, not a developer) see it: on X11, it is working well for me, although sometimes it is a bit complicated to configure. But on Wayland, it is not working at all. Well⌠it is working if you only profile your screen, do not have multiple screens and use a program where you can set the profile manually, and maybe a screen that is perfectly factory calibrated to sRGB which does not need to be profiled or calibrated would not hurt eitherâŚ
it was just a question. it is a possible interpretation of other peopleâs statements, not mine
I mean, I donât really know, since I am not a developer. or linux expert or whatever
I will be the first person (user) that will be happy when wayland color management is finally working
sorry if I made it sound âunconstructiveâ
anyway, my question was answered, thanks for that (and I think I am out of this thread)
Currently Wayland has no support for color management. You can work around it to a degree if you use a compositor (gnome based ?) that will load calibration curves, if you profile the display running X11 and can then manually set your application display profile rather than it picking it up from the X11 atom. But realistically X11 is a better choice currently, since application color management as well as calibration & profiling should just work. (System wide, default color management is a different question. Only OS X seems to make a reasonable attempt at that at the moment.)