P: Edited Mavic 3 Drone Photos changed automatically to washed out photos - version 13.1

[Sebastian.Lehrke]

Hi guys,

I have updated my lightroom classic to the version of 13.1. Now I started editing and realized that all my drone shots of the last years changed their look without me editing or changing something in the settings of the edit. They now look washed out, way brigther and it feels like the yellowish tones faded out and disappeared. All my normal camera photos are not effected of that.

I can see it even live, how lightroom is changing the photos. For example: I click on one photos which looks as contrasty and ready as I edited it. Preview looks fine. If I go into the Edit-Tab, it takes quiet some time till the photos is shown again (something is obviously processed) and then the photo is as explained above: Brigther, washed out and colorless. 

I have no clue what happenes here, but if anybody of you has the same issue and a fix, I would be more than greatful. 

I also asked some friends of mine and some of them are experiencing the same issues with their drone photos. This is not a singular specific problem at my computer (MacOS Ventura). 

Thanks in advance and greetings,

Sebastian 

[GoldingD]

When you review the curent Adobe Camera RAW Supported Cameras document:

https://helpx.adobe.com/camera-raw/kb/camera-raw-plug-supported-cameras.html

And look in the DjI section. It appeasrs that all the various Maviv 3 options calls for LrC v13.1

Now I suspect, that you had support prior to v13.1. This implies IMO that Adobe has changed someting in ACR (and as such in LrC) Or am I looking at the wrong camera?

[Sebastian.Lehrke]

No the original Mavic 3 is missing. The Mavic 3 classic is not the original Mavic 3 but a lighter, smaller version without the zoom. 

[KR Seals]

From your description, are you saying that the images are ok in the Library Module but change in the Develop Module?

I'm not sure if this would work for you. It's worth a try. From you examples, it looks like the lighter photo has about 2/3 stop additional brightness. I just tested this technique on some of my raw files. 

Start with the first photo in a folder where the files are all too bright. Adjust the exposure of the first one to the desired look. Then with that one "most selected" use the control key to select a few more. Then in the Photo menu -> Develop Settings -> Match Total Exposure. That should change the exposures on the additionally selected photo to match the first one. I did this in the library module with the Quick Develop panel to change exposure only.

If this works ok for you, you should be able to fix all the images in a specific folder at the same time. 

[Sebastian.Lehrke]

Unfortunately that's only half of the truth. It appears okay but then turns into the wrong look when hitting the D-Mode. However, when exporting the still good looking image when seeing it in the catalogue, it has the washed out look.... and I mostly have different exposures in my images in dependency of what I wanted to express. Might only work for same looking images. 

weird, really. Would expect a fix by DJI... kind of. 

[Sebastian.Lehrke]

I mean a fix by Lightroom / adobe.

[GoldingD]

 do have the first Mavic 3,

In LrC, can you select one of those images, and in the Library module, show the Camera Info as LrC reports it in the Metadata? (recommend when you create the screenshot that you eliminate anything private like the S/N)

Also, to help nail down what camera, please review the following link, at the bottom in the link a whole slew of DjI drones, what one? You might also create a screenshot highlighting the done in question.

https://en.wikipedia.org/wiki/DJI_Mavic

[Sebastian.Lehrke]

Attached you find what Lightroom Classic gives me as the Make and Model:

[GoldingD]

Hasselblad L2D-20c

When you visit:

Cameras supported by Camera Raw | Adobe

As one would hope/expect , their is no such camera inside the Hasselblad section. This is after all the sensor not a complete camera. And should be in the DjI section.

But what about the DjI section? And specifically is the L2D-20c mentioned as a suffix (or whatever they call it) Well no, that is not listed, And only on Camera/Drone is listed with such a suffix, that being the DJI Mavic 2 Pro (Hasselblad L1D-20c)

So what about the other DjI Cameras/Drones, what sensor is in those units. Does one of those that are not the Mavric 3 (original) use the same sensor?

[JohanElzenga]

Google is your friend, my friend! If the search for "L2D-20c" in Google, the first page you'll find is 

https://www.hasselblad.com/collaborations/dji-mavic-3/

[GoldingD]

Thank you.

And from that source, the following is derived:

DJI Mavic 3 Hasselblad L2D-20c
DJI Mavic 3 Classic Hasselblad L2D-20c
DJI Mavic 3 Cine Hasselblad L2D-20c

