Skip to content

Handle colorspace conflicts with OpenJPEG #28

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

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

acdha
Copy link
Contributor

@acdha acdha commented Aug 9, 2019

I'm not sure how much OpenJPEG handling of JP2s with conflicting color definitions matters to you but if it does, this builds on #27 to add the patch from uclouvain/openjpeg#1207.

@acdha acdha force-pushed the handle-colorspace-conflicts branch 2 times, most recently from f987cc1 to c4d7a42 Compare August 29, 2019 20:11
@acdha acdha force-pushed the handle-colorspace-conflicts branch 2 times, most recently from a8c6aea to 3db4cf6 Compare February 6, 2020 19:20
acdha added 2 commits July 19, 2021 15:40
This installs the patch from uclouvain/openjpeg#1207 to handle the case where an image has a color profile which is not compatible with the actual channel definitions.
This does not allow use of the FFMPEG processor but we didn’t need that and it reduces the container size considerably, not to mention avoiding some CVEs which are in ffmpeg dependencies and currently unfixed such as CVE-2019-14889.
@acdha acdha force-pushed the handle-colorspace-conflicts branch 2 times, most recently from 71688b1 to d0d67ed Compare July 19, 2021 21:09
@acdha acdha force-pushed the handle-colorspace-conflicts branch from d0d67ed to 0010b65 Compare June 26, 2023 20:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant