OpenMAX
OpenMAX, often shortened as "OMX", is a non-proprietary and royalty-free cross-platform set of C-language programming interfaces. It provides abstractions for routines that are especially useful for processing of audio, video, and still images. It is intended for low power and embedded system devices that need to efficiently process large amounts of multimedia data in predictable ways, such as video codecs, graphics libraries, and other functions for video, image, audio, voice and speech.
OpenMAX provides three layers of interfaces: application layer, integration layer and development layer. OpenMAX is managed by the non-profit technology consortium Khronos Group.
History
Initially announced in July 2004. The OpenMAX Working Group was initially founded by members ARM, Motorola, Samsung, STMicroelectronics, and Texas Instruments. Version 1.0 of the specification was published in December 2005. The last draft produced by the OpenMAX Working Group dates from 2011 and no product has been declared as conformant since 2012. The OpenMAX specification were never updated to support recent codecs like HEVC or VP9, making Android the de facto source of updates to the OpenMAX IL standard.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 that support the OpenMAX AL application programming interface.OpenMAX IL is the interface between media framework,, and a set of multimedia components. It allows companies that build platforms 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 as digital signal processor chips, CPUs, GPUs, 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.
Application layer
OpenMAX AL accommodates common multimedia application use cases by standardizing a set of representative objects, 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 for mobile 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.
Features
OpenMAX AL features include:- Video playback and recording
- Audio playback and recording
- Image capture and display
- Camera controls
- Radio and RDS
- Basic MIDI playback
- Metadata extraction and insertion
Digital TV extension
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.
- - dated 2009-06-23
- - dated 2010-03-12
- - dated 2011-01-18
Implementations
- Android 4.0 and later exposes OpenMAX AL as part of its NDK.
- is an open source implementation of OpenMAX AL and OpenMAX IL for Linux.
Comparison with OpenSL ES
- Audio playback and recording
- Basic MIDI playback
- Metadata extraction
Integration layer
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.
The OpenMAX IL API was chosen as the base for the API to integrate Audio and Video codecs on Android, which has resulted in most SoC vendors shipping a minimal implementation that only supports the subset required by Android. Applications do not use those OpenMAX IL components directly, but only through the Android MediaCodec API. Android's subset of OpenMAX IL with its extensions is now the de facto standard.
In 2011 the provisional version 1.2.0 was released.
Implementations
- is an open source OpenMAX IL implementation for Linux that supports version 1.2.0.
- is an open source OpenMAX IL implementation for Linux maintained by STMicroelectronics.
- is an open source implementation of OpenMAX AL and OpenMAX IL for Linux.
- Mesa provides hardware accelerated drivers that can be used with Bellagio or Tizonia.
- , a partial implementation of IL that is the de facto standard.
Development layer
OpenMAX DL is split into five application domains:
- AC - Audio Codecs
- IC - Image Codecs
- IP - Image Processing
- SP - Signal Processing
- VC - Video Codecs
Implementations
- Optimized implementations for NEON and SIMD, as well as an ANSI C reference implementation, were previously available from ARM for registered users.
- The OpenMAX API is supported by the PlayStation 3 console.
Working group