Grzegorz Kraszewski wrote:
Why not just use MPEG-4 Simple Profile or 3GPP?
You can of course. But CPU usage will be much higher.
If that's pretty much all it's doing, does it matter?
The basic point of a device like this, is not that it will be multitasking, doing a POVray render and folding proteins while streaming. Each task is independant but not running at the same time. You will not be watching stored content AND streamed content AND video conferencing at the same time.
As Bill noted; the burden is on the service provider to give an adequately coded stream for the client. RTSP handles this just fine by scaling content, MPEG-4 can change the macroblock size to something huge or discard hpel/qpel information.. quality suffers but consistency of framerate is preserved. People notice held frames and broken audio much more than they do a legobricking effect for a 25th of a second..
The Efika can easily handle decoding MPEG-4 video at low resolutions and bitrates (at least QVGA, possibly higher).
Video conferencing may be a different story, but video conferencing does not necessarily entail such complex scenes (usually a static background and a fairly static subject) and there are specially designed video codecs for this (perhaps H.262 or H.263).
Matt Sealey, Genesi USA Inc.
Product Development Analyst