Viz One 5.13

The Viz One 5.13 update delivers a MAM system that is faster and easier to use, install, and configure.

The latest version of Vizrt’s media asset management (MAM) Viz One system includes high-quality proxy media using Coder, federated search, federated media exchange, PostgreSQL support, graceful concurrent metadata editing, enhanced software installer based on Ansible, HTTP/2 access, enterprise-grade search reindexing, and a web-based metadata and thesaurus editor.

Vizrt will demonstrate Viz One at NAB 2017 stand SL2416. Contact Us and get your personalized demo.

Federated search improves sharing across departments and regions

Users can now simultaneously search multiple Viz One environments as a single request from the Studio browser-based interface. Federated search means users can find media across systems without having to manually authenticate or perform redundant searches. This feature offers a simple way to improve collaboration and media reuse across multiple systems.


Federated media exchange

Federated media exchange simplifies the exchange of assets between different departments and offices. Enhanced cross-site media transfer enables users to easily share assets between Viz One systems. The cross-site transfer can be viewed, managed, and prioritized from both the sending and receiving systems. The transfer copies high-resolution media, monitors transfer progress, and registers a new asset with current metadata.

PostgreSQL support

Viz One now supports PostgreSQL 9.5 database, initially with single server installations only. PostgreSQL has the potential to significantly decrease IT costs compared with other enterprise database options.

High-quality proxy media with Coder for Apple ProRes™

Vizrt’s transcoder, Coder, is now used for proxy generation of Apple ProRes. Coder brings a number of enhancements such as improved proxy quality together with a more efficient H.264 codec and reliable scene detection. In subsequent releases, Coder will successively handle more media formats. Coder is integrated through the Viz One API, so it can be upgraded independently of the Viz One version.

Graceful concurrent metadata editing

Users get a warning when metadata changes they are trying to save are out-of-date. This feature makes it easier for multiple users to simultaneously edit Viz One metadata.

In systems where content is modified by several users over a short time span, especially for high priority assets, this new feature provides users with confidence that their metadata changes will not inadvertently undo any updates another user has performed. Concurrent metadata editing uses etags version information from the API, meaning that any warnings in Studio are also presented to other applications or third party tools that modify metadata.


Metadata administration

Viz One metadata forms can now be created, previewed, edited, and saved from a web-based Vizrt Data Format (VDF) form editor. The editor assists pre-planning for metadata, and is also helpful at installation and setup, as well as during operation.


Faster access with optional HTTP/2

Viz One now ships with HTTP/2 support enabled by default on web servers and file servers. End-users will experience improved speed and performance of the Studio client, as data loading methods have been optimized. This also improves performance when opening multiple Studio tabs in a browser.

Enterprise-grade search reindexing

Viz One search indexes can now be updated (reindexed) as a non-disruptive background process. Viz One search indexes typically need to be updated when implementing new functionality. For system administrators, this search index update, (also known as a reindex), is now significantly easier to manage. Reindexing can now be performed as a background index that an administrator can activate after indexing is complete. The reindexing process can also be paused and resumed. Together, these new improvements give the administrator significantly more control over the reindexing process, whilst ensuring users are not disrupted.

Thesaurus administration

Administrators can now add, remove, and modify concepts in a Viz One thesaurus from a web-browser management page. This feature helps the archivist create and maintain a high quality thesaurus, which means overall metadata quality is more uniform and long-term value of the archive is maximized.

Capture spotcheck

Frame-level quality control (QC) markers can now be created from the Capture utility using a new highres spotcheck mode. The markers are saved as Viz One QC log entries. This feature extends existing quality control functionality over to the Capture utility.

Viz Dart supports Java Web Start

The Viz Dart client can now be launched as a Java Web Start application from the Studio client. It is also possible to configure whether the system should launch the application as an Applet or run locally using Java Web Start. This feature enables a browser plugin-free mode of launching the Dart application, which is necessary both web browsers and Java 9, no longer support Java applets.

Ansible for software installation

Viz One is now installed via Ansible playbooks. An extendable Ansible-based framework simplifies Viz One installation, configuration, management, and upgrade procedures. In particular, multi-host Viz One installations can benefit from faster and more reliable deployment processes.

Improved Viz One API

The REST-based Viz One API has been extended with a number of features, including: 

  • Media Relations Tracking information can now be completely manipulated via the API. This makes it easy to store and maintain detailed media relations tracking information.
  • Media Deletion has been extended to be exposed on a more granular level via the API. This enables tools to specify exactly which media groups and instances that are to be marked for deletion.
  • Audit Trails for media access are now available. This enables keeping track of what users have played a particular video file.
  • Segment Lists now have Access Control information. This enables defining which users can view or change a segment list. This is important as segment lists affect how assets will be played out.
  • Search API now provides information and filtering on whether an asset has meta-graphics. This enables clients to easily show if an asset has meta-graphics.
  • Asset API uses etags version information. This means that warnings in Studio are also presented for any other applications or third party tools that have performed changes since a current user or other application made changes.

See the full release notes available at