Swift News: Manual and overview

Swift News

Manual and overview

ORIGINAL DATE 28/02/2017
VERSION 1.0; 2.0


This document sets out the overall configuration and the constituent applications of the product. It follows the life-cycle of a graphic template from creation to transmission –  from the creation of graphic templates by the design department through the completion of those templates by journalists at their desktops finishing in the transmission of the completed templates manually in a gallery or using automation systems and the MOS protocol.

The newsroom system is a distributed system. It consists of many disparate applications running on a network of computers. The diagram below sets out the platforms, applications and protocols involved. It does not represent an actual newsroom. There is for instance only one journalist desktop platform – in an actual newsroom there would be many.

Data and control flow in the diagram above moves from left to right – creation on the left, storage/distribution on the centre-left, control on the centre-right and playout on the right.

Note: RT graphic servers are grouped into a single box in the diagram but would usually be run on several boxes – so the MediaStore would be run on an RT MediaStore platform etc. The following will refer to these separate platforms. A platform here means a computer that will host one or more RT applications. For example, the RT DataServer will host the DataServer and DataClient applications – see below for platform descriptions.

The workflows are as follows:

  1. Designers and producers use Swift CG and Swift CG+ to create graphic templates on the RT Edit platform (on the left of the diagram). They use the Repository application to store these assets in the Visual SVN repository on the RT Repository platform (part of RT Servers).
  2. Journalists incorporate the graphic templates into running orders using the RT NRCS ActiveX (on the left of the diagram) plugged into the NRCS Journalist Client. These rundowns are then sent to the NRCS server.
  3. The NRCS server will send these rundowns (or any modification of them) to a MOSGateway instance (which is registered with it a MOS device) running on the RT MOSGateway platform. This instance will in turn synchronise the new/updated rundowns to the RT DataServer platform and the new/updated mosObjects to the RT Repurposing platform.
  4. The RT ActiveXPreview platform has the specific purpose of generating final frame previews of graphics configured by the RT NRCS ActiveX. It runs multiple Swift Engine renderers.
  5. The RT Repurposing platform will layoff the graphics described in mosObjects created in 2 as clips (using a combination of the MediaWatcher and Swift Engine applications) and will send these clips to the RT MediaStore platform.
  6. The RT MediaStore platform hosts a folder – assets written to this folder will be automatically synchronised to the appropriate machine. For example, images/movies and data files will be copied to the renderers (to be used when graphics are rendered out) using WinSCP over sFTP.
  7. The RT MediaWatcher platform runs the MediaWatcher application which continually ingests external data and “puts” it in a location accessible to the renderers (either for instance, a local MySQL database or the RT MediaStore platform).
  8. The DataServer instance running on the RT DataServer platform serves up the HTML5 control app Swift Live to a chrome instance running on an RT Control platform.

Related Manuals

  • Swift CG
  • Swift CG+
  • Repository
  • RT Newsroom (this manual)
  • MediaWatcher
  • DataServer
  • MOSGateway
  • ActiveX
  • Swift Live
  • Swift Playout
  • Swift Engine


This section lists and describes the applications used in the RT Newsroom product. These applications can be used in smaller subsets (for example, Swift CG and Swift Playout can be used together as a Character Generator – a simple low cost platform for creating and playing out graphics) but work together in a distributed fashion to provide newsroom functionality.

The descriptions below are cursory and meant as a guide. Please refer to the manuals for the individual applications for a full description of the application’s features and functionality.

All systems have a “Basic Install” which consists of the following:

DataClient: All systems will have a DataClient service installed. The Repository application sends this service commands to update the local version of the graphic project etc.

WinSCP and sFTP: All systems have the OpenSSH service enabled – this will run an sFTP server. Applications on other machines can use WinSCP (also installed) to transfer data and asset files to any other machine.

Miscellaneous:  The following utility applications are installed as part of the basic install: Ruby, 7zip, MPC-HC, Tortoise, Subversion, Vim, Notepad++, ffmpeg, and wget.

