-
Notifications
You must be signed in to change notification settings - Fork 14
Zlib compression #180
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
base: main
Are you sure you want to change the base?
Zlib compression #180
Conversation
… lead to double file creation and corrupted files. The lock solves this.
…into zlib-compression
| ELEVEN_BIT_MONOCHROME = 6 | ||
|
|
||
| ZLIB_COMPRESSED = 8 | ||
| NO_COMPRESSION = 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems redundant to UNCOMPRESSED. If NO_COMPRESSION is a standard name, maybe good to remove uncompressed
|
I'd suggest merging this (assuming it passes test). However, my write access to this repository has been removed. Perhaps @nicost or @marktsuchida could merge it? |
|
Thanks, @henrypinkard! That would be the effect of you retiring from the org, but we can add you as a collaborator on specific repos. I've sent an invite. |
|
Thanks @marktsuchida . I still seem to not have permissions to approve running the tests |
|
@henrypinkard Strangely, I don't see a button to approve either. (Never seen "Waiting for status to be reported" before.) |
This includes the 8bit nd tiff tag bugfix, put_image lock for thread safety, reader optimization (mmap) and zip (zlib) compression.
The compression tag value was chosen to be the same like in tiff specifications (1 for no compression, 8 for zip/zlib compression).
The compression is compatible with standard tiff readers.
For now there are no zlib options (uses zlib standard keys).