Did not see any info on processor, so I do not know if that is an issue, do not know if the combination of Sensor and processor would present different RAW data.

Above does seem to create an question. Does Adobe see all three of those drones as L2D-20C and as such the same RAW analogy.

[JohanElzenga]

Thank you.

And from that source, the following is derived:

DJI Mavic 3 Hasselblad L2D-20c
DJI Mavic 3 Classic Hasselblad L2D-20c
DJI Mavic 3 Cine Hasselblad L2D-20c

Did not see any info on processor, so I do not know if that is an issue, do not know if the combination of Sensor and processor would present different RAW data.

Above does seem to create an question. Does Adobe see all three of those drones as L2D-20C and as such the same RAW analogy.

By @GoldingD

It suggests what I suggested al along, namely that the unsupported Mavic 3 now all of a suddens gets profiles applied to its images that were developed for one of the other two -supported- models. As far as I can tell these models have different sensors.

[dt-photography]

Latest Lightroom Classic version 13.1 has made all my already developed RAW files from DJI drone to look 'washed out', and need developing all over again (thousands of images!).
Am I the only one with this problem?
RAW files from DSLR camera seem to be unaffected, only DJI files.

[moved from bugs to discussions according to the community rules - Mod.]

[Sebastian.Lehrke]

Discussing the topic here already. Still waiting for a solution. Adobe hasn't reacted yet. Still having the issue. 

[Sean_cgn]

I have exactly the same problem. I use the Mavic 3 (not Mavic 3 Classic, Mavic 3 Pro or Cine).
The problem only occurs with raw images.

When I click on an image that was edited in the past, it takes a second and it suddenly becomes brighter and the colors are no longer the same as before.
I haven't made any changes and it doesn't show up in the log. And if I reset it and apply the preset again I also get a different result.

[JohanElzenga]

Thanks. Can you confirm (or deny) that you do have Adobe raw profiles (such as Adobe Landscape) when selecting a DNG from your drone?

[Sean_cgn]

Yes, I always use Adobe Color on all my photos. Regardless of which camera I use.

For example: One year ago I used the DJI Air2S. The edited pictures I took with the old drone are unchanged and there is also the Adobe Colors profile selected.

[JohanElzenga]

I think Adobe Color is always present. The question is if you see the other Adobe profiles such as Adobe Landscape.

[Sean_cgn]

Yes, I do.

[JohanElzenga]

OK, that is more and more beginning to look like a bug. I have two DJI drones. One is not supported (Mavic Air 2), and I only see 'Color' and 'Monochrome' as default profiles. The other drone (Mini 3 Pro) was not supported before Lightroom Classic 13.1 and so I also had only the same two profiles for this drone up to version 13.1. Now I do have all Adobe profiles for it. So either the Adobe documentation is wrong and the Mavic 3 is supported after all, or Lightroom recognizes this drone wrongly, applies the wrong new profile for another Mavic 3 model, and so the appearance of the photos change. Moving this thread to 'Bugs'.

[Kuba30164089ir74]

Hello. Since the same time, the owner has been with an incorrect interpretation of color photos in DNG from my Mavic 3 drone. This means that an error in the national characters exists in the PS and LR programs, equivalent in the form of C1 or DxO, which is a substitution of the problem or does not exist in the limitations. What can result from this and how can it be asked? Attached is a screenshot

[GoldingD]

You might want to join in on the following:

https://community.adobe.com/t5/lightroom-classic-bugs/p-edited-mavic-3-drone-photos-changed-automatically-to-washed-out-photos-version-13-1/idi-p/14318353#comments 

Additional Mavic 3 users with the same problem can reinforce that the issue is a bug.

Or, if you have a solution, then you could help others.

Post by Kuba30164089ir74 merged. (just FYI)

[The Keeper of the Garden]

An educated guess as to what happened:

1. DJI Mavic 3 Pro cameras (all three) were indeed supported by an earlier version of ACR (Adobe Camera Raw), the RAW engine used by LrC and Ps, but in a "preliminary" way. What "preliminary" means in this context, can be found when you scroll all the way down to the bottom of the page others on this thread have linked to: https://helpx.adobe.com/camera-raw/kb/camera-raw-plug-supported-cameras.html#Preliminary_Support_mea... 
   I quote: "Preliminary support means that the image quality and raw format support for the given camera model is not yet finalized and may be updated in a future release."
