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.
convert DSC_2045.NEF DSC_2045.jpg
convert: unable to open image `/var/tmp/magick-DIuu3TqX.pnm': No such file or directory.
convert: missing an image filename `DSC_2045.jpg'.
ufraw-batch -- the executable, to which ImageMagick delegates Nikon's "raw" files -- has not changed on this system.
When invoked directly, the executable creates the file as expected:
With the following trick, I can see, that the filenames that ufraw-batch is instructed to create and what ImageMagick then expects are, somehow, different:
% convert DSC_2045.NEF DSC_2045.jpg & (sleep 0.2; ps -axww | grep ufraw)
[1] 8496
8499 p7 R 0:00,08 /opt/bin/ufraw-batch --silent --wb=camera --black-point=auto --exposure=auto --out-type=ppm16 --output="/var/tmp/magick-ZpohUMj5" /var/tmp/magick-VSCtpJDi
% convert: unable to open image `/var/tmp/magick-MaplldvJ.pnm': No such file or directory.
convert: missing an image filename `DSC_2045.jpg'.
While we are at this, why does IM bother to create the temporary files at all (even if only as symlinks to the originals), instead of directing a delegate to the original (when available)?
To fix the problem you reported, change --output="%u.ppm" to --output=%u.ppm for the DNG tag of config/delegates.xml. Some programs strip the quotes of a filename (e.g. gs), however, ufraw-batch does not. We are going to incorporate this patch and a few others in the 6.3.5-10 release on September 23.
and it returned without complaint and returned the expected image in the PNG format. Did the conversion fail for you? Our delegate file says "--output=%u.pnm". You mentioned %u.ppm which we cannot locate in the delegates.xml.in configuration file.
> Release control?
As always the release was tested on 7 different operating systems and passed the 1000+ included regression tests plus at least 1000 more that are not part of the ImageMagick distribution package including the ones we run when we generate the Usage site at http://www.imagemagick.org/Usage/. If you have a use case that fails we would happy to include it as a regression test for the next release cycle.
