Interesting Thread. As a professional filmmaker flying all kind of DJI drones for more than eight years, I had high hopes in the
Mavic 3 as the successor for the amazing
Mavic 2 Pro. But I'm kind of disappointed, and I really don't understand what DJI was thinking, especially regarding the image quality.
Let's ignore the fact, that as an EU-Citizen I have to be an incredibly optimistic enthusiast to buy an unclassified drone without a secured assurance of a reclassification or postponement of regulation deadlines.
Let's also neglect that with the
Mavic 3 you lose a lot of functionality and ergonomics compared to its predecessor, some of them even permanently. The Fly app does not offer many functions of the GO 4 App, waypoints are not even provided according to DJI.
The standard RC lacks a few buttons, in addition to the display. There is no 2nd function button, no 5-way joystick , no more aperture wheel. And no, the RC Pro is not an alternative for all of us, including me.
Let's also ignore the fact that this time DJI is quite cheeky letting the
Mavic 3 mature for months at the customer, as cardinal functions are not submitted until the end of January.
Never mind, let's just focus on the actual core competence of the
Mavic 3, the image quality.
It's positive that the low-light sensitivity is slightly improved compared to the
Mavic 2 Pro, due to the larger sensor with almost the same number of pixels.
However, like its predecessor, this drone only makes sense if you record with 10 bit color depth, which is only possible with D-Log, like with the
Mavic 2 Pro. You also don't benefit from any higher dynamic range from the sensor in the normal profile. The dynamic range in normal profile is simply limited by the Rec709 standard.
In short, if you only want to film in the normal profile without the need for post-processing, you could also film with an
Air 2S or a
Mavic 2 Pro, because the
Mavic 3 offers no advantages in this regard, and it basically cannot, since the possible dynamics of the sensor cannot be exploited in Rec709.
The problem is that D-Log has been implemented in a very, very peculiar way, and I very much doubt that Hasselblad had a hand in the D-Log implementation.
By compressing the linear luminance values using a log gamma curve, more space should be created in log profiles for very light and very dark values that can no longer be mapped in Rec709.
The D-Log of the Mavic 3 compresses the luminance values not only much too exaggerated for the possible dynamics of 12.8 f-stops, but also doesn't offer more space. In the normal profile (Rec.709) clipping happens at 100 IRE, but in this version of D-LOG the room to 100 IRE is unused, clipping just takes place "earlier", at around 85 IRE. Everything above is not used to capture the lighter areas, but is simply cut off.
Try it out for yourself, film something with clipped highlights and deep shadows, or download this D-Log Sample from The Verge:
D-Log ProRes - Google Drive
Long story short: Where the D-Log-M for the
Mavic 2 Pro was well tuned for its sensor, the D-Log of the
Mavic 3 isn't.
And besides that, from what I have seen from original footage so far, the dynamic range isn't that much higher, if at all.
Now you could say, well, then only film in the normal profile for the time being, even loosing 10 bit and maximum dynamic range. However, the sharpening of the
Mavic 3 in normal profile is again extreme, see for example lots of flickering in details in films on YouTube, especially on larger displays. And there are no settings for that in the Fly app.
It is positive that DJI can revise some of the D-Log issues via software, as they did with the
Phantom 4 Pro (after a while). We will see, if they do.
But until then, the
Mavic 3 is of no use for me as a professional filmmaker at all because at this stage it would be a clear step backwards to the
Mavic 2 Pro, with the exception of filming at night or in late twilight, which are rare in my case, so I willl rent a drone for this kind of shots, like I do today.
Not to mention all the circumstances described above and the lack of support from the SDK and therefore from third-party apps like Dronelink in the foreseeable future...