OpenMAX

From Wikipedia, the free encyclopedia

Jump to: navigation, search

OpenMAX

OpenMAX (Open Media Acceleration) is a royalty-free, cross-platform set ofC-language programming interfaces that provides abstractions for routines especially useful for audio, video, and still images. It's intended for devices that process large amounts of multimedia data in predictable ways.

OpenMAX provides three layers of interfaces: Application Layer (AL), Integration Layer (IL) and Development Layer (DL). OpenMAX is managed by thenon-profit technology consortium Khronos Group.

Contents

[hide]

• 1OpenMAX layers
• 2OpenMAX AL (Application Layer)
  • 2.1Features
  • 2.2Specification versions
  • 2.3Implementations
  • 2.4Comparison with OpenSL ES
• 3OpenMAX IL (Integration Layer)
• 4OpenMAX DL (Development Layer)
• 5OpenMAX Working Group
• 6See also
• 7References
• 8External links

[edit]OpenMAX layers

OpenMAX AL is the interface between multimedia applications, such as a media player, and the platform media framework. It allows companies that develop applications to easily migrate their applications to different platforms (customers) that support the OpenMAX AL API.

OpenMAX IL is the interface between media framework such as DirectShow or GStreamer and a set of multimedia components (such as an audio or video codecs). It allows companies that build platforms (for example an MP3 player) to easily change components like MP3 decoders and Equalizer effects and buy components for their platform from different vendors.

OpenMAX DL is the interface between physical hardware, such asDSP chips and CPUs, and software, like video codecs and 3D engines. It allows companies to easily integrate new hardware that supports OpenMAX DL without reoptimizing their low level software.

[edit]OpenMAX AL (Application Layer)

OpenMAX ALDeveloper(s)Khronos Group, Inc.Stable release1.1 / 18 January 2011Operating systemCross-platformTypeAPILicenseVariousWebsiteKhronos Group, Inc.

OpenMAX AL accommodates common multimedia application use cases by standardizing a set of representativeobjects, as well as interfaces on those objects, to control and configure them. The OpenMAX AL API is divided into two profiles: Media Player and Media Player/Recorder. A platform can be compliant to one or both of these profiles by providing all features included in a profile.

It is an application-level, C-language, multimedia API designed for resource-constrained devices. The OpenMAX AL API design puts particular emphasis on ensuring the API is suitable formobile embedded devices - including basic mobile phones, smart “feature” phones, PDAs and mobile digital music players. Nevertheless, this does not preclude its applicability to other sophisticated media playback and recording devices.

The OpenMAX AL API design devotes particular attention to application-developer friendliness. Its status as an open cross-platform API enables developers to port the same source across multiple devices with minimal effort. Thus OpenMAX AL provides a stable base for application development.

[edit]Features

OpenMAX AL features include:

• Video playback and recording
• Audio playback and recording
• Image capture (camera) and display
• Camera controls
• Radio and RDS
• Basic MIDI playback
• Metadata extraction and insertion

[edit]Specification versions

• OpenMAX AL 1.0 Provisional Specification - a provisional version, dated 2007-09-02, to facilitate feedback from the community before the final 1.0 release.
• OpenMAX AL 1.0 Specification - dated 2009-06-23
• OpenMAX AL 1.0.1 Specification - dated 2010-03-12
• OpenMAX AL 1.1 Specification - dated 2011-01-18^[1]

[edit]Implementations

• An open source implementation of AL is available at LIM OpenMAX.
• Android 4.0 exposes OpenMAX AL 1.0.1 as part of their NDK.^[2]

[edit]Comparison with OpenSL ES

OpenSL ES is another Khronos Group API providing a Sound Library for Embedded Systems.OpenSL ES and OpenMAX AL share the same common architecture and have a few common features:

• Audio playback and recording
• Basic MIDI playback
• Metadata extraction

[edit]OpenMAX IL (Integration Layer)

OpenMAX ILDeveloper(s)Khronos Group, Inc.Stable release1.1.2 / September 15, 2008Operating systemCross-platformTypeAPILicenseVariousWebsiteKhronos Group, Inc.

The OpenMAX IL API strives to give media components portability across an array of platforms using theC-language. In the OpenMAX IL, components represent individual blocks of functionality. Components can be sources, sinks, codecs, filters, splitters, mixers, or any other data operator. Depending on the implementation, a component could possibly represent a piece of hardware, a software codec, another processor, or a combination thereof.

