Yes. That was the result I got, and it is because of the bug. The command is correct.
If you use -level 0,100% the operation should be a no-op but instead my tests should it is comming out negated. It did not do this before.
From previous examples of this -level in IMv6 is being actually being applied to alpha values (0=transparent, 1=opaque). The forumla given is ths correct. That is expanding 50% transparency at the edges (from the alpha channel blur) to full transparency while leaving 100% opaque parts 100% opaque, but that is not what is happening due to the bug.
The above example, IS correct, (works with IMv7 alpha test build too)
I'll go in and have a look at IMv6 -level tonight, and see if I can figure out where it is being negated.
Yeap found the fault, Also found that it was using matte values for 'palette' images, fixing that too.
It is now fixed next release, or an SVN IMv6 build.
Code: Select all
convert rose: -alpha set -background None -virtual-pixel VerticalTile \
-channel A -blur 0x8 -level 50%,100% +channel soft_sides.png
Note that the gradient is a blur feathering, as such the curve is more of a sigmiodal curve falling quite sharply to zero at the edges. A -sigmoidal contrast can make it less sharp.
Better still look at the other link, which adds a linear gradient...
http://www.imagemagick.org/Usage/photos/#overlap
Or apply the distance gradient feather to this virtual pixel method.
http://www.imagemagick.org/Usage/thumbnails/#soft_edges
Either will avoid ths bug, and also work just as well.
The trick is the 'virtual-pixel' setting that use used to give the image transparent sides, while keeping top and bottom fully-opaque.