Lightroom 6.5 bug with DJI Phantom 4 photos

Not sure the reason but it should be possible to use the clone tool to heal. If the artifacts are in the same place on each photo you should be able to select all abd sync. But you may need to check each one individully afterwards to check that the heal has blended to your liking as it may be other than sky in some images.

Please supply an original raw (DNG) photo from the camera for further investigation.  You can upload one to www.dropbox.com and post a public download link in a message, here.

I can confirm this issue happens in PS-CC / ACR 9.5 and PS-CS6 / ACR 9.1.1 and LR 6.5 on Windows 10 with or without the GPU enabled in LR.  Here is a side-by-side with the left image being a render using RawDigger and the right being LR 6.5, but I see the same odd colors and pattern using PS-CS6 / ACR 9.1.1 so I don't think the bug is from the .5 release unless it's something to do with a camera profile or lens profile that has changed with the x.5 of each Adobe product install.  Did this happen in LR 6.4/2015.4?

IMHO if this is happening in exactly the same place on every image of different subjects then it is some type of camera/sensor problem. I suggest you contact the manufacture or post to their forums to see if anyone else is having the same problem and even ask for samples from other users to check their images on your system and LR.

I don't think this is the camera problem, but situation is really weird.

Lightroom and Capture One 9 have those artifacts on the image, and exactly same artifacts in the same place.

While dcraw, ACDSee Pro and RawDigger does not show those artifacts.

At the moment what is not clear is that is this the same bug in LR and  C1, or is dcraw just somehow bypasses/fixes strange RAW data.

I thought it might be a sun-burned sensor, too, but RawDigger doesn't show any problem when looking at the raw data such as the above RGB-render, or this composite which, if the data's been fixed, it's before the demosaicing phase:

None of RawTherapee's demosaicing methods show any issues, either:

Note that the embedded JPEG preview doesn't have the artifact.  You can see the preview by opening the file in Quick Look (Mac) or Photo Viewer (Windows). 

C1's DNG processing might be the same as Adobe's if they shared code at some point in the past.

The Photoshop plug-in ACR 9.1.1 from last year is also not reading your DNG correctly and shows same issue so it does not appear to be just the .5 release of LR that has the problem.

If some other user can supply a DNG from their DJI P4 that also shows the issue it would help prove it's not your sensor.  Are you saying that no one has been able to do this, yet?

I hesitate to submit your DNG to Adobe as an example of a bug without corroborating evidence of other users' DNGs that exhibit the same issue.

I just viewed then opened that DNG in bridge CS5 and ACR 6.7.1 and those artifact are there. It is the sensor. I don't know what those other programs are showing, maybe the embedded jpg, but in LR/ACR they are shown.

Nope, it doesn't look like sensor problem.

Try to develop in any other RAW converter (RawTherapee, Darktable, DxO or just convert with dcraw) and artifacts are not there.

Until we see a DNG with mostly sky from another DJI P4, all we know is that Adobe and C1 processing is different than dcraw-based processing.

Can you forward me your post on the DJI forums? I am very interested in this as I own multiple DJI products.

Thank you! Dji Tim is a good source of information. If he does not reply in a day or two after his first post, keep bugging him. Where are you in Texas ? I am in Fort Worth.

On the DJI forums, they're asking for an original JPG and DNG of the image.  Do you have a JPG, too?  I'm not sure why they're not seeing the DNG in your first post.