I did a lot of multiview and multipart stuff with EXRs and OIIO for stereo VFX
workflow, but always used the library and my own code for this stuff, rather
than oiiotool
The simplest SXR should just be an EXR with set of interleaved channels i.e.
R,G,B,A,right.R,right.G,right.B,right.A
and a multiView attribute e.g. multiView (left,right), which is of StringVector
type in the EXR file - this may not be possible to set with oiiotool directly
as it requires, on the C++ OIIO side, something like:
const char* vals[2]={"left","right"};
OpenImageIO::TypeDesc multiViewAttr(OpenImageIO::TypeDesc::STRING,2);
outputImageSpec.attribute("multiView",multiViewAttr,vals);
and glancing at oiiotools attribute-setting code, there doesn't seem to be much
around setting array-based attributes like this. Not sure how interested Larry
would be in adding this kind of sttribute-setting to oiiotool, as I imagine
parsing a wide range of array types from the command line can get messy and
error-prone.
Note the 'right' and 'left' channel name prefixes are pretty much mandatory for
proper view assignment using 'single part' SXRs - you can use left.R or right.R
but doing something like 'R.R' or 'lview.R' will almost certainly confuse EXR
reading applications.
You can also write out multipart EXRs that have a view identifier for each part
(this would be an OIIO image with multiple subimages), but I would reccomend
getting the single-part interleaved version working first, as there really
isn't too much standardisation around this stuff, and Nuke has its own
conventions for how it wants to represent view naming when reading/writing
multipart EXRs.
exrheader (comes with OpenEXR libs) is your friend for looking at exactly what
metadata is contained in an exr file.. i would usually get an example nuke
render from an artist, dump its metadata with exrheader, and then match the
channel/part naming using my OIIO-based tools so the SXRs I produced would load
back up into nuke with minimal fuss.
Feel free to ping me off-list if you like- I dont have my EXR2 code in front of
me right now but I seem to recall part naming was an issue with OIIO-generated
multipart EXR without getting in there and changing things at a reasonablly low
level.
-Pete
> On 25/10/2015, at 6:04 am, Sebastian Elsner | RISE <[email protected]>
> wrote:
>
> Hello,
>
> I am trying to combine two exrs into one stereo exr, but I fail doing so with
> oiiotool. I am able to create new subimages with -siappend, but it seems this
> is something different from what I want (at least when nuke is reading the
> files). Can I do this with oiiotool?
>
> Regards
>
> Sebastian
>
>
> --
> check out pointcloud9.com
>
> Sebastian Elsner - Pipeline Technical Director - RISE
>
> t: +49 30 20180300 [email protected]
> f: +49 30 61651074 www.risefx.com
>
> RISE FX GmbH
> Schlesische Straße 28, 10997 Berlin
> An der Schanz 1A, 50735 Köln
> Büchsenstraße 20, 70174 Stuttgart
> Gumpendorferstraße 55, 1060 Wien
> Geschaeftsfuehrer: Sven Pannicke, Robert Pinnow
> Handelsregister Berlin HRB 106667 B
>
> _______________________________________________
> Oiio-dev mailing list
> [email protected]
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
