Tips - Flexible Video Ingest Formats

Document created by charliekraus on Sep 2, 2015Last modified by eforan on Oct 2, 2015
Version 2Show Document
  • View in full screen mode

Just as there are many formats your video content can take, Limelight offers a rich choice of ingest options for getting content into the CDN. Just as important, there are globally dispersed ingest points, providing localized connectivity.


                                                 tips pic.png


Limelight has a unified video Live and On-demand workflow supporting single format ingest with MP4, with multiple bit rate outputs for HLS, HDS, MSS, DASH, HTTP, and RTMP.


So, how do you decide which method is best for ingesting your video into the CDN? Let’s look at several scenarios.


FTP Upload

An FTP (File Transfer Protocol) upload is a good choice for the following:

  • Performing initial migration of content to the CDN
  • Batch uploads, used on a regular basis by some customers, often for media files
  • Uploading large media files (those >1 GB)
  • Upload of media asset metadata

FTP-SSL is supported for secure uploads.


Aspera Upload

Like FTP, media files and associated metadata can be uploaded via Aspera’s transport technology. Aspera provides a secure, high-throughput connection that works well in unreliable Internet conditions. Use Aspera over FTP for uploads occurring over great distances in unreliable conditions or for secure uploads. Note that a separate license from Aspera is required.


Secure Transfer

Uploading options are:

  • SCP (Secure Copy protocol)
  • SFTP (Secure File Transfer Protocol)
  • RSYNC (Remote Sync)

SCP and SFTP are file transfer protocols between hosts on a network, and both provide secure file transfer capabilities. Compared to the SCP protocol, which only does file transfers, SFTP can also resume interrupted transfers and remote file removal.  SCP is most frequently implemented on Unix platforms, while SFTP is common on most platforms. RSYNC is a widely-used utility found on Unix systems that keeps copies of a file the same on two systems by synchronizing files between systems. It is designed to minimize network usage by transferring deltas between the copies.


API Upload

The final option is an API upload if you build your own workflow to programmatically upload files and metadata.  Common use cases include:

  • Automatically syncing with an existing CMS or asset management system
  • Uploading media and applying metadata at the same time
  • For an automated ingestion workflow


This broad set of options combined with Limelight’s strong support staff to assist in designing an optimized video solution for your organization, assures success in having the ideal video ingest strategy.