Welcome
Below partners will find delivery specifications required by Markers In Motion; however, some of these specifications may not apply to your production. Please refer to your Markers In Motion Delivery Requirements List or your Markers In Motion Representative to verify which assets apply to your delivery.
Table of Contents
- 1: General Asset Requirements
- 2: IMF Specifications
- 3: Audio Mastering and Archive Specifications
- 4: VFX Archival Asset Specifications
- Appendix
1. General Asset Requirements
There are no exceptions to the following requirements, unless previously approved by your MnM Representative.
- Uncensored: Source material must be uncensored
- Content must be delivered as long-play and cannot be split into multiple deliveries e.g., if the content is 90 minutes in duration, a single asset with a 90-minute duration must be delivered. Two (2) deliverables with 45-minute durations will not be accepted.
- PSE (Photo-Sensitive Epilepsy) Compliance testing (e.g. Harding, Tektronix, or any other algorithm that complies with ITU-R BT.1702-1 guidelines) must be performed for all animated content.
2. IMF Specifications
2.1 Packaging
All deliveries to Markers In Motion must be compliant to either SMPTE ST 2067-21:2016 or SMPTE ST
2067-21:2020 Interoperable Master Format (IMF) Application #2E. Packages containing immersive sound must additionally comply with SMPTE ST 2067-201:2019 Immersive Audio Bitstream (IAB) Level 0 Plug-in.
Markers In Motion IMF Packages should be created directly from the color timeline out of a capable color grading tool OR from an intermediate mezzanine asset. IMF Packages must be delivered in the highest quality and resolution, including High Definition (HD) and Ultra High Definition (UHD). Markers In Motion may explicitly request other resolutions.
If you are creating your IMF package from an intermediate mezzanine asset, Markers In Motion recommends:
HDR Delivery:
- Uncompressed 16-bit TIFF (.tiff)
- Resolution and aspect ratio must match that of the delivered IMF: UHD (3840x2160) or HD (1920x1080).
SDR Delivery
- 10-bit or 16-bit DPX (.dpx)
- Resolution and aspect ratio must match that of the delivered IMF: UHD (3840x2160) or HD (1920x1080).
If creating a mezzanine asset is necessary for your IMF packaging workflow and you need additional guidance, please reach out to your MnM Representative.
The final IMF package must contain the following:
- 1 Asset Map XML file.
- 1 Packing List XML file.
- 1 or more Composition Playlist (CPL) XML file(s), representing a single audio language each, containing.
- For titles mixed in Dolby Atmos®
- 1 image virtual track.
- 1 IAB virtual track.
- 0 or 1 surround audio virtual track (6 channels).
- 0 or 1 stereo audio virtual track (2 channels).
- For titles mixed in 5.1 surround
- 1 image virtual track.
- 1 surround audio virtual track (6 channels).
- 0 or 1 stereo audio virtual track (2 channels).
- For titles mixed in Dolby Atmos®
- All MXF Track Files referenced from the ingested CPL, that have not previously been delivered.
- Volume Index and Output Profile List XML files may be present, but are not required.
For titles mixed in Dolby Atmos® and delivered in IAB in IMF, 5.1 and 2.0 (channel-based) audio tracks are optional within the IMF. 5.1 audio is required as a separate Content Hub delivery for dubbing reference only. Deliveries containing only image and IAB tracks, i.e. no channel-based stereo/surround audio track(s), must be compliant to SMPTE ST 2067-21:2020 (since the absence of channel based audio tracks is not supported by the 2016 edition of the standard).
Special consideration must be taken for 29.97 or 59.94 IMF deliverables. The total number of frames contained within a 29.97 or 59.94 IMF CPL Segment must be divisible by 5 to preserve integer value audio samples. If necessary, trim the picture and audio by the required number of frames (1, 2, 3, or 4) before wrapping IMF to ensure total frames per Segment are divisible by 5.
Note: Track files containing timed text essence are not currently supported.
2.2 VIDEO
2.2.1 GENERAL
- Markers In Motion requires video to be delivered at their native frame rates . Markers In Motion defines this to mean the original capture and editing frame rate. If it was originally a film, Markers In Motion requires the native film frame rate (23.976p, 24p or 25p). This is often different from the frame rate that is used for tape, archival storage, and delivery to broadcasters (typically 29.97i Drop Frame, or 25i). No 3:2 Pulldown flags allowed.
- Markers In Motion requires video to be delivered in the original aspect ratio (e.g. Markers In Motion will not accept a 4x3 version when a 16x9 version was originally created).
- Video must consist of the full feature or episodic program with one (1) second of format black and silence at the head and tail of the program.
- For redeliveries, supplemental IMPs may include video inserts only OR a full video track replacement + any combination of full audio track replacements as applicable.
- Supplemental IMPs must reference all MXF track files which have not been previously successfully delivered and ingested.
- Please confirm with your Markers In Motion representative before proceeding with a full video track replacement supplemental IMP OR a new complete IMP for any redelivery.
- Video must not contain commercial blacks.
- Video must not contain color bars, bumpers, advertisements, slates, ratings cards, FBI warning cards, VITC time code, placards, overlay branding or website link callouts before, during and/or after the program. URLs present during end credits are permissible.
- Video must be non-subtitled. Markers In Motion defines "non-subtitled" as the presence of main titles, end credits, narrative text, location call-outs, and other supportive/creative text, but no burned-in subtitled dialog, regardless of the language in the primary video. This does not apply to textless IMF deliveries (see Section 2.4).
- Track files containing image essence mastered in Dolby VisionTM must embed dynamic metadata for color volume transform within the video track file. At a minimum, L1 Dolby VisionTM metadata must be present for every frame in the track file. Note: We do not support material mastered only for HDR-10 distribution.
2.2.2 UHD
UHD Image Track |
||
Image Frame Width |
3840 |
|
Image Frame Height |
2160 |
|
Color Encoding |
RGB / 4:4:4 / Full Range |
|
Frame Rates |
23.976 / 24 / 25 / 29.97 / 30 / 50 / 59.94 / 60 |
|
Frame Structure |
Progressive |
|
Stereoscopy |
Monoscopic |
|
JPEG 2000 Profile |
Frame rates up to 30 fps use:
Frame rates above 30 fps use:
|
|
Dynamic Range |
Dolby Vision TM HDR |
SDR |
Colorimetry |
P3 D65 / SMPTE ST 2084 (PQ) |
ITU-R BT.709 / D65 / ITU-R BT.1886 (Gamma 2.4) |
Pixel Bit Depth |
12-bit |
10-bit |
Mastering Display Color Volume Metadata |
SMPTE ST-2086 |
n/a |
Dynamic Metadata for Color Volume Transformation 1
|
For CM v4:
<Level254 level="254"> <DMMode>0</DMMode> <DMVersion>2</DMVersion> <CMVersion>4 1</CMVersion> </Level254> |
n/a
|
For CM v2.9:
|
1 To validate the XML version or CMVersion, use the metafier —validate command.
2.2.3 HD
HD Image Track |
||
Image Frame Width |
1920 |
|
Image Frame Height |
1080 |
|
Color Encoding |
RGB / 4:4:4 / Full Range |
|
Frame Rates |
23.976 / 24 / 25 / 29.97 / 30 / 50 / 59.94 / 60 |
|
Frame Structure |
Progressive |
|
Stereoscopy |
Monoscopic |
|
JPEG 2000 Profile |
Frame rates up to 30 fps use:
Frame rates above 30 fps use:
|
|
Dynamic Range |
Dolby Vision TM HDR |
SDR |
Colorimetry |
P3 D65 / SMPTE ST 2084 (PQ) |
ITU-R BT.709 / D65 / ITU-R BT.1886 (Gamma 2.4) |
Pixel Bit Depth |
12-bit |
10-bit |
Mastering Display Color Volume Metadata |
SMPTE ST-2086 |
n/a |
Dynamic Metadata for Color Volume Transformation 2
|
For CM v4:
<Level254 level="254"> <DMMode>0</DMMode> <DMVersion>2</DMVersion> <CMVersion>4 1</CMVersion> </Level254> |
n/a
|
For CM v2.9:
|
2 To validate the XML version or CMVersion, use the metafier —validate command.
2.3 AUDIO
2.3.1 IMMERSIVE AUDIO
Audio Track (Atmos®) |
|
Sample Rate |
48 kHz |
Bit Depth |
24-bit |
Channel Mapping |
|
2.3.2 SURROUND AUDIO
Audio Track (5.1 Surround) |
|
Sample Rate |
48 kHz |
Bit Depth |
24-bit |
Channel Mapping |
|
2.3.3 STEREO AUDIO
Audio Track (2.0 Stereo) |
|
Sample Rate |
48 KHz |
Bit Depth |
24-bit |
Channel Mapping |
|
2.4 TEXTLESS VERSION IMF PACKAGING
Markers In Motion may request the delivery of a textless version IMF package in addition to the texted IMF delivery. Such a textless version IMF package must be created and delivered after the texted IMF package is approved by Markers In Motion. Additionally, the following requirements apply:
- The textless version IMF package should be created as a supplemental IMF package. That supplemental IMF package must be based on the last approved texted IMF package successfully delivered to Markers In Motion.
- A textless background/backplate must be included for any shot/sequence of the content that contains on-screen graphic text. Replacing the entire video track with a full-length textless version is acceptable if the content includes a significant amount of texted shots throughout.
- Please confirm with your Markers In Motion Representative before proceeding with a full-length textless version video supplemental.
- The textless version IMF composition must not change or replace the audio/IAB track(s) of the approved texted IMF delivery. This applies even if a full-length textless version with an entire video track replacement is approved by Markers In Motion.
- Textless inserts must have image properties identical to those of the texted IMF package, e.g. no changes in image resolution, color space etc.
- Dolby VisionTM mastering metadata trim values for textless inserts must be identical to the associated values in the texted IMF package, i.e. any changes in image characteristics due to removal of on-screen text must not be accounted for.
- Textless inserts must be provided cut-to-cut (i.e., the textless insert should not begin or end in the middle of a shot, fade, dissolve, or other transition; instead, the entire shot(s) should be provided).
- Graphic overlays such as emojis or text balloons should be considered texted elements.
3. AUDIO MASTERING & ARCHIVE SPECIFICATIONS
3.1 Audio Prerequisites
Discrete audio is required, except in the following circumstances:
- When mixed audio is inherent to the source, such as audio in an Quicktime, IMF or Atmos® BWAV ADM container.
- Interleaved Secondary Audio .wav deliveries.
48k/24bit sample rate and bit depth for Original Language Mix or M&E Mix - applies to Stems and Mix Masters.
All audio must sync to the final picture, including 1 second of black before the program start FFOA, and 1 second of black after LFOA.
Printmasters, M&Es and stems may include standard 8 second Academy leader and 2-pops.
For all titles, 5.1 audio is required and 2.0 is optional.
Mono audio is acceptable if the program's original source is mono and no stereo and/or 5.1 mix exists. Mono audio must be duplicated on channels 1 & 2 and delivered as 2-channel.
3.2 Audio Mix Requirements
3.2.1 Near Field Atmos® Mix - Mastering and Archive - Original Language Version
The Dolby Atmos® Original Language Home Mix must meet the following requirements:
- At a minimum, must be mixed in a 7.1.4 room.
- Dolby Certification is not required for Home Atmos® mix rooms.
- Atmos® delivered in IMF (IAB) supports 23.976, 24, 25 and 30 frames per second.
- This is a near field mix. The most common monitoring levels for near field are 79db or 82db.
- Must conform to Markers In Motion loudness spec (-27db LKFS +/- 2 LU 1770-1 dialog-gated).
- Peaks should generally not exceed -2dBFS true-peak. To achieve this, we recommend setting true-peak limiters on all beds and objects at -2.3 or lower. Loudness and peaks should be measured via a 5.1 rerender.
- For Atmos® mixes, delivering 5.1 is required and 2.0 audio is optional. The 5.1 and 2.0 re-render outputs must conform to Markers In Motion loudness specification. 5.1 and 2.0 must conform to the Markers In Motion peak specification only if they are delivered for streaming. We suggest achieving this by limiting the output from the renderer, rather than lowering beds and objects.
- Atmos® - Delivered to picture finishing facility for IMF creation and streaming.
- 5.1 - Delivered to Content Hub for dubbing reference. Optional to deliver for streaming.
- 2.0 - Optional.
- All beds and objects are encoded and will always be audible. A printmaster may utilize a composite of all bed material OR multiple beds, but not both.
- For all series/doc/unscripted/comedy content, beds and objects must be separated by Dialog, Music and Effects and must be labeled only as "Dialog", "Music", "Effects" or "Narration." For film content, DME separation should be maintained whenever possible.
- If an 85 db reference theatrical mix is created, two complete sets of deliverables are required. One for theatrical, one for near field.
- Leader and sync pop are preferred but not required. The IMF vendor will sync Atmos® in the IMF.
- Final Home Theater Print Master:
- Dolby Atmos® BWAV ADM File.
- All bed channel configurations are acceptable.
- 48 kHz sample rate, 24-bit.
- Dolby Atmos® BWAV ADM File.
3.2.2 Near Field 5.1 Surround Mix - Mastering and Archive - Original Language Version
- Use 79dB spl or 82dB spl as your standard reference level for mixing.
- Meet a -27 LKFS (+/- 2 LU) dialogue loudness using ITU-R BS.1770-1 measured over entire program.
- Do not exceed +18db (-2 dBFS) maximum level (true-peak) over reference of -20 dBFS, achieved by peak limiting and not lowering the mix level.
- For Original Version: Provide 5.1 Dialog, Music and Effects stems that equal the 5.1 mix when combined.
3.2.3 Near Field 2.0 Stereo Mix - Mastering and Archive - Original Language Version
- Use 79dB spl or 82dB spl as your standard reference level for mixing.
- Provide a Lo/Ro or LT/RT mix with -27 LKFS (+/- 2 LU) dialogue loudness using ITU-R BS.1770-1 measured over entire program.
- Lo/Ro mix is preferred.
- Lo/Ro or LT/RT mix to be mono compatible.
- Do not exceed +18db (-2 dBFS) maximum level (true-peak) over reference of -20 dBFS, achieved by peak limiting and not lowering the mix level.
- When down-mixing from 5.1 to create Lo/Ro or LT/RT 2.0 mix:
- Lower Center channel content by -3db.
- Center channel content should be included in both the LEFT and RIGHT CHANNELS.
- Lower Surround channel content by a minimum of -3db.
- Fold Left and Right Surround content into the corresponding LEFT and RIGHT CHANNELS.
- Optionally include the Low Frequency Effects (LFE) channel between -8db and -12db.
- Fold Low Frequency Effects (LFE) into both the LEFT and RIGHT CHANNELS.
- Low Pass Filter LFE at 200Hz or lower.
- All adjustments must be made to the individual 5.1 channels prior to folding down.
Note: The resulting 2.0 mix must be checked prior to delivery to ensure it is free of any audio artifacts and if necessary, as determined by Markers In Motion, further adjustments shall be made to prevent them. Any 2.0 delivery must meet the specification prescribed in this section.
3. 3 Music & Effects (M&E) Mix
3.3.1 Near Field Atmos® M&E Mix
The Dolby Atmos® Home M&E Mix must meet the following requirements:
- At a minimum, must be mixed in a 7.1.4 room.
- Dolby Certification is not required for Home Atmos® mix rooms.
- This is a near field mix. The most common monitoring levels for near field are 79db or 82db.
- Peaks should generally not exceed -2dBFS true-peak. To achieve this, we recommend setting true-peak limiters on all beds and objects at -2.3 or lower. Peaks should be measured via a 5.1 rerender.
- The 5.1 M&E rerender is required and must conform to Markers In Motion Peak specification.
- Optional tracks are required in addition to the Atmos® M&E when necessary.
- All beds and objects are encoded and will always be audible. A printmaster may utilize a composite of all bed material OR multiple beds, but not both.
- M&E bed and object configuration should match the Atmos® printmaster. Dialog beds and objects should contain only production effects and no discernable language.
- If a 85db reference theatrical mix is created, two complete sets of deliverables are required. One for theatrical, one for near field.
- Leader and sync pop are preferred but not required.
- M&E Mix
- Dolby Atmos® BWAV ADM File or Pro Tools Recorder Session.
- All bed channel configurations are acceptable.
- 48 kHz, 24-bit.
- Single or multiple M&E Options stems as separate WAV file(s) or marked clearly as Optional or OPT within the Pro Tools session, along with any other content-specific labels.
- Channel format should be determined by the re-recording mixer to match the intent of the original mix.
- Dolby Atmos® BWAV ADM File or Pro Tools Recorder Session.
3.3.2 Near Field 5.1 Surround M&E Mix
- Provide a fully filled 5.1 surround submix containing only Music & Effects (no dialog).
- Ambiences and foley fill should be included to correctly match the original mix. Any non-dialog sound present in the main mix must also be represented in the M&E mix.
- All levels should mirror what was used for final Mastering and Archive so that any newly added dubbed dialog can be mixed in easily later.
- Optional tracks are required in addition to the 5.1 M&E when necessary.
- For Dolby Atmos® mixes, the 5.1 M&E should be rendered from the Dolby Atmos® M&E.
- M&E Creation Guidelines documents:
4. VFX Archival Asset Specifications
This document covers the final assets delivered as part of the VFX Archive. The VFX Archive should include assets used in the creation of the final image frames delivered to the finishing facility. This will involve the final shot directory, and all the direct dependencies from which the final images and relevant assets were created.
4.1 VFX Production Assets
4.1.1 Scanning Data
VFX scanning data should be provided using the following guideline:
- Lidar & photogrammetry for any custom-built/key environments (cleaned/processed where available). No raw point cloud data.
- Cyberscans of actors (where contractually applicable), creatures and props must be named in a manner that clearly describes what they are and organized in a folder structure with any accompanying elements.
- Include scan processing facility information.
- Zipped files/directories will not be accepted.
For Imaging and Object file type list see section 4.5.2
4.2 VFX Post Production Assets
4.2.1 VFX Plates
VFX plates must be in one of the following file formats:
- 16-bit EXR (.exr) if color pipeline is ACES, or if the pull color pipeline is set to a Camera Linear color space (such as Linear AWG / Alexa Wide Gamut).
- EXR can be uncompressed or use lossless compression (i.e. ZIP or PIZ).
- 16-bit DPX (.dpx) when the pull color pipeline is set to a Camera Log color space (such as LogC).
- 10-bit DPX (.dpx) ONLY when the primary capture format was 10-bit Log.
- LOG EXRs will not be accepted.
- Zipped files/directories will not be accepted.
4.2.2 VFX Shots
VFX final shot deliveries must be in one of the following file formats:
- 16-bit EXR (.exr) if color pipeline is ACES, or if the pull color pipeline is set to a Camera Linear color space (such as Linear AWG / Alexa Wide Gamut).
- EXR can be uncompressed or use lossless compression (i.e. ZIP or PIZ).
- 16-bit DPX (.dpx) when the pull color pipeline is set to a Camera Log color space (such as LogC).
- 10-bit DPX (.dpx) ONLY when the primary capture format was 10-bit Log.
- LOG EXRs will not be accepted.
- VFX Shot names should adhere to Markers In Motion's VFX Shot and Version Naming Recommendations
- Provide a proxy reference for each final shot (i.e. a QT with color baked in).
- Include any already-rendered mattes generated for final shots, either embedded or as separate elements.
For Proxy Video Format requirements see section 4.5.1.
4.3 VFX Wrap Assets
4.3.1 Final Models
VFX models and supporting files should be provided using the following guideline:
- Include 3D models and CG asset project files for final hero characters, creatures, props and environments only.
- Provide a proxy video reference for each asset (i.e. a turntable QT for each model).
- Assets must be named in a manner that clearly describes what they are and should be organized in a folder structure with accompanying elements (e.g. base model geo (hull), texture maps, paint, shaders (with maps), rigging/chaining (non-evaluated skeleton rigging), scene files and geo topologies where applicable).
- Zipped files will not be accepted.
For Proxy Video Format requirements see section 5.5.1. For Imaging and Object file type list see section 5.5.2.
Note: Some productions may require additional VFX Wrap assets to be delivered beyond the core assets outlined in this specification document. If you're unsure if your production requires these assets for delivery, please reference your production's Delivery List and reach out to your MnM Representative.
4.4 VFX Document Specifications
VFX Shot and Asset Status Report
A VFX Shot and Asset status report must be submitted with status, scope of work, methodologies, and cost summary data per shot and asset. A template will be provided to you by your Markers In Motion Representative for completion. Please notify your Markers In Motion Representative once the data is submitted.
VFX Financial Report
For all projects, the VFX Financial Report must be submitted with final costs per vendor and episode. Please reach out to your Markers In Motion Representative for access to the financial reporting page.
VFX Production Reports
VFX Supervisor Onset Reports / VFX Exposure Reports, detailing potential cost exposure identified during principal and additional photography if specified by your Markers In Motion VFX Representative.
VFX Breakdown (Budgeted)
Supporting material for locked VFX Budget. VFX cost breakdown with context on approach assumptions and associated VFX bids if specified by your Markers In Motion VFX Representative.
4.5 VFX Appendix
4.5.1 Proxy Video Formats
When delivering VFX shot & asset references for final archive, please use a proxy video format as below:
Proxy Video Format Requirements |
|
Container |
MP4, MOV |
Video Codec |
H.264 (Closed GOP only) ProRes 422 (HQ) ProRes 4444 (XQ NOT supported) DNxHD (ProRes 422 (HQ), ProRes 4444, DNxHD supported in MOV container only) |
Resolution |
640x480 to 4096x2160 (W and H pixel counts must be integers evenly divisible by 4. It is recommended to encode content at its native aspect ratio, padding with black to the nearest integer evenly divisible by 4.) |
Frame Rates |
23.976, 24, 25, 29.97, 30, 50, 59.94, 60 |
Color Space |
Rec. 709 |
Audio Codec for H.264 |
HE-AACv1, HE-AACv2, AAC-LC (44.1kHz or 48kHz Sample Rate) |
Audio Codec for ProRes, DNxHD |
PCM (48kHz Sample Rate) |
Bit Depth |
16 |
Channel Mapping |
|
4.5.2Imaging and Object File Types
Note: Imaging and Object File Types are constantly evolving. Formats may be added or removed from the list as standards and applications change in the dynamic VFX industry.
Imaging and Object File Types |
|
Image File Types |
JPEG, PNG, TIFF, PSD, PDF, EPS, AI, RAW, HDR, EXR, DPX, OBJ, PIC |
Production Scene/DCC Files |
.mb, .ma, .hip, .hda, .nk, .unity, .unity3d, .uproject, BLEND |
Geometry, CG Formats |
.abc, .usd, .fbx, .pts, .las, .dxf, .obj, .ztl |
For any specific questions or concerns related to any VFX asset or document requirements listed, please reach out to your MnM Representative.
Shot Name and Version Name Fields: Usage reference table
(FX Shot and Version Naming Recommendations)
Field (Example) |
Best practice recommendation for usage |
|||||||
showID (AGM) |
Required for series projects (except optional for IO). Optional for all other project types. |
|||||||
episode (104) |
Required for all series projects. Not applicable for features. |
|||||||
seq (TCC) |
Optional. (Not all projects get broken down by sequence) |
|||||||
scene (067) |
Optional but required if project naming does not use sequences. |
|||||||
shotID# (0010) |
Required |
|||||||
task (comp) |
Encouraged (helps quickly identify the type of work that will appear in a given version) |
|||||||
vendorID (NFX) |
Required for series projects (except optional for IO). Encouraged for all other project types. |
|||||||
version# (v001) |
Required. Must begin with 'v'. |
Series: Example shot name options
No sequence |
No scene |
Both sequence and scene |
showID_episode_scene_shotID# |
showID_episode_seq_shotID# |
showID_episode_seq_scene_shotID# |
AGM_104_065_010 |
AGM_104_TCC_0010 |
AGM_104_TCC_065_0010 |
AGM_104_065_020 |
AGM_104_TCC_0020 |
AGM_104_TCC_065_0020 |
AGM_104_066_010 |
AGM_104_TCC_0030 |
AGM_104_TCC_066_0030 |
AGM_104_066_020 |
AGM_104_TCC_0040 |
AGM_104_TCC_066_0040 |
AGM_104_066_030 |
AGM_104_TCC_0050 |
AGM_104_TCC_066_0050 |
AGM_104_066_040 |
AGM_104_TCC_0060 |
AGM_104_TCC_066_0060 |
AGM_104_067_010 |
AGM_104_TCC_0070 |
AGM_104_TCC_067_0070 |
AGM_104_067_020 |
AGM_104_TCC_0080 |
AGM_104_TCC_067_0080 |
Version example: AGM_104_065_010_comp_NFX_v001
Feature: Example shot name options
No sequence |
No scene |
Both sequence and scene |
showID_scene_shotID# |
showID_seq_shotID# |
showID_seq_scene_shotID# |
AGM_065_010 |
AGM_TCC_0010 |
AGM_TCC_065_0010 |
AGM_065_020 |
AGM_TCC_0020 |
AGM_TCC_065_0020 |
AGM_066_010 |
AGM_TCC_0030 |
AGM_TCC_066_0030 |
AGM_066_020 |
AGM_TCC_0040 |
AGM_TCC_066_0040 |
AGM_066_030 |
AGM_TCC_0050 |
AGM_TCC_066_0050 |
AGM_066_040 |
AGM_TCC_0060 |
AGM_TCC_066_0060 |
AGM_067_010 |
AGM_TCC_0070 |
AGM_TCC_067_0070 |
AGM_067_020 |
AGM_TCC_0080 |
AGM_TCC_067_0080 |
Appendix
Language Codes
If the desired language code is not found in the table below please contact your MnM Representative.
Language Name | Language Code | Audio | Text |
Acoli | ach | √ | √ |
Afrikaans | af | √ | √ |
Albanian | sq | √ | √ |
Amharic | am | √ | √ |
Arabic | ar | √ | √ |
Arabic (Algeria) | ar-DZ | √ | √ |
Arabic (Bahrain) | ar-BH | √ | √ |
Arabic (Chad) | ar-TD | √ | √ |
Arabic (Comoros) | ar-KM | √ | √ |
Arabic (Djibouti) | ar-DJ | √ | √ |
Arabic (Egypt) | ar-EG | √ | √ |
Arabic (Eritrea) | ar-ER | √ | √ |
Arabic (Iraq) | ar-IQ | √ | √ |
Arabic (Israel) | ar-IL | √ | √ |
Arabic (Jordan) | ar-JO | √ | √ |
Arabic (Kuwait) | ar-KW | √ | √ |
Arabic (Lebanon) | ar-LB | √ | √ |
Arabic (Libya) | ar-LY | √ | √ |
Arabic (Mauritania) | ar-MR | √ | √ |
Arabic (Morocco) | ar-MA | √ | √ |
Arabic (Oman) | ar-OM | √ | √ |
Arabic (Palestine) | ar-PS | √ | √ |
Arabic (Qatar) | ar-QA | √ | √ |
Arabic (Saudi Arabia) | ar-SA | √ | √ |
Arabic (Somalia) | ar-SO | √ | √ |
Arabic (South Sudan) | ar-SS | √ | √ |
Arabic (Sudan) | ar-SD | √ | √ |
Arabic (Syria) | ar-SY | √ | √ |
Arabic (Tunisia) | ar-TN | √ | √ |
Arabic (United Arab Emirates) | ar-AE | √ | √ |
Arabic (Western Sahara) | ar-EH | √ | √ |
Arabic (Yemen) | ar-YE | √ | √ |
Aramaic | arc | √ | √ |
Armenian | hy | √ | √ |
Assamese | as | √ | √ |
Aymara | ay | √ | |
Bambara | bm | √ | √ |
Bangla | bn | √ | √ |
Bantu | bnt | √ | |
Bashkir | ba | √ | √ |
Basque | eu | √ | √ |
Belarusian | be | √ | √ |
Berber | ber | √ | |
Bodo | brx | √ | √ |
Bosnian | bs | √ | √ |
Bulbovian | xa | √ | √ |
Bulgarian | bg | √ | √ |
Burmese | my | √ | √ |
Cantonese | yue | √ | √ |
Catalan | ca | √ | √ |
Cebuano | ceb | √ | |
Chechen | ce | √ | √ |
Cheyenne | chy | √ | √ |
Croatian | hr | √ | √ |
Czech | cs | √ | √ |
Danish | da | √ | √ |
Dari | fa-AF | √ | √ |
Dinka | din | √ | √ |
Dogri | doi | √ | |
Dutch | nl | √ | √ |
Dzongkha | dz | √ | √ |
Efik | efi | √ | √ |
Elamite | elx | √ | √ |
English | en | √ | √ |
English (Australia) | en-AU | √ | √ |
English (Britain) | en-GB | √ | √ |
English (India) | en-IN | √ | √ |
English (Kenya) | en-KE | √ | √ |
English (Nigeria) | en-NG | √ | √ |
English (Philippines) | en-PH | √ | √ |
English (South Africa) | en-ZA | √ | √ |
Esperanto | eo | √ | √ |
Estonian | et | √ | √ |
Faroese | fo | √ | √ |
Filipino | fil | √ | √ |
Finnish | fi | √ | √ |
Flemish | nl-BE | √ | √ |
French | fr | √ | √ |
French (Canada) | fr-CA | √ | √ |
Fulah | ff | √ | |
Galician | gl | √ | √ |
Georgian | ka | √ | √ |
German | de | √ | √ |
Gogo | gog | √ | √ |
Greek | el | √ | √ |
Gujarati | gu | √ | √ |
Hausa | ha | √ | √ |
Hawaiian | haw | √ | √ |
Hebrew | he | √ | √ |
Hindi | hi | √ | √ |
Hindi (Latin) | hi-Latn | √ | |
Hokkien | nan | √ | √ |
Hungarian | hu | √ | √ |
Icelandic | is | √ | √ |
Igbo | ig | √ | √ |
Ijaw | ijo | √ | √ |
Indonesian | id | √ | √ |
Inuktitut | iu | √ | √ |
Irish | ga | √ | √ |
Italian | it | √ | √ |
Jamaican Patois | jam | √ | √ |
Japanese | ja | √ | √ |
Javanese | jv | √ | √ |
Kannada | kn | √ | √ |
Kashmiri | ks | √ | √ |
Kazakh | kk | √ | √ |
Khasi | kha | √ | √ |
Khmer | km | √ | √ |
Kikuyu | ki | √ | √ |
Kinyarwanda | rw | √ | √ |
Klingon | tlh | √ | √ |
Konkani | kok | √ | √ |
Korean | ko | √ | √ |
Kurdish | ku | √ | √ |
Kyrgyz | ky | √ | √ |
Lango (Uganda) | laj | √ | √ |
Lao | lo | √ | √ |
Latin | la | √ | √ |
Latvian | lv | √ | √ |
Lingala | ln | √ | √ |
Lithuanian | lt | √ | √ |
Luxembourgish | lb | √ | √ |
Macedonian | mk | √ | √ |
Maithili | mai | √ | |
Malagasy | mg | √ | √ |
Malay | ms | √ | √ |
Malayalam | ml | √ | √ |
Maltese | mt | √ | √ |
Mandarin | zh | √ | |
Mandarin (Mainland China) | zh-CN | √ | |
Mandarin (Taiwan) | zh-TW | √ | |
Mandingo | man | √ | |
Manipuri | mni | √ | √ |
Maori | mi | √ | √ |
Marathi | mr | √ | √ |
Masai | mas | √ | √ |
Mayan | myn | √ | √ |
Mende | men | √ | √ |
Mongolian | mn | √ | √ |
Multiple languages | mul | √ | √ |
Nepali | ne | √ | √ |
Newari | new | √ | √ |
Nigerian Pidgin | pcm | √ | √ |
No linguistic content | zxx | √ | √ |
North Ndebele | nd | √ | √ |
Northern Sami | se | √ | √ |
Northern Sotho | nso | √ | √ |
Norwegian | nb | √ | √ |
Nyanja | ny | √ | |
Odia | or | √ | √ |
Oromo | om | √ | |
Papiamento | pap | √ | |
Pashto | ps | √ | √ |
Persian | fa | √ | √ |
Polish | pl | √ | √ |
Portuguese (Brazil) | pt-BR | √ | √ |
Portuguese (Portugal) | pt | √ | √ |
Punjabi | pa | √ | √ |
Quechua | qu | √ | √ |
Quechua (Bolivia) | qu-BO | √ | √ |
Quechua (Ecuador) | qu-EC | √ | √ |
Quechua (Peru) | qu-PE | √ | √ |
Romanian | ro | √ | √ |
Romansh | rm | √ | √ |
Romany | rom | √ | √ |
Russian | ru | √ | √ |
Sami | smi | √ | √ |
Samoan | sm | √ | √ |
Sanskrit | sa | √ | √ |
Santali | sat | √ | |
Scottish Gaelic | gd | √ | √ |
Serbian | sr | √ | |
Serbian (Cyrillic) | sr-Cyrl | √ | |
Serbian (Latin) | sr-Latn | √ | |
Sherdukpen | sdp | √ | √ |
Shona | sn | √ | |
Simplified Chinese | zh-Hans | √ | |
Sindhi | sd | √ | |
Sinhala | si | √ | √ |
Slovak | sk | √ | √ |
Slovenian | sl | √ | √ |
Somali | so | √ | √ |
Songhai | son | √ | √ |
South Ndebele | nr | √ | √ |
Southern Sotho | st | √ | √ |
Spanish (Latam) | es | √ | √ |
Spanish (Argentina) | es-AR | √ | √ |
Spanish (Colombia) | es-CO | √ | √ |
Spanish (Mexico) | es-MX | √ | √ |
Spanish (Spain) | es-ES | √ | √ |
Swahili | sw | √ | √ |
Swati | ss | √ | √ |
Swedish | sv | √ | √ |
Swiss German | gsw | √ | √ |
Taiwanese | nan-TW | √ | |
Tamashek | tmh | √ | √ |
Tamil | ta | √ | √ |
Taroko | trv | √ | |
Telugu | te | √ | √ |
Thai | th | √ | √ |
Tibetan | bo | √ | √ |
Tongan | to | √ | √ |
Traditional Chinese | zh-Hant | √ | |
Traditional Chinese (Hong Kong) | zh-Hant-HK | √ | |
Tsonga | ts | √ | √ |
Tswana | tn | √ | √ |
Turkish | tr | √ | √ |
Tuvinian | tyv | √ | √ |
Ugaritic | uga | √ | √ |
Ukrainian | uk | √ | √ |
Urdu | ur | √ | √ |
Venda | ve | √ | √ |
Vietnamese | vi | √ | √ |
Welsh | cy | √ | √ |
Wolof | wo | √ | √ |
Xhosa | xh | √ | √ |
Yiddish | yi | √ | √ |
Yoruba | yo | √ | √ |
Zapotec | zap | √ | √ |
Zulu | zu | √ | √ |