>>
>>
>[snip]
>> Has anyone else found this? Is it a B&W G3, extension conflict or MacOS 8.5
>> problem?
>
>This brings to mind a problem that Alain and I have encountered, of a
>feature 'disappearing'.
>
>As most folks know, Alain distributes FB here in France, which means doing
>tech support...
>
>So, a user bought the Staz's RdWrUtilities and the Image ones. And now says
>that he can no longer access LZW compression with the filter. I was at
>Alain's place when the mail arrived, so we launched FB, dug out the filters,
>ploughed over the commands, and sure enough, whether we saved a TIFF file
>with or without LZW, the file was identical in size. Thinking that we must
>be at fault we grabbed FuturePaint and did the same from there. Identical in
>size (down to the same number of bytes) with or without LZW compression.
>We believed that LZW was available in the Code that the installer placed in
>the app, but now we're wondering if it was in a version of QuickTime.
>
>We're using French System 8.5, QuickTime 3 (pro) installed.
>
>Has anyone else come up against this?
>
>jonathan
>PS. We also tried with CCITT, and Packbits compression. Niet.


I've never been able to use the TIFF filter with compression too.
I don't think that the TIFF filter uses QuickTime.
QuickTime doesn't contain an encoder for LZW-based graphics,
only a decoder. This way, they don't have to pay UNISYS.
(I'm not 100% sure, only 99.99999%)

Also, with the PICT filter, when i choose a codec, it is offset by 1 !!!
I mean, if the codec-lister routine tells me that the animation codec's
ID is 3, i have to use 4. And i get different results with different
versions of QuickTime.

The Gif filter gives me gibberish 10% of the time, and
it crashes often when trying to just read other application's Gif files.
(yes, Gif87a)

Yep, it's cheap, but it's totally unreliable.
I have all the filters (180$), and i would not recommend it
to anyone. Too bad, i could have used this money for something
else.

Sylvain