Multimedia OpenMAX integration
Captures the requirements and dependencies of the OpenMAX integration for the Multimedia WG. Vendor Survey, including code study and summarizing the issues, verification of compliance in the presented code. Publication of any findings. Reference implementation
Blueprint information
- Status:
- Not started
- Approver:
- Kurt Taylor
- Priority:
- High
- Drafter:
- Kurt Taylor
- Direction:
- Needs approval
- Assignee:
- Benjamin Gaignard
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Summit Actions and Closure Notes
ACTION: collect source code
TI gstreamer components (and gst-openmax and gst-ducati) https:/
Freescale Android OMX Components
Note that Freescale doesn't use Stagefright directly, but their own Graph Manager framework
Graph Manager itself is an IL client, and interfaces with OMX components
Do implement complete OMX graph (parsers, clock, etc)
Look at Android OMX standard glue
ACTION (Kiko): identify OpenMAX representatives from members
Nikhil (TI)
Thierry (ST-Ericsson)
Jim (Nvidia)
Bryan Murray (Freescale)
(ARM; no OMX rep)
ACTION (Kiko): set up call with QC/Nvidia to talk about VDPAU/VAAPI as an alternative
ACTION (Rob, Kurt): set up wikipage to collect input for API; collect survey data here
ACTION (Kurt, Kiko): share initial set with Google, Linaro TSC and collect input
ACTION: Jim/Kurt/Thierry call with Neil to define collaboration model
ACTION: study how to formally communicate to OMX IL WG Tuesday meeting
ACTION: prepare reference for OpenMAX F2F meeting (Phoenix, September)
Work Items
Dependency tree
* Blueprints in grey have been implemented.