Swift CG and Swift CG+

Swift CG creates 2D graphics with simpler structure and more limited data requirements.

Swift CG+ is the full editor and can be used to create any form of broadcast graphic of any complexity.

These are the standard RTSW tools for creating and authoring graphics. The final outcome from using these tools is a graphics project. This is a folder which contains all the assets used by the graphics (font, images, geometries etc.) and the scripts and manifests that encapsulate the structure and behaviour of the graphics.


RT divides graphic assets into three kinds:

– assets that make up a project of graphics which have a very long life, typically being current until the look of a program or channel is redesigned). These are managed by the Repository application.

– image/movie assets that are relevant for just a single day. These are distributed by being dragged onto the Swift Live interface (see below). This sends them to the DataServer application which in turn sends them to the renderers for immediate use.

– image/movie assets that are relevant for a long period of time – images of politicians, sports club logos would be examples. These are usually handled by a MAM but RT provides a simple solution using a central folder of assets called MediaStore which is synchronised using WinSCP over sFTP to similar folders on other renderers and servers.

The Repository application is used to maintain a “versioned database” of graphic templates (and associated assets) where each change is logged and to distribute the latest version of these graphics to an editable list of client machines – in the newsroom case this would be some of the servers and all the rendering machines.

NRCS ActiveX

NRCS ActiveX implements the ActiveX functionality for NRCS desktop clients as described in the MOS Protocol. The purpose of these controls is to enable a non-expert user (for example, a journalist) to add graphic templates to a story in an NRCS running order.

These ActiveX controls allow users to select a graphic template,  complete the template (by entering values for template parameters), preview the completed graphic template and then add it to a story as a new item. The user can specify the objSlug and mosAbstract for the item. RT maintains separate ActiveX controls for each of the supported NRCS Desktop Clients.


MOSGateway communicates with the Newsroom Control System.

It uses the standard MOS protocol to query the NRCS about the status and contents of the running orders compiled using the NRCS. It also handles MOS messages from the NRCS reflecting changes to the current running order – especially the addition of graphics. It creates graphic stacks and pages for later playout from the running orders it receives from the NRCS.

Automated newsroom systems can control Swift Engine renderers indirectly. They do this by sending the MOS Protocol roCtrl messages to the MOSGateway.

This message commands MOSGateway to play out an item from a story in a running order (the running order, story and item are specified in the message). The item will have been created by dragging from a NRCS ActiveX embedded in a NRCS Desktop Client onto a story in a running order. The graphic template and parameters

The graphics that have implemented the cueGraphic, bringOn and takeOff methods. These map to the READY, EXECUTE and STOP commands in the MOS message.

The url of the Swift Engine to control is specified in the MOSGateway .conf file. Only one Swift Engine instance can be controlled by a MOSGateway instance.


The DataServer application is essentially a web server with broadcast graphic specific extra functionality.

DataServer serves up project manifest data to the NRCS ActiveX. The ActiveX actually makes a HTTP request for the data to the DataServer.

DataServer serves up the Swift Live control application to a chrome running on an RT Control platform. The DataServer will also handle HTTP requests from Swift Live to save and load preference, page and other file types stored on the RT DataServer platform.


The DataClient is a service which takes command from the Repository application over tcp/ip. It runs on any platform that needs graphic projects to be available locally – this includes all renderers and even some servers e.g. DataServer. There commands are:

RemoteVersion: return the current revision of the specified project in the locally checked out projects repository.

RemoteUpdate: update the specified project in the locally checked out projects repository. This will drag down changes to the project in the central repository and apply them to the local project – essentially bringing all the files and folders in the project on disk up to the latest version.

RemoteSynchronize: the local renderers will load a project when they are run up or when told to do so under external control. This command will send a command to the renderer to update its loaded version of the project with any of the changes made to the project on disk by the RemoteUpdate command.

