Live data from Hacker News

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

blog.google

31–40 of 102 posts

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

#31
HDR+ is one of my favorite features from my 6p.

I am routinely blown away by how well it performs at all lighting. Everyone i've shown pictures from low light scenarios is always impressed.

HDR+ is a big reason I bought the Pixel 2, I know its going to keep getting better.

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

#32
In addition to still photos, would love to see exposure fusion (or HDR+ as Google calls it) in mobile video too. RED Epic and Scarlet cameras do this with 2 exposures per frame and call it HDRx, I've found it adds about 4 stops of dynamic range in grading. RED doesn't do any fancy anti-ghosting stuff though like HDR+. Magic Lantern firmware for Canon dSLR's also does something similar with dual ISO frames.

This together with 10bit video profile for h265 (think phone hardware is capable now but haven't seen any phones with 10bit video yet) would make mobile video a whole lot better, right now it frankly sucks for anything with high contrast or dynamic range.

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

#33
Anyone feels it's tech for the sake of tech ? I don't even appreciate the HDR processed shades. There's a lot more detail that's true, but 1) it's fake IMO 2) pics don't have to be perfect, it's just a moment of life, the details are precise enough.

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

#34

Earlier quoted context omitted.

I don't think the Pixel Visual Core is supposed to do anything new or revolutionary -- the primary purpose is to do these old things FASTER for the user.

But a simple histogram stretch can be done with very little processing power by modern standards. 50 ms on one core of the application processor would be enough. I think they just chose bad examples. The results from this Google Research blog post are much much more impressive: https://research.googleblog.com/2017/04/experimental-nightti... I wish my smartphone could do _that_ automatically.

You end up with a lot more noise with simple histogram adjustment from a single image, plus the dynamic compression to a final 8bit image won't look as good for many use cases.

Exposure fusion from multiple images has much higher usable dynamic range and lower noise.

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

#35
post #12
post #3

Cool, but am I the only one who thinks the photos on the right (toward the bottom) are a little overexposed / bland / washed-out?

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 summ…

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+.

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

#36
post #3

Cool, but am I the only one who thinks the photos on the right (toward the bottom) are a little overexposed / bland / washed-out?

Those are challenging circumstances for taking photos (backlit). The point here is to recover shadow detail.

Them looking bland is a function of them being made in challenging circumstances.

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

#37
post #28

Earlier quoted context omitted.

Hopefully the idea is that it looks at the scene, decides which exposures are needed to capture the DR (for example 1/100s ISO800 for the foreground and 1/200s at ISO100 for the background) and then quickly captures exactly those two exposures in rapid succession. Then the software would try to compensate movement between the frames and stack these exposures into one. So long as it involves multiple pictures and the…

Yes you can, there are multiple inputs BUT the effect is about extending dynamic range only (not create an artistic effect between the inputs). You can always extend numerically the DR of any set of values but you will stumble upon some noise eventually.. This HDR+ module is supposed to have less noise in the shadows OR have better sun effects / beautiful highlights (candles for example) / good looking clouds. A good…

Right, the key "artistic" thing is identifying foreground/background, faces, interesting elements etc., and simply try to balance the exposure to create a pleasing end result. I have no idea what this thing does, or even if it uses multiple exposures (or even multiple cameras), but I was simply thinking that facial recognition/focus and automatic toning has been around for ages, it has to do something that requires fast decision (at trigger time) about exposure params.

I couldn't see whether that was done though, it could be done with most of the same effect by simply exposing e.g. +2EV and -2EV and simply deciding afterwards how to blend those images into a HDR given the image content (faces, ...)

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

#39
It seems odd to me that they’ve made this special part of the chip but it won’t be enabled until a future software update that will come out 1+ months after release.

The basic idea of using special hardware makes sense. Apple has done the same thing, and as you get more and more data off the sensor this seems like the only way to do analysis/adjustment in real time without wasting a ton of power.

Post reply on HN