Legacy ImageMagick Discussions Archive

convert input1.jpg -sigmoidal-contrast 3x45% output1.jpg
convert input2.jpg -sigmoidal-contrast 3x45% output2.jpg

Can I claim $250? Or is this a scam?

To avoid problems like this, I use the "caption:@file.txt" style.

See, for example, http://en.linuxreviews.org/Defunct_process

I don't think IM will ever create a chequer backgound, unless you ask it to. Perhaps your image viewer is showing that for transparency.

Please post your EPS file and exact command you are using.

I understand that 100% means the images are identical. But I don't know what you want 50% or 0% to mean.

The command above will return zero when the images are identical.

It will overwrite old images. It creates imagename-0 etc when you don't fully specify "crop" or whatever.

Show us the exact command you are using.

See the documentation on "compare", eg will return a numerical measure of the difference between the two frames. Higher numbers are more different.

Can you define exactly what you mean by "percentage of similarity"?

I suppose you have tried the obvious basic tests:

Have you tried:

\( picture.jpg'[600x450]' -geometry +116+76 -modulate 120 \) -composite

?

In Windows 7, but it should work in XP:
Then you can use %ww% and %hh% for width and height.

That is "Notepad++", which is a different program. There are lots of workarounds. For this purpose, I use a program that strips out any BOMs from a file. But it is annoying; the correct behaviour for IM, I feel, is to act like any text editor and not to display the "?" glyph or a...

Windows 7, IM 6.5.8-8: convert -size 1920x1080 -gravity South ^ -background None ^ -fill blue ^ -font Verdana -pointsize 100 ^ caption:@captCopy.txt ^ captCopy.png captcopy.txt is encoded in UTF-8: {ef}{bb}{bf}Copyright {c2}{a9} 2010 Alan Gibson\r\n Where {ef} is the single byte, represented in hex ...

You are missing +0+0 on the crop.

Rule of thumb: geometry (axb+c+d) with no offsets always needs "+0+0".

I dumped them using a filter called DumpBin that converts nonprintable characters to hex. Then I counted the characters until I reached FF D8 FF, which is hex for the octal "\377\330\377", which IM expects to be at the start. You might find other files have a different number of spurious b...

The extra output files will be because your shave or splice or both will need zero offsets: "+0+0". If you post your original file, we can test with what you've got, so our advice may be more precise.

Also, let us know what IM version you are using.