on September 23, 2010 at 3:05 AM PDT
I am here once again to report decoding issues related to JIIO J2K
Recently, I reported some decoding issues with the NATIVE JIIO J2K
ImageReader. A related bug was then submitted by someone on the list:
Following to the discovery of those issues, we switched to the PURE-JAVA
JIIO J2K ImageReader in our application, which is a bit slower but seemed to
But now, I am encountering some "decoding issues / artifacts" also with the
pure-Java J2K ImageReader. Please see the images contained in the following
As you can see, in this case the native J2K Image Reader seems to work fine,
but the pure-Java version doesn't.
In other cases, it is the opposite.
Hence, which J2K ImageReader shall we use??? :-(
Do you have suggestions or workarounds to these decoding issues?
Thanks in advance and best regards,