Return-Path: <tiff-bounces@lists.maptools.org>
Received: from mailgate102.isp.belgacom.be (mailgate102.isp.belgacom.be [195.238.6.83])
        by inmx019.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-2.32) with ESMTP id l3O26EDw015960
        for <joris.at.lebbeke@skynet.be>; Tue, 24 Apr 2007 04:06:33 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from r153.dmsolutions.ca (HELO duke.maptools.org) ([209.217.116.153])
  by in.mx.skynet.be with ESMTP; 24 Apr 2007 04:06:32 +0200
Received: from duke.maptools.org (duke.maptools.org [127.0.0.1])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id l3O1tFHC015268;
	Mon, 23 Apr 2007 21:56:18 -0400
Received: from adi25.advdata.com.au (mail.avand.com.au [210.18.214.26])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id l3O1t9MB015261
	for <tiff@lists.maptools.org>; Mon, 23 Apr 2007 21:55:12 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: [Tiff] O-JPEG problems
Date: Tue, 24 Apr 2007 11:55:04 +1000
Message-ID: <8D9A26DA9EA4C844A93E308798D74E8F02241A70@adi25.advdata.com.au>
In-Reply-To: <001401c77ca8$27293370$0201a8c0@AWareCore2Duo>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tiff] O-JPEG problems
Thread-Index: Acd8qDAY21aFanD8R7azy2ixjE1LFAJaV2yA
References: <8D9A26DA9EA4C844A93E308798D74E8F020F87B7@adi25.advdata.com.au>
	<001401c77ca8$27293370$0201a8c0@AWareCore2Duo>
From: "Mick O'Neill" <mick.oneill@avand.com.au>
To: "Joris" <joris.at.lebbeke@skynet.be>,
        "TIFF mailing list" <tiff@lists.maptools.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by duke.maptools.org id
	l3O1t9MB015261
Cc: 
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=subscribe>
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org
X-UIDL: 000000000023ceae.00002310
X-MSP-STORE: Tue, 24 Apr 2007 04:06:43 +0200
Status:   

I have built this new library, and it does work better than the old.
However, it still could not render all of the pages in that TestBig
file. It looks like it dows, but pages 2-11 come out as plain black
backgrounds. The error being reported is "Improper call to JPEG library
in state 0. `LibJpeg'. 

There were a couple of minor compile problems in tiff_dirinfo.c that
were easily fixed. An if statement was placed before the other variable
declarations in  TIFFFindFieldInfo and TIFFFindFieldInfoByName (legal in
C++, but not in C).

I have left the TestBig.tif file in http://midimick.com/temp , and have
also included the rendered jpeg files in the same folder. If you have
anu ideas, they would be much appreciated. The TIFF file is viewable in
the free "Brava" reader, so the image data is there and intact...its
just a matter of getting to it.

Thanks for any assistance.


Mick O'Neill


> -----Original Message-----
> From: Joris [mailto:joris.at.lebbeke@skynet.be] 
> Sent: Thursday, 12 April 2007 12:13 PM
> To: Mick O'Neill; TIFF mailing list
> Subject: Re: [Tiff] O-JPEG problems
> 
> Mick,
> 
> Mick O'Neill wrote:
> > I have encountered a number of TIFF files that have images in the 
> > OJPEG format (type 6), but do not contain the JPEGInterchangeFormat 
> > Tag. When this problem was first recognised (about 18 
> months ago), I 
> > was able to put the following modification into the 
> OJepgSetupDecode 
> > function to allow for it:
> 
> You've found one of the problems of the old OJPEG decoder, 
> but unfortunately this problem was far from the only one. 
> There were many other types of OJPEG this decoder didn't 
> like, and on some it actually crashed access violation style, 
> so can't actually safely recommend it which is why it was 
> disabled by default.
> 
> This is why we've replaced it with a totally new one, build 
> from scratch, that is far more robust, and supports very 
> nearly all OJPEG images out there, including many types 
> without JPEGInterchangeFormat tag. We feel more confident 
> with this new OJPEG codec, which is why this one is enabled 
> by default. We did this new OJPEG after the release of the 
> latest stable version, so if you need it you need to get a 
> hold of a CVS copy. In order to do that, see the instructions 
> on LibTiff homepage (http://www.remotesensing.org/libtiff/). 
> Make sure you check out the stable branch-3-9, not CVS head 
> that is a currently unstable BigTIFF upgrade in progress.
> 
> Unfortunately, we cannot actually do any bug hunting and 
> patching of the previous unstable OJPEG decoder. It would be 
> mission impossible given its inadequate design, and waste of 
> time seeing the new one is there to replace it. I did test 
> your TestBig.tif file with the new OJPEG decoder, though, and 
> all 14 IFDs decode fine.
> 
> Best regards,
> 
> Joris Van Damme
> info@awaresystems.be
> http://www.awaresystems.be/
> Download your free TIFF tag viewer for windows here:
> http://www.awaresystems.be/imaging/tiff/astifftagviewer.html
> 
> 

_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
