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

pngtoimage() and imagetopng() have wrong byte order for 16-Bit image #365

Closed
gcode-importer opened this issue Jun 29, 2014 · 2 comments
Closed

Comments

@gcode-importer
Copy link

Originally reported on Google Code with ID 365

In pngtoimage() and imagetopng() the byte order is wrong for 16-Bit
images.

See attached patches.

winfried


Reported by szukw000 on 2014-06-29 08:08:29


- _Attachment: [openjpeg-1.5.x-branch-r2871-convert.c.dif.gz](https://storage.googleapis.com/google-code-attachments/openjpeg/issue-365/comment-0/openjpeg-1.5.x-branch-r2871-convert.c.dif.gz)_ - _Attachment: [openjpeg-2.x-trunk-r2871-convert.c.dif.gz](https://storage.googleapis.com/google-code-attachments/openjpeg/issue-365/comment-0/openjpeg-2.x-trunk-r2871-convert.c.dif.gz)_
@gcode-importer
Copy link
Author

No, no, no.
I was confused by the MATLAB image mentioned in

 [OpenJPEG] Reading and writing comments like Matlab does

This image turned out to have

 <Pixels BigEndian="true" Interleaved="true"

Please remove this issue.

winfried

Reported by szukw000 on 2014-07-01 12:29:04

@gcode-importer
Copy link
Author

Reported by mayeut on 2014-11-24 22:30:01

  • Status changed: Invalid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant