Version 4.16

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.16.3

2019-03-28

Bug fixes

  • Mutable range write failing if transcoder writes large “gaps” in file (#3713).
  • Move metadata migration fails if target group exists (#3708).
  • Very slow file write completion when using segment files on Azure (#3694).
  • Failing to reindex collection if the collection number is high (#3668).
  • Incorrect normalization of combining characters for JSON (#3663).
  • Filename scripts that fail due to a temporary error causes jobs to fail instead of retry (#3573).
  • Transcoding documents using CloudConvert fails (#3533).

Transcoder fixes

  • MPEG-TS erroneously detected as MPEG-PS (#3666).
  • Closed captions not recognized in MXF (#3620).
  • Transcoder hangs on media check of tar file with encrypted MXF (#3559).
  • Automatically adjust odd dimensions for H.264 output (#3414).

4.16.2

2019-03-13

Bug fixes

  • Slow add/delete of item from large collection (#3671).
  • CORS does not work with /API/user/{user-id} (#3662).
  • Transfers to storage with read=false on method end up in WAITING state (NO_SUCH_METHOD) (#3622).
  • Signed S3 URL generation doesn’t take into account SSE algorithm configuration (#3619).
  • Jobs that had been in WAIT state can not be deleted (#3555).
  • Unable to use scene change detection with thumbnail jobs (#3493).
  • Repeated “Ingoring no longer waiting job” error in logs (#3681).

Transcoder fixes

  • Transcode crashing on transcode of certain PSD files (#3691).

Agent fixes

  • Incorrect Guava version in VSA 4.16.1 causing writes to fail (#3676).
  • S3 files are not properly written by VSA when using mutable range writes (#3664).

4.16.1

2019-02-08

Improvements

Bug fixes

  • Using empty:/// URI does not work for truncating audit log and transfer logs (#3609).
  • HTTP 400 when setting external ids or metadata field groups in metadata (#3599).
  • Incorrect file list counts if a file belongs to multiple items for Elasticsearch (#3595).
  • Incorrect search result if the search value contains “literal” spaces for Elasticsearch (#3594).
  • Auto-completion not case insensitive for string-exact for Elasticsearch (#3593).
  • SAML authentication broken with Bouncy Castle 1.60 (#3588).
  • Too strong SSH key generated by Vidispine on Java 1.8u91 and later (#3583).
  • Proxy links for manually getting file data does not respect ‘apiNoauthUri’ property (#3096).
  • Sorting users by username/realname not working when searching for users (#2961).

Transcoder fixes

  • Tearing in video output when deinterlacing source (#3606).

4.16

2019-01-13

Sequence rendering using Vidinet

Sequence rendering can now be performed using Vidinet. This works just like when using a Vidinet transcoder to transcode or conform (#3221).

POST /sequence/render?tag=h264&resourceId=VX-42

Stream files from agent

You can now get access to read files directly from the VSA. Previously you could only access the files by streaming them through Vidispine. This make sense, if you for example are on the same on-premise network as the VSA and you have Vidispine server running in the cloud. The access is requested with a new methodType: AUTO-VSA.

Paging using cursors

It is now possible to use the cursorMark/search after features from Solr/Elasticsearch to improve the deep paging performance during a search (#3476).

This feature is supported on collection and item search as well as when listing files using the new the cursor parameter.

Note

Only metadata searches in the generic interval supports cursor.

Query boosting

It is now possible to boost field values in item and collection searches by adding boost factors in the search documents or metadata field definitions.

PUT /item
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>
<ItemSearchDocument xmlns="http://xml.vidispine.com/schema/vidispine" version="2">
  <operator operation="OR">
    <field>
      <name>title_field</name>
      <value boost="10">phoenix</value>
    </field>
    <field>
      <name>description_field</name>
      <value>phoenix</value>
    </field>
  </operator>
  <sort>
    <name>_score</name>
    <value>descending</value>
  </sort>
</ItemSearchDocument>
<MetadataFieldDocument xmlns="http://xml.vidispine.com/schema/vidispine">
  <name>title_field</name>
  <type>string</type>
  <boost>10.0</boost>
</MetadataFieldDocument>

Key-value metadata improvements

Support for key-value metadata has been added to:

  • Shape tags (#3440)
  • Libraries (#3412)
  • Task definitions (#3439)

The JavaScript job object has also been updated with additional functions for working with the job data (#3441 and #3437):

Improvements

Bug fixes

  • Authentication failure when VSA connects over SSH to Vidispine running on Java 1.8u91 or later (#3569).
  • Generating a pre-signed Azure URL results in a HTTP URL, expected HTTPS (#3551).
  • Only sidecar files with lower case file extensions are picked up as sidecars (#3429).
  • Resolution and aspect ratio not marshalled properly with useJackson=false when getting shapes as JSON (#3422).
  • OptimisticLockException if JavaScript job problem is checked while job is running (#3565).
  • JavaScript notification actions cannot be configured when running on a MS SQL Server database (#3315).
  • GET or DELETE of a non-existent metadata lock returns 500 (#3303).
  • Possible metadata migration failure due to long running database queries (#3280).
  • Component import to shape fails because of duplicate job creation (#3278).
  • Don’t allow transient metadata fields to be modified (#3277).
  • HTTP 500 response when importing a Final Cut XML that has a project element with no children (#3226).
  • Missing mediainfo section for shapes imported by placeholder imports (#3206).
  • GET storage ignores the status parameter (#3148).
  • NPE instead of proper error message if export template fails to evaluate (#2889).
  • Incorrect file key logged for API requests (#3568).

Transcoder fixes

  • The transcoders StatsD metrics not compliant with collectd (#3192).

Upgrading from 4.15

  • Solr: No changes to the documents. Re-indexing is not required.