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.

Sign up for GitHub

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

Jump to bottom

compliant J2K code stream can trigger decode error (0xFFFF bug) #8

Open
dcbullock opened this issue Oct 17, 2023 · 1 comment
Open

compliant J2K code stream can trigger decode error (0xFFFF bug) #8

dcbullock opened this issue Oct 17, 2023 · 1 comment

Comments

@dcbullock
Copy link

dcbullock commented Oct 17, 2023 •
edited

Two d-cinema J2K decoders, the Dolby Cat. No. 862 (installed in DSS200) and Dolby DSP100 will fail to correctly decode a J2K codestream with a specific byte pattern (0xFFFF) at specific locations.

The attached PDF provides:

  • specific pattern details
  • a method to constrain J2K codestreams to avoid the error
  • link to a validation tool that can be used to detect the pattern in existing codestreams
  • specific CLI invocations of Kakadu to generate a codestream that complies with the included constraints

v7 deprecated by v8
cat862-j2k-constraint_v7.pdf
@dcbullock
Copy link
Author

Edit the URLs in the PDF to work correctly - v8 attached.

cat862-j2k-constraint_v8.pdf

@remia remia mentioned this issue Nov 19, 2023
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dcbullock