Daniel,
I put together a small program in VB that launches both applications with the appropriate parameters. It basically does the following:
1. takes the image file with full path as single parameter
2. calls DNG converter with the file as a parameter
3. if the DNG converter succeeds it deletes the NEF
4. calls the DNG Recover Edges with the image file as the parameter (now the NEF extension is replaced with DNG)
5. sends an [ENTER] key using sendkeys to get rid of that annoying confirmation dialog box (not too elegant but works)
I wanted to call this program after ingesting the photos. Why would that be dangerous? I do not think it is more dangerous than automatically wiping the cards after copying, which is available in PM. If safety is a concern then you could show a warning (like you do when selecting 'Erase source disks after ingest').
Some other ingesting programs offer this option.
Dangerous, why? Because unlike you, most of our users are not programmers. The options you describe like the erasing of source disks after Ingest, are only executed when the *entire* process completes with no errors. If we execute a program after each file is copied, then if there was a failure at some point in the process, we wouldn't erase your disk, but your program would have done its job on a subset of the available photos. This could be OK, or this could be a bad thing.
We could add such a feature to Ingest, and put up a warning dialog that Photo Mechanic is not responsible for what happens to your photos when an external program is run on each file.
I'll put it on the wish list.
-Kirk