Version 4.15

The release notes will tell you what’s new in each version, and any changes that you must be aware of when upgrading. For reference, Vidispine ticket numbers are printed as (#1234).

4.15

2018-10-12

AWS Elemental Media Convert

Transcoding using AWS Elemental Media Convert is now supported via Vidinet (#3420) for files on S3.

<ResourceDocument xmlns="http://xml.vidispine.com/schema/vidispine">
  <id>VX-1</id>
  <vidinet>
    <url>vidinet://e1423727-...:...@42a73b4c-8974-4402-a237-17b80bd11350</url>
    <name>My AWS Media Convert</name>
    <endpoint>https://services.vidinet.net</endpoint>
    <type>ELEMENTAL_MEDIACONVERT</type>
    <state>ONLINE</state>
    <scheme>s3</scheme>
  </vidinet>
</ResourceDocument>

To transcode with the new Vidinet resource you need a new shape-tag with the mediaconvert tag in it.

 <TranscodePresetDocument xmlns="http://xml.vidispine.com/schema/vidispine">
   <description>
     BROADCAST, XDCAM, MXF, MPEG2 HD422, WAV, 16x9 DAR, 1920x1080p, 23.98 Hz, 50 Mbps CBR
   </description>
   <name>
     __mediaconvert_Broadcast_Xdcam_Mxf_Mpeg2_Wav_16x9_1920x1080p_24Hz_50Mbps
   </name>
   <audio/>
   <video/>
   <mediaconvert>
     <outputSetting>
       { "Type": "SYSTEM", "Category": "BROADCAST-XDCAM", ... }
     </outputSetting>
   </mediaconvert>
 </TranscodePresetDocument>

Temporary credentials for S3/Azure

It is now possible to generate temporary credentials for S3 (#3389). These credentials are limited to a specific object and expire after a user defined time period.

POST /storage/file/VX-56/uri?scheme=s3&write=true
<URIListDocument xmlns="http://xml.vidispine.com/schema/vidispine">
  <uri>s3://ASIA....:...@example/image.jpg?sessionToken=...</uri>
</URIListDocument>

If you prefer to work with HTTP, then presigned HTTP URLs can be requested instead. This works with both S3 and Azure Blob Storage.

POST /storage/file/VX-98/uri?scheme=http&write=true
<URIListDocument xmlns="http://xml.vidispine.com/schema/vidispine">
  <uri>https://example.blob.core.windows.net/image.jpg?sig=...</uri>
</URIListDocument>

CORS

Vidispine can be configured to emit Cross-Origin Resource Sharing (CORS) heades (#3299). For example, to configure that web application running on example.com may access the API:

<CORSConfigurationDocument xmlns="http://xml.vidispine.com/schema/vidispine">
  <entry>
    <request/>
    <response>
      <allowOrigin>http://example.com</allowOrigin>
    </response>
  </entry>
</CORSConfigurationDocument>

Deletion locks

It’s now possible to set deletion locks on collections, items and files, to prevent them from been moved or deleted (#3283).

<DeletionLockDocument xmlns="http://xml.vidispine.com/schema/vidispine" >
  <id>VX-1574</id>
   <user>admin</user>
   <expiryTime>2018-10-22T14:27:03.175+02:00</expiryTime>
   <modified>2018-10-12T14:27:03.175+02:00</modified>
   <entityType>Item</entityType>
   <entityId>VX-32140</entityId>>
</DeletionLockDocument>

Deletion locks can be inherited from parent to child entities, and used in searches. They also support notifications.

New features

  • Get storage that would be used for ingest (#3390).
  • Transcoder discovery via SRV records for secure HTTPS transcoder URLs (#3388).

Improvements

Transcoder improvements

  • Remove incorrect file and folder name in shape metadata (#3433).

Bug fixes

  • Old items/files not removed from Solr after reindex (#3432).
  • Placeholder raw import for binary files fail due to NPE (#3349).
  • Search index not updated after adding/removing item sequences (__sequence_size) (#3346).
  • HTTP 401 when fetching components for shape (#3343).
  • Jobs gets stuck if defaultTranscoder is not a valid Vidinet resource (#3328).
  • Self tests halting on transcode self test failure (#3325).
  • HTTP 500 on transcoder resources when schema validation is enabled (#3307).
  • HTTP 500 when fetching job and specifying custom timezone (#3225).
  • HTTP 404 on import request using shape-tag with comma in name (#3213).
  • Can’t set user metadata when creating a new user (#2926).
  • Incorrect “loc” element for access controls (#2879).
  • Not able to set metadata-field values using JSON (#2755).

Upgrading from 4.14

  • Solr: No changes to the documents. Re-indexing is not required.
  • The type of job that is created for the placeholder raw import request has changed from THUMBNAIL/TRANSCODE to PLACEHOLDER_IMPORT.