[GEM-dev] TIFF files from pix_buffer (and others?) missing some "standard" tags?
B. Bogart
ben at ekran.org
Wed Nov 5 18:41:04 CET 2008
Hi Johannes,
Same reason as Cyrille,
I did a quick compile at some point, imagemagick caused a segfault, and
so I turned it off and have not turned it back on.
I'll give that a try and and report the bug if it still exists.
I hope it will also fix the Y-flip issue I have with pix_buffer_save.
I'll need to save lots of copies of the same image into a pix_buffer.
Obviously copying from mem will be much faster than copying from disk.
How about a pix_buffer message to copy from one slot to another?
Then I could load a black image into all slot with something like:
open black.tif 0
copy 0 1
copy 1 2
.
.
.
B. Bogart
IOhannes m zmoelnig wrote:
> hi
>
> B. Bogart wrote:
>> Hey all,
>>
>> I've had trouble loading some TIFs generated in pd/Gem in PIL (python
>> imaging). I asked on the list and it seems PIL expects some particular
>> TIF tags being set in order to recognize the image.
>
> ok, i have fixed this now.
>
>>
>> I think it can only be an improvement to add these tags so that tifs
>> generated in pd/Gem can be loaded by as many applications as possible.
>>
>> The attachment contains the specific tags.
>>
>
> nevertheless: Gem tries to default to use imagemagick for
> reading/writing images (on lin and win).
> imagemagick does produce correct files (with all tifftags set).
> the missing tifftags only occured (though this is know fixed) when using
> the fallback libtiff library.
> is there any reason why you are not using imagemagick?
>
> mfg.ui.,xdf
> IOhannes
>
More information about the GEM-dev
mailing list