Pixel Visual Core: Google’s first custom-designed co-processor
1–10 of 102 posts
Re: Pixel Visual Core: Google’s first custom-designed co-processor
#2This is pretty much Tensorflow on metal. Considering that tensorflow works pretty well on most mobile phone GPU, im betting this feature can be turned on for most phones if Google wants.
I would love to see the apples to apples comparison of the Pixel tensorflow computation running on a vanilla snapdragon GPU vs this custom core.
Also will be interesting to know why halide and not opencv.
Re: Pixel Visual Core: Google’s first custom-designed co-processor
#3Cool, but am I the only one who thinks the photos on the right (toward the bottom) are a little overexposed / bland / washed-out?
Re: Pixel Visual Core: Google’s first custom-designed co-processor
#4It looks like they are releasing these bits and pieces before the Finale. Custom ARM core, SOC in entirety.
Re: Pixel Visual Core: Google’s first custom-designed co-processor
#5It looks like they are releasing these bits and pieces before the Finale. Custom ARM core, SOC in entirety.
I'm not so sure... Have they bought or hired any taken like apple did?
Re: Pixel Visual Core: Google’s first custom-designed co-processor
#6The left/right comparison for HDR are pointless : they should show the same image with same contrast/exposure with the two techniques at 100% pixel. The difference between without HDR and with HDR should be less noise (otherwise if it's just about having more exposure in the darkest parts of the image, then a little bit of image processing can do the trick)
Re: Pixel Visual Core: Google’s first custom-designed co-processor
#7This is pretty much Tensorflow on metal. Considering that tensorflow works pretty well on most mobile phone GPU, im betting this feature can be turned on for most phones if Google wants. I would love to see the apples to apples comparison of the Pixel tensorflow computation running on a vanilla snapdragon GPU vs this custom core. Also will be interesting to know why halide and not opencv.
Halide and OpenCV are not comparable. Halide is mainly about decoupling the description of a low-level image processing operation from implementation details regarding tiling, storage of intermediate results, etc. OpenCV is a library implementing high level algorithms like multi-view 3D reconstruction that Halide does not even attempt to address.
Re: Pixel Visual Core: Google’s first custom-designed co-processor
#8This is pretty much Tensorflow on metal. Considering that tensorflow works pretty well on most mobile phone GPU, im betting this feature can be turned on for most phones if Google wants. I would love to see the apples to apples comparison of the Pixel tensorflow computation running on a vanilla snapdragon GPU vs this custom core. Also will be interesting to know why halide and not opencv.
Halide and OpenCV are not comparable. Halide is mainly about decoupling the description of a low-level image processing operation from implementation details regarding tiling, storage of intermediate results, etc. OpenCV is a library implementing high level algorithms like multi-view 3D reconstruction that Halide does not even attempt to address.
My mistake, I phrased my question incorrectly. Why not opencv with a halide backend. The tensorflow whitepaper compares the TF ir to the halide ir. In fact, the work in tensorflow core is around XLA https://www.tensorflow.org/performance/xla/ (which brings compatibility across various architecture)
It seems that this is more an attempt at locking the tensors to target custom metal, so that it can't be copied and made to work on other phones.
For examples, the Google Camera NX version is a port of the HDR+ feature on compatible phones.. Even the cheap Xiaomi. They actually give results comparable to Nexus.
However, by locking the model to a very custom image processor (and custom IR) , this can't be ported. This looks to me as a version of walled garden more than a performance win.
Re: Pixel Visual Core: Google’s first custom-designed co-processor
#9Cool, but am I the only one who thinks the photos on the right (toward the bottom) are a little overexposed / bland / washed-out?
The point is they recovered the shadow detail of people’s faces which would otherwise be lost.
Re: Pixel Visual Core: Google’s first custom-designed co-processor
#10The left/right comparison for HDR are pointless : they should show the same image with same contrast/exposure with the two techniques at 100% pixel. The difference between without HDR and with HDR should be less noise (otherwise if it's just about having more exposure in the darkest parts of the image, then a little bit of image processing can do the trick)
Yep.
Here is a real image on the left, here's one that's been edited to an inch of it's life and looks nothing like the real capture.
HDR is awesome, but so easily used for the wrong things. Makes a good shot turn into some weird half-baked fantasy view.