https://bugs.kde.org/show_bug.cgi?id=520803
--- Comment #2 from Russell Ault <[email protected]> --- (In reply to caulier.gilles from comment #1) > There is no ImageMagick CLI tools in digiKam bundle. So you need to use an > external ImageMagick installation on your system (your case) and to disable > the default path to the IM codecs used by digiKam. If this is "works as designed", then at a minimum there's a fairly serious problem with the documentation. The Custom Script section in the digiKam manual includes an ImageMagick-based example that, for most practical purposes, doesn't work on the current Windows build (after the necessary `sh`-to-`bat` conversion, that is). Also, nowhere is it mentioned that `MAGICK_CODER_FILTER_PATH` and `MAGICK_CODER_MODULE_PATH` are going to be set in the execution environment (even despite mentioning the existence of several other added environment variables). To me, though, it would make more sense if ImageMagick "just worked" in user scripts, perhaps by noting the state of the `MAGICK_CODER_FILTER_PATH` and `MAGICK_CODER_MODULE_PATH` environment variables when the program launches and then restoring them to that state for the Custom Script execution environment. > Problem with your solution: all extra and exotic image formats supported by > the internal ImageMagick cannot be loaded anymore in BQM. I just did a diff on the outputs of `magick -list format` when using the default modules and the digiKam-provided ones, and the only addition I can see in the digiKam-provided modules is that the Magick Script Language format is listed as `rw+` instead of `r--`. Regardless, ImageMagick appears to only be capable of loading modules from a single directory (e.g. even if you provide multiple paths to `MAGICK_CODER_FILTER_PATH` it will only use the first one that it finds modules in), so the only way solve this problem would be for digiKam to ship with all of the standard ImageMagick modules (which would likely also resolve this bug, at least for most common use-cases). Thanks! -Russ -- You are receiving this mail because: You are watching all bug changes.
