Legacy ImageMagick Discussions Archive

45/1, 5946/100, 0/1,8/1, 5697/100, 0/1<--------------------------- ???? The right order is DMS(d + m/60 + s/3600) and not DSM Why do you say that this is in DSM order? It isn't. IM simply prints the text that is in the EXIF GPS tag: 45/1, 5946/100, 0/1,8/1, 5697/100, 0/1n 5946/100 minutes is 59.46 ...

OK. Now I'm with you. The "magick" command line program in my IM install is not HDRI enabled but I've just checked the MagickWand code (from the same package) and it has MAGICKCORE_HDRI_ENABLE defined so the command line and the program aren't exactly the same.

Pete

Version: ImageMagick 7.0.5-5 Q16 x64 2017-04-25 http://www.imagemagick.org Copyright: Copyright (C) 1999-2015 ImageMagick Studio LLC License: http://www.imagemagick.org/script/license.php Visual C++: 180040629 Features: Cipher DPC Modules OpenMP Delegates (built-in): bzlib cairo flif freetype jng ...

Hi snibgo:
I just tried "QuantumRange*50./100" and "QuantumRange*0.5" and they don't change the output.
I'm using ImageMagick 7.0.5-5 Q16 x64
I did output intermediate images but I only eyeballed them. I'll let IM compare them to see if there are any differences.

Thanks
Pete

Thanks for posting your code. It produces the same output for the logo: image as my code does and they don't agree with the command line output. This command line: convert one.jpg -scale '50x50!' -depth 8 \ '(' -clone 0 -colorspace HSB -channel gb -separate +channel -threshold 50% -compose multiply ...

It works for me with ImageMagick 7.0.5-5 Q16 x64.

Pete

Could you post the code which does the first convert command? I'm using the logo: image as input and my code produces two extra colours in the output, all the other are identical to the output from the convert command.

Pete

Thanks.
I was dividing the pixel colours by 256 instead of QuantumRange. I'm using a Q16 IM so 256 doesn't work too well.
Now to figure out why I get 6 colours but they aren't the right ones.

Pete

@rpatelob
Would you mind showing your code? I've almost got that working except for the last step.

Pete

I searched for "AcquireKernelInfo" in the source code. Then look in the results for a line beginning with a percent sign like this: % AcquireKernelInfo() takes the given string (generally supplied by the That's the beginning of the comment about the function before the actual code. Then below that ...

In Anthony's grayscale examples, the link in this line:

This is an identical result to using "-fill DodgerBlue -colorize 100%" to Colorize Images (see below).

doesn't work (The requested URL was not found on this server.)

Pete

I'd suggest you first try modifying one of your images using the IM command line. Anthony has several sections about this kind of operation. For example, see the four subsections which start with Sepia Tone and then the whole section here: Recoloring Images with Lookup Tables Try those methods and ...

Looks like this has swapped the red and blue: void test_wand(void) { MagickWand * m_wand; KernelInfo *ki; ExceptionInfo *ei; m_wand = NewMagickWand(); MagickReadImage(m_wand,"rose:"); ki = AcquireKernelInfo("3x3:0, 0, 1, 0, 1, 0, 1, 0, 0",ei); MagickColorMatrixImage(m_wand, ki); MagickWriteImage(m ...

I, obviously, hadn't used HSL before. Hue is specified in degrees (thus the /360.0) and Saturation and Lightness are fractions from zero to one (often specified as a percentage).

Pete

The arguments to PixelSetHSL are double floating point fractions of QuantumRange. Note that the first one has to be cast to double (or written as 120.0) so that the division isn't done as integers which would result in zero.

Pete