

It just doesn't work well (nor is it intended for) a more full featured RAW editor like Iridient Developer that is designed to output fully rendered images. DNG is just a minor variant of the TIFF format that adds some special metadata for better support of RAW image data.ĭNG works reasonably well (still has some major drawbacks) for a minimal, converter type program like Iridient X-Transformer. If you "bake in" any of the adjustments most users would typically make in Iridient Developer you would end up with a DNG that acts basically just like a TIFF and wouldn't really be very "raw" at all. At that point it just makes more sense to use TIFF for wider application compatibility, support for somewhat better lossless compression (ZIP), etc. Basically the only panels that sort of make sense are Detail and Lens Corrections, but even then a lot of the final result is going to depend on the baseline sharpening and noise reduction in later RAW processors that will vary from program to program you still don't get "what you see is what you get" when making fine edits to sharpening or noise reduction. The whole Exp panel basically doesn't make any sense with DNG, nor does the whole Color panel, for the most part nor do Curves or Mono. Photivo - handles your raw files, as well as your bitmap files, in a non-destructive 16 bit processing pipeline. It can be used on its own or as a GIMP plug-in. UFRaw - a utility to read and manipulate raw images from digital cameras. There are actually many reasons why DNG doesn't make any sense out of Iridient Developer. Darktable - an open source photography workflow application and RAW developer. Nothing wrong w/ maybe a popup warning if DNG output is selected. Using ID by itself is/can be fairly complicated like any raw processor. I personally think that that really underestimates the user base. The only real 'argument' Brian stated against adding DNG output support to ID is that it might confuse the user that the on-screen presentation would no longer 'match' the output file.