2. Updating to LrC 13.1, which uses a newer version of the RAW engine (ACR 16.1), included "full" support of the Mavic 3 Pro cameras.
3. What the OP is seeing when he now looks at his Mavic 3 Pro photos in LrC 13.1, namely a significant change in contrast and colour rendering between the "new" versions and the "older" ones ("older" meaning edited in a previous version of LrC using a previous version of ACR), is simply the change that unavoidably happens when "preliminary" support of RAW (or DNG) files becomes "full" support.
4. The photos now look more "washed out" and have colours or grades of colours that have changed, but will now actually have more "latency" in editing/post-processing as far as contrast, colours, and other elements are concerned (perhaps less noise in the shadows also). 
5. Unfortunately, in order to get the same "look and feel" of the photos back, just like they were edited by the OP in a previous version of LrC, they will need to be edited again. The down side, of course, being that it will need a lot of work, the up side being that, after re-editing, the new version may even look better than the old version as "full" support should yield better results than "preliminary" support of RAW (and DNG) files.

Once again: This is my educated guess... I could be wrong, but looking at the photos the OP has published on this thread, I think this is the cause of the "washed out" look. 

[GoldingD]

An educated guess as to what happened:

.....

By @The Keeper of the Garden

The Drones listed in the Adobe Camera RAW supported Cameras, are not the camera in question. The original Mavic 3. That Drone is not listed. This Drone is not the Classic, not the Cine, not the Pro.

DJI Mavic 2 Pro (Hasselblad L1D-20c)
DJI AIR 2S
DJI Mini 2 
DJI Air 3 Wide Camera 
DJI Air 3 Telephoto Camera
DJI Mini 3 Pro
DJI Mini 4 Pro
DJI Mavic 3 Classic 
DJI Mavic 3 Cine Super Telephoto Camera
DJI Mavic 3 Cine Wide Camera
DJI Mavic 3 Pro Super Telephoto Camera
DJI Mavic 3 Pro Telephoto Camera
DJI Mavic 3 Pro Wide Camera
DJI Osmo Pocket 3 D	

A completely different Discussion exist for the Mini 3 Pro. Those posters are happy as bugs as that camera has gained support in ACR, and apparently now has camera matching profiles.  They are not discussing watched out images (at least not yet)

https://community.adobe.com/t5/lightroom-classic-discussions/is-dji-mini-3-pro-supported/m-p/1347427...

I could be wrong, maybe in that discussion they are just so happy something has occurred and they have camera matching profiles and they have not noticed any oddities just yet.

So I do not think going away from preliminary for the drones listed is the issue for this specific drone.

[The Keeper of the Garden]

OK, I misread the Mavic 3 for the Mavic 3 Pro. But... the Mavic 3 came out before the Pro and before the Classic. Why would it not be supported? Maybe the Adobe "supported cameras" list is not complete? Anyway, it's up to Adobe now to come up with an answer. Perhaps LrC (ACR...) interprets the Mavic 3 files as coming out of the Mavic 3 Pro or Cine or Classic? There's indeed something wrong here, with the newer versions of the Mavic 3 drone being supported and the original one not... (at least not according to the list).  

[JohanElzenga]

OK, I misread the Mavic 3 for the Mavic 3 Pro. But... the Mavic 3 came out before the Pro and before the Classic. Why would it not be supported? Maybe the Adobe "supported cameras" list is not complete? Anyway, it's up to Adobe now to come up with an answer. Perhaps LrC (ACR...) interprets the Mavic 3 files as coming out of the Mavic 3 Pro or Cine or Classic? There's indeed something wrong here, with the newer versions of the Mavic 3 drone being supported and the original one not... (at least not according to the list).  

By @The Keeper of the Garden

Why would it not be supported? Because Adobe decided not to add support. Adobe added support for several DJI drones in Lightroom Classic 13.1, but not for all of them. My Mini 3 Pro is now supported, but my older Mavic Air 2 is not. That's life.

And that is most likely the cause of the problem. Because all Mavic 3 drones seem to write the same 'L2D-20c' into their files, Lightroom suddenly applies the wrong profile to the files of the Mavic 3. It should keep the generic 'Color' profile (the profile for unsupported DNG), but it apparently applies the 'Adobe Color' profile for a newer Mavic 3 version.