A note that the babl roadmap towards enabling use of multiple
working/sensor/target RGB spaces in a single GEGL graph has been
slightly updated. Now also mentions why accumulating floating point
errors if more conversions than desired happens isn't a real concern
with current photo technology
On 10/13/2014 06:36 PM, Elle Stone wrote:
How do you plan to tell when an image is an sRGB image and when it's not
an sRGB image?
The roadmap specifies 24 different formats for sRGB images and 24
additional formats for non-sRGB images.
Presumably the 24 additional formats for non-sRGB
On Tue, Oct 14, 2014 at 11:20 AM, Elle Stone
ellest...@ninedegreesbelow.com wrote:
On 10/13/2014 06:36 PM, Elle Stone wrote:
How do you plan to tell when an image is an sRGB image and when it's not
an sRGB image?
The roadmap specifies 24 different formats for sRGB images and 24 additional
The planned architecture as outline in babl/docs/roadmap.txt will likely
collapse under its own weight.
If the devs are determined to pursue this course to the bitter end, here
are some considerations regarding encoding trc_gamma as double (you
really can't do this):
//begin quote from the
The sRGB as PCS architecture outline in babl/docs/roadmap.txt will
likely collapse under its own weight. The roadmap should be amended to
reflect a more accurate assessment of the amount of work the planned
architecture will entail.
The babl roadmap says:
Babl currently only supports formats
On Mon, Oct 13, 2014 at 8:19 PM, Elle Stone
ellest...@ninedegreesbelow.com wrote:
The sRGB as PCS architecture outline in babl/docs/roadmap.txt will likely
collapse under its own weight. The roadmap should be amended to reflect a
more accurate assessment of the amount of work the planned
On 10/13/2014 03:25 PM, Øyvind Kolås wrote:
On Mon, Oct 13, 2014 at 8:19 PM, Elle Stone
ellest...@ninedegreesbelow.com wrote:
As the purpose of the roadmap seems to be guiding future development, the
list of editing operations that rely on the chromaticities of the RGB
working space needs to
According to the babl roadmap, sRGB images won't need special-case
treatment.
But every time the user opens an image that isn't an sRGB image,
special-case treatment will be required for chromaticity-dependent
editing operations.
How do you plan to tell when an image is an sRGB image and
The planned architecture as outline in babl/docs/roadmap.txt will likely
collapse under its own weight.
But if the devs are determined to pursue this course to the bitter end,
here are some suggestions regarding white_reference:
//begin quote
. . . permitting at least linear formats with
