Editing OpenMAX (section)

==Integration layer==
{{Infobox software
| name                   = OpenMAX IL
| logo                   = [[File:OpenMAX IL Logo.svg|OpenMAX IL Logo|220px]]
| developer              = Khronos Group
| latest_release_version = 1.1.2
| latest_release_date    = {{Start date and age|2008|09|15}}
| latest preview version = 1.2.0
| latest_preview_date    = {{Start date and age|2011|11|07}}
| operating_system       = [[Cross-platform]]
| genre                  = [[Application programming interface|API]]
| license                = Various
}}
The OpenMAX IL API strives to give media components portability across an array of platforms using the [[C (programming language)|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.<ref>{{Cite book |last=The Khronos Group |title=OpenMAX™ Integration Layer Application Programming Interface Specification: Version 1.2.0 Provisional |date=2011-11-07 |publisher=The Khronos Group Inc. |edition=1.2.0.0 |language=en}}</ref>

=== Implementations===
* [http://tizonia.org Tizonia] is an open source OpenMAX IL implementation for Linux that supports version 1.2.0.<ref>{{Cite web|url = http://www.juanrubio.me/2013/01/announcing-tizonia-openmax-il/|title = Announcing Tizonia OpenMAX IL|access-date = 2013-12-04|archive-date = 2014-11-12|archive-url = https://web.archive.org/web/20141112121026/http://www.juanrubio.me/2013/01/announcing-tizonia-openmax-il/|url-status = dead}}</ref>
* [http://omxil.sourceforge.net Bellagio] is an open source OpenMAX IL implementation for Linux maintained by [[STMicroelectronics]].<ref>{{Cite web|url = http://elinux.org/images/e/e0/The_OpenMAX_Integration_Layer_standard.pdf|title = The OpenMAX Integration Layer standard}}</ref>
* [http://limoa.sourceforge.net/ LIM OpenMAX] is an open source implementation of OpenMAX AL and OpenMAX IL for Linux.
* [[Mesa (computer graphics)|Mesa]] provides hardware accelerated drivers that can be used with Bellagio or Tizonia.<ref>{{cite mailing list |url=https://lists.freedesktop.org/archives/mesa-dev/2013-October/046943.html |title=OpenMAX state tracker |date=24 October 2013 |access-date=28 November 2015 |mailing-list=mesa-dev |last=König |first=Christian}}</ref><ref>{{Cite web|url = https://summerofcode.withgoogle.com/archive/2017/projects/6355967214092288|title = Add OpenMAX state tracker in Mesa/Gallium that uses Tizonia}}</ref>
* [https://android.googlesource.com/platform/frameworks/av/+/nougat-mr2.1-release/media/libstagefright/omx/ Android StageFright], a partial implementation of IL that is the de facto standard.