Skip to content

Media Profile: CMAF MPEG‐H Audio multi‐stream ('cmhm')

Matteo Agnelli edited this page Nov 2, 2017 · 1 revision

"Audio profile using the MPEG-H Audio Media Profile as defined in CMAF supporting multi-stream functionalities."

For a Provisional media profile: CMAF MPEG-H Audio multi-stream

Name/company of designated proponent

Matteo Agnelli / Fraunhofer IIS matteo.agnelli@iis.fraunhofer.de

Note: The Designated proponent is responsible for providing all deliverables necessary to meet the WAVE Media Profile requirements.

Market relevance

Meet at least one of the following conditions.

Codec with existing market relevance

  1. Digital Media Service Providers (at least 3): NAMES

  2. Digital Media Playback Devices available in the market (at least 5): NAMES

Codec with WAVE membership support

  1. Device manufacturers which are WAVE members (at least 2): Sony, Samsung, Qualcomm Incorporated

  2. Content providers which are WAVE members (at least 2): Apple, BBC

  3. Other Wave members (at least total of 6 including the above members): Fraunhofer, castLabs

Note: A WAVE member company self-declares at the time of voting whether they wish to be considered a device manufacturer, a content provider or other.

Open standards

List the standard for the media profile:

  • ISO/IEC 23000-19 Common Media Application Format, Amendment 1

Note: To meet the WAVE Media Profile ‘open standard’ requirement, the media profile in question must have been developed following an open specification process which supports independent implementations, or is in the process of being published under such a process.

Normative references

List the normative reference of the media profile:

  • ISO/IEC 23000-19 Information technology — Coding of audio-visual objects — Part 19: Common media application format (CMAF) for segmented media, Amendment 1

Note: To meet the WAVE Media Profile ‘normative referenceable’ requirement, the organization where the media profile has been or will be published must meet the CTA normative reference policy and be at a level of technical maturity where only editorial changes are possible.

Test and conformance tools

Please provide a timeline for test content and conformance tools.

Test Content

Timeline:

Content for MPEG-H Audio is available from other OTT relevant organization, e.g. DASH-IF. Test content for WAVE can be provided as soon as requested, upon clarifications of some open issues, like for example role of manifests within WAVE.

Conformance Tools

Timeline:

Timeline for conformance software follows the MPEG CMAF conformance schedule, if such a software is suitable. If changes are needed on top of that software, additional time is required.

Note 1: To become an approved WAVE Media Profile the test and conformance tools for content verification as well as test vectors for device verification must be available to WAVE.

Note 2: Media Profiles included in this specification for which no test and conformance material is provided are only published as Provisional WAVE Media Profiles and may be removed if no test and conformance material is provided before releasing a new version of this specification.

For an Approved media profile:

WAVE compatibility

  1. Does the media profile specification include its ISOBMFF encapsulation? (Y/N): Y

    1.1. If the case of Y, which organization/spec? ISO/IEC 23000-19

    1.2. In the case of N,

    Do you have a preliminary draft to be included in a WAVE spec? (Y/N):
    
    When will the complete media profile specification be published by external org? DATE
    
  2. Have you tested the media profiles with W3C MSE? (Y/N): Y

  3. Any reported incompatibilities with W3C MSE? (Y/N): N

Note: The CMAF MPEG-H Audio media profiles specifies the merging of multiple streams into a single stream before decoding. The processing is based on the unique packetized format of the MPEG-H Audio stream and standardized in ISO/IEC 23008-3 MPEG-H 3D Audio, section 14.6. Additional information is provided in ETSI TS 101 154.

Merging multiple MPEG-H Audio streams into a single stream requires only one MSE buffer. Therefore the media profile fulfils the MSE compatibility requirement.

Clone this wiki locally