Larry Gritz

Do you want a multi-layer file (an OpenEXR 1.x file with many channels, having a particular naming convention that allows them to be logically grouped)? Or do you want a...

`oiiotool layer1.exr layer2.exr layer3.exr --siappendall -o merged.exr`

`oiiotool deep_tiled.exr --scanline -o deep_scanline.exr` `oiiotool deep_scanline.exr --tile 64 64 -o deep_tile.exr`

We use / have used tiled deep very extensively over the years, just because it was a better fit when outputting from our tile-based renderer. But, yeah, we had to...

Note to those who may look at the above referenced OIIO PR: the magic is that in my overloaded Imf::IStream, I handled UTF-8 filenames properly when opening the files in...

But it's not supposed to be "bare". #include is fine. But #include is not going to find it in the include directory.

Yes, the fully qualified `#include ` is always preferred in any context, IMHO.

Do I recall that this has been addressed in 3.0? Can we close?

I think we're crazy not to test against C++11 (unless we're going to say we no longer support it) as well as C++20 (because at the very least, why not...

Testing VFX Platform configurations (in particular, on CentOS images) is necessary, but nowhere near sufficient.