Legacy ImageMagick Discussions Archive

Hello,

I have two problems with the setup of IM regarding coders/delegates:

I want to process nef-files with my own delegate, not the dng-delegate. The only way to prevent the dng-delegate to take control is to redefine the dng-decoder in delegates.xml (but then I loose the ability to process real dng files).

The same holds true with a special image-format which is xml-based. IM always identifies this as svg (and processing fails). I have added a type in mime.xml, an entry in magic.xml and an entry in delegates.xml. In my former versions of IM (6.5.4), this was enough and IM used the defined delegate. My current version (6.6.1) only uses the delegate if I give the image-type explicitly (type:filename-notation). But this is no workaround e.g. for running montage on a directory with a lot of different image-types.

Is this a bug or is there a way to tell IM not to use any predefined coders, but just to use the defined delegate? Probably the real problem is to tell IM the order in which to "guess" the image-type.

Thanks, Bernhard

Modify the dng delegate in delegates.xml to point to a script. Include needed parameters as script command-line arguments (e.g. %i %o). The script can be any scripting language (e.g. Perl, bash, Python). Finally include logic in the script to use one program to read NEF and another for other formats (.e.g. CR2).

This workaround works for the NEF case, but not for the SVG case (my version doesn't even call the delegate for svg defined in delegates.xml).

Another point: why should I reproduce the logic to identify image-types in my script? In general IM does a very good job at this. And to stress one point again: it is a regression compared to 6.5.4. And it does not fit the logic of magic.xml/delegates.xml: why should I add entries to these files if IM just ignores the information?