– Both lack flat-field correction
– Both provide incomplete matrix-only color profiling: no DCP
– Neither use compression
– HTC One M9 DNG is 10 bit stored in 16bit uncompressed data: 39MB per 20 Mpixel image.
– LG G4 DNG is 10 bit stored uncompressed, 20MB per 16 Mpixel image
– Both have non-optimal noise profiling settings: HTC One M9 set noise reduction too high and LG G4 lacks noise profiling entierly.
Notes on flat-field correction:
Mobile camera modules require such correction to correct both vignetting and color cast (like pink spot / greenish or blueish corners).
HTC One M9 requires less correction than the LG G4.
It is only possible to compensate for light fall-off, in RAW image editors, not color cast.
As a result, the color cast in corners is essentially non-fixable.
Attached: the #LGG4 DNG sample provided by +Colby Brown rendered in Lightroom with only modification an increased contrast and exposure slightly, to make both vignetting and color cast more obvious.
The least I can say is that there's room for improvement, both DNG implementation being non-optimized and incomplete.
#supercurioBlog #LG #DNG #color #camera #calibration
25 thoughts on “Some facts after a quick analysis of both +HTC #ONEm9 and +LG Mobile Global #LGG4 produced DNG”
I always enjoy seeing your insight into these things. Keep up the great work
Hey +François Simond did you ever do an in depth like this on the OnePlus One? I'm curious to read it if you did. Would you be able to link me to it? Keep up the awesome work!
+Juve Zavala as I did the profiling in CM Camera for the +OnePlus One, including on everything that's missing in those I'm not in a position to review my own work 😉
I published some bits on +Francois@Cyanogen Inc. page while working on it however.
Sorry, that's right, thanks man!
Thanks +François Simond!
How is DNG for the Nexus 6 compared to LG and HTC?
+Charles Sewell because it's reliant on Android's DNGCreator:
– Uncompressed 10 bit values packed in 16 bit words like the HTC One m9 (large files)
– No dcp color profile
I never looked at samples however, feel free to send me some if you'd like.
upload a picture to g+ -> autocrapp.
+Cedrik L Not necessarily: one can actually upload full, uncompressed .DNG files as well as untouched JPEG files to Google+ without them being compressed by the platform… Facebook and other sites however, will recompress and downscale them.
+Taylor Wall the presented picture is pretty much comprised. You only have the possibility to download the full quality pic on the desktop.
+Cedrik L needless to say that the attached picture is without auto awesome or any other G+ effect (it's disabled entirely in my account's preferences, you can do it too.)
The vignetting and Green/Blue color cast is the one from the G4 lens and sensor.
+Taylor Wall BTW the file attached was rendered in Lightroom as JPEG with little compression, as it's the reference DNG implementation, instead of relying on Google's raw converter.
+François Simond, what is causing the speckled blue arch that comes from the top on the rock out and down to the left? Is that present in the DNG file?
(As far as I know, you can upload them straight without going through light room to get a JPEG… I've done it before with my OnePlus One.)
Edit: that makes sense not relying on Google+ to present the RAW if most software does it differently. I figured it was mostly the same.
+Taylor Wall what makes this oval shape is the vignetting and corner color cast added to the sky itself.
If things look speckled, it's the result of compression G+ re-compression artifacts on the sensor noise, which is why I I would recommend to download the original file I uploaded, which is a 16MB JPEG.
This was rendered with Lighroom CC on destkop BTW.
+François Simond of course it is, but it isn't shown uncompressed on the g+ stream. Otherwise it would take some time to load it with my connection. Contrary, it's instantaneously loaded, so no 16 MB pic on the stream.
+Cedrik L that's why I encourage to download the original for pixel peeping purposes, which is available on mobile in the app and on desktop.
However, the lack of flat field correction is illustrated perfectly even in thumbnail size (if not even better)
If forced to chose between the 2 … which would you take home?
+Chris Dartois the quality of profiling doesn't matter to me because I can build mine and rewrite the DNG files.
To shoot in re-profiled RAW:
I would choose the G4 because it has an OIS and better AF which matters most usually.
However for landscapes in good light I would pick the M9 because its 20 Mpixel sensor is also equipped with a sharp lens.
Of all phones on the market, which do u recommend?
+Chauntelle A Russell you don't want me to choose for you, all I see is FLAWS EVERYWHERE 😵
That's a condition named perfectionist or something 😉
But it's useful in my line of work at least.
+François Simond i know what you mean about being a perfectionist. I often envy the people that can just buy something, use it and enjoy it.
+Matthew Leo hehe yes.
I was just being silly about that being a condition tho, it was just a way to dodge a question that's impossible to answer when knowing nothing about the person asking 😋
No i think it's a condition. Lookingforissuesitis…can be terminal.
+François Simond would it make a difference if they used the lollipop API for their cameras? Camera2?
Cheers mate, job well done
+Davi Porciuncula unfortunately no, Android DNGCreator does not support dcp color profiles at all nor compression.
Also I see that the made they flat-field correction gainmap optional: it was required in previous versions of the SDK if I remember correctly.