View online version
http://gyt2.mjt.lu/nl2/gyt2/1qyj4.html?m=AEkAFpIvtx0AAUlJNS4AAGmMNpUAARpaV6oAGf6kAAdlMQBYNW9DrYFG_jcSTqWxhF0hFMIPngAHDG0=b6eabab3=df2bf4ec=681...@bugs.debian.org[http://gyt2.mjt.lu/img/gyt2/b/1q375/0yyio.jpeg]
[http://centralflags.co.uk/]FORECOURT FLAGS - OCTOBER OFFERSWe are
For more reference see the thread at:
http://groups.yahoo.com/group/jasper-discussion/message/717
This group is not public, however one can find the message forwarded here:
https://groups.google.com/group/comp.protocols.dicom/msg/c93276d13fc6d74
--
To UNSUBSCRIBE, email to
On Thursday, June 30, 2005 5:53:52 PM UTC+2, Mathieu Malaterre wrote:
Ok just for future references, I send the very same question on jasper
mailing list, and Marco (you are everywhere !) answer me, he already saw
the problem and had a very detailed description of the problem:
I followed suggestion from:
http://tech.groups.yahoo.com/group/jasper-discussion/message/1452
I downloaded geojasper:
http://www.dimin.net/software/geojasper/geojasper_src_1.4.0.zip
$ autoreconf make
- still the exact same issue. 16bits lossy simply does not work in
jasper and/or geojasper.
Package: libjasper1
Severity: grave
I cannot decompress a 16bits J2k codestream. Using jasper leads to
incorrect result (noisy?).
Steps:
$ jasper --input CT_Phillips_JPEG2K_Decompr_Problem.j2k --output
CT_Phillips_JPEG2K_Decompr_Problem_jasper.pnm
Compare the output with openjpeg (which is
5 matches
Mail list logo
