This page contains an overview of the new features in each release. For a full listing of the features, bug fixes and upgrade notes, please see the release notes.
$ node stats.js config.js 17 Dec 12:23:31 - reading config file: config.js 17 Dec 12:23:31 - server is up 17 Dec 12:23:31 - DEBUG: Loading backend: ./backends/graphite 17 Dec 12:23:34 - DEBUG: vs.job.total.aborted:99|g 17 Dec 12:23:34 - DEBUG: vs.job.total.aborted_pending:0|g 17 Dec 12:23:34 - DEBUG: vs.job.total.failed_total:520|g 17 Dec 12:23:34 - DEBUG: vs.job.total.finished:50491|g 17 Dec 12:23:34 - DEBUG: vs.job.total.finished_warning:3|g 17 Dec 12:23:34 - DEBUG: vs.job.total.ready:0|g 17 Dec 12:23:34 - DEBUG: vs.job.total.started:1|g 17 Dec 12:23:34 - DEBUG: vs.job.total.waiting:0|g 17 Dec 12:23:34 - DEBUG: vs.service.load.5:0.02|g 17 Dec 12:23:34 - DEBUG: vs.service.load.60:0.02|g ...
Multithreaded transcoder pipeline¶
The decoding part of the transcoder is now multithreaded for I-frame-only content. This means that for content such as ProRes, D10/IMX, etc, you will see a speed-up, especially if the input material is in high resolution.
FileCatalyst is now available as a transfer method between storage locations. The Vidispine application acts as a FileCatalyst client which can communicate to FileCatalyst servers for transferring files.
In order to register a FileCatalyst server for a storage, add a new transfer method to the storage.
<method> <uri>filecatalyst://fc:s3cret@localhost:2100/incoming/</uri> <type>TRANSFER</type> </method>
For more information, see FileCatalyst Integration.
StorNext file information¶
For files residing on a Quantum StorNext file system, Vidispine can now show metadata on the file. In order to use this, enable web services on StorNext and add a HSM method to the storage.
<method> <uri>stornext://webservice:webservice@localhost:81/stornext/snfs/</uri> <type>HSM</type> </method>
For more information, see StorNext Integration.
It is now possible to create standalone documents with arbitrary metadata. If you are using global metadata but need to store a large amount of data, leading to a large metadata documents, then consider splitting it up into smaller documents, for example by entity or group of entities.
<MetadataDocument xmlns="http://xml.vidispine.com/schema/vidispine"> <timespan start="-INF" end="+INF"> ... </timespan> </MetadataDocument>
Filters and facets¶
Search filters have been added to replace the facet filters. They support arbitrary queries compared to facet filters that only allow a single field to be queried.
Filters can also be excluded from certain facets. This can be used to reduce the number of search requests need to display search pages that uses multiple facets and multiple drill down options.
PUT API/item Content-Type: application/xml <ItemSearchDocument xmlns="http://xml.vidispine.com/schema/vidispine"> <filter name="typeFilter"> <field> <name>mediaType</name> <value>audio</value> </field> </filter> <facet count="true"> <field>mediaType</field> <exclude>typeFilter</exclude> </facet> </ItemSearchDocument>
<ItemListDocument xmlns="http://xml.vidispine.com/schema/vidispine"> <hits>1</hits> <item end="+INF" id="VX-361763" start="-INF"> <timespan end="+INF" start="-INF"/> </item> <facet> <field>mediaType</field> <count fieldValue="none">1867</count> <count fieldValue="image">33</count> <count fieldValue="video">10</count> <count fieldValue="audio">1</count> <count fieldValue="data">1</count> </facet> </ItemListDocument>
- It is no longer necessary to use the application server’s /tmp directory to store output files for Azure, S3, FTP destinations. Instead, this can be handled using segment files on the destination storage.
- The timestamp handling for generating MP4/H.264 files have been rewritten. This means that proxy files are frame accurate without without the previous tweaks (“useDTSmode” et al).
For the full list of changes, see the release notes.
Thumbnails on cloud storages¶
Thumbnails can now be stored on cloud storages such as Amazon S3 and Azure. Thumbnails will be stored using one file per thumbnail.
<ResourceDocument xmlns="http://xml.vidispine.com/schema/vidispine"> <thumbnail> <path>direct+azure://:+kLZrqckLZrqckLZrqckLZrqc==@mystorage/my-container/</path> </thumbnail> </ResourceDocument>
Use job pools to ensure that long running low priority jobs don’t block high priority jobs from running.
PUT /configuration/job-pool Content-Type: application/xml <JobPoolListDocument xmlns="http://xml.vidispine.com/schema/vidispine"> <pool> <priorityThreshold>HIGH</priorityThreshold> <size>2</size> </pool> <pool> <priorityThreshold>LOWEST</priorityThreshold> <size>3</size> </pool> </JobPoolListDocument>
Shape and file search¶
PUT /search/shape Content-Type: application/xml <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <ShapeSearchDocument version="2" xmlns="http://xml.vidispine.com/schema/vidispine"> <field> <name>language</name> <value>en</value> </field> </ShapeSearchDocument>
Support for joins has also been added to allow for cross-entity search between items, shapes and files.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <ItemSearchDocument version="2" xmlns="http://xml.vidispine.com/schema/vidispine"> <text>peach</text> <shape> <field> <name>language</name> <value>en</value> </field> </shape> </ItemSearchDocument>
This release brings support for:
- PostgreSQL 9.3.
- Java 7 update 67.
A number of improvements have been made to the WADL file. Missing parameters have been added and duplicate parameters have been removed for example. It has been updated to also include:
- Parameter options.
- Markers for repeating parameters.
The WADL file can be obtained using GET API/application.wadl.
The API documentation has been moved from the Vidispine wiki into this documentation that you are now reading.
It is available online at http://apidoc.vidispine.com/latest/ and also on your local installation at /APIdoc.
The 4.2 series now requires Java 7, specifically Java 7 update 25 as later versions have known bugs with GlassFish 3.x.
Efficient file I/O¶
The new Java 7 File API is used to reduce the number of file system operations that are used when scanning local storages.
The Solr configuration now exists in the indexing configuration, but note that the Solr configuration properties are still supported.
This configuration can also be used to specify which fields should be included in the full text index, unless specified explicitly for a specific field.
PUT /configuration/indexing Content-Type: application/xml <IndexingConfigurationDocument xmlns="http://xml.vidispine.com/schema/vidispine"> <solrPath>http://localhost:8088/solr</solrPath> <fieldDefault> <name>xmp_*</name> <fullText>false</fullText> </fieldDefault> </IndexingConfigurationDocument>
Detect renamed files¶
Renamed files can be detected and and re-associate based on the file checksum. Enable it using the detectRenamedFiles storage property.
This release adds support for Ubuntu 14.04, Windows 2012 R2 and MySQL 5.6. At the same time, support for PostgreSQL 8.x, MySQL 5.1 and Java 1.6 has been discontinued.
For the full list of changes, see the release notes.