<-AI Workflows Go to ToC Data Types->

1. Technical Specification 2. Conformance Testing 3. Performance Assessment

1. Technical Specifications

Table 1 provides the links to the specifications and the JSON syntax of all AIMs specified by Technical Specification: Context-based Audio Enhancement (MPAI-CAE) – Use Cases (CAE-USC) V2.4. The AI Modules specified by CAE-USC V2.4 supersede those specified by previous versions. These may be used if their Version is explicitly signaled. AIMs in bold are Composite.

Table 1 – Specifications and JSON syntax of AIMs used by CAE-USC V2.4

Acronym AIM Name JSON Acronym AIM Name JSON
CAE-AAP Audio Analysis for Preservation File CAE-PAP Packaging for Audio Preservation File
CAE-AAT Audio Analysis Transform File CAE-PEI Prosodic Emotion Insertion File
CAE-ADP Audio Description Packaging File CAE-SFD Sound Field Description File
CAE-AMX Audio Descriptors Multiplexing File CAE-SDS Speech Detection and Separation File
CAE-AOI Audio Object Identification File CAE-SF1 Speech Feature Analysis 1 File
CAE-ASE Audio Separation and Enhancement File CAE-SF2 Speech Feature Analysis 2 File
CAE-ASL Audio Source Localisation File CAE-SMC Speech Model Creation File
CAE-AST Audio Synthesis Transform File CAE-SRA Speech Restoration Assembly File
CAE-EFP Emotion Feature Production File CAE-TAR Tape Audio Restoration File
CAE-NEI Neural Emotion Insertion File CAE-TIC Tape Irregularity Classification File
CAE-NCM Noise Cancellation Module File CAE-VAP Video Analysis for Preservation File

2. Reference Software

As a rule, MPAI provides Reference Software implementing the AI Modules released with the BSD-3-Clause licence and the following disclaimers:

  1. The CAE-USC V2.4 Reference Software Implementation, if in source code, is released with the BSD-3-Clause licence.
  2. The purpose of this Reference Software is to provide a working Implementation of CAE-USC V2.4, not to provide a ready-to-use product.
  3. MPAI disclaims the suitability of the Software for any other purposes and does not guarantee that it is secure.
  4. Use of this Reference Software may require acceptance of licences from the respective copyright holders. Users shall verify that they have the right to use any third-party software required by this Reference Software.

Note that at this stage CAE-USC V2.4 specifies Reference Software only for some AIMs.

3. Conformance Testing

An implementation of an AI Module conforms with CAE-USC V2.4 if it accepts as input _and_ produces as output Data and/or Data Objects (the combination of Data of a Data Type and its Qualifier) conforming with those specified by CAE-USC V2.4 .

The Conformance is expressed by one of the two statements

  1. “Data conforms with the relevant (Non-MPAI) standard” – for Data.
  2. “Data validates against the Data Type Schema” – for Data Object.

The latter statement implies that:

  1. Any Sub-Type of the Data conforms with the relevant Sub-Type specification of the applicable Qualifier.
  2. Any Content and Transport Format of the Data conform with the relevant Format specification of the applicable Qualifier.
  3. Any Attribute of the Data
    1. Conforms with the relevant (Non-MPAI) standard – for Data, or
    2. Validates against the Data Type Schema – for Data Object.

The method to Test the Conformance of an instance of Data or Data Object is specified in the Data Types chapter.

Note that at this stage the CAE-USC V2.4 specifies Conformance Testing only for some AIMs.

4. Performance Assessment

An implementation of an AI Module conforms with CAE-USC V2.4 if it accepts as input _and_ produces as output Data and/or Data Objects (the combination of Data of a Data Type and its Qualifier) conforming with those specified by CAE-USC V2.4.

The Conformance is expressed by one of the two statements

  1. “Data conforms with the relevant (Non-MPAI) standard” – for Data.
  2. “Data validates against the Data Type Schema” – for Data Object.

The latter statement implies that:

  1. Any Sub-Type of the Data conforms with the relevant Sub-Type specification of the applicable Qualifier.
  2. Any Content and Transport Format of the Data conform with the relevant Format specification of the applicable Qualifier.
  3. Any Attribute of the Data
  4. Conforms with the relevant (Non-MPAI) standard – for Data, or
  5. Validates against the Data Type Schema – for Data Object.

The method to Test the Conformance of an instance of Data or Data Object is specified in the Data Types chapter.

Note that at this stage the CAE-USC V2.4 specifies Conformance Testing only for some AIMs.

<-AI Workflows Go to ToC Data Types->