<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	> <channel><title>Comments on: Truly Lossless JPEG2000 Compression</title> <atom:link href="http://dltj.org/article/lossless-jpeg2000/feed/" rel="self" type="application/rss+xml" /><link>http://dltj.org/article/lossless-jpeg2000/</link> <description>We&#039;re Disrupted, We&#039;re Librarians, and We&#039;re Not Going to Take It Anymore</description> <lastBuildDate>Wed, 23 May 2012 16:01:37 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: Anonymous</title><link>http://dltj.org/article/lossless-jpeg2000/comment-page-1/#comment-229350</link> <dc:creator>Anonymous</dc:creator> <pubDate>Tue, 06 Mar 2012 20:23:39 +0000</pubDate> <guid isPermaLink="false">http://dltj.org/2007/05/almost-lossless-jpeg2000/#comment-229350</guid> <description>&lt;!--%kramer-ref-pre%--&gt;[...]  [...]&lt;!--%kramer-ref-post%--&gt;</description> <content:encoded><![CDATA[<p><img src="http://cdn.dltj.org/wp-content/plugins/kramer/kramer.gif" class="technorati-balloon" alt="Kramer auto Pingback" style="border:0;" />[...]  [...]</p> ]]></content:encoded> </item> <item><title>By: ImageMagick &#8226; View topic - Lossless JPEG2000 isn't lossless in IM</title><link>http://dltj.org/article/lossless-jpeg2000/comment-page-1/#comment-33360</link> <dc:creator>ImageMagick &#8226; View topic - Lossless JPEG2000 isn't lossless in IM</dc:creator> <pubDate>Fri, 30 May 2008 13:18:34 +0000</pubDate> <guid isPermaLink="false">http://dltj.org/2007/05/almost-lossless-jpeg2000/#comment-33360</guid> <description>&lt;!--%kramer-ref-pre%--&gt;[...] and ImageMagic looked like a good solution.Before I tried anything I came accross this info:http://dltj.org/article/lossless-jpeg2000/Quote:it would appear Jasper/ImageMagick is not using the reversible (integer) wavelet transform.I [...]&lt;!--%kramer-ref-post%--&gt;</description> <content:encoded><![CDATA[<p><img src="http://cdn.dltj.org/wp-content/plugins/kramer/kramer.gif" class="technorati-balloon" alt="Kramer auto Pingback" style="border:0;" />[...] and ImageMagic looked like a good solution.Before I tried anything I came accross this info:<a href="http://dltj.org/article/lossless-jpeg2000/Quote:it" rel="nofollow">http://dltj.org/article/lossless-jpeg2000/Quote:it</a> would appear Jasper/ImageMagick is not using the reversible (integer) wavelet transform.I [...]</p> ]]></content:encoded> </item> <item><title>By: Ron Murray</title><link>http://dltj.org/article/lossless-jpeg2000/comment-page-1/#comment-15172</link> <dc:creator>Ron Murray</dc:creator> <pubDate>Sat, 12 May 2007 21:25:04 +0000</pubDate> <guid isPermaLink="false">http://dltj.org/2007/05/almost-lossless-jpeg2000/#comment-15172</guid> <description>Now that parties in the Cultural Heritage community can verify to their satisfaction that the lossless feature of JPEG 2000 is indeed lossless, they can focus on what the image encoding results tell them.For example, large differences in file size between the uncompresssed TIFF and the lossless JPEG 2000 can be indicative of &quot;oversampling&quot; of the digital image. This can occur when the ability of the scanner to resolve actual detail in the image falls below the ability to sample the available detail with scanner driver software. While the actual content of the image strongly determines compression savings with the JPEG 2000 wavelet method, one should start getting a little suspicious when compression savings are greater than 1.5:1Note: Sampled image resolution is not identical to available image resolution. The latter is bound by the laws of Physics and hardware design, while the former is a characteristic of the driver software.Oversampling conditions can be measured using image quality target analyses like those based on the ISO 16067 standard, and have notable consequences for digitizers (and their clients, if the task is outsourced):* The image is not as resolute as it is supposed to be. * The file sizes for uncompressed delivered and/or archived formats (like TIFF) is much larger than it needs to be to support the actual quality captured.This phenomenon is not necessarily detectable if target-based methods have not been used to establish the capabilities of in-house or vendor operated scanning systems.</description> <content:encoded><![CDATA[<p>Now that parties in the Cultural Heritage community can verify to their satisfaction that the lossless feature of JPEG 2000 is indeed lossless, they can focus on what the image encoding results tell them.</p><p>For example, large differences in file size between the uncompresssed TIFF and the lossless JPEG 2000 can be indicative of &#8220;oversampling&#8221; of the digital image. This can occur when the ability of the scanner to resolve actual detail in the image falls below the ability to sample the available detail with scanner driver software. While the actual content of the image strongly determines compression savings with the JPEG 2000 wavelet method, one should start getting a little suspicious when compression savings are greater than 1.5:1</p><p>Note: Sampled image resolution is not identical to available image resolution. The latter is bound by the laws of Physics and hardware design, while the former is a characteristic of the driver software.</p><p>Oversampling conditions can be measured using image quality target analyses like those based on the ISO 16067 standard, and have notable consequences for digitizers (and their clients, if the task is outsourced):</p><p>* The image is not as resolute as it is supposed to be.<br /> * The file sizes for uncompressed delivered and/or archived formats (like TIFF) is much larger than it needs to be to support the actual quality captured.</p><p>This phenomenon is not necessarily detectable if target-based methods have not been used to establish the capabilities of in-house or vendor operated scanning systems.</p> ]]></content:encoded> </item> <item><title>By: JPEG 2000 in Archives and Libraries</title><link>http://dltj.org/article/lossless-jpeg2000/comment-page-1/#comment-14687</link> <dc:creator>JPEG 2000 in Archives and Libraries</dc:creator> <pubDate>Fri, 04 May 2007 17:02:04 +0000</pubDate> <guid isPermaLink="false">http://dltj.org/2007/05/almost-lossless-jpeg2000/#comment-14687</guid> <description>&lt;!--%kramer-pre%--&gt; Truly Lossless JPEG2000 Compression — Except for Grayscale? GeoJPEG2000 and JPEG2000 Info, by Greg Coats JPSEC: Security for JPEG-2000 images JPEG 2000: Good Things in Smaller Packages - Geospatial Solutions &lt;!--%kramer-post%--&gt;</description> <content:encoded><![CDATA[<p><a class="technorati-balloon" href="http://www.technorati.com/cosmos/search.html?url=http://dltj.org/article/lossless-jpeg2000/"><img src="http://static.technorati.com/images/bubble_h17.gif" class="technorati-balloon" alt="links from Technorati" style="border:0;" /></a> Truly Lossless JPEG2000 Compression — Except for Grayscale? GeoJPEG2000 and JPEG2000 Info, by Greg Coats JPSEC: Security for JPEG-2000 images JPEG 2000: Good Things in Smaller Packages &#8211; Geospatial Solutions</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Served from: dltj.org @ 2012-05-23 14:58:35 by W3 Total Cache -->