RemoteDelete: delete the specified project in the locally checked out projects repository.

Swift Engine

The Swift Engine is a rendering application – it is a lightweight wrapper around the RT DLL renderer.

Swift Engine is used on a variety of platforms.

It is used on the RT Single and RT Duo platforms to provide preview channels to the Swift Live control application by streaming WebRTC. It can also be used to stream NDI but doesnt output SDI or 2110 – so it cannot be used for the main transmission channels at the moment if those output formats are required (Swift CG in Live mode is currently used).

It is used on the RT ActiveXPreview platform to render the final frame of a graphic (the last frame of the bringOn method) for use in preview in the NRCS ActiveX plugin.

It is used on the RT Repurposing platform to render out clips of the graphics described in MOS Objects created in the NRCS ActiveX plugin.

Swift Live

Swift Live is a HTML5 application served by DataServer (dataServer is a web server like apache or IIS but with broadcast graphic specific features). It allows the operator to control up to three channels of graphics with preview and NRCS integration.

Swift Live can load the playlists and pages obtained from the NRCS via MOSGateway and DataServer. Swift Engine is a lightweight version of Swift CG+ which outputs a WebRTC transport stream. This is used for preview in the web control application.

The Swift Live application is accessible from any desktop (that has network access to the server). Playlists or action button pages of graphic templates can be compiled and previewed at the desktop – these playlists and pages are automatically available to operators for transmission. This route to transmission by-passes the NRCS completely.


The MediaWatcher application ingests data from external sources, processes it and stores it away ready for use by the renderers.

To configure the application, the user creates a list of “InBoxes”. These match up a source of data (file, url, web server or serial port) with a destination (file, database, MOS). The application periodically checks the inboxes inputs (checking a watch folder, downloading a file etc). The application checks a list of internal plugins  to see which one will accept the input data.  The plugin will then process the data and write to the specified output. The plugins handle many standard and third party data types but new plugins can be added to handle specific customer data requirements on a services basis.

Communication Protocols

These protocols are used to move assets, data and newsroom rundowns between machines, to control renderers and stream graphic template preview to the Swift Live application.


This is a communication protocol based on websockets. It was developed by RT Software to support the development of HTML5 control applications. The messages are json packets. As well as the basic communications protocol (heartbeats etc), the WebSocket Protocol includes apis for running graphics, accessing databases, accessing graphic assets and manifests etc.

This protocol is used in three ways:

  • to allow DataServer to serve and support the Swift Live control application.
  • to allow Swift Live to control Swift Engine (to render graphics to air)
  • to allow DataServer to serve graphic project manifests and icons to NRCS ActiveX so the journalist can select and configure graphics.


The Repository application uses the svn command (part of the Collab Subversion  library) to communicate with a Visual SVN server on the RT Repository platform – to store and access graphic project assets in the repository etc.

The DataClient uses the svn command  to update checked out projects on the local machine.

WinSCP over sFTP

sFTP can be enabled on all machines by enabling the OpenSSH server under Windows 10 and WinSCP can be used to distribute files either putting the file on a remote machine or by synchronising folders across machines.

MOSGateway can be configured to send rundowns to the server running DataServer – from which it can be served up to Swift Live. It can also send MOSObjects to a server (the RT Repurposing platform) running a MediaWatcher configured to process MOSObjects and use the graphic info in them to drive a Swift Engine to render those graphics and save them to a movie file.

Images and movies can be distributed to renderers using Swift Live. The files are dragged onto the Manage Assets section of the application – this automatically sends those assets to the DataServer machine. They can then be sent to the renderers using the Synchronise option – this uses WinSCP to synchronise the folders containing these assets on the DataServer machine with the corresponding folders on the renderers.

Images and movies can be distributed to renderers using the RT MediaStore platform. They are copied onto the MediaStore folder on the platform. From there they are copied onto registered target machines by synchronising the folder with corresponding folders on those machines – using WinSCP over sFTP.


