Guru's Verification engine ensures consistency, confidence, and trust in the knowledge your organization shares. Learn more.

VOD Specifications for Transcoding

The platform supports transcoding from source mezzanine files to OTT Adaptive bitrate outputs, suitable for distribution to end users devices. The outputs combined with end device player optimization, can help handle different device & network performance conditions (see Broadband Network Conditions https://app.getguru.com/card/idpnjgMT/Broadband-consumption-speed-recommendation)

  • VOD Outputs: Up to 5 adaptive bitrate outputs: SD, SD, HD, HD, FHD
  • Live & Linear: Up to 5 adaptive bitrate outputs: SD, SD, HD, FHD

ABR - Adaptive Bitrates are handled:

  • During the transcoding process, the files are output to different bitrate and resolution specifications.
  • During playback in the end user device, the player continuously monitors playback performance and will switch to the most optimal bitrate stream depending on the device / network conditions.

It is possible to start the transcoding of a file through two ways:

  1. Standard: You start the transcoding through the Magine Pro Console. The system will perform a pre-check of your files before transcoding and inform you of any issues that you might need to address.
  2. Advanced: You start the transcoding through a direct API call. This allows you transcode more media and audio formats than on the standard path but there will be no pre-check of your files.

General Specifications

The following specifications apply to all files you prepare for transcoding independently of the method you choose.

Requirements for all file paths

  • No spaces in file and folder names.
  • File and folder names must only contain alphanumeric characters, dash, underscore and dot.

Best practices

  • The program starts and ends with 1 second of black and silence.
  • Video and audio have passed as few transcoding steps as possible.
  • Video and audio has the best possible quality.
  • Audio levels are normalised.
  • The filename is human readable and identifies the content.
  • The filename is free of long and messy internal ID codes.
  • Prefer non-interlaced video with integer frame rates.

Video

  • Fractional frame rates will be adjusted to the nearest integer frame rate - the output duration will be adjusted in order to maintain frame count.
    • When a fractional frame rate source is adjusted, subtitle timing is automatically compensated to remain synchronised with the adjusted output — no manual adjustment to your subtitle file is needed.

Subtitles

  • Separate files, one language per file.
  • Subtitles must be provided together with the VOD assets.
  • Subrip (.srt) format.
  • UTF-8 encoding.
  • No formatting or positioning tags.
  • Time codes must correctly synchronise with the audio.
    • (Time codes should be authored against your original source file's timeline — the platform automatically adjusts subtitle timing to match any frame rate conversion applied during transcoding.)
  • At least one blank line at end of .srt file.

Media containers

  • Submit a collection of media containers that include the desired audio, video and subtitle track(s) for an asset.
  • Exactly one video track per asset.

Specifications for transcoding through the Magine Pro Console

If you transcode through the Magine Pro Console these codecs for media, audio and subtitles are supported.

Video

Containers and codecs:

Container

Codec

mpeg-4

avc (h264), hevc (h265), mpeg-2

quicktime

avc (h264), hevc (h265), mpeg-2, prores

Audio

Containers and codecs:

Container

Codec

mpeg-4

aac, pcm

quicktime

aac, pcm, mp3

Additional requirements:

  • Supported channel layouts are stereo and 5.1 surround. The channels in a layout must be in the same track, e.g. a container could have a number of stereo tracks (2 channels each) and/or some surround tracks (6 channels each).
  • Mono tracks which need to be combined to multichannel layouts are not supported.
  • Language information about each track in ISO 639-2 format must be correctly set in the container metadata.
  • A track with no language set, or tagged as und ("undetermined"), is treated as invalid — the pre-check will fail and the file will need to be re-tagged with a valid ISO 639-2 language code and re-uploaded.
  • Avoid duplicate language labelling across tracks of the same layout — e.g. two separate stereo tracks both tagged "eng" — each track's language tag should be distinct for its layout.
  • If your account regularly delivers content in one predominant language, ask your Magine Pro contact about enabling an account-level default audio language. When set, a single audio track with an undefined/missing language tag will automatically resolve to that default instead of failing the pre-check. This only resolves one affected track per asset — it will not help if more than one track has an undefined language — and the platform cannot automatically detect which language is actually spoken in the audio (that would require speech-to-text and translation analysis, which is not performed).
  • Minimum one stereo audio track per asset, even if surround audio is provided.
  • Resolution of video must have a minimum width of 640px and height of 480px.
  • Audio Description (AD) — an additional narrated audio track describing on-screen visual content (e.g. "A woman enters the dark room. Thunder rumbles outside."), for blind and low-vision viewers. To include one, tag the track's Service Kind as "VI" (Visually Impaired) — a standard Dolby AC-3/E-AC-3 metadata field most professional audio tools can set — in addition to giving it a valid language code as described above. In the apps, this track appears in the audio-track menu labelled e.g. "English – Audio Description".

Subtitles

Containers and codecs:

Container

Codec

subrip (srt)

text

Additional requirements:

  • Subtitles must be associated with a language.
    • To set this, the subtitle filename must end with a ISO 639-2 language code. Separate the language with a dot e.g. "mymovie.eng.srt" or mymovie.swe.srt".
  • Optionally, subtitle type metadata can be set in the filename following the language code.
    • Closed Captions (CC) or Subtitles for the Deaf and Hard-of-hearing (SDH) — subtitles that, in addition to transcribing spoken dialogue, also describe important non-dialogue sound (e.g. "[door creaks]", "[tense music]"), for viewers who are deaf or hard of hearing. On this platform "cc" and "sdh" are treated as exactly the same subtitle type — there is no behavioural difference between them, so use whichever term you prefer. Set with a "cc" or "sdh" suffix, e.g. "mymovie.eng.cc.srt" or "mymovie.swe.sdh.srt".
    • Foreign-only (FO), also known as forced subtitles — subtitles that appear only for the portions of a video where the dialogue is in a different language than the main audio track (e.g. a scene of untranslated foreign dialogue), rather than for the whole runtime. Set with an "fo" suffix, e.g. "mymovie.eng.fo.srt".

How subtitle types render for viewers:

  • Normal (no suffix) — shown in the subtitle menu simply as the language name, e.g. "English".
  • CC / SDH — shown as a distinct, clearly-labelled option, e.g. "English (CC)", separate from the plain-language subtitle track.
  • Foreign-only (FO) — not shown as a selectable menu option; these subtitles appear automatically only during foreign-language dialogue, without the viewer needing to turn them on.
  • On some Smart TV devices (e.g. Vizio), if no CC/SDH-tagged track exists for a title, the player automatically labels the first English subtitle track as "CC" so a caption option is always available in the menu — tag your files correctly to avoid an untagged plain subtitle being mislabelled this way.

Adding support for more formats through the Magine Pro Console

When files and formats are not supported, we want to add support for them if it's possible. This is the process:

  1. Provide a sample file.
  2. Magine Pro will test this file in platform transcode API.
  3. Magine Pro will inspect the file to understand the format and recommened a pre-processing step that can be taken by your using standard video & subtitle tooling availble for post production workflows.

Possible to transcode through the Platform Transcode API

If you transcode through the transcoding API these codecs for media, audio and subtitles are supported.

https://developers.maginepro.com/reference/post_partner-transcode-asset

Video

Containers and codecs:

Container

Codec

mpeg-4

avc (h264), hevc (h265), mpeg-2

quicktime

avc (h264), hevc (h265), mpeg-2, prores

mxf

mpeg-2

Audio

Container

Codec

mpeg-4

aac, pcm

quicktime

aac, pcm, mp3

mxf

pcm

Additional requirements:

  • The same language-tagging requirements described for the Magine Pro Console path above apply here too.
  • To include an Audio Description (AD) track, set audioType: "descriptive-audio" on that track in the request — see "Audio Description (AD)" above for what this means and how it renders for viewers.

Subtitles

Containers and codecs:

Container

Codec

subrip (srt)

text

Additional requirements:

  • The same language-tagging requirements described for the Magine Pro Console path above apply here too.
  • To set the subtitle type explicitly, use subtitleType in the request: "captions" for CC/SDH, or "foreign-only" for FO — see "How subtitle types render for viewers" above for what these mean.

You must have Author or Collection Owner permission to create Guru Cards. Contact your team's Guru admins to use this template.