jpylyzer icon indicating copy to clipboard operation
jpylyzer copied to clipboard

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 able to e...

Results 20 jpylyzer issues
Sort by recently updated
recently updated
newest added

See also third issue mentioned here: This consistency check should be done at the level of the main codestream header, as well as the tile-part level.

feature
P3

## Dev Effort TBC ## Description Currently jpylyzer doesn’t support the full set of marker segments that can occur in a codestream. Missing ones should ideally be included at some...

feature
P2

## Dev Effort 1D ## Description I use jpylyzer in some of the unit tests for my jpeg 2000 codec. I am getting "Conditional jump or move depends on uninitialised...

bug
P2

``` https://buildd.debian.org/status/fetch.php?pkg=jpylyzer&arch=all&ver=2.0.0-2&stamp=1582319718&raw=0 ... dh_auto_test -i -O--buildsystem=pybuild I: pybuild base:217: cd //.pybuild/cpython3_3.7/build; python3.7 -m pytest tests ============================= test session starts ============================== platform linux -- Python 3.7.6, pytest-4.6.9, py-1.8.1, pluggy-0.13.0 rootdir: /...

bug
P1

If I run the new 32-bit Windows executables on an arbitary (set of) JP2(s), the following warning is printed to STDERR: ``` C:\Temp\JPYLYZ~1.0RC\jpylyzer\jpylyzer\etpatch.py:74: FutureWarning: The behavior of this method will...

bug
P3

The code in the [findFiles](https://github.com/openpreserve/jpylyzer/blob/94c11a5ef7033346dce0e4b06c0d4b5549438995/jpylyzer/jpylyzer.py#L538) function is very complex and difficult to read. It might be possible to simplify things using e.g. the [Pathlib](https://docs.python.org/3/library/pathlib.html) module, which also supports glob patterns....

Supporting both Python 3 and Python 2.7 at the same time is getting increasingly difficult, so I'd suggest to remove Python 2.7 support in the foreseeable future. Probably wise to...

These were introduced in 2.0 for backward compatibility for workflows that expect 1.x output, perhaps remove by 2.2 release. If so, show a warning if these features are used in...

Example: Validating this file with jpylyzer results in the following reported *codeBlockHeight* value: ```xml 50216813883093446110686315385661331328818843555712276103168 ``` Validating the output against the XSD schema then results in this: ``` oj-jp2.xml:69784: element...

## Dev Effort 1D ## Description Currently > 200 MB, this is getting ridiculous. Some clues:

bug
P2