OpenSL ES & OpenMAX Multimedia APIs

Transcription

1 Copyright Khronos Group, Page 1 OpenSL ES & OpenMAX Multimedia APIs Erik Noreke Chair of OpenSL ES Working Group Chair of OpenMAX AL Working Group

2 Copyright Khronos Group, Page 4 Why Create Khronos Multimedia APIs? Khronos APIs Conformance Tests Portable IP Protection Profiles & Components Predictable set of functionality Open Source Framework Free to change Every implementation unique GPL license Plugins Functionality dependent on implementation

3 Integration Layer Copyright Khronos Group, Page 5

4 Copyright Khronos Group, Page 6 OpenMAX IL Portable Media Integration Low-level interface for audio, video, and imaging codecs Developed for embedded and mobile devices Enables interfacing with multimedia components in a unified manner Allows components to be any combination of hardware or software completely transparently to the media chain The goal of OpenMAX IL is to abstract multimedia components - Combat the problem of integration portability - Consistent functionality

5 Copyright Khronos Group, Page 7 OpenMAX IL Component Networks Enables arbitrary multimedia pipelines by plugging blocks together - Componentized architecture abstracts multimedia functionality block interfaces Wide variety of building blocks for imaging, video and audio functions - Encode, decode, apply an effect, capture, render, split, mix, etc Enables blocks from different sources to work together - Blocks can be implemented in software or hardware Portable & Re-usable streaming media building blocks

6 OpenMAX IL Example Graph Standardized component interfaces enable flexible media graphs Includes multi-stream synchronization Allows for custom plug-ins OpenMAX Component Interfaces Enables components to be flexibly connected in any graph topology E.g. send dance beats to 3D application for visualization AAC Audio Audio Decoder Plug-in Audio Renderer Speakers *.mp4 / *.3gp File Reader Clock for AV Sync MPEG4/ H.264 Video Video Decoder Time Data Decompressed Video Video Scheduler Video Renderer Display Example: MPEG-4 video synchronized with AAC audio decode Copyright Khronos Group, Page 8

7 Copyright Khronos Group, Page 9 & Application Access Layer

8 Copyright Khronos Group, Page 10 The Need for Application Access Hardware and low level access is powerful but complex - More power than most application developers require Most application developers just want to playback and record media - Specifying where the content comes from - Specifying where the content should be rendered to - Manipulate a few playback controls - Have simple configurability That are what OpenMAX AL and OpenSL ES provide - Simple high-level multimedia APIs for playback and recording use cases - With hardware acceleration capabilities built in With Cross-platform portability - No need to rewrite an application for every platform

9 Copyright Khronos Group, Page 11 OpenMAX AL Focused on Streaming Media Media playback and recording - Playback and recording of everything from video files to radio to camera input Full range of video effects and controls including playback rate, post processing, and image manipulation - Apply advanced effects to captured images and video before sending to friends Complete metadata support - Read, Edit, and Set the metadata for most types of content OpenMAX AL gives easy access to streaming media - Allowing time to be spent on developing applications, not using frameworks Designed as a complete set of multimedia functionality - Unlike any other streaming media API

10 Copyright Khronos Group, Page 12 OpenSL ES Powerful Mobile Audio Full range of effects and controls, including advanced 3D effects such as Doppler and virtualization - Experience rich, enhanced sound from locations other than the handset, even moving, for the ultimate multimedia experience Create theater quality audio experience - In a mobile device! Full 3D audio functionality enhances any gaming experience - Perfect companion to OpenGL ES Designed for implementation by either a hardware or software solution - Take full advantage of system capabilities

11 Copyright Khronos Group, Page 13 Object Oriented Media Access Simplified object-oriented streaming media - Built to enable common use cases - But also has access to advanced functionality Media Objects enable PLAY and RECORD of content - Media Objects input and output to Devices - Perform some operation on an input and emit the result as output Objects have control interfaces - Play, Record, Seek, Rate Media Input Audio Mix Camera (AL) Display Window (AL) URI DSrc Player Object DSnk URI Memory Memory Content pipe Content pipe

