Overview: Using Aspera for Ingestion to Video Cloud

IBM Aspera is a popular solution for reliable high-speed file transfers. Brightcove offers a simple and flexible solution for adding videos and media assets to Video Cloud using Aspera. The topics in this section explain the details.

Using Aspera with Brightcove

The basic workflow for using Aspera to transfer your files to Video Cloud as shown below. Note that you will need to install the IBM Aspera Desktop Client. For more information, see Installing Desktop Client.

  1. Go to http://ingest-transfer-aspera.brightcove.com/ and login using you Video Cloud credentials with the proper permissions (see Credentials below).
  2. Upload the files you want to ingest into Video Cloud.
  3. Wait for the transfer to finish
  4. Monitor the rest of the ingestion in Video Cloud using Studio or the CMS API.


There are two kinds of credentials for using Aspera ingestion:

  • Upload - for simple ingestion of videos without metadata or additional assets. Simply upload the video files. If a manifest of metadata is present, it will be ignored.
  • Upload with Metadata - in this case, file transfer will start when the manifest file providing metadata information is uploaded. This operation can be used to:
    • Add metadata and assets to a video on upload
    • Update metadata for existing videos
    • Add assets to existing videos
    • Re-transcode or replace existing videos

    See the Manifest Reference for details of this XML file. Note that there is a limit of 20 videos per manifest file.


The list below shows the current limitations of Aspera Host for ingesting videos.

  • If you try to upload a file with an existing name, it will not be uploaded (be it a video or an XML file).
  • Aspera considers the Upload and Upload With Metadata permissions to upload only videos or videos with metadata, respectively.
  • If files with the same name need to be uploaded, they can be uploaded in different folders to avoid name validation and the file being ingested.
  • Aspera v1.4 can only be accessed through its CLI and the Desktop Client. The webUI has already been deprecated in this version.
  • Suppose an XML is uploaded, and the video is not yet in the bucket. In that case, the video is not ingested until the video(s) are in the bucket, and vice versa: if the videos are uploaded but the XML does not yet exist, they will be ingested until the XML is in the bucket.
  • If you need to use a specific profile, upload the video with its metadata (the XML). The account's default profile will be used if a video is ingested without metadata.