Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Applies to 

An environment where Vidispine VidiCore API / Vidinet VidiNet needs to read and write files and metadata from Azure Blob Storage.

...

The article describes the basic configuration from a Vidinet VidiNet point of view. The Azure permissions are to be handled according to best practices to allow an external service to read and write to Azure Blob Storage.

...

Pre-requisites and system requirements.

...

  • a verified and working Azure account to manage Azure Blob Storage permissions.

  • understanding how to configure the Vidispine VidiCore API. In below example, we are using CURL

...

Table of contents

Table of Contents

Updating the

...

VidiCore API using CURL

You can of course also use Azure Blob Storage as regular Vidispine VidiCore storage, including importing and storing high-res and proxy copies in Azure, as well as transcoding to/from Azure storage.

...

This is easily achieved by registering storage in Vidispine VidiCore with a method that has a URI on the form azure://:{accessKey}@{accountName}/{containerName}/.

Create a configuration document XML

We start out by creating and example xml document to post to vidispine: storage.xml.

...

Navigate to the same directory and continue to update and configure Vidispine VidiCore API with the Azure example configuration.

Use CURL to update and configure

...

VidiCore API

In the below examples, we are using CURL to

...

Code Block
curl -uadmin:admin -X POST http://demo.myvidispine.com/API/storage -d@storage.xml -Hcontent-type:application/xml 

What's next?

  • When doing this Vidispine VidiCore will monitor and use the storage according to current storage rules.

  • Vidispine transcoding media is proxied by the Vidispine VidiCore application server.

  • For formats where headers are rewritten after transcoding is done, the transcoded file is cached locally and transferred to Azure after transcoding.

  • During transcoding, the files are available via the Vidispine VidiCore API function and are served by the application server.

  • All Vidispine VidiCore codecs are available, including H.264, ProRes, VC-1 (WMV), VC-3 (DNxHD) (subject to license)

...

Info

You can find more information on the different storage methods in the API documentation.

Configuring and adding a S3 bucket to Vidinet

Send Vidispine VidiCore API service logs to an AWS S3 bucket

...