Forwarding reply to ocio-dev, not sure if there's another way to send out the zip* https://github.com/imageworks/OpenColorIO/pull/119 -- Jeremy * The zip is only 19K so spamming ocio-dev seems fine

https://github.com/imageworks/OpenColorIO/pull/119 First pass at a iPhone cross compile toolchain. eg cmake -DCMAKE_TOOLCHAIN_FILE=../share/cmake/iPhone-toolchain.cmake .. It compiles but I don't

Hey guys, was just wondering if you could give me an advice on Luts for Mari. I saw that ocio now supports Mari, but only in version v1.3. We're using v1.2 and I'm not sure we're gonna upgrade in the

Ok, thanks a lot for the fix Jeremy. Oliver

In case the nan/inf bug is holding you up - I've fixed the crash and pushed it to a local branch: https://github.com/jeremyselan/OpenColorIO/tree/naninf I'm holding off though in pushing this to the

What problems were you having? Cmake seems to generate usable MSCV 2008 solutions for me when I do cmake -G "Visual Studio 9 2008 Win64" .. in the build dir. There were a few changes I've had to

Hi Paul, I've also been working on gettting a windows version of the OCIO libraries here, and I ran into similar problems to you. We managed to build the GCC version fine, but on windows I resorted

Paul, We're sorry you're having difficulties building OCIO on Windows. Unfortunately, I dont have daily access to a Windows machine for testing, but I know the Foundry is successfully using OCIO on

Hey folks. I'm starting to look at OCIO for integration into one or more of my applications and am having trouble getting it built on Windows (my primary dev machine). I use Visual Studio 2008. I

I've been able to reproduce this now - thanks. -- Jeremy

Thanks for the report. I'll try to get this fixed asap. What platform are you on?

Hey Jeremy, sorry about the late reply, I seem to have looked over this email. This is really helpful, thanks for this. I found a crash bug in the OCIO code. Ocioconvert crashes when you feed in EXR's

Yah, I'm in the same place. The OSX target is fine, it's the ipod/ipad arm targets that fail. (The first error I encounter is that when building yaml-cpp the compiler is tested by building a

Yep that's what I saw last night, everything builds for a OSX target fine other than PyOpenColor which fails to link because of some Python symbols. Did you find a fix for this? The xcode build spits

funny I just saw the article about Lasseter watching dailies for all of Cars 2 on his ipad2. There is already the horror of people looking at quicktimes on different machines and it doesn't always

I verified what the new.ocio output looks like, and the shortened "-FileTransform" syntax you mention does not appear to be enabled by default, though perhaps there's an additional switch we can set

Sounds good! I seem to recall Malcolm mentioning that an updated yaml-cpp would allow tidying up the config syntax a bit - allowing "-FileTransform{src:blah}" instead of "-!<FileTransform>{src:blah}",

https://github.com/imageworks/OpenColorIO/pull/117 Added a bunch of windows build fixes. Thanks to the Foundry for providing this hitlist. Biggest change of note is the updated from yaml-r423 to

Heh, an OCIO image viewer for iPad? \o/ I've compiled OCIO via the Xcode project generator a while ago, when adding the CSP prelut support (to get Xcode's nice error reporting) - wasn't for iOS, but

FYI, The Foundry has successfully gotten OCIO working on Windows, but it required bumping up to the latest stable yaml-cpp version. So just a heads up, that library version will be changing soon.