Cinegy Traffic Gateway’s core purpose is to translate a weak reference for a media item into a fully-described, absolute reference that is described in a format Cinegy products can consume directly.

A system can provide a list of media identifiers, along with start time and approximate duration values, for items to playout, and Cinegy Traffic Gateway will be responsible for locating media files based on that identifier. It will also discover the specifics of the media (e.g. such as finding audio tracks, reading the actual media durations and time-code values) before creating an XML-based document which is ready for immediate use by other Cinegy software (most notably Cinegy Air).

Cinegy Traffic Gateway can also translate secondary events indicated against the primary media item into commands, such as displaying a logo, making an SDI route, or any other generic event available via the Cinegy Event Manager plugin sub-system.

Some other workflows can be triggered by Cinegy Traffic Gateway, for example, creating placeholder objects inside a Cinegy Archive database or using the placeholder provider scripts to trigger other custom workflow steps while attempting to find a match.

The standard workflow of a basic playlist submission task is described below:

  1. 3rd party application generates XML or CSV traffic playlist.

  2. Cinegy Traffic Gateway opens the playlist and parses it.

  3. Cinegy Traffic Gateway looks for the media via TrafficID in Cinegy Archive or other file storage.

  4. If media cannot be found, Cinegy Traffic Gateway creates a Placeholder Roll in Cinegy Archive and adds a reference to the placeholder in the Cinegy Air playlist.

  5. The playlist is loaded into Cinegy Air.

  6. Cinegy Air tracks the status of all Placeholder Rolls and updates the playlist with the media once the Rolls are filled.