2.0 is now a release candidate, aiming to be the official release on Dec 1 if
nothing critical is found to be broken.
If upgrading to 2.0 is a possibility and solves the problem, that's certainly
the easiest for me. :-) But I totally understand if somebody needs this fixed
before they are ready to throw the switch (there are some API changes, the
swtich from 1.8->2.0 requires a little preparation), I am happy to try to
backport a fix.
Tip:
oiiotool --help
will show you (at the bottom) all the available color spaces in whatever OCIO
configuration it finds. That doesn't necessarily explain seg faults (which
should never happen), but it can help you diagnose if color transforms produce
other errors or don't turn out like you think. Sometimes people realize it's
not finding the ocio config file they intended, or that their config doesn't
know about the color space they are requesting.
-- lg
> On Nov 28, 2018, at 7:06 AM, Daniel Flehner Heen <[email protected]>
> wrote:
>
> We use ocioconvert all the time to apply/bake "view luts" (which do primary
> conversion when needed) and it works like a charm. Currently running 1.8.14,
> but worked with 1.8.5 before we upgraded.
> Might be worth a shot testing it. If not only to narrow down what's failing.
> If not, I hope 2.0 works for you :)
>
> On Wed, Nov 28, 2018 at 2:02 PM Etienne Fleurant <[email protected]
> <mailto:[email protected]>> wrote:
> As far as I know, you can't bake an OCIO color profile using colorconvert.
> You can only use aforementioned ociodisplay function to do that.
>
> Etienne
>
> On Nov 28, 2018, at 03:03, Daniel Flehner Heen <[email protected]
> <mailto:[email protected]>> wrote:
>
>> Have you tried using ImageBufAlgo.colorconvert() instead?
>>
>> On Wed, Nov 28, 2018 at 4:14 AM Stephen Mackenzie <[email protected]
>> <mailto:[email protected]>> wrote:
>> Yes, I had the same issue described here. The pybind11 work being done for
>> then-oiio-1.9-alpha fixed it for me, so I've just been awaiting the oiio-2
>> release as a solve.
>> YMMV.
>>
>> On Tue, Nov 27, 2018 at 9:00 PM Etienne Fleurant <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> Hi,
>>
>> We are getting a seg fault using ImageBufAlgo ociodisplay in python. We're
>> using:
>> oiio 1.8.10
>> compiled on CentOS 7 64bit
>>
>> Here's a code snippet of what I'm doing:
>>
>> print os.getenv( 'OCIO' ) # ---> prints '<SOME_PATH>/spi-anim/config.ocio'
>> inputPath = '<MY_PATH>/test_for_ocio.tif'
>> outputPath = '<MY_PATH>/output.tif'
>> srcBuf = OpenImageIO.ImageBuf( inputPath )
>> OpenImageIO.ImageBufAlgo.ociodisplay( srcBuf , dstBuf , 'sRGB' , 'Film' )
>> dstBuf.write( outputPath )
>>
>> ---> outputs : Segmentation fault (core dumped)
>>
>> I'm able to make it work through oiiotool though:
>> oiiotool '<MY_PATH>/test_for_ocio.tif' --iscolorspace 'lnh' --ociodisplay
>> 'sRGB' 'Film' -o '<MY_PATH>/output.tif'
>>
>> but ultimately I'd like to make it work in python. It's a bit hard to debug
>> since I have no idea why it's seg faulting...
>>
>> By the way, I also tried adding:
>> srcBuf.specmod().attribute( 'oiio:ColorSpace' , 'lnh' ) after my srcBuf
>> declaration above to no avail.
>>
>> That was to replicate what I have in my oiiotool example, since if I omit
>> this from that command line, I was getting the following error:
>> oiiotool ERROR: ociodisplay : DisplayTransform error. Cannot find
>> inputColorSpace, named 'Linear'.
>>
>> Maybe I'm having a similar error with python resulting in the seg fault, but
>> I'm not sure.
>>
>> I'm using the spi-anim config with this example.
>> Any help would be appreciated. I could send an example files if needed.
>>
>> Thanks in advance
>>
>> _______________________________________________
>> Oiio-dev mailing list
>> [email protected] <mailto:[email protected]>
>> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
>> <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org>
>> _______________________________________________
>> Oiio-dev mailing list
>> [email protected] <mailto:[email protected]>
>> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
>> <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org>
>>
>>
>> --
>> -Daniel
>> _______________________________________________
>> Oiio-dev mailing list
>> [email protected] <mailto:[email protected]>
>> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
>> <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org>
> _______________________________________________
> Oiio-dev mailing list
> [email protected] <mailto:[email protected]>
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
> <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org>
>
>
> --
> -Daniel
> _______________________________________________
> Oiio-dev mailing list
> [email protected]
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
--
Larry Gritz
[email protected]
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
