News

#HTJ2K - does it need SIMD or does it need Rust? As one of the key features of J2K is great quality progression I am holding my judgement for now.

The first stable release of #Jpylyzer 2.2 is out now!

Main new feature is the support for High Throughput #JPEG2000 (#HTJ2K), and its JPH file format.

Also lots of other fixes and improvements, as well as some API and output enhancements:

https://jpylyzer.openpreservation.org/2024/01/23/jpylyzer-2-2-release

Jpylyzer 2.2 stable release

In other news, the production version of #jpylyzer 2.2 will finally be out this Wednesday. For those who can't wait, I (more or less by accident!) already uploaded it to the Python package index today #jpeg2000 #HTJ2K

Just a reminder for who missed this earlier: a few weeks ago we published a release candidate for #jpylyzer 2.2, which is available for testing.

This release adds support of High Throughput #JPEG2000 #HTJ2K and its associated file formats, various codestream validation/parsing improvements, some output enhancements (including reporting of warnings), and an improved Python API.

Details here:

https://jpylyzer.openpreservation.org/2023/11/07/jpylyzer-2-2-release-candidate

Please let us know any issues, so we can fix them for the stable release!

Jpylyzer 2.2 release candidate

The release candidate for #Jpylyzer 2.2 is out now! This is a truly action-packed release. Among other things, it adds support for High Throughput #JPEG2000 #HTJ2K. More info here:

https://jpylyzer.openpreservation.org/2023/11/07/jpylyzer-2-2-release-candidate

@general

Jpylyzer 2.2 release candidate

High Throughput #JPEG2000 #HTJ2K files are still rare in the wild, but I added a few to the Jpylyzer test files repo:

https://github.com/openpreserve/jpylyzer-test-files

Additional test files are welcome!

GitHub - openpreserve/jpylyzer-test-files: Test files for conformance testing and benchmarking Jpylyzer.

Test files for conformance testing and benchmarking Jpylyzer. - openpreserve/jpylyzer-test-files

GitHub

For the adventurous #Jpylyzer users out there, I published a (strictly unofficial!) beta of version 2.2.0, which includes support for High Throughput #JPEG2000 #HTJ2K.

Install using:

pip install --pre jpylyzer

To validate a JPH file:

jpylyzer --format jph oj-ht-byte.jph > out-jph.xml

To validate a HTJ2K codestream:

jpylyzer --format jhc oj-ht-byte_causal.jhc > out-jhc.xml

Draft docs are here:

https://github.com/openpreserve/jpylyzer/blob/2-2-dev/doc/jpylyzerUserManual.md#user-content-fnref-14-7410ff13fdb411aef53ee8e1065145c4

An "official" release candidate will follow later.

jpylyzer/doc/jpylyzerUserManual.md at 2-2-dev · openpreserve/jpylyzer

JP2 (JPEG 2000 Part 1) validator and properties extractor. Jpylyzer was specifically created to check that a JP2 file really conforms to the format's specifications. Additionally jpylyzer is ab...

GitHub

Spent some time looking into software support for High Throughput #JPEG2000 #HTJ2K.

The only open source software I could find that can write the JPH format is OpenHTJ2K:

https://github.com/osamu620/OpenHTJ2K

And below some observations on a few other encoders I looked into:

https://github.com/openpreserve/jpylyzer/issues/197#issue-1873560610

GitHub - osamu620/OpenHTJ2K: An open source implementation of ITU-T Rec.814 | ISO 15444-15 (a.k.a. HTJ2K).

An open source implementation of ITU-T Rec.814 | ISO 15444-15 (a.k.a. HTJ2K). - GitHub - osamu620/OpenHTJ2K: An open source implementation of ITU-T Rec.814 | ISO 15444-15 (a.k.a. HTJ2K).

GitHub

(Not so) random quote from the High Throughput #JPEG2000 (#HTJ2K) white paper:

"As open source software, of course, the implementation has not been optimized nearly to the same extent as full commercial offerings such as that of Kakadu."

đŸ€·â€â™‚ïž (noteworthy to mention here that the white paper's lead author is also the developer of Kakadu)

Link to full document:

https://www.htj2k.com/wp-content/uploads/white-paper.pdf