Manifest Edit

This demo showcases some common customizations to a manifest that boost compatibility and improve the viewer experience such as adjusting default languages or removing tracks that cause playback issues on some devices.

Each DASH or HLS use case is described by a YAML configuration file. A typical installation would maintain one YAML file per use case that needs to be handled. Use cases are triggered by appending a query parameter to the manifest URL.

e.g. the URL https://[...]/tears-of-steel-multi-lang.ism/.m3u8?python_pipeline_config=default_audio_it is used to activate the default_audio_it use case.

Many use cases addressed by Manifest Edit are designed to resolve playback issues; this makes it a challenge to display them in a demo. Check out the docs to see what else is possible.

The benefits of this solution:

  • Produce device specific manifests
  • Boost Compatibility
  • Provide the best user experience
  • Easy to create single or multi-stage workflows
  • Edit prepackaged manifests or as part of a dynamic workflow

First select the desired output format and player, then select a use case.
Some will allow a further selection to choose amongst several customization of the same use case.
After loading the video you will see a before and after comparison of changes to the manifest.
These changes are also reflected in the playback and/or in the corresponding player dropdowns.
Output format: 

Select Use Case: 
Customize Use Case: 

Original Manifest
Edited Manifest
Original Manifest playback (.M3U8)
Edited Manifest playback (.M3U8)