I think it should be the other way around as I expect production builds to be
smallest possible to speed up any IO when software is installed on network
storage.
It’s a bit like saying your expecting the software to crash so make the library
3x bigger.. OIIO is pretty stable in most places I
For embedded icc profiles it would be a binary blob, is this even supported?
.malcolm
On 19/07/2013, at 12:33 AM, Larry Gritz wrote:
I have to admit that my knowledge is sketchy as to precisely what data makes
up an ICC profile.
So anyway, the way that the ImageSpec is organized is that
On 23/06/2012, at 11:56 PM, Stefan Stavrev wrote:
Malcolm can you please give me more details what do you mean by pivot
parameter?
With unbounded images especially (values over 1.0) the average value most
likely is not the centre of the visual range. Contrast conceptually as it is
reduced
Can contrast also have a pivot parameter please? Depending on the luminance
encoding of the image this needs to be diffrent.
On 23/06/2012, at 2:43 PM, Chris Foster wrote:
On Sat, Jun 23, 2012 at 7:24 PM, Stefan Stavrev stavrevste...@gmail.com
wrote:
I implemented everything we talked about
There is no install target for the test binary that is compiled.
@richard it's only used at build time to create a unittest binary, this is what
gets run when you do a 'make test'. This code never makes it into the released
code so it can be ignored in terms of the packaging I would guess,
Maybe in the short term just moving them into another folder exampleapps might
do?
On 06/12/2011, at 7:44 PM, Jeremy Selan wrote:
The core OCIO library does *not* link to OIIO, to avoid cyclical
dependencies, as you suggest.
What you're seeing is that OCIO comes with two example apps,
