On Tue, 10 Dec 2019 at 23:25, Erwin Burema wrote:
>
> > Wanted to post this to the list as an FYI for an implementation I did for
> > setting the color space for a wl_surface. This has now been merged into the
> > Chromium codebase. I was going to wait until this all settled
implement the protocol as
proposed by Sebastian Wick
(https://lists.freedesktop.org/archives/wayland-devel/2019-November/040978.html)
. I know it currently is missing HDR support but that is because there is no
good way to describe HDR colorspace yet (there is nothing like ICC profiles for
so it would be nice to let the compositor know it shouldn't
lock the screen, go standby, or let other application draw over the
critical regions (or at least have a way to
* stand alone KMS - Horrible use experience, harder to program for,
but have full access to everything
* drm lease - Better
On Wed, 22 May 2019 at 12:41, Sebastian Wick
wrote:
>
> On 2019-05-22 05:17, Erwin Burema wrote:
> > On Tue, 21 May 2019 at 21:07, Sebastian Wick
> > wrote:
> >>
> >> On 2019-05-21 19:32, Erwin Burema wrote:
> >> > Hi,
> >> >
>
On Tue, 21 May 2019 at 21:07, Sebastian Wick
wrote:
>
> On 2019-05-21 19:32, Erwin Burema wrote:
> > Hi,
> >
> > This is the second version of my color manager calibration protocol,
> > biggest change is that I now use a surface this surface is set up in a
>
/wp_wayland_calibration.xml
new file mode 100644
index 000..dbeeb42
--- /dev/null
+++ b/unstable/color_calibration/wp_wayland_calibration.xml
@@ -0,0 +1,247 @@
+
+
+
+
+Copyright © 2019 Erwin Burema
+
+Permission is hereby granted, free of charge, to any person obtaining a
+copy of this software
doing this as
a hobbyist) and I am actually a physicist not a software engineer I will
probably need some help with that.
Erwin Burema (1):
Adding color calibration protocol
.../wp_wayland_calibration.xml| 247 ++
1 file changed, 247 insertions(+)
create
On Wed, 1 May 2019 at 13:00, Graeme Gill wrote:
>
> Erwin Burema wrote:
>
> Hi,
>
> > 1) Will always be a single solid color, so no need for the full
> > wl_buffer/wl_surface interface
>
> you don't know that, as it's up to the calibration and profili
On Wed, 17 Apr 2019 at 13:37, Sebastian Wick
wrote:
>
>
>
> On April 17, 2019 12:38:15 PM GMT+02:00, Erwin Burema
> wrote:
> >On Wed, 17 Apr 2019 at 11:32, Pekka Paalanen
> >wrote:
> >>
> >> On Tue, 16 Apr 2019 23:42:30 +0200
> >> Erwin B
On Wed, 17 Apr 2019 at 11:32, Pekka Paalanen wrote:
>
> On Tue, 16 Apr 2019 23:42:30 +0200
> Erwin Burema wrote:
>
> > On Tue, 16 Apr 2019 at 17:03, Pekka Paalanen wrote:
> > >
> > > On Tue, 16 Apr 2019 13:33:02 +
> > > Erwin Burema wrote:
&
On Tue, 16 Apr 2019 at 17:03, Pekka Paalanen wrote:
>
> On Tue, 16 Apr 2019 13:33:02 +0000
> Erwin Burema wrote:
>
> > On Tuesday, 16 April 2019, Pekka Paalanen wrote:
> > > On Tue, 16 Apr 2019 13:11:06 +0200
> > > Erwin Burema wrote:
> > >
> &g
On Tuesday, 16 April 2019, Pekka Paalanen wrote:
> On Tue, 16 Apr 2019 13:11:06 +0200
> Erwin Burema wrote:
>
> > On Tue, 16 Apr 2019 at 12:45, Pekka Paalanen wrote:
> > >
> > > On Sun, 14 Apr 2019 12:57:47 +0200
> > > Erwin Burema wrote:
> >
On Tue, 16 Apr 2019 at 12:51, Pekka Paalanen wrote:
>
> On Sun, 14 Apr 2019 12:57:48 +0200
> Erwin Burema wrote:
>
> > ---
> > .../cm_wayland_calibration.xml| 106 ++
> > 1 file changed, 106 insertions(+)
> > create mod
On Tue, 16 Apr 2019 at 12:45, Pekka Paalanen wrote:
>
> On Sun, 14 Apr 2019 12:57:47 +0200
> Erwin Burema wrote:
>
> > Without a way to calibrate/profile screens an color management
> > protocol looses a lot of its value. So to add this missing feature I
> >
On Tue, 16 Apr 2019 at 08:42, Sebastian Wick
wrote:
>
> On 2019-04-15 23:38, Erwin Burema wrote:
> > On Mon, 15 Apr 2019 at 20:30, Sebastian Wick
> > wrote:
> >>
> >> On 2019-04-14 12:57, Erwin Burema wrote:
> >> > Without a way to calibrate/pro
On Mon, 15 Apr 2019 at 21:11, Simon Ser wrote:
>
> On Sunday, April 14, 2019 1:57 PM, Erwin Burema wrote:
> Thanks for your patch! Here are a few comments, mostly from a protocol
> perspective since I don't know about color management.
>
> > ---
> >
On Mon, 15 Apr 2019 at 21:46, Simon Ser wrote:
>
> On Monday, April 15, 2019 10:42 PM, Sebastian Wick
> wrote:
> > > How would the client "measure"?
> >
> > With a colorimeter. Write some values that you expect to have a certain
> > color, read the actual colors, calculate the error.
> > I'm not
On Mon, 15 Apr 2019 at 20:30, Sebastian Wick
wrote:
>
> On 2019-04-14 12:57, Erwin Burema wrote:
> > Without a way to calibrate/profile screens an color management
> > protocol looses a lot of its value. So to add this missing feature I
> > wrote the following protocol.
s not
available a HDR screen should be treated as if it is a rec2020+PQ or HLG since
it will do its own compositing+color managing (which might or might not be
correct)
Erwin Burema (1):
Add color manager calibration protocol v1
.../cm_wayland_calibration.xml
-calibration/cm_wayland_calibration.xml
new file mode 100644
index 000..be9bb4b
--- /dev/null
+++ b/unstable/color-manager-calibration/cm_wayland_calibration.xml
@@ -0,0 +1,106 @@
+
+
+
+
+Copyright © 2019 Erwin Burema
+
+Permission is hereby granted, free of charge, to any person
On Fri, 15 Mar 2019 at 14:49, Kai-Uwe wrote:
>
> Am 15.03.19 um 11:41 schrieb Pekka Paalanen:
> > Can an ICC file include a per-channel degamma and gamma LUTs? That
> > is, in addition to the usual profile data that allows mapping between
> > PCS and the device space.
>
> Not in absolute terms. Bu
On Thu, 14 Mar 2019 at 14:04, Pekka Paalanen wrote:
>
> On Thu, 14 Mar 2019 13:27:45 +0100
> Erwin Burema wrote:
>
> > On Thu, 14 Mar 2019 at 12:29, Pekka Paalanen wrote:
> > >
> > > On Wed, 13 Mar 2019 15:50:40 +0100
> > > Erwin Burema wrote:
>
On Thu, 14 Mar 2019 at 12:29, Pekka Paalanen wrote:
>
> On Wed, 13 Mar 2019 15:50:40 +0100
> Erwin Burema wrote:
>
> > Hi,
> > On Wed, 13 Mar 2019 at 10:06, Pekka Paalanen wrote:
> > >
> > > On Tue, 12 Mar 2019 17:02:53 +0100
> > > Erwin Burema
Hi,
On Wed, 13 Mar 2019 at 10:06, Pekka Paalanen wrote:
>
> On Tue, 12 Mar 2019 17:02:53 +0100
> Erwin Burema wrote:
>
> > Hi,
> >
> > Comments inline
> > On Tue, 12 Mar 2019 at 14:01, Pekka Paalanen wrote:
> > >
> > > On Th
Hi,
Comments inline
On Tue, 12 Mar 2019 at 14:01, Pekka Paalanen wrote:
>
> On Thu, 7 Mar 2019 12:37:52 +0100
> Erwin Burema wrote:
>
> > Wed Mar 6 17:09:27 UTC 2019 Sebastian Wick :
> > >...
> >
> > > 2. The whole pipeline should look something like
C profiles (RGB ones only of course) in
which case so long as it is not an output profile it should be fine to
use a blending space.
> ...
---
[1] If that is even possible, although if we run into that case we are
probably dealing with a cheap consumer moni
ansform, which albeit not accurate should
be good enough. Device link profiles are most useful for when
something doesn't support color management and you need to do it
externally (probably in a batch), for example certain printers,
desktop backgrounds, etc.
Kind regards,
Erwin Burema
Hi,
On Wed, 27 Feb 2019 at 05:47, Nautiyal, Ankit K
wrote:
>
> From: Ankit Nautiyal
>
> This protcol enables a client to send the hdr meta-data:
> MAX-CLL, MAX-FALL, Max Luminance and Min Luminance as defined by
> SMPTE ST.2086.
> The clients get these values for an HDR video, encoded for a vide
; \
> > >> diff --git a/unstable/color-management/README b/unstable/color-
> > >> management/README new file mode 100644 index 000..140f1e9
> > >> --- /dev/null
> > >> +++ b/unstable/color-management/README
> > >> @@ -0,0 +1,4 @@
On Thu, 14 Feb 2019 at 16:38, Sebastian Wick
wrote:
>
> Thanks. I don't really know about all the standards so I'll just trust
> you on this.
>
These are correct suggestions and do improve the readability by a lot
> On 2019-02-14 05:47, Chris Murphy wrote:
> > On Wed, Feb 13, 2019 at 7:55 PM Seba
stable/color-management/color-management-unstable-v1.xml
> new file mode 100644
> index 000..1615fe6
> --- /dev/null
> +++ b/unstable/color-management/color-management-unstable-v1.xml
> @@ -0,0 +1,183 @@
> +
> +
> +
> +
> +Copyright © 2019 Sebastian Wick
> +Copyright ©
31 matches
Mail list logo
