12 <concept xml:lang="en" id="GUID-CC95D475-98B9-5279-94BD-1E12449AC0CC"><title>OpenMAX IL Overview</title><prolog><metadata><keywords/></metadata></prolog><conbody><p>This document introduces you to the Symbian approach to OpenMAX IL (Integration Layer). </p> <section><title>Purpose</title> <p>OpenMAX IL is a low-level interface used in mobile devices that allows the Multimedia Device Framework (MDF) to </p> <ul><li id="GUID-F57898EA-3992-5CB2-8ADB-95A4F2C193FF"><p>load audio, video and imaging components </p> </li> <li id="GUID-73031271-DB54-5A75-B8B2-6F4105AA3478"><p>control audio, video and imaging components </p> </li> <li id="GUID-83BF7642-A5C0-52AB-9FCB-738761388461"><p>connect audio, video and imaging components </p> </li> <li id="GUID-6E101230-E4C7-5554-84FE-F8F1AE9819F4"><p>unload audio, video and imaging components. </p> </li> </ul> </section> <section><title>Required background</title> <p>You should be familiar with the <xref scope="external" href="http://www.khronos.org/openmax/">OpenMAX IL</xref> standard developed by The Khronos Group, which enables the portability of media components across any OS platform. </p> </section> <section><title>Key concepts/terms</title> <p>The following terms are introduced here and will be used throughout this documentation: </p> <dl><dlentry><dt>OpenMAX IL Client</dt> <dd><p>MDF plays the role of the OpenMAX IL client within the OpenMAX IL architecture. </p> </dd> </dlentry> </dl> <dl><dlentry><dt>OpenMAX IL Core </dt> <dd><p>OpenMAX IL Core is a platform-specific entity which is used to load and unload OpenMAX IL Components, and to facilitate communication between them. </p> </dd> </dlentry> </dl> <dl><dlentry><dt>OpenMAX IL Component </dt> <dd><p>OpenMAX IL Component is an individual block of functionality such as codec, source, sink, filter, splitter, mixer, or any data processing functionality. </p> </dd> </dlentry> </dl> <dl><dlentry><dt>OpenMAX IL Content Pipe</dt> <dd><p>OpenMAX IL Content Pipe is an entity that provides abstraction of access to content data. </p> </dd> </dlentry> </dl> <p> <b>Note:</b> The <xref href="GUID-CC95D475-98B9-5279-94BD-1E12449AC0CC.dita#GUID-CC95D475-98B9-5279-94BD-1E12449AC0CC/GUID-E8EEF013-A773-5848-BF97-7F44D770ECE2">OpenMAX IL libraries</xref> have the same naming convention as the key terms described above. </p> </section> <section><title>Architectural relationships</title> <p>MDF interacts with OpenMAX IL to communicate with the OpenMAX IL Components. </p> <fig id="GUID-ABCCFEF8-6D51-5B16-89EE-0A9451B202D9"><title> |
12 <concept xml:lang="en" id="GUID-CC95D475-98B9-5279-94BD-1E12449AC0CC"><title>OpenMAX IL Overview</title><prolog><metadata><keywords/></metadata></prolog><conbody><p>This document introduces you to the Symbian approach to OpenMAX IL (Integration Layer). </p> <section><title>Purpose</title> <p>OpenMAX IL is a low-level interface used in mobile devices that allows the Multimedia Device Framework (MDF) to </p> <ul><li id="GUID-F57898EA-3992-5CB2-8ADB-95A4F2C193FF"><p>load audio, video and imaging components </p> </li> <li id="GUID-73031271-DB54-5A75-B8B2-6F4105AA3478"><p>control audio, video and imaging components </p> </li> <li id="GUID-83BF7642-A5C0-52AB-9FCB-738761388461"><p>connect audio, video and imaging components </p> </li> <li id="GUID-6E101230-E4C7-5554-84FE-F8F1AE9819F4"><p>unload audio, video and imaging components. </p> </li> </ul> </section> <section><title>Required background</title> <p>You should be familiar with the <xref scope="external" href="http://www.khronos.org/openmax/">OpenMAX IL</xref> standard developed by The Khronos Group, which enables the portability of media components across any OS platform. </p> </section> <section><title>Key concepts/terms</title> <p>The following terms are introduced here and will be used throughout this documentation: </p> <dl><dlentry><dt>OpenMAX IL Client</dt> <dd><p>MDF plays the role of the OpenMAX IL client within the OpenMAX IL architecture. </p> </dd> </dlentry> </dl> <dl><dlentry><dt>OpenMAX IL Core </dt> <dd><p>OpenMAX IL Core is a platform-specific entity which is used to load and unload OpenMAX IL Components, and to facilitate communication between them. </p> </dd> </dlentry> </dl> <dl><dlentry><dt>OpenMAX IL Component </dt> <dd><p>OpenMAX IL Component is an individual block of functionality such as codec, source, sink, filter, splitter, mixer, or any data processing functionality. </p> </dd> </dlentry> </dl> <dl><dlentry><dt>OpenMAX IL Content Pipe</dt> <dd><p>OpenMAX IL Content Pipe is an entity that provides abstraction of access to content data. </p> </dd> </dlentry> </dl> <p> <b>Note:</b> The <xref href="GUID-CC95D475-98B9-5279-94BD-1E12449AC0CC.dita#GUID-CC95D475-98B9-5279-94BD-1E12449AC0CC/GUID-E8EEF013-A773-5848-BF97-7F44D770ECE2">OpenMAX IL libraries</xref> have the same naming convention as the key terms described above. </p> </section> <section><title>Architectural relationships</title> <p>MDF interacts with OpenMAX IL to communicate with the OpenMAX IL Components. </p> <fig id="GUID-ABCCFEF8-6D51-5B16-89EE-0A9451B202D9"><title> |
14 </title> <image href="GUID-B39483E2-15FC-5214-8B45-58BBB68A7841_d0e536764_href.png" placement="inline"/></fig> <p>OpenMAX IL Core uses OpenMAX IL Loader to load and unload OpenMAX IL Components. The high-level view of the Symbian implementation of OpenMAX IL using the OpenMAX IL Loader pattern is shown below: </p> <fig id="GUID-D74D16AF-33D3-55CC-B39A-BC1A686064C0"><title> |
14 </title> <image href="GUID-B39483E2-15FC-5214-8B45-58BBB68A7841_d0e544224_href.png" placement="inline"/></fig> <p>OpenMAX IL Core uses OpenMAX IL Loader to load and unload OpenMAX IL Components. The high-level view of the Symbian implementation of OpenMAX IL using the OpenMAX IL Loader pattern is shown below: </p> <fig id="GUID-D74D16AF-33D3-55CC-B39A-BC1A686064C0"><title> |
16 </title> <image href="GUID-F618EE02-927E-584B-8F80-79DE766AA62F_d0e536773_href.png" placement="inline"/></fig> </section> <section id="GUID-E8EEF013-A773-5848-BF97-7F44D770ECE2"><title>OpenMAX IL library summary</title> <p>The Symbian platform provides support to OpenMAX IL with the following libraries: </p> <dl><dlentry><dt>OpenMAX IL Core</dt> <dd><p>OpenMAX IL Core handles the IL client requests to load or unload components by delegating these requests to the appropriate OpenMAX IL Loader. OpenMAX IL Core also facilitates communication with these components. For more information see <xref href="GUID-148B1188-8007-5077-A813-50F728CAC5D5.dita">OpenMAX IL Core Overview</xref>. </p> </dd> </dlentry> </dl> <dl><dlentry><dt>OpenMAX IL Loader Interface</dt> <dd><p>You need to install the OpenMAX IL Loader interface, which is an ECom plug-in. This interface is used to instantiate and access a group of OpenMAX IL Components. For more information see <xref href="GUID-F97ABEDE-C318-5EA2-B8CB-6510725413A0.dita">OpenMAX IL Loader Interface Overview</xref>. </p> </dd> </dlentry> </dl> <dl><dlentry><dt> OpenMAX IL Component Interface</dt> <dd><p>You need to install the OpenMAX IL Component interface, which is an ECom plug-in. This interface is loaded by OpenMAX IL Loader to provide access to OpenMAX IL Component. For more information see <xref href="GUID-24D99069-438E-5CC4-90B6-5609A2E50953.dita">OpenMAX IL Component Overview</xref>. </p> </dd> </dlentry> </dl> <dl><dlentry><dt>OpenMAX IL Content Pipe Interface</dt> <dd><p>You need to install the OpenMAX IL Content Pipe interface, which is an ECom plug-in. This interface is loaded by OpenMAX IL Core to provide access to OpenMAX IL Content Pipe. For more information see <xref href="GUID-89CFD892-16B0-5B70-AE46-D4BFB8412BC4.dita">OpenMAX IL Content Pipe Overview</xref>. </p> </dd> </dlentry> </dl> </section> <section><title>Typical uses</title> <p>OpenMAX IL Components are used like any typical Multimedia features such as playing video, recording audio and capturing images. For example, two OpenMAX IL Components, decoder and render, are loaded by OpenMAX IL and communicate with each other for decoding and rendering. </p> </section> </conbody></concept> |
16 </title> <image href="GUID-F618EE02-927E-584B-8F80-79DE766AA62F_d0e544233_href.png" placement="inline"/></fig> </section> <section id="GUID-E8EEF013-A773-5848-BF97-7F44D770ECE2"><title>OpenMAX IL library summary</title> <p>The Symbian platform provides support to OpenMAX IL with the following libraries: </p> <dl><dlentry><dt>OpenMAX IL Core</dt> <dd><p>OpenMAX IL Core handles the IL client requests to load or unload components by delegating these requests to the appropriate OpenMAX IL Loader. OpenMAX IL Core also facilitates communication with these components. For more information see <xref href="GUID-148B1188-8007-5077-A813-50F728CAC5D5.dita">OpenMAX IL Core Overview</xref>. </p> </dd> </dlentry> </dl> <dl><dlentry><dt>OpenMAX IL Loader Interface</dt> <dd><p>You need to install the OpenMAX IL Loader interface, which is an ECom plug-in. This interface is used to instantiate and access a group of OpenMAX IL Components. For more information see <xref href="GUID-F97ABEDE-C318-5EA2-B8CB-6510725413A0.dita">OpenMAX IL Loader Interface Overview</xref>. </p> </dd> </dlentry> </dl> <dl><dlentry><dt> OpenMAX IL Component Interface</dt> <dd><p>You need to install the OpenMAX IL Component interface, which is an ECom plug-in. This interface is loaded by OpenMAX IL Loader to provide access to OpenMAX IL Component. For more information see <xref href="GUID-24D99069-438E-5CC4-90B6-5609A2E50953.dita">OpenMAX IL Component Overview</xref>. </p> </dd> </dlentry> </dl> <dl><dlentry><dt>OpenMAX IL Content Pipe Interface</dt> <dd><p>You need to install the OpenMAX IL Content Pipe interface, which is an ECom plug-in. This interface is loaded by OpenMAX IL Core to provide access to OpenMAX IL Content Pipe. For more information see <xref href="GUID-89CFD892-16B0-5B70-AE46-D4BFB8412BC4.dita">OpenMAX IL Content Pipe Overview</xref>. </p> </dd> </dlentry> </dl> </section> <section><title>Typical uses</title> <p>OpenMAX IL Components are used like any typical Multimedia features such as playing video, recording audio and capturing images. For example, two OpenMAX IL Components, decoder and render, are loaded by OpenMAX IL and communicate with each other for decoding and rendering. </p> </section> </conbody></concept> |