A couple of weeks ago we wrote up that tiny PixelWorks had announced what it claimed to be the world’s first Mobile Video Display Processor. The chip was codenamed Iris, and the company said it would allow handset manufacturers to offer cinematic picture quality on mobile screens.
The Iris chip turns out to be a 5m x 5m package, that sits between the App Processor and the screen, and targets scaling, motion blur, judder removal, color management and image enhancement.
So our first question to Graham Loveridge SVP Strategic Marketing at Pixelworks, when we followed up with him this week, was to ask if there was any battery life left in the device after it had done all that.
‘Actually it saves power. It saves 25% of the power that was used on the screen.’ That got our attention.
Pixelworks came out of video processing in projectors, and then went on to TV chipsets, and offered its own TV SoC (not too good according to Loveridge) and tried to make money in the flat panel TV transition.
‘If the SoC was not good, the company’s underlying algorithms were very good,’ said Loveridge, and he goes straight into what those algorithms do, ‘there can be disjoints in the frame rate that is being sent and what the screen can show, the content can need upconverting, and we affect the vibrancy of the color and improve the backlight management.’
‘Our TV chips were in the 5 Watt range, but we re-engineered them from the ground up and hardwired in the logic circuits. Until now there has been nothing like this on a phone.’
‘MediaTech had an idea it called Clear Motion in its Octocore chip that is similar, though doesn’t go as far. It takes part of the pipeline, but it looks to us more of a checkbox than something that actually made a difference.’
‘Hardware in the App Processor is power hungry, so we meaningfully offload that.’
‘The difference in the video is like night and day. We remove judder, displays on smartphones now are high quality, you can no longer see individual pixels. This is fine in a still picture, but in motion there is blurring because the screens are not fast enough. There are content issues, and viewer fatigue is quite common and has been measured in some studies, particularly one by Ooyala.
We wondered if it was just a matter of time before this function was sucked into the all-powerful App Processor SoC. ‘It lends itself to either being integrated into the display itself or into the App processor, but we are starting to think that it is a new location entirely inside the device.
This is because the display needs to be thinner, and the App Processors is getting to be too power hungry, so you want more times when it is not on.
The CPU and GPU goes into a low power state more often when this chip is used and that’s where the power savings come from. There are also better cache hits said Loveridge.
It turns out that savings can also be made on the backlight on a screen, turning it down rather than off, when the screen needs to be darker. This is not quite as effective as separately controlling backlight LEDs as in the modern TV set, but that too may come, and anyway it’s built into OLED phone screens, so needs controlling.
LCD screens on TV’s just cannot switch fast enough to keep up with motion, so the TV manufacturers have a number of tricks to make it look more realistic, such as strobing the backlight, or doing motion interpolation where intermediate frames are generated between existing frames, to make animation appear more fluid. This is what’s missing from phone screens, and by adding it, the phone (or tablet) is pushed more and more towards being the primary video source for an individual. If this cannot be added, because it is too power hungry, it would limit what you can do with their screens.