what is the difference between eis 2.0 in pixel camera and old one in nexus 6p ?

bartolo5

Senior Member
Dec 1, 2010
267
103
0
EIS can't help with pictures, is only used for video, and even when it does somehow the job, the results are not so good, and it tends to have a lot of jelly effect. When you have OIS available, you can also make it work in conjunction with EIS and the results are awesome. Another point for the OIS is that it works with all resolutions, while EIS is dependant on the resolution and the processing power.

You can think this: best smartphone's cameras are the ones which include OIS, and they present really decent results even in low light. OIS helps you both in photo and video, while EIS is only for video.
All this talk may have been true a couple of years ago, but software based stabilization techniques have improved a LOT in these past two years.

For video, gyroscope based EIS can easily surpass OIS alone and even perfectly correct rolling shutter effects (the jelly effect you talk about). OIS can't do nothing about rolling shutter effect. Check this video of someone running with the Pixel XL and Gyroscope EIS. It's mind boggling. https://goo.gl/tH19KM The one thing you need on the phone is precise gyroscope data, which Google has explicitely bothered to nail down on the Pixels.

For pictures in low light, you can have very short multiple exposures and combine them up after the fact. Results rival that those of OIS. Let's see how Pixel XL does in this respect

BTW, here is the Stanford paper that started the whole gyroscope based EIS https://goo.gl/HqqY4d. It's an amazing read.
 

Jsunn

Senior Member
Jan 14, 2010
262
20
0
I don't shoot video at all with my phone, never saw the need. But I do take a lot of pictures, so the absence of OIS is a bit of a bummer. But until we get some more real world examples, it's hard to say that it will make a difference.
 

Galaxo60

Senior Member
May 25, 2012
2,315
872
193
The Nexus 6P does not use the same camera as the Pixel phones. It's a different sensor. Although both phones have 1.55 micron pixels. The Nexus 6P also doesn't use any hardware based stabilization like the Pixel phone either.

And while focusing didn't happen in that videos. It's a single instance where OIS wouldn't have made a difference since the Nexus 6P did focus.

The best thing to do is just wait and see. I'm sure Google will give us something stellar.
With the f2.0 aperture, the pictures will have less depth vs a f1.7/1.8 aperture. Is that correct?

Sent from my Nexus 6P using Tapatalk
Does the Pixel have any sort of non-software based image stabilization for photos? (Gyroscope stabilization has only been mentioned for videos).
I have a guess why no OIS, think this , without a OIS Gyroscope data perfectly match how camera lens moves, and software can pull the data out to correct the image, with OIS, the data from Gyroscope doesn't match the lens move any more, the EIS can only use the data from the camera to do stabilization which is less effective (cost more CPU and worse result). Some prople may argue OIS hardware can do the work, to be honest, OIS can offset some hand shake during low light taking pics, but during video recording, that little OIS can offer very little help smooth out the image, which actually not worth losing the ability to actually use Gyroscope to correct the image which can create more stable image. and Consider the pixel size of the camera is very large, much larger than even note 7, the low light shutter speed is actually fast enough so OIS really can't make much difference here. I use GS7 and I do notice taking low light pics take longer expose time, but google claim the pixel phone doesn't, which proves what I am guessing here. Let's see some real life test before jump to a conclusion, OIS is good, unless it is a big rig or on a big camera. On a phone, we just pick whatever works.
So it seems that the Pixel XL is suffering heavenly from the lack of OIS after all:

https://www.youtube.com/watch?v=vG711jCHDOA

Video is good, but pictures in low light are average.

:(