AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
September 2008

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



Valid HTML 4.01!



Thread

2008.09.27 16:32 "Compression code 34719", by Comsquare Martin Osieka
2008.09.27 17:30 "Re: Compression code 34719", by Toby Thain
2008.09.28 07:05 "Re: Compression code 34719", by Comsquare Martin Osieka
2008.09.28 12:17 "Re: Compression code 34719", by Gene Amtower
2008.09.30 18:03 "Re: Compression code 34719 (MDI Tiffs)", by Comsquare Martin Osieka
2008.09.30 19:04 "Re[2]: [Tiff] Compression code 34719 (MDI Tiffs)", by Igor Skochinsky
2008.09.30 23:34 "Re[2]: [Tiff] Compression code 34719 (MDI Tiffs)", by Bob Friesenhahn
2008.10.05 10:14 "Re: Compression code 34719 (MDI Tiffs)", by Brad Hards
2008.10.05 20:47 "Re: Compression code 34719 (MDI Tiffs)", by Comsquare Martin Osieka
2008.10.06 16:09 "Re: [SPAM] Re: [Tiff] Compression code 34719 (MDI Tiffs)", by Edward Lam
2008.10.06 16:31 "Re: [SPAM] Re: [Tiff] Compression code 34719 (MDI Tiffs)", by Bob Friesenhahn
2008.10.06 20:45 "Re: [SPAM] Re: [Tiff] Compression code 34719 (MDI Tiffs)", by Brad Hards
2008.10.08 03:20 "Re: Compression code 34719 (MDI Tiffs)", by Edward Lam
2008.10.08 13:29 "Re: Compression code 34719 (MDI Tiffs)", by Edward Lam
2008.10.08 21:47 "Re: Compression code 34719 (MDI Tiffs)", by Comsquare Martin Osieka
2008.10.07 04:59 "Re: [SPAM] Re: [Tiff] Compression code 34719 (MDI Tiffs)", by Comsquare Martin Osieka

2008.09.27 17:30 "Re: Compression code 34719", by Toby Thain

On 27-Sep-08, at 12:32 PM, ComSquare Martin Osieka wrote:

> Does anybody know what the compression code 34719 in the  
> compression tag stands for?
>
>
> These are tifs generated from a MS tool. Everything else in the tif  
> looks fine (RGB, 8bits per channel,…).
> But for sure the resulting image shows completely black because of  
> the missing decoder in libtiff.
>
> MS is able to open and view these tiffs.
>

And that's the whole point. An un-interoperable (non standard) codec  
*ensures* lock-in to their tools. Good luck finding documentation.

--Toby

>
>
> There is only one strip in the file and it starts with
>
>
>
> 0x02,0x00,0x00,0x00,0x7B, 
> 0x00,0x00,0x00,0x08,0x33,0x00,0x00,0x03,0x00,0x00,0x00,
>
> 0x00,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF, 
> 0x00,0x00,0x00,0x00,0x78,0x01,0xED,0x9B,
>
> 0x5B,0x88,0x55,0x55,0x18,0xC7,0xBF,0xD9,0x67,0x8E, 
> 0x33,0xA6,0x96,0x86,0xA5,0x65,
>
> 0xD9,0x9E,0x83,0x9A, 
> 0x43,0x12,0x13,0x47,0xA1,0x87,0x22,0xA5,0x53,0x54,0x2A,0x1C,
>
>
> Martin
>
>
>
> _______________________________________________
> Tiff mailing list: Tiff@lists.maptools.org
> http://lists.maptools.org/mailman/listinfo/tiff
> http://www.remotesensing.org/libtiff/