Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DPX writing should support endian switch #36

Closed
jeremyselan opened this issue Mar 14, 2011 · 5 comments
Closed

DPX writing should support endian switch #36

jeremyselan opened this issue Mar 14, 2011 · 5 comments
Assignees
Labels
enhancement Improvement of existing/working features.

Comments

@jeremyselan
Copy link
Contributor

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.

@sanjay-nambiar
Copy link

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.

@inequation
Copy link
Contributor

So was there any agreement on the attribute name? If there is a consensus, I can code it in.

@jeremyselan
Copy link
Contributor Author

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.

Thanks!

@inequation
Copy link
Contributor

Jeremy, please see #69. As far as I can see it should do the trick.

@jeremyselan
Copy link
Contributor Author

thanks - ill check it out

On Wed, Apr 20, 2011 at 1:52 AM, inequation
reply@reply.github.com
wrote:

Jeremy, please see #69. As far as I can see it should do the trick.

Reply to this email directly or view it on GitHub:
#36 (comment)

@ghost ghost assigned inequation Apr 22, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement of existing/working features.
Projects
None yet
Development

No branches or pull requests

3 participants