If you can’t find it here, it’s not worth knowing.
Yes, with the launch event at IBC, we opened Vidinet for everyone.
Read the Vidinet Primer in the blog.
You need Vidispine Server 4.11 to make use of the Vidinet features. Upgrade to Vidinet Server is done the usual way (Vidispine db migrate), and is a smooth process. Vidispine Server 4.11 is now available in the Vidispine repo, and in the download section of the Support Portal (registration needed)
Currently, it is by invoice only. We are working on other payment methods.
We will start with AWS eu-west-2 (London) and AWS us-west-1 (N. California). New regions will follow soon.
We are working on making Vidinet available on Azure (ETA Q2’2018) and Google Cloud as well.
Vidinet is built for this operation. With an enterprise agreement, you will use Vidinet as above, but workers and media traffic will not leave the boundaries of your account.
Yes, we use secure traffic in all steps, both for commands and data.
Yes, APIdoc is included in the 4.11 package (as with all versions), updated with the Vidinet information. The 4.11 APIdoc is of course also available online.
It is in the making, expect it to be available mid-October.
At launch we offer transcoding and QC. Coming up is watermarking, studio-grade standards conversion, and document conversion.
This is on the roadmap for Q1’2018. This will make it possible to deploy a Vidispine system without any parts residing on-premise or in own cloud resources.
Not yet, but soon.