Audio, Video and Graphics Working Group

Table of Contents:

Contents

  1. Audio, Video and Graphics Working Group
    1. Charter
    2. Scope
    3. Chair
    4. Relationship to other working groups
  2. Mailing Lists
  3. Resources
  4. Task List
  5. Member provided links

Charter

Audio, video, and graphics processing is at the core of many CE products. The AVG requirements for CE devices are different than those for PCs/Servers, notably with respect to footprint, input devices, interlacing, streaming, etc.. Multiple graphics planes and video planes may be combined using e.g., alpha blending and animation.

No single default/standard interfaces exist for AVG. Having a well defined, well supported interface for AVG devices will reduce fragmentation of solutions and encourage the CE community to develop solutions that apply to conforming interfaces, so that they can be deployed across a wider range of systems.

Emerging Linux API developments have been and will continue to be studied. They may be endorsed if they cover the requirements. Alternatively, they may be extended or new (function level) APIs may need to be defined. The work group may also recommend new drivers for various CE-based AVG technologies not currently included in the kernel distribution.

Scope

1. Establish requirements for graphics and video-out presentation APIs from a kernel point of view. The WGs will start here with evaluating existing APIs and recommend solutions. Existing APIs may be endorsed if applicable and the WG may provide implementations for various CE peripherals (firmware).

2. For video-input, a low-level (device/ioctl) API is available (Video for Linux 1/2), but a higher level API may be required. For streaming audio/video, new proposals may be made. Particular attention may be given to audio/video and graphics synchronization issues.

3. For audio, ALSA rather than the default OSS will be considered in the context of CE Linux. If audio proves to be largely independent from video, the Video Graphics charter may also be amended to split off audio. If such a split is necessary, the two WGs would need to maintain a close relation due to AV synchronization requirements.

4. Frameworks for various audio, video, and graphics APIs may need to be discussed and defined.

Chair

Ruud Derwig, Philips (mailto:Ruud.Derwig@philips.com)

Relationship to other working groups

* Real Time WG - smooth capture and presentation of audio and video depends on the ability to schedule cyclical tasks with low latency and low jitter, relying on the real-time abilities of the kernel.

* Reliability/File Systems WG - for reliable storage of captured audio/video.

* System Size WG - for CE devices it is essential that the Audio Video Graphics support have a small memory footprint; choices made in one WG will influence the other.

* Focus projects:

(For more, see Resources below).

Mailing Lists

Resources

Task List

The TechConference2005Docs includes the AVG WG discussion. On the last page of that PDF the following task list was presented:

Please go to the AudioVideoGraphicsTaskForces page for more details.

Member provided links

CategoryTaskList

AudioVideoGraphicsWorkingGroup (last edited 2008-05-07 18:21:39 by localhost)