Re: [Oiio-dev] passing UNKNOWN to write_scanlines removed in python?

2019-11-29 Thread Andrew Gartner
No worries on the reply time, I think this might work and I'll give it a shot when I get back to the office after the holiday. You're correct I only need to preserve what I read and the bit pattern doesn't really matter, so if I can just leverage setting the channelformats on the spec I should be

Re: [Oiio-dev] passing UNKNOWN to write_scanlines removed in python?

2019-11-28 Thread Larry Gritz
Sorry for the delay in replying. I see, you are correct. When we switched to pybind11 (the patch is from 14 Nov 2017, and has been in release 2.0+), it changed from Unknown meaning "raw native format bit pattern" to "one type that is adequate for any/all of the native channel types". I think

[Oiio-dev] passing UNKNOWN to write_scanlines removed in python?

2019-11-19 Thread Andrew Gartner
Hey Larry (and anyone else who may be able to help), Just moved to OIIO 2.0 and realized I've got issues with how i was using write_scanlines from python now. Prior to 2.x I had been passing oiio.UNKNOWN to the call as I had been treating all my pixel data as raw char*'s under the hood. I was