Jasper JP2 reads as black for some JP2 images

[kyngchaos]

(I thought I submitted a bug a while back, but I must have spaced out, sorry)

Some JP2 images read/convert as all black, using the Jasper JP2 driver. It may be a problem reading some optimizations from other JP2 writers? The RGB example I got from Greg Coats was made with the Kakadu tools outside of GDAL. The GDAL MrSID and Kakadu drivers read the image correctly (my ECW driver is currently broken, so I couldn't try that).

I tried applying the patch from r13715 in trunk but there was no change.

[Even Rouault]

But what's interesting is that :

jasper --input rgbwcmyk03.jp2 --output test.bmp --output-format bmp

generates a test.bmp which looks good ! So it seems it's a bug in the Jasper driver, but not in libjasper itself

[Even Rouault]

10953

[warmerdam]

Adding Andrey to cc: as he is the primary maintainer of the JPEG2000 (JasPer) driver.

[Even Rouault]

Fixed in trunk in r16036, in branches/1.6 in r16037 and in branches/1.5 in r16038

[Coatman]

Thanks for your quick response, and for changing GDAL's Jasper-based JPEG2000 processing in 1.6/gdal/frmts/jpeg2000/jpeg2000dataset.cpp so that it now properly processes JP2 images whose dimensions are not a multiple of 256.

At ​http://download.osgeo.org/gdal/ the most recent version of gdal-1.6.0.tar.gz is dated 04-Dec-2008. I am unfamiliar with the GDAL source code update procedure. Approximately when would the updated jpeg2000dataset.cpp be included in downloadable GDAL source code available at ​http://download.osgeo.org/gdal/ ? Perhaps ​http://download.osgeo.org/gdal/ is usually updated monthly?

[warmerdam]

Nightly snapshots appear at ​http://download.osgeo.org/gdal/daily. The "stable" series is 1.6 branch, and the trunk series is the development trunk. We don't produce nightly snapshots of 1.5 anymore.

I anticipate a 1.5.4 release will be produced within a few weeks. It is hard to predict when 1.6.1 will be produced. Likely by the end of February or so.