I have taken some RAWs on my Google Pixel 7 phone. Occasionally in Art they look fine in the thumbnails but when opened they are a bit desaturated. I use the auto-matched curve profile. This pair (sorry for the terrible holiday selfie) are very washed out. Is there a way to match the thumbnail for colour saturation and balance?
Hello, that photo doesn’t look good in ART, so confirmed.
However, when you set the Tone curve to Luminance mode, the photo looks already a bit better. Add to that a bit of Saturation (the graph under Tone curve 2) and set White point to 3.2 (or something) and you’ll end up with the following.
Just fine-tune for your DNGs and save as a profile, use that profile to open your Pixel 7 shots.
Hit it with the dehaze module…that will bring the punch back to the colors…it’s strong and has an auto setting in RT… I think you might have to dial it in with ART I can’t recall… should totally recover the washed out bit…
Here is with log tone mapping auto setting instead of the tone curve and dehaze and local contrast… 3 edits… not maybe great but might be closer to your expectations…
Apart from that: I have a Pixel 6 Pro and have similar experience like you. You can try the Adobe DCP and their base- & lookup table stuff, but I must say since the colors I get from the Pixel raws are so terrible I haven’t really messed around with it.
Barry also be sure that you always use your gainmap with cell phone DNG… its enabled by default in DT for supported phones… in ART you use the Flat field correction and use embedded…it relights the image and removes the strong vignette that cell phones have…
the embedded profile desaturates a lot. Using the DCP profile from Adobe (which has a specific one for both the front and the rear camera) improves things considerably, bringing the situation (wrt. saturation) back to normal.
The second problem is in the auto-matched curve. I never managed to get good results with it for pixel phones. This is not really surprising, as pixels in their HDR+ mode do a lot more than a simple tone curve. I would simply use a fixed S-shaped curve for pixels, and try to apply other settings as needed. If you really want to match the preview, here’s one way (for this photo). You do need the “right” Adobe DCP profile though (called “Google Pixel 7 Front Camera Adobe Standard.dcp”)
Thanks for the suggestions everyone Of course I had tried fiddling with saturation (a lot), and generally managed to match the thumbnail, it was just the slightly random occurence of the issue that threw me. Usually Art gets it right, once in about 20 it goes off the map.
Thanks @agriggio for the pointer to the .DCP which nails it. I’ll just stick with my usual home brew variation of “auto-matched curve” and if the image seems to be taken through a 20% saturation filter, I’ll pull in the DCP and carry on as usual.
Also, thanks @priort for the heads up on vignetting. Good tip.
Of course this resolution doesn’t make me any prettier. There’s only so much even Art can do.
While once looking at a raw, my thoughts were literally “No vignette correction in the lens profile. Ok, you could correct that with a white frame, but why bother, the colors are useless.” I did not expect this result.
At least on my pixel 3a… in DT a good dose of chroma and saturation. Local contrast and diffuse and sharpen instance and they are not bad… I find that the processing Google does at least in my generation of phone to faces is often terrible with massive artifacts and in the raw you don’t seem to have that so you can often save a photo… My only gripe is that if you zoom since its a computational raw you get a really small and useless DNG. I only use the raw files if I don’t zoom. My old Lumia phone has better DNG… and they are full sensor even if I zoomed in …