Follow-up conversation on the ticket:  
https://github.com/OpenImageIO/oiio/issues/600

I can't reproduce the segfault, but I agree that an oiiotool fix is needed to 
let you specify per-channel data format for the output.



On May 17, 2013, at 11:08 AM, Larry Gritz wrote:

> There may be some inherent limitations that need to be fixed in oiiotool that 
> make it hard to express that you want to output channels that are not all the 
> same data type.
> 
> I'm going to give this a try, stay tuned.
> 
>       -- lg
> 
> 
> On May 16, 2013, at 4:48 PM, Andrew Wood wrote:
> 
>> opened a ticket on this as well, since its segfaulting, but maybe someone 
>> knows a workaround to get --chappend working?
>> https://github.com/OpenImageIO/oiio/issues/600
>> 
>> using oiiotool (1.1.9 tag) I am trying to make a little tool that changes 
>> exrs to 16-bit, except for the depth channel, which stays at 32 bit.
>> I'm shuffling out depth.Z, swapping, converting to 16-bit, selecting rgba, 
>> then hoping that chappend will grab depth.Z from the stack and put it back. 
>> However, --chappend seems to have no effect.
>> 
>> here's my command:
>> oiiotool /var/tmp/nuky.exr --attrib order "" --chnames R,G,B,A,depth.Z 
>> --compression ZIPS --dup --ch depth.Z --chnames depth.Z --scanline --swap -d 
>> half --ch R,G,B,A --chnames R,G,B,A --chappend -o /var/tmp/test.exr
>> 
>> original image attached.
>> 
>> 
>> 
>> -> exrinfo /var/tmp/nuky.exr
>> 
>> 
>> /var/tmp/nuky.exr:
>> 
>> file format version: 2, flags 0x0
>> channels (type chlist):
>> A, 32-bit floating-point, sampling 1 1
>> B, 32-bit floating-point, sampling 1 1
>> G, 32-bit floating-point, sampling 1 1
>> R, 32-bit floating-point, sampling 1 1
>> depth.Z, 32-bit floating-point, sampling 1 1
>> compression (type compression): zip, individual scanlines
>> dataWindow (type box2i): (1 1) - (38 38)
>> displayWindow (type box2i): (0 0) - (39 39)
>> lineOrder (type lineOrder): increasing y
>> nuke/node_hash (type string): "fb62c576d8dfd9c3"
>> pixelAspectRatio (type float): 1
>> screenWindowCenter (type v2f): (0 0)
>> screenWindowWidth (type float): 1
>> 
>> here's the gdb stack trace:
>> 
>> 0x00002acdb2464506 in boost::thread::start_thread () from 
>> /tools/package/boost/1.47.0/lib/libboost_thread.so.1.47.0
>> (gdb) bt
>> #0 0x00002acdb2464506 in boost::thread::start_thread () from 
>> /tools/package/boost/1.47.0/lib/libboost_thread.so.1.47.0
>> #1 0x00002acdb2003d00 in OpenImageIO::v1_1::ImageBufAlgo::parallel_image, 
>> boost::reference_wrapper, boost::reference_wrapper, boost::arg, 
>> boost::_bi::value > > > ()
>> from 
>> /dd/dept/software/users/bsloan/swdevl/bsloan/3ps/openimageio/oiio-Release-1.1.9/dist/linux64cent5_64/lib/libOpenImageIO.so.1.1
>> #2 0x00002acdb1ff7980 in OpenImageIO::v1_1::channel_append_impl ()
>> from 
>> /dd/dept/software/users/bsloan/swdevl/bsloan/3ps/openimageio/oiio-Release-1.1.9/dist/linux64cent5_64/lib/libOpenImageIO.so.1.1
>> #3 0x00002acdb1ff8480 in OpenImageIO::v1_1::ImageBufAlgo::channel_append ()
>> from 
>> /dd/dept/software/users/bsloan/swdevl/bsloan/3ps/openimageio/oiio-Release-1.1.9/dist/linux64cent5_64/lib/libOpenImageIO.so.1.1
>> #4 0x0000000000428fae in action_chappend ()
>> #5 0x00002acdb2017c37 in OpenImageIO::v1_1::ArgParse::parse ()
>> from 
>> /dd/dept/software/users/bsloan/swdevl/bsloan/3ps/openimageio/oiio-Release-1.1.9/dist/linux64cent5_64/lib/libOpenImageIO.so.1.1
>> #6 0x000000000041cc40 in getargs ()
>> #7 0x0000000000430b2b in main ()
>> 
>> any ideas? I tried both --chappend and --chappend depth.Z
>> 
>> 
>> thanks!
>> Andrew
>> 
>> 
>> 
>> Andrew Wood
>> Pipeline Engineer, Digital Domain
>> x2914
>> <nuky.exr>_______________________________________________
>> Oiio-dev mailing list
>> [email protected]
>> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
> 
> --
> Larry Gritz
> [email protected]
> 
> 
> _______________________________________________
> Oiio-dev mailing list
> [email protected]
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org

--
Larry Gritz
[email protected]


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

Reply via email to