Create an RGB - RGB transform and re-sample it on a regular grid,
for instance like below (code is a bit older, still using lcms1, though).
Regards,
Gerhard
#define GRIDPOINTS 64
static GLushort clut[GRIDPOINTS][GRIDPOINTS][GRIDPOINTS][3];
static GLuint img_texture;
static GLuint
Quoting Gerhard Fuernkranz nospam...@gmx.de:
Create an RGB - RGB transform and re-sample it on a regular grid,
for instance like below (code is a bit older, still using lcms1, though).
Great idea. lcms2 works fine in this way. Please note in lcms2 you can
get float, double or half float
Am 11.03.2015 um 00:36 schrieb marti.ma...@littlecms.com:
Quoting Gerhard Fuernkranz nospam...@gmx.de:
Create an RGB - RGB transform and re-sample it on a regular grid,
for instance like below (code is a bit older, still using lcms1, though).
Great idea. lcms2 works fine in this way. Please
On 5 March 2015 at 16:10, Noel Carboni ncarb...@prodigitalsoftware.com wrote:
Why in this day and age don't operating systems provide color-management
services beyond being a storage system for profiles? For decades I've been
wondering.
They do, but they often give slightly different results,
Quoting Noel Carboni ncarb...@prodigitalsoftware.com:
Speaking of what the Adobe Color Engine can do... Is anyone
considering porting Little CMS transformations to run on a GPU? :-)
Hi,
The trick is to use lcms2 to create a 3D Lut and then use the GPU and
trilinear interpolation. I
A recent message reminded me...
Anecdotally, I've had my (Little CMS-based) products occasionally produce
different color than Adobe Photoshop.
Each time I've investigated, I've learned that ACE just isn't perfect. Okay, a
couple of times I admit it was me setting things up
wrongly for
