IGO Architecture
Distributed Architecture
Database Engine
IGO is based around a distributed architecture whereby not just the data but also the implementation script is
stored in the industrial strength Microsoft SQL Server database. For smaller implementations we can of course
use the free MSDE or SQL Express engine.
Resilience
Multiple SQL Servers can be configured using log shipping or replication for "warm backups", or a SQL Server cluster can be implemented for maximum resilience.
IGOEditor
IGOEditor is the primary IGO component. It contains both the graphic creation and stacking/transmission user interfaces, and the script authoring interface.
Create, search for, edit, stack and transmit graphics all from within IGOEditor. Multiple machines can be configured for transmission, with optional interlocking where they are driving a single render head.
IGOView
IGOView runs on a multi-head machine, and is responsible for rendering monitoring feeds for presenters and the gallery.
In most cases we provide a "preview" (ie the next graphic in the stack), a "midview" (the current graphic in an "easy to read" format) and a "postview" (a scolling view of recent lower third graphics).
IGODataLink
The DataLink component is responsible for interfacing IGO to wires feeds via a TCP sockets or serial connections.
Incoming data messages can be processed with script inside the IGO event handlers to automatically create graphics for applications such as elections or gameshows.