Have you tried the ICC verification tool on those profiles? It can
detect any deviation from standard...
http://color.org/profdump.xalter
I've tried it and the profiles are just checked ok. Then it is just a
matter of guessing; you could modify lcms source code and do some trial
and error.
On Tue, Feb 26, 2013 at 5:01 PM, Marti Maria marti.ma...@littlecms.com wrote:
Have you tried the ICC verification tool on those profiles? It can
detect any deviation from standard...
http://color.org/profdump.xalter
Oh right, I didn't know there was one freely available. Silly me.
So I
On Tue, Oct 16, 2012 at 1:43 AM, Graeme Gill gra...@argyllcms.com wrote:
Pascal de Bruijn wrote:
Another peculiar fact is that Argyll's iccdump reports this:
tag 0:
sig 'desc'
type 'desc'
offset 288
size 140
Unable to read: 1, icmTextDescription_read: ScriptCode
Am 25.02.2013 19:09, schrieb Pascal de Bruijn:
On Tue, Oct 16, 2012 at 1:43 AM, Graeme Gill gra...@argyllcms.com wrote:
Pascal de Bruijn wrote:
Another peculiar fact is that Argyll's iccdump reports this:
tag 0:
sig 'desc'
type 'desc'
offset 288
size 140
On Wed, Sep 12, 2012 at 11:00 PM, Marti Maria marti.ma...@littlecms.com wrote:
Ideally, I'd love to match the canonical Microsoft HP profile.
Would that be possible using LCMS2?
Sure, just create a plain sRGB and overwrite the media white point with D65.
I'm not entirely sure how to go
On Wed, Sep 12, 2012 at 2:26 AM, Graeme Gill gra...@argyllcms.com wrote:
Marti Maria wrote:
Not according ICC, see
http://www.color.org/srgbprofiles.xalter#v2
They require D50 for media white point to avoid the wrong Von-Kries issue.
Hi,
They may do it that way with their profiles, but
On Tue, Sep 11, 2012 at 11:51 PM, Pascal de Bruijn
pmjdebru...@gmail.com wrote:
On Mon, Sep 10, 2012 at 10:28 PM, Marti Maria marti.ma...@littlecms.com
wrote:
Hi,
Apparently Firefox only handles v2 by default (v4 can be enabled in
settings)
Unfortunately Firefox only handles a very
Unfortunately Firefox only handles a very limited set, matrix-shaper
only. Either V2 and specially V4 are largely unsupported by Firefox.
See this test page on ICC site:
http://www.color.org/browsertest.xalter Try with IE9 and then with
Firefox
Well, with v4 enabled, that works
Hmmr... It seems that creates a v2 profile, but still with a D50
whitepoint encoded (instead of the traditional D65, for v2 sRGB). I
know for v4 the white point is adapted using a different tag, but that
tag shouldn't end up in v2 profiles right?
Hi,
Not according ICC, see
Marti Maria wrote:
Not according ICC, see
http://www.color.org/srgbprofiles.xalter#v2
They require D50 for media white point to avoid the wrong Von-Kries issue.
Hi,
They may do it that way with their profiles, but nothing in the V2 specs
requires it, the canonical Microsoft HP sRGB
On Mon, Jun 25, 2012 at 4:18 AM, Graeme Gill gra...@argyllcms.com wrote:
marti.ma...@littlecms.com wrote:
Hi Marti,
Yes, as Kai-Uwe says, this is the expected behavior for a V4 CMM, and
that is what lcms2 is. Please note most if not all modern CMMs behaves
in such way, for example all Adobe
Am 23.06.12, 20:51 +0200 schrieb Pascal de Bruijn:
We've recently discovered that Darktable's (a photography application)
internal sRGB profile seems to encode a D50 whitepoint even though we
are passing a D65 whitepoint. The current theory is that this changed
when we migrated from lcms1 to
Hi Pascal,
We've recently discovered that Darktable's (a photography application)
internal sRGB profile seems to encode a D50 whitepoint even though we
are passing a D65 whitepoint. The current theory is that this changed
when we migrated from lcms1 to lcms2.
Yes, as Kai-Uwe says, this is
marti.ma...@littlecms.com wrote:
Hi Marti,
Yes, as Kai-Uwe says, this is the expected behavior for a V4 CMM, and
that is what lcms2 is. Please note most if not all modern CMMs behaves
in such way, for example all Adobe products.
Right, but V2 profiles should be processed according to the V2
Hi,
We've recently discovered that Darktable's (a photography application)
internal sRGB profile seems to encode a D50 whitepoint even though we
are passing a D65 whitepoint. The current theory is that this changed
when we migrated from lcms1 to lcms2.
This is our code:
15 matches
Mail list logo