Hi
When try to identify SVS file I get "identify: compression not supported" message.
./magick identify 3931.svs
identify: compression not supported `3931.svs' @ error/tiff.c/ReadTIFFImage/1543.
SVS is just a multipage TIFF, GIMP can open them, IM should be able to open them too. Is there any ...
Search found 7 matches
- 2019-07-05T04:44:50-07:00
- Forum: Users
- Topic: SVS: compression not supported
- Replies: 1
- Views: 7549
- 2017-07-11T05:26:21-07:00
- Forum: Bugs
- Topic: TIFF64 is not supported ANYMORE
- Replies: 1
- Views: 6097
Re: TIFF64 is not supported ANYMORE
But portable version works!
C:\Users\xxx\ImageMagick-7.0.6-0-portable-Q16-x64>identify.exe X:\xxx\s1.tif
X:\xxx\s1.tif TIFF64 57856x72578 57856x72578+0
+0 8-bit sRGB 7.79679GiB 0.000u 0:00.014
Something wrong with the magick command?
C:\Users\xxx\ImageMagick-7.0.6-0-portable-Q16-x64>identify.exe X:\xxx\s1.tif
X:\xxx\s1.tif TIFF64 57856x72578 57856x72578+0
+0 8-bit sRGB 7.79679GiB 0.000u 0:00.014
Something wrong with the magick command?
- 2017-07-11T05:16:55-07:00
- Forum: Bugs
- Topic: TIFF64 is not supported ANYMORE
- Replies: 1
- Views: 6097
TIFF64 is not supported ANYMORE
Hi
Version ImageMagick-7.0.3-Q16 can't read BigTIFF TIFF64 anymore - but version 6 could!
C:\Program Files\ImageMagick-7.0.3-Q16>magick.exe identify -verbose X:\s1.tif
identify: Can not read TIFF directory count. `TIFFFetchDirectory' @ error/tiff.c
/TIFFErrors/565.
identify: Failed to read ...
Version ImageMagick-7.0.3-Q16 can't read BigTIFF TIFF64 anymore - but version 6 could!
C:\Program Files\ImageMagick-7.0.3-Q16>magick.exe identify -verbose X:\s1.tif
identify: Can not read TIFF directory count. `TIFFFetchDirectory' @ error/tiff.c
/TIFFErrors/565.
identify: Failed to read ...
- 2013-12-11T14:17:30-07:00
- Forum: Users
- Topic: command to determine current configuration
- Replies: 1
- Views: 3832
command to determine current configuration
Is there a command to printout the current disk cache path, memory limits etc?
- 2013-12-11T14:14:38-07:00
- Forum: Users
- Topic: -limit memory: no RAM used
- Replies: 4
- Views: 6906
Re: -limit memory: no RAM used
Does this mean that if IM asks for 12G but say only 8G is available it just ignores the available memory and does everything on disk?
- 2013-12-11T12:17:24-07:00
- Forum: Users
- Topic: -limit memory: no RAM used
- Replies: 4
- Views: 6906
-limit memory: no RAM used
Hi
I have this command:
convert -verbose -define tiff:tile-geometry=256x256 -limit memory 12GB source.png -type TrueColor -compress lzw output.tif
If I run it it works very slow, it creates a huge temp file but no memory is used. Do I misunderstand "-limit memory" somehow?
The source file is ...
I have this command:
convert -verbose -define tiff:tile-geometry=256x256 -limit memory 12GB source.png -type TrueColor -compress lzw output.tif
If I run it it works very slow, it creates a huge temp file but no memory is used. Do I misunderstand "-limit memory" somehow?
The source file is ...
- 2013-12-05T15:53:54-07:00
- Forum: Users
- Topic: wildcards: Invalid argument @ error/blob.c/OpenBlob/2643
- Replies: 1
- Views: 11940
wildcards: Invalid argument @ error/blob.c/OpenBlob/2643
Hi
This works:
convert -verbose C:\source_folder\*.png C:\output_folder\*.tif
But this one gives me convert.exe: unable to open image `C:\output_folder\*.tif': Invalid argument @ error/blob.c/OpenBlob/2643.
convert -verbose C:\source_folder\*.png -set colorspace RGB -compress lzw C:\output_folder ...
This works:
convert -verbose C:\source_folder\*.png C:\output_folder\*.tif
But this one gives me convert.exe: unable to open image `C:\output_folder\*.tif': Invalid argument @ error/blob.c/OpenBlob/2643.
convert -verbose C:\source_folder\*.png -set colorspace RGB -compress lzw C:\output_folder ...