Are you running make with parallel jobs enabled (e.g. "make -j 4")? If so, the real error is likely buried further back in the build output.

Should it not be considered ITU-BT-709 if and only if it complies with the specification range? Further, that headroom and footroom should be baked into the YCbCr. It would seem there are several

Interesting! Of course, this only applies if your source is arriving with headroom and footroom, which it often does not. After all, Rec. 709 is really YCrCb, right? So you rarely would access the

Jeremy: You said: > " If we wanted to encode that in 8 bits, we would use integer values 0-255. And for 10 bits, we would using 0-1023. Note that scaling from 8 to 10 bits (or back) is NOT a simple

Oups, I didn't finish this sentence… …to work with big-endian streams. ;-)

Hi Jeremy, Thanks so much for your reply. For now, I "only" want to find a way to get the most accurate, richest, "objectively" (standalone) scene-referred images from my camera in ACES-linear. This

Vincent, Interesting code, thanks for sharing! My apologies for not replying sooner, my bandwidth has been way too limited of late. :( There are quite a few different questions here. Let me take a

Hi, I'm trying to convert the S-Log2/S-gamut 10-bit 422 XAVC footage coming out of my Sony F55 camera to a sequence of Linear ACES RGB OpenEXR files. I would like to validate the assumptions I make

Not sure exactly what you are asking, but.. The P3 to XYZ transform is typically done as a colour matrix and gamma adjustment, which could also be baked into a 3D LUT There is a description of the

Thanks Jeremy, We use a 3rd party tool that is built against OCIO. Their recent release includes a custom namespaced OCIO build, but with no header file installation. The issue is that whilst they

Hmmm... I hadnt thought about passing an alternate soname to the build process, but it makes sense that you could need it for applications which load both a public and private version of OCIO. Can

Hi All, I am looking to build the core lib with the -D OCIO_NAMESPACE=foo option. Whilst this builds just fine, I see that the SONAME is unchanged with the above. So, how do you resolve ambiguities

>Unfortunately, it seems that PlanarImageDesc also requires at least 3 channels of >data. I tried passing it NULL pointers for the other, non existing channels, though it >complains at runtime that

Hi Jeremy, Thanks for your quick reply! Unfortunately, it seems that PlanarImageDesc also requires at least 3 channels of data. I tried passing it NULL pointers for the other, non existing channels,

If your image is packed separately per channel (ex: RRRRRRR... GGGGG... BBBB.... ), the Planar ImageDesc is probably what you're looking for. Give that a try? PlanarImageDesc(float * rData, float *

Hi, In my application, images are split into their separate channels, and operations are performed per channel. I have individual float arrays for each channel (obtained via openimageio), and I would

Your other option is to select Other -> All Plugins -> Update, and then finding it in the Other -> All Plugins -> O menu. Hugh Macdonald nvizible – VISUAL EFFECTS +44(0) 20 3167 3860 +44(0) 7773

It looks like Nuke 7.0v6 ships with the OCIOLookTransform node, though it's not exposed in the menus by default. Quoting the release notes... BUG ID 24785 - OCIOLookTransform was missing from the

It seems like the OCIOLookTransform node mentioned on this page: http://opencolorio.org/userguide/looks.html Is missing from the OCIO bundled with Nuke 7.0v4. Has the LookTransform node been

Hi! So you shouldnt have to muck around with any of the specific underlying Transforms (you mention the log transform, and the file transform). The typical use case with OCIO is that these are all