Viz One 5.10: Tighter Avid integration, better HTML5 video, and a more powerful API

Version 5.10 of Vizrt’s media asset management (MAM) system is released with fast access to currently ingesting material in Studio, support for using meta-graphics with Avid Media Composer, and more functionality to drive web portals using the Viz One API.

Using growing files in the Studio web interface

Viz One’s browser-based editor and HTML5 video player, Studio, now supports growing files. This allows users to preview and rough cut material as media ingests. The package player in Studio has also been extended to enable users to make changes to packages directly in Studio without using Logger.

Saving meta-graphics from Avid Media Composer and Avid Interplay

Meta-graphics offers a new way of adding and storing graphics up to the time of playout. Rather than burning graphics into video and rendering a final version of the clip within the graphics plugin, Meta-graphics lets Avid Media Composer and Avid Interplay editors save the graphics metadata alongside clean newly-edited video, saving both to Viz One. Both elements can then quickly be moved into a playlist or rundown ready for on-air play­out. This means journalists and operators in the control room can make changes to graphics right up until moments before air. The clean video and graphics elements can now be quickly composited and rendered as finished clips with graphics to be played out to air or sent to online.

Access to more functions in the Viz One API

The Viz One Third Party API has been extended with a number of features, including:

  • Super users can now masquerade as other users via the API and perform actions on behalf of another user. This allows using the API to automate production steps while ensuring audit trails and other data is consistent with the end-user that kicked-off a particular sequence of events.
  • Search facets are now available via the API. This enables clients to build powerful search interfaces that use facets to refine and explore search results.
  • The multi-level search API that allows searching across different levels in the data model now also shows related assets on other levels in the search results. This enables clients using the API to easily display far more relevant search results.
  • Search suggestions are now also available for clients using the API. Search suggestions are a great addition to any client offering a search interface against the API.
  • Timecode information, including all information on any timecode jumps in the material, is now available via the API. This allows clients to display the correct timecode for material that has timecode jumps.
  • The thesaurus data model entity can now be completely manipulated via the API. This enables clients to create or modify all properties of a thesaurus via the API. The new API makes it very easy to build both clients and external sync mechanisms to other SKOS-based thesauri and data sources.
  • The custom javascript menu items in Studio can now provide their own logic for when a menu item should be made available to a user. This can be used to hide menu items based on for example asset metadata or media status.

Apple ProRes p24.00 and p18.00

The system now fully supports storing and editing p24.00 and p18.00 in Apple ProRes. The p24.00 variant is commonly used for film production in addition to the p23.98 frame rate we already support. The p18.00 variant will be used to store historical footage in the p18 frame rate and is not supported in all of the third party systems with which Viz One integrates.

More asset relationship types

Studio can now display more media relationships that an asset may have. Relationships already show what media was used to compose the asset, what other assets the asset has been used to create, what tapes are linked to an asset, what rundowns or playlists the media appears in and many more. Several new media relationships have now been introduced to allow representing and showing assets that are bound by contract assets as well as assets that are strongly connected to the asset and have the same exact timing information - for example for dubbing and subtitles.