You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I understand, JPEG 2000 (.jp2, .j2k) is a subset of JPEG 2000 Extended (.jpx, .jpf) - therefore JPX.js should be able to render J2K files.
However, working with JPEG2000 data extracted from the Enterix data set, I get unexpected results with JPX.js as compared with openjpeg.js (and the openjpeg command line tool).
Incidentally, JPX.js is much faster than openjpeg.js and could be incredibly useful as a standalone library for JPEG2000 reading in Javascript (one key application would be for use in DICOM web viewers). Are any of @ivmartel, @chafey and @mi-kas interested in contributing from this point of view?
From what I understand, JPEG 2000 (.jp2, .j2k) is a subset of JPEG 2000 Extended (.jpx, .jpf) - therefore JPX.js should be able to render J2K files.
However, working with JPEG2000 data extracted from the Enterix data set, I get unexpected results with JPX.js as compared with openjpeg.js (and the openjpeg command line tool).
Result with jpk.js
Result with openjpeg.js
Here is the code I am using: https://gist.githubusercontent.com/louismullie/dca8a3fa351cc955b38f/raw/199dbfc000088b125dffa2235308d2baf73d0464/jpx-j2k-bug.html
Anybody have ideas as to what explains this kind of behaviour? Is JPX.js built to support J2K as a subset of JPX?
The text was updated successfully, but these errors were encountered: