Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.

Changes between Version 4 and Version 7 of Ticket #5092


Ignore:
Timestamp:
05/12/11 03:31:58 (13 years ago)
Author:
mlinkert
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5092

    • Property Cc smithd@… added
    • Property Remaining Time changed from 1 to 5
    • Property Summary changed from Update tile-based JPEG decoder to handle images that are too large to Support .ndpi files with width or height > 65500
    • Property Milestone changed from OMERO-Beta4.3 to Unscheduled
    • Property Sprint changed from 2011-05-19 (12) to
  • Ticket #5092 – Description

    v4 v7  
    1 Many .ndpi files contain JPEG streams that have a width and/or height larger than 65535 (the maximum size allowed in a JPEG stream).  For images where (width * height) <= (65535 * 65535), we can solve the problem by setting an artificial width and height, then re-pack the tiles with the correct dimensions after they have been decoded. 
     1Many .ndpi files contain JPEG streams that have a width and/or height larger than 65500 (the maximum size supported by Java's JPEG decoder.  The maximum size allowed in the JPEG specification is 65535, and it is not uncommon to have .ndpi files that contain much larger images. 
    22 
    3 For images with (width * height) > (65535 * 65535), though, we need a different strategy. 
     3After some investigation, it looks like Hamamatsu has written their very own JPEG encoder/decoder to work around the limitations in the JPEG specification, as no other decoder that I can find actually supports this. 
     4A lot of investigation has already gone into this ticket, and given the scope of work required I don't see it happening for 4.3. 
     5 
     6When we finally do have time to sort this out, the plan is roughly: 
     7 
     81) See if there is a way to strip off the dimension information and just read all of the tiles using Java's built-in JPEG support.  We can then re-pack the tiles using the dimension information stored in the .ndpi file. 
     9 
     102) Failing (1), see if we can write our own Java interface to the JPEG native libraries included with the JRE that would accomplish the same thing as (1). 
     11 
     123) If neither (1) nor (2) work, we'll need to write our own baseline JPEG decoder that allows the image dimensions to be overridden. 

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.14381 sec.)

We're Hiring!