Hi,
Am 15.03.2019 um 15:28 schrieb Erwin Burema:
> "degammaed" https://drive.google.com/open?id=1gS8F6ZXyfoobVWoHxD-IXM6_Hx7OJGCu
> "gammaed" https://drive.google.com/open?id=1BpVG_Xvy0C4o9FBahseClFItyYeoz9zq
>
> As you can see this is quite awe-full, no white balance, shift in
> white balance ov
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
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. But most monitor 3D LUT profiles contain as well
TRC (tonal r
On Thu, 14 Mar 2019 14:29:23 +0100
Erwin Burema wrote:
> 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
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:
> > >
> > > > Hi,
> > > > On Wed, 13 Mar 2019 at 10
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:
> >
> > > Hi,
> > > On Wed, 13 Mar 2019 at 10:06, Pekka Paalanen wrote:
> > >
> > > >
> > > > On Tue, 12 Mar 2019
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 wrote:
> > >
> > > > Hi,
> > > >
> > > > Comments
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 wrote:
> >
> > > Hi,
> > >
> > > Comments inline
> > > On Tue, 12 Mar 2019 at 14:01, Pekka Paalanen wrote:
> > >
>
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 Thu, 7 Mar 2019 12:37:52 +0100
> > > Erwin Burema wrote:
> > >
> > > > We
On Wed, 6 Mar 2019 18:09:27 +0100
Sebastian Wick wrote:
> Sending in v2 with small fixes only. I'm using this in the hope to focus
> the previous discussion in the direction of the actual protocol and
> implementation.
>
> It looks like we have come to at least some consensus on a few points.
>
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 Thu, 7 Mar 2019 12:37:52 +0100
> > Erwin Burema wrote:
> >
> > > Wed Mar 6 17:09:27 UTC 2019 Sebastian Wick :
> > > >...
> > >
> > > > 2. 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
> > >
> > > [surface cs] -cs conversion-> [
On Wed, 6 Mar 2019 18:09:27 +0100
Sebastian Wick wrote:
> Sending in v2 with small fixes only. I'm using this in the hope to focus
> the previous discussion in the direction of the actual protocol and
> implementation.
>
> It looks like we have come to at least some consensus on a few points.
>
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
> >
> > [surface cs] -cs conversion-> [output cs] -tone mapping-> [output cs]
> >-degamma-> [output linear cs] -blending-> [o
On Wed, 2019-03-06 at 18:09 +0100, Sebastian Wick wrote:
> 2. How exactly should the client be informed of the "prefered" color
>spaces?
>IMO there are a few requirements:
>* the client should know when the prefered color space changes
>* the client should know when multiple color
Wed Mar 6 17:09:27 UTC 2019 Sebastian Wick :
>...
> 2. The whole pipeline should look something like
>
> [surface cs] -cs conversion-> [output cs] -tone mapping-> [output cs]
>-degamma-> [output linear cs] -blending-> [output linear cs] -gamma->
>[output cs].
>
>Where some parts can
Thu Mar 7 08:37:11 UTC 2019 Kai-Uwe
> Am 06.03.19 um 18:09 schrieb Sebastian Wick:
> ...
>> Which brings me to open issues:
>>
>> 1. Does it make sense to support device link profiles? I'm against it
>>but would love to hear if anyone has objections given that they are
>>supported in the ot
On Wed, 2019-03-06 at 18:09 +0100, Sebastian Wick wrote:
[...]
> 4. How do universal planes handle gamma when blending? This hopefully
>has a sinmple answer and there probably is some documention which
>I just can't find.
I think they currently don't, and it will depend on the driver. Ther
Am 06.03.19 um 18:09 schrieb Sebastian Wick:
> Sending in v2 with small fixes only. I'm using this in the hope to focus
> the previous discussion in the direction of the actual protocol and
> implementation.
>
> It looks like we have come to at least some consensus on a few points.
> If anyone disa
19 matches
Mail list logo
