- From: ccameron-chromium <notifications@github.com>
- Date: Thu, 29 Nov 2018 13:50:47 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/315/443006430@github.com>
> For example, unlike XYZ or linear sRGB, , this is not a linear-light space. So computing, for example, the color that results from mixing two lights of different colors will not give the correct result. (It may still be useful to do, especially if performance is more important than accuracy, but note that the errors are significant and certainly visible). Yes, we spent a while (independently on several different occasions) trying to push users to use a physically linear space, but that ended up backfiring on us. There's no one thing that people consistently want ... I found that * Users (in my experience) want physical linear interpolation for... * anti-aliasing * decimation/magnification of images * physically-based rendering * Users (in my experience) want perceptually linear interpolation for... * gradients * alpha blending transparency And of note is that sRGB (and Extended-sRGB) are ... closer ... to perceptually linear than physically linear (if one doesn't change color hue it is pretty close to perceptually linear ... if one does change hue, horribleness results). > This is probably enough to deal with WCG and _may_ be enough to deal with HDR. We've done some experiments with the Windows 10 HDR support (on HDR TVs) in WebGL, and the results have been promising! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/315#issuecomment-443006430
Received on Thursday, 29 November 2018 21:51:08 UTC