Re: Review: ociocheck

Malcolm Humphreys <malcolmh...@...>

I was looking at oiio argparse but that too seems dependant on boost for something I remember.


On 05/02/2011, at 7:00 AM, Jeremy Selan wrote:

Agreed about the --inputconfig / $OCIO option. I've added that.

I'll see what I can do about remove the boost dependency. I agree
that if we can avoid it, we should.

-- Jeremy

On Fri, Feb 4, 2011 at 2:57 AM, dbr/Ben <b...@...> wrote:
Looks good!

Perhaps if --inputconfig flag is not set, it could check $OCIO? Might be a convenient way to verify the env is setup correctly, and may answer many "why doesn't OCIO work!" questions. Something like:

$ ociocheck
Checking $OCIO environment variable
Loading /wrong/path/to/config.ocio
Error: File does not exist
$ ociocheck -i /correct/path/to/config.ocio
Loading /correct/path/to/config.ocio ...

Could be useful when there env is less simple, such as inside applications that might be launched from wrapper scripts (e.g run subprocess.Popen("ociocheck") in Nuke's script editor)

Also, I wonder if requiring boost for the config-validation utility is reasonable? While I'm not fussed about the dependency, it seems like ociocheck is something that should always be available, even if built without the optional Boost. I guess the alternatives is to use something standalone like optparse.h, or copy that bit of boost?

On 04/02/2011, at 10:49 AM, Jeremy Selan wrote:


ociocheck now does much better error checking.
It will test each colorspace and see which conversions conversions
to/from scene-linear work, and which do not. This will catch
potential errors related to missing luts, etc.

-- Jeremy

Join to automatically receive all group messages.