12 OpenMAX AL & OpenSL ES Copyright Khronos Group, Page 14

13 Copyright Khronos Group, Page 15 OpenSL ES and OpenMAX AL Working groups collaborated to define the common API functionality Independent, Compatible, Consistent and Distinct Audio Effects Advanced MIDI 3D Audio Buffer queues Audio Playback Audio Recording Basic MIDI Video playback Video recording Radio and RDS Camera Image capture & display

14 Copyright Khronos Group, Page 16 Why Profiles? Functionality divided into basic groups - Most common groupings Profiles reduce fragmentation - Not all devices support all functionality - Only support the profiles you need Applications can query available profiles - To adapt to the current device - Facilitates porting of applications Profiles can be combined - To best suit any product Optional features - Some features are optional in all profiles - APIs are consistent when feature is available

15 Copyright Khronos Group, Page 17 OpenSL ES and OpenMAX AL Independent - But designed to work together - No dependency between the APIs either one can exist by itself Compatible - Working groups collaborated to make sure the APIs work together well Consistent - Identical API architecture - Identical APIs for same functionality Distinct - OpenMAX AL represents basic multimedia functionality (audio, video, and image) - OpenSL ES represents advanced audio functionality

16 Copyright Khronos Group, Page 18 OpenSL ES / OpenMAX AL Implemented on top of OpenMAX IL OR URI DataSource Media Player Output Mix File Reader Audio Decoder Audio Effect Audio Mixer Audio Sink Clock

17 Copyright Khronos Group, Page 19 Complete Multimedia Use-Case Audio stream to DSP 3D Audio Rendering Multimedia Processing Application on CPU Video stream to GPU EGLStream OpenGL ES GL_TEXURE_EXTERN AL_OES texture OpenGL ES EGLSurface Much more flexibility than just show a video

18 Copyright Khronos Group, Page 20 Android NDK for Multimedia NDK Native Development Kit Introduced in Android 2.3 Gingerbread Advanced Audio Mobile 3D

19 Copyright Khronos Group, Page 21 Why the NDK? Better control of fuctionality and timing Access to hardware acceleration Multimedia is the primary reason for the NDK Increases application complexity Requires compilation for each platform family - ARMv5TE - ARMv7-A - x86 instructions

20 Copyright Khronos Group, Page 22 Focus is on Standardized APIs Earlier internal APIs not stable enough Avoid fragmentation Well tested and documented Focus on functionality - Not on implementation Access to hardware acceleration

21 Copyright Khronos Group, Page 23 Native Multimedia APIs in Android 2.3 OpenGL ES 2.0 EGL 1.4 OpenSL ES Partial implementation - Almost complete Phone + Music profiles - Buffer queues from 1.1 as Android extension - Google version compliant as far as implemented - Other vendors offer fully compliant solution Mobile 3D Graphics Context Management Advanced Audio

22 Copyright Khronos Group, Page 24 Ice Cream Sandwich Android 4.0 Same OS for both phones and tablets Better multitasking Better support for hardware accelerated graphics DRM Partial OpenMAX AL implementation - Streaming use-case only - Does not interoperate with OpenSL ES Streaming Media

23 Copyright Khronos Group, Page 25 Android & OpenMAX IL Android uses OpenMAX IL in their Multimedia framework - Codecs only - No graph building Main Multimedia framework is still Stagefright - Introduced in Éclair Allows for both software implemented and hardware accelerated codecs Not part of NDK - Not intended to be accessible from applications

24 What is Google saying? Copyright Khronos Group, Page 26

25 What is Google saying? Copyright Khronos Group, Page 27

26 What is Google saying? Copyright Khronos Group, Page 28

27 Copyright Khronos Group, Page 29 Where is Android Headed? Fler enheter - TV? - Netbooks? - Chrome OS? What does the future hold? - Compliant OpenSL ES? - Better OpenMAX AL support? - OpenMAX AL EGL Stream Extension? - Support for OpenCL? - Content Pipes? Its anybody s guess!

28 Any Questions? Copyright Khronos Group, Page 30

29 Thank You Copyright Khronos Group, Page 31