Configurations and Streams (VOD)

 

Configurations

Configurations for VOD assets function in the same manner as for live streams.  This page details the operational differences in setup, specific to VOD.  Depending on the structure of the VOD content library, thousands of streams can be integrated through a single Transmit configuration.  

As the initial setup for Live and VOD configurations is identical, please refer to this page for instructions on how to create them.  

Prefixes

Configuring a VOD origin as a Transmit prefix provides a scalable solution to integrate Transmit SSAI into your VOD library.  Below are some tips and best practices.  

Note: In order to adopt this workflow, your VOD content must be configured as an HLS playlist.

• The more generally your content is grouped/stored reduces the amount of prefixes
• Example:
  • The following playlists all share the same root-origin
    • http://client.com/vod1.m3u8
    • http://client.com/vod2.m3u8
    • http://client.com/vod3.m3u8
    • http://client.com/vod4.m3u8
    • http://client.com/vod5.m3u8
  • This allows the publisher to set up a content origin as such:
    • http://client.com
  • Which, in turn, allows all of the above playlists to share the same Transmit prefix:
    • i.e. https://abcd1234.global.transmit.live/hls/efhg5678/
• From this point, the process for activating Transmit SSAI is the same as on a live stream:
  1. Configure Transmit prefix in CMS/player
  2. Call Transmit prefix, append unique path to VOD content playlist
  3. Stream is configured in Transmit console with SSAI enabled

Considerations

• If SCTE markers are preserved in a VOD asset, Transmit ingests and honors those markers
  • Full-screen/midroll ads - standard SCTE
  • Instream units (LBar/PIP) - UPID SCTE values required
• If no SCTE markers are present, reach out to your Transmit contacts to coordinate next steps for establishing insertion points