Pixel Visual Core: Google’s first custom-designed co-processor

Re:Pixel Visual Core: Google’s first custom-designed co-proc... by jwarren on Wednesday October 18, 2017 @03:18AM (#15497467)

As landscapes, they may well be less interesting. As communicative portraits, they're (IMO) more successful. The first one is probably the best example. Having a clearer and brighter picture of (for example) your partner and daughter would likely be preferable. If it was a candid and unposed shot, it might look weird and unnatural though. This is why the fourth example is probably the least successful, that hazy summer glow in the "before" picture is somewhat desirable.

To my eyes, the shadow boost is a little too much. I'd ideally like a slider to customise exactly how much brightness you're adding. Personally, I'd probably turn most of these down a touch.

Google clearly has fantastic technology driving this image processing, but I think they need a little more work on their taste.

[ Parent | on HN ]

Re:Pixel Visual Core: Google’s first custom-designed co-proc... by rndmio on Wednesday October 18, 2017 @04:51AM (#15497733)

IMO from a photography point of view the first is the worst displaying very clear haloing around the subjects, one of the clear signs of "not good" HDR. I guess it depends what exactly you're optimising for but the results aren't pleasing to my eye.

[ Parent | on HN ]

Re:Pixel Visual Core: Google’s first custom-designed co-proc... by dharma1 on Wednesday October 18, 2017 @08:07AM (#15498387)

I would also like more controls. You can have that shooting RAW and editing with Snapseed, but it's a bit more involved and the usable dynamic range of a single mobile raw image is below exposure fusion from HDR+.

[ Parent | on HN ]