Thanks Sandy, just to further complicate things I'm running a windows system - the only DNG cleaner I can find is DJI's own one - which (unsurprisingly) won't touch DNG files written by the Phantom 4 Pro
Did you ever find a solution? I'm looking for the same thing.
Can you post a download link to a DNG that has not been edited, straight off the camera?
I may be wrong, however looking at some OEM samples with ExifTool, I don’t believe that there is any metadata that can be removed using ExifTool that will create a different result in ACR/Lightroom vs. other software (i.e. this is how Adobe have designed and hard coded their raw converter to behave). Or perhaps it is just that ExifTool does not see this data and the tools such as DNG Cleaner do.
This is not unique to this camera make/model, I have seen similar reported with other cameras where there are more pixels available to other softwar.
1 person found this helpful
So if anyone is looking for a solution, the answer is Yes you can. Here's the command below. Everything referenced here is available (and possibly an updated version) in the GitHub repo at github.com/darana/P4P__color-profiles
Simple answer is to use EXIFTOOL to strip -OpcodeList3 from the file. This EXIF field contains the binary data that equates to the lens profile. Here's the command (link to readme on GitHub)
exiftool.exe -OpcodeList3= -m -overwrite_original -progress -v3 -ext DNG -if "$EXIF:OpcodeList3 ne ''" FILENAME\PATH
-OpcodeList3=sets that field to null, i.e. deleting it.
-msuppresses low priority warnings. There is a message about offset that will come up for every single file, otherwise.
overwrite originalwell, overwrites your original
-ext DNGtells the command only to run against DNG files, whether you specify a filename or a folder/path
-v3provide detailed progress and logging
-if "$EXIF:OpcodeList3 ne ''"makes the command conditional, running against the file only if the file's -OpcodeList3 isn't already blank. This is optional, I just use it to speed things up in the case where I have already run against part of the list.
FILENAME\PATHis the filename or the folder of files to execute against.
So I got tired of running this command, and having multiple steps to ingest, so wrote a full ingest, rename, then nuke the profile powershell script for Windows. The details are here with download link With this workflow, I run the Powershell script, which pulls everything in, sorts into folders by date, strips the profile, then I ADD to Lightroom. Saves a lot of headache with ingesting, then updating metadata and previews.
As you noted, @andy_kay, you will then be left with a file with all of the barrel distortion of lens, so you'll need to either apply distortion, or use another lens profile. We've got one created, however, thanks to Dingoz at PhantomPilots.com. He created this using the Adobe Lens Profile Tool. Do note that he focused on distortion so the vignetting may not be perfect. There are actually two versions of it, v2 has greater distortion into the corners, but I find that I prefer v1, which retains a bit more sharpness to the edges. My default is to use v1 with 100 distortion and 75 vignetting sliders. Here are the profiles documentation with download link.
And last but not least, there are Color Profiles for the P4P created with a Colorchecker Passport under various lighting conditions.