You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DPX files come in two endian flavors, and all systems are expected to read both. However, for hardware compatibility purposes it's often preferable to force Big Endian. The dpx writer currently does not allow the writing endian to be toggle at runtime. We should add writer support for an optional hint such as oiio:Endian, to control the output.
See this previous email chain on oiio-dev, "DPX Endian", 12/08/10.
The text was updated successfully, but these errors were encountered:
Hi, I would like to work on this issue. I want to particiate in GSOC 2011 OpenImageIO projects so fixing this issue will give me the prerequisite patch. I have good C/C++ knowledge and a decent knowledge on Image processing and Computer Graphics. Im new to contributing to oen source software, please help me on how to do this.
Let's go with oiio:Endian for now.
It can have values: "big", "little", or "native".
The writer will obey the value, if set. And I think DPX's writer should default to 'Big' if not specified. (Which is the default used in many other linux packages).
We can always adjust the defaults in the future, I think 99% of the work will just be getting the code path in there.
DPX files come in two endian flavors, and all systems are expected to read both. However, for hardware compatibility purposes it's often preferable to force Big Endian. The dpx writer currently does not allow the writing endian to be toggle at runtime. We should add writer support for an optional hint such as oiio:Endian, to control the output.
See this previous email chain on oiio-dev, "DPX Endian", 12/08/10.
The text was updated successfully, but these errors were encountered: