Version 21.3

21.3.1

2021-10-01

Improvements

  • Inefficient VidiCore startup check (#4943).
  • Better dataset validation error messages (#4939).
  • Only doing S3 URI validation for storages with methodTypes == NONE (#4916).
  • Ability to set fixed work delay for ReindexCruncher (#4906).
  • Add support for getting AWS credentials from EC2 roles with Glacier Vault (#4876).
  • Send shape modify notification if any child component has changed (#4633).

Bug fixes

  • Failed transcode step would close a growing file (#4938).
  • Too many parameter error in SQL query from group deletion on SQL Server (#4935).
  • Elasticsearch: highlight result missing from some of the timespan segments (#4933).
  • Search hit not correct on Elasticsearch if the query is using “facet with exclude” (#4925).
  • SNS notification on Item Metadata Change did not include the value of metadata-field (#4907).

Transcoder fixes

  • Keep outputting frames until end of interval (#190421).
  • Transfer job that can’t write to destination should fail (#190427)
  • Backport new R3D SDK to 5.5 and upwards (#190701)
  • Nablet XDCamHD encoder sets wrong GOP size (#191468)

21.3

2021-08-23

New versioning scheme for VidiCore and VidiCoder

In order to align versions within the Vidispine product portfolio, the versioning scheme for VidiCore and VidiCoder has been changed to YEAR.QUARTER[.PATCH], e.g., 21.3, 21.3.1, 21.4, and 22.1. Users can still upgrade from any 5.x to 21.3 directly.

VidiNet Cognitive Service support in VidiCore

A number of new features and improvements has been added to support VidiNet Cognitive Service (VCS) on VidiNet:

For more information about how to setup and use VCS, please refer to the documentation on VidiNet.

Enhanced AWS IAM role support

User is now able to specify a roleARN parameter when setting up a AWS resource in VidiCore. It makes cross account access using IAM role possible. This is supported in S3 storages method, S3 Event SQS Notifications, SQS/SNS notification action

Proxying HTTP connection via a VSA

It’s now possible to use VSA as a HTTP proxy, so that the http javascript object in VidiCore is able to access on-prem resources:

http.uri("http://localservice:7777/integration")
      .proxy("vxa://742c17e4-8f6f-489a-8caf-aae4c39d272f/")
      .proxy("vxa://e2c4c766-4a3e-4662-975c-7f4251385d8c/")
      .get()

Improvements

  • Add external id when creating placeholder item (#4789).
  • Support for AWS Restore Notifications (S3:ObjectsRestore:Completed) for SQS and SNS (#4723).
  • Doing quota calculation in small chunks (#4931).
  • Return 503 instead of 401 when the database is down (#4910).
  • Include database in the health check endpoint: /APInoauth/is-online?checkdb=true (#4798).
  • Implementation of Wildcard/Regex within the path logs in Audit Trails (#4625).
  • Add a new collection/{id}/collection endpoint to fetch child collections (#4017).

Transcoder improvements

  • Allow pass-through of URIs in SequenceDocument to NLEJobDocuments (#4845).

Bug fixes

  • Possible integer overflow during timecode comparison (#4924).
  • VSA connections may lead to race conditions (#4909).