Legacy ImageMagick Discussions Archive

Thanks.

I am using a Q64 version of ImageMagick, and am trying to work with an image at 16-bit instead of 64-bit depth. At 64-bit depth, the pixel values span the 64-bit range (0 to 1.84E19); however, if I use `-depth 16` with the intention of rescaling the pixel values to the 16-bit range (0-65,535), I ...

Thanks, I tried the command you posted and read the pointers. I still fail to obtain output, but I will try on my linux machine when I get the chance. Temporary files with the names plot_1_17538.mpc and plot_1_17538.cache (or similar) are created in the working directory while the program is running ...

I wanted the log of the counts (ordinate). My apologies for omitting my system information: I am using 6.9.7-4 Q16 x86_64 on debian and 7.0.7-1 Q16 x86_64 2017-09-15 on macos, both running bash version 4. I found and tried your plot script on the latter system (which has gnuplot 5.2), but obtained ...

I am viewing histograms of grayscale images by means of the following command magick "$file" -define histogram:unique-colors=false histogram:miff:- | display - Are there any ImageMagick commands/options to log-scale the counts/frequencies? I would be OK with adding 1 or some other small value to ...

I can confirm that the patch worked. Thanks again!

Yes, it's a 64-bit tiff, so the majority of image viewers fail to open it. The resolution is 65 nm/px, expressed as cm^-1 (TiffTag RESUNIT_CENTIMETER = 3, https://www.awaresystems.be/imaging/tiff/tifftags/resolutionunit.html ). The resolution shouldn't matter to an image viewer. I'm not sure about ...

That was very fast, thanks!

Conversion to miff fails on some images, such as this one: https://ufile.io/2v40w This works fine: convert a.tif -depth 8 -colorspace gray PNG:- | display - whereas this fails: convert a.tif -depth 8 -colorspace gray miff:- | display - The error is: display-im6.q16: unexpected end-of-file `/tmp ...

Thanks, I'll keep pfm and mpc in mind for future work with floating point data.

Oh, it actually must be a bug with `miff:` since `-depth 8 PNG8:` works just fine.

I see, maxima/minima works for both (+/- fx) while the non-fx version also accepts the abbreviated forms. Supposing that I have done some manipulation on the image myself, is it possible to reduce the bit depth afterwards without altering the image? For instance magick a.tif -fx "(u-0.1)/0.9" -level ...

Hmm, I wonder why it is read as 16-bit. It began as a double-precision matrix in matlab (originally acquired with a 16-bit ADC but then convolved with a Gaussian, making it no longer 16-bit) and I saved it using that software's libtiff API with the BitsPerSample tag set to 64). Could it be because ...

Here is an example image: http://s000.tinyupload.com/index.php?file_id=38010744925170768467 Unzip to recover the 64-bit tiff. I am using mac osx and debian v9. I could not get `identify -verbose` to output a histogram (just the summary statistics). Your `auto-level` command seems to do the job ...

I have some 64-bit IEEEFP tiff files. I can convert them to 8-bit unsigned integer (0-255) tiffs using Matlab, but I cannot seem to accomplish it using ImageMagick. $ identify <file> TIFF 144x149 144x149+0+0 64-bit Grayscale Gray 173050B 0.000u 0:00.000 $ magick <file> -depth 8 miff:- | identify ...