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 profiling
> application. It may well want to paint gui
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 profiling
application. It may well want to paint guide graphics for the positioning
of the instrument. It could want t
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 Burema wrote:
>>
>> > On Tue, 16 Apr 2019 at 17:03, Pekka Paalanen
>wrote:
>> > >
>> > > On Tue, 16 Apr 2019 13:33:02 +
>>
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 Burema wrote:
> >>
> >> > On Tue, 16 Apr 2019 at 17:03, P
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 Burema wrote:
>>
>> > On Tue, 16 Apr 2019 at 17:03, Pekka Paalanen
>wrote:
>> > >
>> > > On Tue, 16 Apr 2019 13:33:02 +
>>
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 Tuesday, 16 April 2019, Pekka Paal
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 Tuesday, 16 April 2019, Pekka Paalanen wrote:
> > > > On Tue, 16 Apr 2019 13:11:06 +0200
> > > > Erwin
On Tue, 16 Apr 2019 at 17:03, Pekka Paalanen wrote:
>
> On Tue, 16 Apr 2019 13:33:02 +
> Erwin Burema wrote:
>
> > 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
On Tue, 16 Apr 2019 13:33:02 +
Erwin Burema wrote:
> 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
>
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:
> > >
> > > > Without a way to calibrate/profile scr
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:
> >
> > > Without a way to calibrate/profile screens an color management
> > > protocol looses a lot of its value. So
On 2019-04-16 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
wrote the following protocol.
The idea is that the calibration/
> > Btw. how would a compositor know the bit depth of a monitor and the
> > transport (wire)? I presume there should be some KMS properties for
> > that in addition to connector types.
>
> Huh, this surprises me a bit would have expected KMS to know something
> about the screens attached and which
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
> > wrote the following protocol.
> >
> >
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
> wrote the following protocol.
>
> The idea is that the calibration/profiling SW only sets the RGB
> tri
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/profile screens an color management
> >> > protocol loo
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/profile screens an color management
> protocol looses a lot of its value. So to add this missing feature I
> wrote the following pr
Simon Ser wrote:
I guess most people don't have a colorimeter at home.
Most people who are doing color critical work will have access to
a color measurement instrument, or will have some other method of
ensuring the consistency and availability of accurate display
characterization information (
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.
> >
> > The idea is that th
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 sure if that answers your question.
Sorry, I'm not familiar wi
On 2019-04-15 21:01, Simon Ser wrote:
On Monday, April 15, 2019 9:30 PM, 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 p
On Monday, April 15, 2019 9:30 PM, 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.
> >
> > The idea is tha
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.
The idea is that the calibration/profiling SW only sets the RGB
triplet and then the composit
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.
The idea is that the calibration/profiling SW only sets the RGB triplet and
then the compositor is responsible to draw a rectanglular
25 matches
Mail list logo
