Legacy ImageMagick Discussions Archive

Hello,

I know it's an old post but still worth asking.

Have you ever managed to get Cutout result like in Photoshop ?

Thanks

Hello fmw42, Yes, I'm aware of the way -fx operator works and that's why I think it would be easier for IM developers to extend evaluate or function operators or even create a new one that would perform basic mathematical operations like floor, trunc, abs, mod etc. without having to parse ...

Well, I actually think that's just "-evaluate" (and some other operators) that rounds up results to the nearest integer after the operation otherwise it would be silly trying to guess what value should be pixel channel divided or multipled by to get an integer result and for example -fx works with ...

It must be a bug in my version then convert -version Version: ImageMagick 6.7.7-2 2012-07-07 Q16 http://www.imagemagick.org convert -depth 16 image.jpg[1x1+0+0] txt: # ImageMagick pixel enumeration: 1,1,65535,srgb 0,0: (29812,27242, 8738) #74746A6A2222 srgb(116,106,34) I'm pretty sure that by ...

Hello fmw42, Yes, I did all that - the problem is that there doesn't seem to be an easy and fast way of flooring pixel values in IM without using -fx. It would be good if -evaluate offered more operations like those available with -fx e.g. ceil, floor, int, abs etc. [EDIT] BTW 've just found out ...

Hello, The solution to my question is: -evaluate divide 64 -fx "trunc(p*255)/255" -evaluate multiply 85.333 All this command does is 4th level posterization. The only problem with it is -fx (to floor the values) which is slow. The reason why I'm not using the built-in "-posterize" is purely the ...

Hello, I think there is a bug when performing evaluate on certain values. My original pixel values are: 0,0: (29812,27242, 8738) #74746A6A2222 srgb(116,106,34) Now: -evaluate divide 64 -evaluate subtract 124 gives: 0,0: ( 257, 257, 0) #010101010000 srgb(1,1,0) which is correct if I subtract 125 then ...

OK,

I'm certainly missing something here as :
on RGB(116,106,34) gives RGB(128, 129, 63)

????

Hello, At first I thought it would be a trivial task but after spending two evenings trying i give up and hope somebody can help. I want to apply 3 simple operations to each pixel i.e.: 1. divide each channel value by a floating number 2. floor the result 3. multiply by a floating number In 8 bit ...

Hello,

Unfortunately I've tried various methods with different results which were nowhere near the result I get with PS. The following:
seems to help in getting closer to PS result though the colors just don't match up.

Hello,

I know it's an old post however I'd be curious to know if anybody has any ideas how the PS cutout filter could be done in IM ? Thanks

See my post above as I solved the monochromatic noise issue. I've seen somewhere in the Docs here example of transforming one image based on another where the second image was a straight line - I think it was sine + line - can't find it !!! I am not sure how this relates to noise? But perhaps you ...

and I thought that that might be the way to go so could you please tell me how this could be implemented? I understand that the line length would then work as radius in the example above. Note sure if this would be radius 2 filt="\ 1 0 0 0 0 \ 0 1 0 0 0 \ 0 0 1 0 0 \ 0 0 0 1 0 \ 0 0 0 0 1 " or (one ...

I don't think there is an easy answer that I know to convert from your intensity in percent to the -attenuate factor. It depends upon what strength of the noise is internally generated within IM. If anyone knows more, I would like to hear. The reason was that I had assumed in my last example with ...

fits perfectly my purpose - the only thing is that when using 0 - 400 (intensity range) with gaussian type XX needs to be divided by 10. Also to make results closer to PS I add 0.2 * Intensity to Intensity What do you mean by 0-400 intensity range? What intensity -- of the image? Please clarify. By ...