Search
×
FR

Placeholder headline

This is just a placeholder headline

MSS SP-44-2026: Steel Pipeline Flanges

$

450

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 576: Inspection of Pressure-relieving Devices

$

460

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 591: Process Valve Qualification Procedure

$

226

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 576: Inspection of Pressure-relieving Devices: Addendum 1

$

0

BUY NOW

Placeholder headline

This is just a placeholder headline

API Technical Report TDB-6 Chapter 6 – Density

$

204

BUY NOW

Placeholder headline

This is just a placeholder headline

API STD 560: Fired Heaters for General Refinery Services

$

721

BUY NOW

Placeholder headline

This is just a placeholder headline

API STD 64: Diverter Equipment Systems

$

324

BUY NOW

Placeholder headline

This is just a placeholder headline

API MPMS CH 17.10.1: Refrigerated Light Hydrocarbon Fluids – Measurement of Cargoes on Board LNG Carries

$

417

BUY NOW

ISO 23006:2016

ISO 23006:2016 Information technology – Multimedia service platform technologies – Part 2: MPEG extensible middleware (MXM) API

CDN $312.00

Description

ISO/IEC 23006-2:2016 specifies a set of Application Programming Interfaces (called for short MXM APIs) so that MPEG-M Applications running on an MPEG-M Device can access the standard multimedia technologies contained in its Middleware as MPEG-M Engines, as specified by ISO/IEC 23006‚Äë1.

The MXM APIs belong to two classes:

– the MPEG-M Engine APIs, i.e. the collection of the individual MPEG-M Engine APIs providing access to a single MPEG technology (e.g. video coding) or to a group of MPEG technologies where this is convenient;

– the MPEG-M Orchestrator API, i.e. the API of the special MPEG-M Engine (called Orchestrator Engine) that is capable of creating chains of MPEG-M Engines to execute high-level application calls such as “Play a video”, as opposed to the typically low-level MPEG-M Engine API calls.

Edition

3

Published Date

2016-12-05

Status

PUBLISHED

Pages

40

Language Detail Icon

English

Format Secure Icon

Secure PDF

Abstract

ISO/IEC 23006-2:2016 specifies a set of Application Programming Interfaces (called for short MXM APIs) so that MPEG-M Applications running on an MPEG-M Device can access the standard multimedia technologies contained in its Middleware as MPEG-M Engines, as specified by ISO/IEC 23006‚Äë1.

The MXM APIs belong to two classes:

- the MPEG-M Engine APIs, i.e. the collection of the individual MPEG-M Engine APIs providing access to a single MPEG technology (e.g. video coding) or to a group of MPEG technologies where this is convenient;

- the MPEG-M Orchestrator API, i.e. the API of the special MPEG-M Engine (called Orchestrator Engine) that is capable of creating chains of MPEG-M Engines to execute high-level application calls such as "Play a video", as opposed to the typically low-level MPEG-M Engine API calls.

Previous Editions

Can’t find what you are looking for?

Please contact us at: