A good point, but I was thinking more along the lines that since encoding is order of magnitude slower than decoding, having order of magnitude more processing power would come to a good use..;)-
Who cares about the decoder? 2.0 GHz Core 2 Duo can handle the decoding without breaking a sweat. Encoding 20 minutes of 1080p H.264 video, however, takes a fair chunk of time. Encoding is where we want to see some action. OK, nice _extra_ to free some CPU time when watching a video.. but typical use case is such that when you watching the video you don't have much else with HIGH realtime priority going on.
So.. encoding.. make it faster, make it smooth, make me cum!
Interesting that you mention battery life. You realize that doing UI with dedicated circuits takes less power than using generic ALU to compute color for each pixel? The UI is what takes most of the processing power. If we have low-power graphics core in there, we can keep the CPU clocked lower and have total power savings.
A smooth UI is not bloatware, it makes the device easier and nicer to use. Initializing OGLES+EGL driver stack takes like 20 ms at most, that nothing. Most of this time is retrieving the driver binaries from storage.
Slashdot Mirror
A good point, but I was thinking more along the lines that since encoding is order of magnitude slower than decoding, having order of magnitude more processing power would come to a good use.. ;)-
Who cares about the decoder? 2.0 GHz Core 2 Duo can handle the decoding without breaking a sweat. Encoding 20 minutes of 1080p H.264 video, however, takes a fair chunk of time. Encoding is where we want to see some action. OK, nice _extra_ to free some CPU time when watching a video.. but typical use case is such that when you watching the video you don't have much else with HIGH realtime priority going on. So.. encoding.. make it faster, make it smooth, make me cum!
Interesting that you mention battery life. You realize that doing UI with dedicated circuits takes less power than using generic ALU to compute color for each pixel? The UI is what takes most of the processing power. If we have low-power graphics core in there, we can keep the CPU clocked lower and have total power savings. A smooth UI is not bloatware, it makes the device easier and nicer to use. Initializing OGLES+EGL driver stack takes like 20 ms at most, that nothing. Most of this time is retrieving the driver binaries from storage.