IIRC, we need to occasionally read Cineon files for legacy reasons, but
couldn't think of a circumstance in which we'd want to write them, so we
accepted the plugin code with a reader only. In light of that, I think we can
live with the non-existant writer also having the limitation of only bei
The cineon spec seems to say the same as dpx. "Valid component sizes
are 1-, 8-, 10-, 12-, and 16-bit integers and 32- and 64-bit reals
(IEEE floating-point)." and I think it means both Cineon and DPX.
But as Jeremy says seeing a float Cineon file in the wild would be
really unusual... it's not cl
Well, duh, hardly matters since the writer is completely unimplemented. :-)
-- lg
On Apr 18, 2012, at 11:35 PM, Jeremy Selan wrote:
> For what it's worth, I've never seen a .cin file that wasn't 10-bit ints.
>
> So either choice - or a segfault, or an exception - beats the compile
> wa
For what it's worth, I've never seen a .cin file that wasn't 10-bit ints.
So either choice - or a segfault, or an exception - beats the compile
warning in my book. ;)
-- Jeremy
On Wed, Apr 18, 2012 at 11:22 PM, Larry Gritz wrote:
> We're getting some compiler warnings (have for a long time, now
We're getting some compiler warnings (have for a long time, now I'm
investigating) in the Cineon code.
Looking at
src/cineon.imageio/libcineon/Writer.cpp (circa line 284)
src/dpx.imageio/libdpx/Writer.cpp (circa line 313)
See how they're different? No warnings result from DPX.
