Jump to content

OpenMAX

From Wikipedia, the free encyclopedia
(Redirected from OpenMAX IL)
OpenMAX
Developer(s)Khronos Group
Websitewww.khronos.org/openmax/

OpenMAX (Open Media Acceleration), 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.[1][2] It is intended for low power and embedded system devices (including smartphones, game consoles, digital media players, and set-top boxes) 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.[3]

OpenMAX provides three layers of interfaces: application layer (AL), integration layer (IL) and development layer (DL). OpenMAX is managed by the non-profit technology consortium Khronos Group.[4]

History

[edit]

Initially announced in July 2004.[5] 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.[6] The last draft produced by the OpenMAX Working Group (1.2.0) dates from 2011[7] and no product has been declared as conformant since 2012.[8] 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.[9]

Layers

[edit]

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 application programming interface (API).[10]

OpenMAX IL is the interface between media framework, (such as StageFright or MediaCodec API on Android, DirectShow on Windows, FFmpeg or GStreamer on Linux), and a set of multimedia components (such as an audio or video codecs). It allows companies that build platforms (e.g. allowing an implementation of an MP3 player) to easily change components like MP3 decoders and Equalizer effects and buy components for their platform from different vendors.[11]

OpenMAX DL is the interface between physical hardware, such as digital signal processor (DSP) 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

[edit]
OpenMAX AL
Developer(s)Khronos Group
Stable release
1.1 / January 18, 2011; 13 years ago (2011-01-18)
Operating systemCross-platform
TypeAPI
LicenseVarious
Websitewww.khronos.org/openmax/ Edit this on Wikidata

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

[edit]

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

Digital TV extension

[edit]

A digital television (DTV) extension specification of OpenMAX AL adds standards-agnostic mobile TV tuning, playback, recording and electronic program guide functionality to OpenMAX AL Multimedia API, as a modular royalty-free, cross-platform C-language API for high-performance digital TV-related applications on mobile and embedded devices. DTV Extension is compatible with all major mobile TV standards (e.g. DVB-H, ISDB-T, T-DMB, etc.), and supports broadcast, unicast and multicast delivery methods for Digital TV.[12][13]

Specification versions

[edit]

Implementations

[edit]

Comparison with OpenSL ES

[edit]

OpenSL ES (Open Sound Library for Embedded Systems) is another Khronos Group API that also provides an audio library for the same target market as OpenMAX AL, while OpenMAX target the complete multimedia services. OpenSL ES and OpenMAX AL audio subset share the same common architecture and have a few common features:

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

Integration layer

[edit]
OpenMAX IL
Developer(s)Khronos Group
Stable release
1.1.2 / September 15, 2008; 16 years ago (2008-09-15)
Preview release
1.2.0 / November 7, 2011; 13 years ago (2011-11-07)
Operating systemCross-platform
TypeAPI
LicenseVarious
Websitewww.khronos.org/openmax/ Edit this on Wikidata

The OpenMAX IL API strives to give media components portability across an array of platforms using the C-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.

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.[16]

Implementations

[edit]
  • Tizonia is an open source OpenMAX IL implementation for Linux that supports version 1.2.0.[17]
  • Bellagio is an open source OpenMAX IL implementation for Linux maintained by STMicroelectronics.[18]
  • LIM OpenMAX 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.[19][20]
  • Android StageFright, a partial implementation of IL that is the de facto standard.

Development layer

[edit]
OpenMAX DL
Developer(s)Khronos Group
Stable release
1.0.2 / December 21, 2007; 16 years ago (2007-12-21)
Operating systemCross-platform
TypeAPI
LicenseVarious
Websitewww.khronos.org/openmax/ Edit this on Wikidata

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 media codecs and other integrated media processing engines. The functional scope of the OpenMAX DL interface spans several domains including signal 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 (H.264 and MP4 components)

Implementations

[edit]

Working group

[edit]

The OpenMAX working group was founded alongside sister project OpenVG on July 6, 2004. Promoting members in 2008 were 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 and Texas Instruments.

See also

[edit]

References

[edit]
  1. ^ http://www.cnx-software.com/2011/11/11/openmax-open-media-acceleration/ OpenMAX (Open Media Acceleration)
  2. ^ https://events.linuxfoundation.org/images/stories/pdf/lceu2012_debski.pdf Archived 2014-01-06 at the Wayback Machine Video4Linux2 - Path to a Standardized Video Codec API
  3. ^ http://jan.newmarch.name/LinuxSound/Sampled/OpenMAX/ Archived 2016-03-12 at the Wayback Machine Contents of full book "Linux Sound" - Chapter 13: OpenMAX/OpenSL
  4. ^ http://www.khronos.org/openmax/ OpenMAX - The Standard for Media Library Portability (by Khronos Group)
  5. ^ "Khronos Group Announces New OpenMAX Open Standard for Enabling Effective Media Acceleration". 6 July 2004.
  6. ^ https://www.khronos.org/files/openmax_il_spec_1_0.pdf [bare URL PDF]
  7. ^ "Khronos OpenMAX IL Registry - the Khronos Group Inc".
  8. ^ "The Khronos Group". 21 November 2021.
  9. ^ "Include/Media/Openmax/OMX_VideoExt.h - platform/Frameworks/Native - Git at Google".
  10. ^ http://elinux.org/images/e/e0/The_OpenMAX_Integration_Layer_standard.pdf The OpenMAX Integration Layer standard
  11. ^ http://elinux.org/images/5/52/Elc2011_garcia.pdf Integrating a Hardware Video Codec into Android Stagefright using OpenMAX IL
  12. ^ http://www.khronos.org/openmax/al/dtv/ OpenMAX AL - Digital Television (DTV) Extension
  13. ^ https://www.khronos.org/news/press/khronos-group-releases-provisional-openmax-al-digital-tv-extension-specific Khronos Group Releases Provisional OpenMAX AL Digital TV Extension Specification
  14. ^ Khronos Group Releases OpenMAX AL Specification for Application-level Video, Audio and Image Processing on Mobile and Handheld Devices Archived 2011-03-17 at the Wayback Machine, Khronos press release
  15. ^ "Ice Cream Sandwich".
  16. ^ https://www.khronos.org/registry/OpenMAX-IL/specs/OpenMAX_IL_1_2_0_Specification.pdf [bare URL PDF]
  17. ^ "Announcing Tizonia OpenMAX IL". Archived from the original on 2014-11-12. Retrieved 2013-12-04.
  18. ^ "The OpenMAX Integration Layer standard" (PDF).
  19. ^ König, Christian (24 October 2013). "OpenMAX state tracker". mesa-dev (Mailing list). Retrieved 28 November 2015.
  20. ^ "Add OpenMAX state tracker in Mesa/Gallium that uses Tizonia".
  21. ^ "Khronos Standards - ARM". 12 September 2022. Archived from the original on 2013-10-04.
  22. ^ "Using NEON optimized libraries". 12 September 2022.
  23. ^ "VideoToolbox - Apple Developer Documentation". developer.apple.com. Retrieved 2018-08-05.
  24. ^ "Archived copy" (PDF). Archived from the original (PDF) on 2011-04-09. Retrieved 2012-01-16.{{cite web}}: CS1 maint: archived copy as title (link) OpenVideo Decode (OVD) API
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=OpenMAX&oldid=1258241279#Integration_layer"