Copyright © 2022 Traco Systems a.s.

version 2022.3

Introduction

This is the essential guide to Traco GFX Administration, covering all the major tasks that administrators need to complete. Configuration of the Traco GFX app in Cloud UX is very straightforward and does not require regular maintenance.

All important settings can be found in the Cloud UX Administration interface and are accessible only for Cloud UX administrators.

Register MOS Server ID in iNews

Viz MOS server ID must be specified in the iNews MOS-MAP queue. Otherwise, the Rundown app in Cloud UX will reject drops of MOS items to a story.

  1. Connect to iNews server using iNews desktop app or Cloud UX
  2. Navigate to SYSTEM folder, open MOS-MAP queue, and select the first story (named 'MOS-MAP')
  3. Add your MOS server ID and display name between TABLE-START and TABLE-END lines: 
TABLE-START
...
mymos-server my-mos-server-title
...
TABLE-END
  1. After saving the story with new MOS mappings, re-login in to Cloud UX to pick up the new settings

Cloud UX | Traco GFX Administration Interface

Here is the list and description of all available settings for the Traco GFX app. After changing the settings the administrator has to manually save the changes with the Save button. Traco GFX Administration App

Traco GFX

  • NRCS: Enable/Disable integrations with the selected NRCS. Supported NRCS are iNews and Octopus.
  • PAM Engine ID: Interplay (Media Central | Production) Engine ID. This can be identified by using Interplay Access or by parsing the interplay-pam systemID from the Cloud UX url when PAM asset is opened.
  • Viz Pilot Edge URL: URL of the Viz Pilot Edge (https://<pilot_edge_fqdn_or_ip>:<port>/path). IMPORTANT! Must be HTTPS with a trusted certificate.
  • Viz Pilot Data Server URL: URL of the Viz Pilot Data Server (http(s)://<dataserver_fqdn_or_ip>:<port>).
  • Viz Preview Server Frame API URL: URL of the Viz Preview Server Frame API or Viz Connection Broker (http(s)://<preview_frame_api_fqdn_or_ip>:<port>/api/preview)
  • Viz Transition Logic: Enable/Disable Working with Viz transition logic within Traco GFX.
  • Viz Transition Logic - Layers Order: This determines the z-index (order) of layers when displaying them in the sequence timeline. Layer names must exactly match with the layer names defined in Viz scenes and must be prefixed with "-vizlayer-". Order of the layers must be defined ascending, starting from the lowermost.
    Layers not defined in this field will deafult to DEFAULT layer with the lowest z-index.
  • Viz Pilot MOS ID:
    • Primary: Regular Viz Pilot MOS ID. For more details see Viz Pilot MOS Gateway documentation.
    • Secondary: Used when the element's template has an assigned template tag TRACO_GFX_SECONDARY_MOS_ID
  • Viz Pilot NCS ID: NRCS ID for creating MOS graphical elements.
  • Camio Interface (LUCI) URL: URL of the Camio Luci (https://<camio_luci_fqdn_or_ip>:<port>/luci). IMPORTANT! Must be HTTPS with a trusted certificate.
  • Camio MOS ID: Camio MOS ID. For more details see Camio MOS Gateway documentation.
  • Camio NCS ID: NRCS ID for creating MOS graphical elements.
  • Rendered GFX Preview:
    • On Demand: Allow animation rendering of dataelements' preview in Cloud UX | MediaPlayer.
      IMPORTANT! Rendering the preview can overload the Viz Engine(s) used by the Preview Server Frame API if the number and performance of Viz Engines used for rendering is not adequate for the number of requests.
    • All - Except Viz Transition Logic Scenes: If enabled, all non-transition logic Viz graphics will be automatically rendered
  • Rendered GFX Preview for Transition Logic: Allow/Prevent animation rendering of dataelements' preview in Cloud UX | MediaPlayer for transition logic dataelements.
    IMPORTANT! Rendering the preview can overload the Viz Engine(s) used by the Preview Server Frame API if the number and performance of Viz Engines used for rendering is not adequate for the number of requests.
  • Traco GFX in Asset Inspector: Future use. Leave disabled.
  • Traco AI API URL - Service Interface: URL of the Traco AI API (http://<tracoai_api_fqdn_or_ip>:<port>). Defining Traco AI is necessary only when integrating with Traco AI.