MOS is a protocol for communications between Newsroom Computer Systems (NRCS) and Media Object Servers (MOS) such as Video Servers, Audio Servers, Still Stores, Character Generators, Automation Servers, and Prompters.  The MOS Protocol development is supported through cooperative collaboration among equipment vendors, software vendors and end users.

An NRCS is a centralised system that enables the creation of running orders of news stories. RT supports three so far (iNews, ENPS and OpenMedia).

It has three  uses in the newsroom configuration:

  • It allows MOSGateway to communicate with the NRCS. MOSGateway uses MOS messages to obtain running orders and to respond to MOS messages from the NRCS to update current running orders and MOS objects
  • It allows the NRCS ActiveX (NRCS desktop client plugin) to insert graphic templates selected and configured by the journalist into running order stories as items (which are in turn passed onto MOSGateway).


WebRTC is a free, open project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The RT renderers can create a WebRTC (unbuffered) video stream of the graphics it renders.

The Swift Engine application (a lightweight wrap of the full RT renderer) uses it to provide a desktop preview of graphics for Swift Live.

The WebSocket Protocol has been extended to support this protocol to facilitate the inclusion of a movie window for preview in an HTM5 application.


The platforms involved vary from high-end graphics workstations used to create graphic assets to low-end desktop computers used to host the playout HTML5 application in a Chrome browser. The hardware recommended by RT can be found on the RT website at: https://rtsw.co.uk/support_specs/#EnablingTechnology.

The types of platform are:

RT Edit

Applications: Swift CG, Swift CG+, Repository
Hardware: high-end graphics workstation.

Designers will use tools like Photoshop and AfterEffects to create images and movies and Maya and Studio Max to create geometries and shaders. These can be imported into Swift CG and CG+ (via the fbx exchange format file) along with other assets like fonts and used to author graphics.

Once ready the graphics can be stored in a central repository (on the RT Repository platform) and then distributed to the RT Single, RT Duo, RT ActiveXPreview, RT Repurposing and RT DataServer platforms using the Repository application.

RT Repository

Applications: Visual SVN
Hardware: file server

This hosts Visual SVN repository server – the graphics assets repository. It stores the initial version of a graphics project and then every change (with a comment) made to it. The repository will grow in size over time as graphics are added and changed. Projects are typically less than a Gigabyte.

RT Single and RT Duo

Applications: Swift Engine, Swift CG+, DataClient, OpenSSH sFTP
Hardware: high-end graphics server with SDI/IP video card

The graphics templates and associated assets are held locally – distributed here by DataClient dragging down project changes from RT Repository platform. Any transient assets (movies and images mainly) needed by playout are copied locally (to ensure speed and security of access) into the MediaStore folder over sFTP.

Swift Engine is launched by clicking a desktop icon. It loads all the graphic assets on startup (templates are loaded when required and then cached), opens up SDI video inputs and outputs and any network sockets needed for control.

It then waits for a control application to connect. Under control it will play graphics and methods and render the output to the SDI video out. It can either produce a fill and key output and be keyed onto the transmission stream downstream or it can take the transmission stream as input and render the graphics onto it.

The RT Duo platform runs four renderers (two tOG Lives producing 2110 video outputs for the live channels and two Swift Engines producing WebRTC transport streams for the preview channels on the Swift LIve control interface).

The RT Single platform runs two renderers (one tOG Live producing a 2110 video output for the live channel and one Swift Engine producing a WebRTC transport stream for the preview channel on the Swift LIve control interface).

Windows bat files and desktop icons which start and stop the renderers are also provided.

Newsroom desktop and NRCS ActiveX

Applications: NRCS Journalist Client, NRC ActiveX plugin
Hardware: desktop computer

This hosts the desktop client of the NRCS which journalists can use to create running orders, enter their stories and store them in the central database of the NRCS (hosted on the NRCS server).

