Hey all,

I'm trying to set custom channel names when creating a .tx file, but it
seems that I'm particular feature either may not work correctly, or that
I'm overlooking something. This is using OIIO 1.5.0.

The first thing I tried was setting the "maketx:channelnames" attribute on
my output ImageSpec to a comma-separated string (e.g. "R,G,B,A,Z,mask").,
but when I inspect the file using iinfo, it lists the channels as "R, G, B,
A, channel4, channel5".

I also tried manually populating the `.channelnames` vector on the
destination ImageSpec, as well as the `spec.alpha_channel` and
`spec.z_channel` indices, but this didn't seem to work either.

Lastly, since my code is passing a filled ImageBuf to
ImageBufAlgo::make_texture, I tried the manual population process again,
except on the ImageSpec that is passed to the constructor of the ImageBuf
I'm populating to be written (since it looked like make_texture_impl could
potentially allow the source ImageBuf to be written directly).

Then, just to sanity-check myself, I wrote out an EXR with the channels I
wanted, and then converted it to a .tx file using `maketx --oiio
--channelnames "R,G,B,A,Z,mask" /path/to/file.exr`, but iinfo still showed
the last two channels as being named "channel4" and "channel5". I also
wrote some code to read the same image back in and print out the contents
of its channel names as seen by OIIO (to sanity-check iinfo), with the same
results.

My question is, is this A) a limitation of libtiff, B) a limitation of the
OIIO tiffoutput plugin, C) an OIIO feature that hasn't been hooked up yet,
D) a bug, or E) something else?

Thanks for any help.


-Nathan
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org

Reply via email to