The interface abstracts the hardware and software architecture in the system. The OpenMAX IL API allows the user to load, control, connect, and unload the individual components. This flexible core architecture allows the Integration Layer to easily implement almost any media use case and mesh with existing graph-based media frameworks. The key focus of the OpenMAX IL API is portability of media components

The OpenMAX IL API design devotes particular attention to use case flexibility and optimized data transfers between components.

Open source OpenMAX IL implementations are available,

• Bellagio, is maintained by STMicroelectronics.
• LIM OpenMAX, an implementation that has both AL and IL.

[edit]OpenMAX DL (Development Layer)

OpenMAX DLDeveloper(s)Khronos Group, Inc.Stable release1.0.2 / December 21, 2007Operating systemCross-platformTypeAPILicenseVariousWebsiteKhronos Group, Inc.

The OpenMAX DL API defines a set of low-level multimedia kernels or media processing building blocks. The building blocks might be used to accelerate traditional computational hotspots within standardized mediacodecs and other integrated media processing engines. The functional scope of the OpenMAX DL interface spans several domains includingSignal processing and Image processing, audio coding, image coding, and video coding.

OpenMAX DL is split into five application domains:

• AC - Audio Codecs (MP3 decoder and AAC decoder components)
• IC - Image Codecs (JPEG components)
• IP - Image Processing (Generic image processing functions)
• SP - Signal Processing (Generic audio processing functions)
• VC - Video Codecs (H264 and MP4 components)

OpenMAX DL is, among other companies, openmax_armlibraries implemented by ARM and ANSI C sample code can be downloaded from their webpage.

The OpenMAX API is supported by the PlayStation 3 console.

[edit]OpenMAX Working Group

The OpenMAX Working Group was founded alongside sister project OpenVG on July 6th, 2004. Promoting members (2008-01-17) are AMD, Apple, ARM, Creative, Dell Inc, Ericsson,Freescale, Imagination Technologies Group plc, Intel, IBM, Motorola, Nokia,Nvidia Corporation, Samsung Electronics Co. Ltd, SK Telecom, Sony Computer Entertainment Inc, Sun Microsystems Inc and Texas Instruments.

OpenMAX API documentation is publicly available on the Khronos website.

[edit]See also

• Video Acceleration API (VA API)
• VDPAU (Video Decode and Presentation API for Unix)
• X-Video Bitstream Acceleration (XvBA)
• X-Video Motion Compensation (XvMC)
• DirectX Video Acceleration (DxVA) API -Microsoft Windows analogue
• Distributed Codec Engine (libcde) is aTexas Instruments API for the video codec engine in OMAP based embedded systems
• Video Decode Acceleration Framework isApple Inc.s API for hardware-accelerated decoding of H.264 onMac OS X
• VideoToolBox is an undocumented API fromApple Inc. for hardware-accelerated decoding onApple TV andMac OS X 10.5 or later.^[3]
• OpenVideo Decode (OVD) – an new open cross-platform video acceleration API fromAMD.^[4]
• Nvidia PureVideo - thebit-stream technology from NVIDIA used in their graphics chips to accelerate video decoding on hardware GPU.
• UVD (Unified Video Decoder) - thebit-stream technology from ATI Technologies used in their graphics chips to accelerate video decoding on hardwareGPU.

[edit]References

1. ^Khronos Group Releases OpenMAX AL Specification for Application-level Video, Audio and Image Processing on Mobile and Handheld Devices, Khronos press release
2. ^http://developer.android.com/sdk/android-4.0-highlights.html
3. ^http://www.tuaw.com/2011/01/20/xbmc-for-ios-and-atv2-now-available/ XBMC for iOS and Apple TV now available
4. ^http://developer.amd.com/gpu/AMDAPPSDK/assets/OpenVideo_Decode_API.PDF OpenVideo Decode (OVD) API

[edit]External links

• Khronos Group — OpenMAX Overview and API specifications
• Khronos Group — Public API Registry
• Khronos Group — OpenMAX AL 1.1 Specification
• Khronos Group — OpenMAX IL 1.1.2 Specification
• Khronos Group — OpenMAX DL 1.0.2 Specification
• Public forums
• Khronos Group — Press Releases — OpenMAX
• ARM - Free OpenMAX Library
• Mentor Graphics - Nucleus MMF Leverages OpenMAX IL
• Mentor Graphics - Press Release, Mentor Achieves Industry-First OpenMAX Conformance for Nuclues OS Multimedia Framework