Post any defects you find in the released or beta versions of the ImageMagick software here. Include the ImageMagick version, OS, and any command-line required to reproduce the problem. Got a patch for a bug? Post it here.
Something serious was messed up in the never versions because sometimes works (after format), sometimes not. Note that I didn't checked every version after this, it was a random choice. The 6.9.2 and newer has that bug too and many others like problem with "PNG32:" parameter.
Maybe it's related to some Windows package, but there are no informations on main page which should be downloaded.
Last edited by Timbi on 2016-05-14T11:35:30-07:00, edited 1 time in total.
@ECHO OFF
rem ImageMagick path:
PATH = "C:\Program Files\ImageMagick-6.8.8-Q16\"
rem convert BMP to PNG
for %%f in (*.bmp) do (
rem create alpha channel of the bitmap
convert "%%~nf.bmp" -fill white -fuzz 0% +opaque "#980088" "outputa.bmp"
convert "outputa.bmp" -fill black -opaque "#980088" "outputa.bmp"
rem replace alpha color to black
convert "%%~nf.bmp" -fill black -opaque "#980088" "outputrgb.bmp"
rem create png file based on outputrgb and outputa bitmaps
convert "outputrgb.bmp" "outputa.bmp" -compose CopyOpacity -composite -debug coder PNG32:"%%~nf.png"
rem clean up
del "outputa.bmp"
del "outputrgb.bmp"
)
pause
del *.bmp
ECHO ON
convert: unable to load module 'C:\Program Files\ImageMagick-7.0.1-Q16\modules\c
oders\IM_MOD_RL_png_.dll': Nie można odnaleźć określonego modułu.
@ error/module.c/OpenModule/1275.
convert: no encode delegate for this image format `PNG32' @ warning/constitute.c
/WriteImage/1153.
which indicates that libpng wasn't properly installed, or that
you are using an incorrect link to libpng.
I checked something. I moved folder with these "missing" files to other place, and then convert throws the errors only in English and it didn't generated any images. It behave different than with the files in proper place. It looks like some part of the program know where the files are, and some can't find them but they are in the correct path which is thrown in the error. It's strange. The program was installed correctly, just like older working version.
There was also restart to check if it could help with some path registering, but it didn't helped.
I can check more versions and see from which the error appears.