This posting used to have the tag “– Except for Grayscale?” appended to the end of the title. That is no longer needed; see the bottom of the post for an explanation. We have been implementing University of Michigan’s DLXS software, and DLXS uses JPEG2000 for its image masters. We have been investigating reports of perceived changes in images in the conversion from our old media server to DLXS, and along the way I discovered an important fact: the default parameters for two popular JPEG2000 codecs results in an irreversible transformation. Here is how to address that.
The discussion has died down on Jack Nack’s blog posting about the future of JPEG2000 support in Photoshop. Since I last updated my own commentary on the issue, there have been a few more comments, including one by Erich Kesse from the University of Florida. Jack has added a few follow-ups to comments left on his blog, including this one at the bottom of Erich’s comment:
[Thanks for the detailed feedback. I would note that regardless of what Adobe does with JPEG 2000, other developers can create JPEG 2000 reading/writing plug-ins for the app. –J.]
OhioLINK is not participating in the Google Summer of Code this year (too many other things going on for our staff to be effective mentors), which is why it is refreshing to see work on the wider adoption of JPEG2000 — one of our core goals — continue on other fronts. Among this year’s are two that involve J2K. All of this is welcome news, coming in the same month that Adobe is questioning the need for JPEG2000 support in Photoshop. My public gratitude goes out to Google for their third year of offering financial and logistical support to their Summer of Code program.
John Nack, Senior Product Manager for Adobe Photoshop, posted a query recently to his blog seeking customer reactions to the possibility of removing JPEG2000 support from Photoshop:
Adobe developed the plug-in in anticipation of cameras entering the market with native JPEG 2000 support on board. The thing is, that hasn’t happened, nor have we seen other widespread adoption of the format in places we know Photoshop is being used. […] As we plan for the future, we need to retire features that no longer make sense & focus instead on capabilities that matter. So, do you use JPEG 2000? If so, please give a shout and let us know how & why you use it.
Last month was an interesting month for discussion and news of JPEG2000 as an archival format. First, there was a series of posts on the IMAGELIB about the rational for using JPEG2000 for master files. It started with a posting by Tom Blake of Boston Public Library asking these questions:
What can I do with a JPEG200 that I can’t do with a TIFF, a good version
of Zoomify, and a well-designded DAMS?
Don’t you need to rely on a proprietary version/flavor of JPEG2000 and a
viewer to utilize its full potential?
OhioLINK was excited and privileged to participate in the second annual Google Summer of Code — a program to inspire young developers and provide students in Computer Science and related fields the opportunity to do work related to their academic pursuits during the summer, and to support existing open source projects and organizations. This is the first of three posts summarizing the efforts of three students; this one details the work of Juan Pablo Garcia Ortiz, a Ph.D. candidate at the University of Almeria in Spain, to build a JPEG2000 JPIP Streaming Server and Client Browser Viewer Applet. This is an edited version of his final report.
Attending: M. Anderson, U of Iowa; A. Laas, LexisNexis; Y. Han, U of Arizona; P. Howell, Western Michigan University; Y. Kaganovia, Princeton U; P. Murray, OhioLINK; K. Thompson, Smithsonian Libraries
Participants talked about their interest in JPEG2000 and their institution’s use of the standard: Western Michgan University is digitizing manuscripts and other special collections materials and using JPEG2000 for access; LexisNexis is using JPEG2000 in the maps portion of the U.S. Serials Set digitization program; the Smithsonian Libraries has started converting archival TIFFs to JPEG2000 and is considering use of the standard in the Biodiversity Heritage Library project (including a capability to cross-link taxonomic names in digitized text to oneline databases).
OhioLINK is pleased to mentor three students working on projects for Ohio’s higher education and libraries around the world during the Google Summer of Code 2006. The three projects are:
- JPIP Browser Applet and Streaming Server