These NRCS Desktop Clients all have support for MOS Protocol compliant ActiveX controls. The NRCS ActiveX can be loaded as part of the NRCS Client (selected from a list of controls or by clicking on an item in a story). The journalist can then select a graphic template and enter data for it (which can then be previewed using a still supplied by a Swift Engine on the RT ActiveXPreview server). The template and data can then be dragged onto a story (creating a mosObject). This creates an item within the story with a mosPayload that holds a description of the graphics template and a mosObject reference.

RT ActiveXPreview

Applications: Swift Engine, DataClient, OpenSSH sFTP
Hardware: high-end graphics server

The NRCS ActiveX plugin is used by the journalist to select and configure a graphic (to be added to the NRCS rundown). To preview the graphic the ActiveX can request a final frame from a Swift Engine instance running on this platform. It runs up to 10 instances and the ActiveX randomly picks between them.

RT MOS Gateway

Applications: MOS Gateway, WinSCP
Hardware: file server

This hosts the MOSGateway application which runs in the background without interaction reading, saving and converting running orders and messages from the NRCS. This uses very little disk (running orders are typically small).

It also copies NRCS Rundowns to the RT DataServer platform and NRCS MOS Objects to the RT Repurposing platform.

RT Repurposing

Applications: MediaWatcher, Swift Engine, DataClient, OpenSSH  sFTP
Hardware: high-end graphics server

The purpose of this platform is to automatically render out graphics as movie files (with alpha) for use in NLEs. The graphics are specified by the journalists in the ENPS Client and passed to the MOS Gateway server as MOS Objects. The MOS Gateway passes them to this server using WinSCP over sFTP. A MediaWatcher application watches a folder for these MOS Object files. It sends commands to a Swift Engine instance to render the graphics described in the MOS Object files to movie files. The movie files are then moved to the Facilis SAN using WinSCP over sFTP.

RT MediaWatcher

Applications: MediaWatcher, WinSCP, MySQL
Hardware: file server

This hosts the MediaWatcher application which handles external data sources – acquiring the data, processing it and storing the results away. For example it will read social media files pushed by NeverNo. It processes the xml files containing the message info into a MySQL database and the avatar images or associated images/movies to the Facilis SAN (from where it is distributed to the renderers).

RT DataServer

Applications: DataServer, OpenSSH sFTP
Hardware: file server

This hosts the DataServer application – this is a Web server that serves up graphic manifest data to the NRCS ActiveX or the Swift Live HTML5 application running in a chrome browser on an RT Control platform. It also serves up MOS Rundowns copied onto the platform using sFTP (from the RT MOS Gateway platform) to Swift Live.

RT MediaStore

Applications: WinSCP
Hardware: file server

This platform hosts a folder called MediaStore (containing image/movie or data files) and it synchronises with corresponding folders on other platforms (mainly the renderers). The folder may exist on a local disk or on a SAN mounted on the platform.

Note: the image/movie folder should also be available to the NRCS ActiveX running inside the NRCS Desktop Client on the journalist’s desktop.

RT Control desktop

Applications: Chrome
Hardware: desktop computer

There are two applications that do playout control and the application used will decide which platform is appropriate.

Swift Live

This requires the simplest platform – any pc that can run the Chrome browser. The operator starts the browser and directs it to the DataServer on the data/preview server machine. The operator can then login and select which session to use. This will load the Swift Live application and connect it to the Swift Engine (for preview) and Swift Engine (for transmission) specified in the session. The operator can then select, configure, preview and playout graphics.

Swift Playout

This is usually a high-end graphics workstation. Stacks derived from the running orders in the NRCS by MOSGateway (copied to this machine by the synchronisation of transient assets) can be loaded into Swift Playout. Items on the stack can be previewed and then taken to air. The preview is done within Swift Playout and the application (using the MOS Protocol) commands a connected Swift Engine to transmit it.