K2 Edge Engineering Manual - Grass Valley

K2 Edge Engineering Manual Document version: 4.1 - 2013/6/28

K2 Edge Engineering Manual- document version: 4.1 - Page 2

Table of Contents

1 Grass Valley Product Support ......................................................................................................... 3 2 K2 Edge Playout Automation Introduction ....................................................................................... 4

2.1 K2 Edge Playout Automation ................................................................................................... 4 2.2 Assets ...................................................................................................................................... 5 2.3 Channel Design........................................................................................................................ 6 2.4 Scheduling and Channel Pack activation ................................................................................. 6 2.5 Channel Composer Basic Concepts ........................................................................................ 8

3 K2 Edge Indicators and status information .................................................................................... 12 3.1 Backpanel .............................................................................................................................. 12 3.2 Power supply indicator ........................................................................................................... 13 3.3 IP Manager connection indicator ............................................................................................ 13 3.4 LAN connection indicator ....................................................................................................... 13 3.5 LEDs (hard disks) ................................................................................................................... 13

4 Remote control and system configuration via the IP Manager (K2 Edge) ..................................... 14 4.1 Starting the IP Manager web interface ................................................................................... 14 4.2 The LCD front panel ............................................................................................................... 14 4.3 The IP Manager menu ........................................................................................................... 15 4.4 System configuration > Network configuration ....................................................................... 16 4.5 System configuration > Channel configuration ....................................................................... 16 4.6 GPIO ...................................................................................................................................... 18 4.7 System configuration > Time settings .................................................................................... 19 4.8 System configuration > Licenses ........................................................................................... 19 4.9 System monitoring > System info ........................................................................................... 19 4.10 System monitoring > Fans .................................................................................................. 20 4.11 System monitoring > UDP Monitoring................................................................................. 20 4.12 System administration ........................................................................................................ 21

5 Linux.............................................................................................................................................. 22 6 The Cobalt processes ................................................................................................................... 23 7 Workflow Playout........................................................................................................................... 24 8 Playout directories ......................................................................................................................... 26 9 The nexusproc script ..................................................................................................................... 27 10 dataserver .................................................................................................................................. 28 11 sequencer .................................................................................................................................. 30 12 ingest_distri ............................................................................................................................... 32 13 playout_distri ............................................................................................................................. 33 14 schedulesync ............................................................................................................................. 34 15 Workflow Assets and Ingest ...................................................................................................... 35 16 Manually configuring the TX/MAM main and backup server ...................................................... 38 17 Failover, manual backup and restore of the TX/MAM servers ................................................... 39 18 Log files overview ...................................................................................................................... 41 19 Connecting with PuTTY ............................................................................................................. 42 20 Appendix: K2 Edge network ports.............................................................................................. 43 21 Appendix: TX/MAM server network ports .................................................................................. 43 22 Appendix: Workflows Channels ................................................................................................. 44

Copyright © Grass Valley USA, LLC. All rights reserved. This product may be covered by one or more U.S. and foreign patents.


1 Grass Valley Product Support Contact information: http://www.grassvalley.com/support/contact

U.S Technical Support: +1 800-547-4989 or +1 530 478 4148 or E-mail: Please use our online form

All other countries Technical Support: +800 80 80 20 20 or +33 1 48 25 20 20 or E-mail:

[email protected]

FAQ: http://grassvalley.novosolutions.net/

Training: https://grassvalley.csod.com/LMS/catalog/Main.aspx?tab_page_id=-67&tab_id=6

Documentation can be found on the grass valley website > Resources > Smart Playout Center.

https://grassvalley.csod.com/LMS/catalog/Main.aspx?tab_page_id=-67&tab_id=6


2 K2 Edge Playout Automation Introduction The K2 Edge system is purpose-built for multichannel, integrated, automated playout. While traditional playout solutions take advantage of IT-based technologies to control separate components, K2 Edge integrated systems work together from the ground up.

2.1 K2 Edge Playout Automation

The integrated K2 Edge playout systems and applications are:

K2 Edge server: Linux-based, software-centric, automated, multichannel, integrated Playout

Server. Brings all of the components of integrated playout together in a unified system: media

playout, channel graphics, asset management and automation.

TX/MAM server: contains the TX/MAM database.

Cobalt: playout control; manage and create on-air and off-air Playlists.

Channel Composer: create the static and animated, 2D and 3D on-air look of Channels.

K2 TX/MAM: Asset management; create and control Assets.

Storage: media files storage.

K2 TX/MAM dashboard: manage the K2 Edge services.


The K2 Edge workflow

2.2 Assets

Asset info is created in TX/MAM, or imported. Asset info is stored in the TX/MAM database. Asset files (Essences) are ingested via Inboxes on the K2 Summit (storage server). Assets can also be ingested via TX/MAM.

Files and Assets are linked based on the Asset’s External reference, as shown below:

Example Asset

Original Filename External reference AssetID Filename in TX/MAM

abc123.mpg abc123 153 a0000153.avf

Media files are renamed to a0000<AssetID>.<file extension> (7 digits) during ingest. The file extension for clip files is renamed to .avf. Example: a0000153.avf When a schedule is imported and Assets in the schedule do not yet exist, empty Assets are created. When a Playlist is activated, playout_distri will check if Asset files are still in cache on the playout node. If not, playout_distri will fetch files from the Storage-server and transfer files using FTP to the playout directories on the playout nodes.


2.3 Channel Design

A Channel Composer Project contains all the elements that together compose a Channel’s on-air design: fixed Assets, Objects, Templates, Applets and Formats. Projects are designed in Channel Composer and are then exported to the TX/MAM-database or to Storage as a Channel Pack. Formats are now available for scheduling.

Before playout, the Channel Pack is transferred to the playout nodes. Dynamic content is fetched from Storage and is also transferred to the playout nodes.

2.4 Scheduling and Channel Pack activation

Schedules can be imported or created in POC. On-air and off-air Playlists can be edited and monitored in POC. Off-air Playlists are stored in the TX/MAM database or on the POC client PC. Activated Playlists are stored in the playout database on the playout server.

When creating a Schedule, the Cobalt scheduling process will apply the Channel Pack that is active at the Events’ planned start time. This means that Events are scheduled with the Formats from this Pack. Events in a Playlist play out the Formats they were scheduled with.

Example:

Schedule Channel Pack

Events are scheduled with the Assets, Templates, Applets and Formats from:

Event Start time: 13/02/12 12:00:00

Channel Pack ID: 2400 Activation starts: 13/02/12 12:00:00 Event

Start time: 13/02/12 12:03:00

Event Start time: 13/02/12 and so on

Event Start time: 14/02/12 12:00:00

Channel Pack ID: 2312 Activation starts: 14/02/12 12:00:00 Event

Start time: 14/02/12 12:03:00

Event Start time: 14/02/12 and so on

Objects

Assets

Formats

Templates

Applets

Project

Channel Pack


Databases and storage

Asset info

TX/MAM databases

Asset info and Metadata: Assets contain Asset info and metadata such as file type, external reference, duration. Metadata field are customizable metadata, for instance artist, title, and episode. Jobs and statuses: Assets can have configurable jobs and statuses that are visible in TX/MAM. Jobs can be executed automatically and/or manually. Workflow: Workflow steps can be defined using the status of an Asset or Asset Job.

Essences Media Files

Storage

Essences (Asset media files) are stored on the K2 Summit storage server. Files are transferred to the playout nodes for playout.

Playlists POC client/TX/MAM db Playout databases

Playlists are saved on the POC client or in the TX/MAM database. Activated Playlists are stored in the playout databases on the main and backup nodes.

Channel Packs Storage TX/MAM database

A Channel Pack contains the following items: Scene graph: The scene graph contains all Objects, Templates and Scene Parameters that were defined during the design process. Assets: All fixed Assets that were imported during the design process are stored in content-type specific folders within the Channel Pack. The following folders can be found in a Channel Pack: Animations. Applets. Audio files. Font files. Mesh clip files. Metadata definition files. These files are not used during playout (only used during design by Channel Composer). Still graphic files. Video files.

Channel Pack Assets are not listed in the TX/MAM Asset list. Channel Composer Project

This is the project file used by Channel Composer and it is not used during playout (it is only used during design by Channel Composer). Contents Description

The contents description file (contents.xml) is intended for third-party implementers and describes the contents of a Channel Pack in detail in XML-format.


2.5 Channel Composer Basic Concepts

Channel Composer is used to create 2D and 3D scenes. Look-and-feel, presentation and content metadata is assembled to a complete Channel design, ready for on-air presentation.

Objects

Channel Composer works with Objects such as Clip, Still, Animation, Audio and so on. Objects have properties, such as opacity, position and scale that can be modified and animated.

The example shows the Object properties window for a Clip Object.

Templates

Templates are used to transform Objects’ properties such as opacity, position and scale in time. The example above shows a Template used to play a Clip. The column on the left lists the Objects included in the Template. Each Object has its own track on the Timeline.


Assets, Metadata and Scene Parameters

An Object can refer to fixed content or to dynamic content.

Example reference to fixed content: a Template plays out a

logo.

Example reference to dynamic content: a Template plays

out a different video clip each time it is activated.

Fixed files are added to the Channel Composer Project as Assets. Assets are included in the Channel Pack when the Project is exported to the TX/MAM database. To refer to dynamic content, Scene Parameters are defined. These parameters are dynamically updated when Events are scheduled.

Example:

Scene Parameter Event ID Scene Parameter Value

clip 12345 a0000548.avf

clip 12346 a0000978.avf

clip 12347 a0000564.avf

An Object can also refer to a file's metadata fields. This metadata information can be played out, or is used to schedule Events. Two examples:

Clip title and artist information is derived for playout from the clips' <title> and <artist> metadata fields.

Formats

Formats describe the concept and on-air design of a program. They are built of main Events (for example playout of a music clip) and secondary Events (for example playout of a strap or logo). Events (main and secondary) are built of Templates and Applets. Secondary Events are timed relative to the main Event.

The example above shows the Format Play Clip. The column on the left lists the Templates and Applets included in this Format. Templates and Applets are timed on the Timeline using the Timing Offset property.


Example timing (and dynamic reference) for Template Clip.

Example timing for Template Logo Out.

Events in the Playlist

A Playlist lists Events. Each Event consists of a main Event and secondary Events.

Example: in a music show format, playout of the clip is the main Event and the clip is the main Asset. This dynamic reference to a music clip file (scene parameter) is updated with the filename of the Asset when Events are scheduled.

Secondary Events are timed relative to the main Event’s duration. Example secondary Events:

o Fade in the logo (fixed asset) 5 seconds after the start of the main Event;

o Fade out the logo 3 seconds before the end of the main Event.

Example playlist in Playout Control, listing Events.


Example Event (when double-clicked) in POC.

The example above shows an Event with ID 181. The dynamic reference has been updated with a ‘commercial’ clip with Asset ID 386 and external reference CM_UB14.

The Event is linked to two Formats: DFLT and BG. The BG-Format is expanded in the example above and contains one Template bug on. This Template is timed with an offset of 00:00:00:00 from start, relative to the main Event (the dynamic reference, here the ‘commercial’ clip).

The number behind the Template icon shows the Channel pack ID (398) .

All design elements for this Event, Templates, fixed Assets, and so on, are taken from this Channel Pack.


3 K2 Edge Indicators and status information

3.1 Backpanel

K2 Edge back panel.

Connectors

IPM IP Manager

M Mouse (not connected)

KBD Keyboard

USB USB

COM Serial COM

VGA VGA

eth0-3 eth0-3

LTC LTC

GPIo GPIo (open collector)

AC Power supplies

GL blackburst/trilevel sync

IO1-IO8 SDI IOs.

Presets are defined for port configuration.

Bypass can be enabled on IO1 (in) and IO2 (out).


3.2 Power supply indicator

green ON

red Failure

LED off Standby

3.3 IP Manager connection indicator

Left LED

yellow (blink) System online

Right LED

green Speed 100 Mbps

3.4 LAN connection indicator

Left LED

green (blink) System online

Right LED

green Speed 100 Mbps

orange Speed 1 Gbps

3.5 LEDs (hard disks)

Top LED (activity)

green Indicates read/write actions on the disk.

Bottom LED

green Hard disk OK.

red (blink) Hard disk not in RAID and probably broken.

orange (blink) Hard disk will fail soon.

blue (blink) No hard disk detected.

blue Hard disk seems slower than usual.

green (pulse) Hard disk is being added to the RAID (RAID rebuild).

Please refer to the Dell manual for information on status indicators of the TX/MAM Dell servers.


4 Remote control and system configuration via the IP Manager (K2 Edge)

The IP Manager enables remote server configuration, monitoring and administration. The IP Manager is accessible via web, or via the LCD-panel on the front of the server. Two menus are available:

the K2 Edge-menu: standard menu

the IP Manager menu: also available when the system is unreachable (note that this menu

has less options)

If the system is unreachable, press the knob for 3 seconds to switch from the K2 Edge menu to the IP Manager menu.

Changing settings and executing commands via the IP Manager can interrupt a broadcast.

4.1 Starting the IP Manager web interface

To access the IP Manager, enter the IP Manager's IP-address in a web browser and log in with the credentials for the IP Manager.

4.2 The LCD front panel

Use the rotary knob to operate the IP Manager via the front panel:

Turn the rotary knob backwards and forwards to scroll through

options.

Press the rotary knob to select an item. Selected items are marked by

[], <>, an arrow, or are highlighted.

To confirm changes, rotate the knob to the OK option, and then press the knob.

Some changes in Channel settings require a restart of the nexos processes: select OK to set changes and then Activate settings to activate changes. Note that you may have to scroll to this option.

To discard changes, return to the main menu from a sub menu or rotate the knob to the back/cancel/discard option, and then press the knob.


4.3 The IP Manager menu

Example IP Manager menu via the web browser. The system’s hostname is shown in the upper right corner and on the web page’s tab. The highlighted menu item shows where you are in the navigation tree.

To confirm changes, click Set. Some changes in Channel settings require a restart of the nexos processes: select OK to set changes and then Activate to activate changes.


4.4 System configuration > Network configuration

Hostname: the K2 Edge hostname

IP-manager: specify network settings for the IP Manager. Note that the IP Manager has its own

IP-address.

Use DHCP: On/Off

IP-address

Netmask

Gateway

Nameserver

K2Edge: specify network settings for the K2 Edge server

Network port <nr>

Method: Auto, using DHCP/Manual or Manual

IP-Address

Netmask

The system’s MAC address is displayed.

Gateway

Nameserver

TX/MAM server virtual IP: the TX/MAM servers’ virtual IP-address

4.5 System configuration > Channel configuration

Video Bypass: enable (activate) or disable the bypass

Channel layout: select one of the following presets:

1xSD (1) : single SD (with preset 1)

1xSD (2) : single SD (with preset 2)

1xHD (1) : single HD (with preset 1)

1xHD (2) : single HD (with preset 2)

1xSD+preview (1) : single SD + preview (preset 1)

1xSD+preview (2) : single SD + preview (preset 2)

1xHD+preview (1) : single HD + preview (preset 1)

1xHD+preview (2) : single HD + preview (preset 2)

Simulcast

Custom setup

Region: select PAL or NTSC

HD-format: for HD-channels, select 720p or 1080i

http://10.250.51.129/?path=0:

http://10.250.51.129/?path=0:


Genlock: select Blackburst or Trilevel sync

Audio channels: specify audio groups per SDIO

SDIO1-8:

Single audio group

Two audio groups

Three audio groups

Four audio groups

SDI port misc

SDIO in

VBI: Enabled/Disabled

HBI: Enabled/Disabled

SDIO out

Key/Fill

Enable recording channel: enable or disable the recording channel: On/Off

Enable JIP channel: enable or disable the JIP channel: On/Off

Delay: not used for the K2 Edge, only for VDS (Video Delay Server)


4.6 GPIO

Example. Internal GPIO: DB9M External GPIO: 410E GPIO action: specify an action, for example GPI-5 switches to off

Use the pinning table to define conditionals for pins 1-8.

x: don't care (0 or 1)

0: low

1: high

Timecheat: check to enable cheat

type None: results in no action

Script: runs a Linux shell script upon incoming GPIO commands, delayed by the configured delay

time if applicable.

Argument: script name preceded by the full path

Template: trigger a Composer template.

Argument: the template name which is configured in the channel pack

DB9M GPIO off: triggers a level on the specified GPIO bit, delayed by the configured delay

time if applicable.

Argument: GPI pin number

DB9M GPIO on: triggers a level on the specified GPIO bit, delayed by the configured delay time if

applicable.

Argument: GPI pin number

censor IO off: disables the censor on a SDI output port for the specified SDI port number

Argument: SDI port number (number only)

censor IO on: censors a SDI output port

Argument: SDI port number (number only)

Cheat delay: execute actions with an extra offset in hh:mm:ss:ff.

Note that cheat delays are only possible when in input mode.

Click Delete to delete a rule.


Click New rule to add a new rule.

Click Set to confirm.

4.7 System configuration > Time settings

Set the system date and time.

Current date: yyyy-mm-dd

Current time: hh:mm

4.8 System configuration > Licenses

Licenses are preconfigured.

4.9 System monitoring > System info

SNMP monitoring: not implemented yet

System info:

RAID partition free space (K)

Memory installed (MB)

CPU usage (percentage)

Non-running programs

Serial number and system installer version

PSU status

GPU Temperature (Celsius)

HD raid status

HD SMART status

HD temperature (Celsius)

Fans (speed in rotations per minute)

http://10.250.51.129/?path=0:

http://10.250.51.129/?path=0:

http://10.250.51.129/?path=1:


4.10 System monitoring > Fans

Displays fan speed in rounds per minute.

4.11 System monitoring > UDP Monitoring

UDP Monitoring: use this option to monitor Channel 0 (the single HD or SD Channel, or the HD

Channel in a simulcast setup) via IP. When enabled, a MPEG- transport stream with encoded

video, graphics, subtitles and audio (first stereo track) is sent over Ethernet using the UDP-

protocol. A video player such as VLC is installed on a workstation to view output.

The UDP-monitoring option is described in more detail in the K2 Edge User Manual.

Resolution: 320x240/ 240x180/ 160x120

Aspect Ratio: 4:3/ 16:9

Video Bitrate: in kbit/s

Audio Enabled: On/Off

Audio Bitrate: in kbit/s

Ethernet Output: select On to enable monitoring and start streaming, Off to disable.

IP-address: IP-address of the target workstation (can be a multicast address)

IP-port: port the player will listen to. Default 4000

http://10.250.51.129/?path=1:

http://10.250.51.129/?path=1:


4.12 System administration

Server start/stop

Reboot

shutdown

Forced power off: only use when a shutdown is not possible.

Forced reset: only use when a Reboot is not possible.

Manage services

Services are:

database

dataserver

encoderd

firebird

nexos

playout_distri

pt_guard

schedulesync0

sequencer0

sequencer1

Options for each service are:

View the service’s version and status.

Start the service.

Stop the service.

Restart the service.

http://10.250.51.129/?path=2:


5 Linux K2 Edge uses the Linux operating system. In this section we will cover a number of Linux commands which we will use during this training.

On older systems, replace the /system directory with the /publitronic directory.

Command Example Usage Description when used and with option

grep grep ‘text’

file.txt

text search and filter – can be combined with other commands using pipe |

ls ls –l lists files in the current directory (-l gives long listing)

ls ls –l |grep pt adding the pipe symbol (|) and grep, filters the result (in this case by pt)

cd cd /system change to the specified directory

man man ls shows a manual for the command (in this case ls)

ifconfig shows network configuration

cat cat blade.ini will display a text file on the screen (in this case blade.ini)

less less blade.ini similar to cat but allows searching by using ‘/’ & ‘?’

tail tail –f blade.ini used to view the last 10 lines of a file

df df shows current disk usage

ps ps aux detailed listing of all processes running

ps ps aux |grep play detailed listing of running processes with “play” in the name

killall killall nexos killall of the nexos processes


6 The Cobalt processes assetinboximporter

Checks the Inbox for files.

Creates Assets (Asset info in TX/MAM database).

Moves files from the Inbox to the TX/MAM controlled folders.

dataserver

Handles all communications with the TX/MAM and playout databases. Other processes such

as the assetinboximporter use the dataserver to communicate with the databases.

playout_distri

Transfer files from storage (media files) and the TX/MAM server (channel packs) to the

playout nodes.

ingest_distri

Delete Assets (file and info).

sequencer

Translates the active Playlist to commands that are rendered by the nexos render engine.

schedulesync

The schedulesync process synchronizes the Schedule from the main playout server to the

backup playout server (if applicable).


7 Workflow Playout The active Playlist list Events. Each Event defines an Asset ID, Event ID, Timing info, Channel Pack ID ([390] in the example below) and more:

Example Event. The active Playlist is stored in the playout databases on the playout nodes. All communications with

the playout database are handled by the dataserver.

Playout is managed by a number of processes running on the K2 Edge: the Cobalt processes and the nexos process.


1) When a Playlist is activated, playout_distri will check if files are still in cache on the playout

node. If not, playout_distri retrieves transfer metadata from the TX/MAM database (via

dataserver). Transfer metadata specifies where Assets are stored.

2) Based on the transfer metadata, playout_distri will fetch files from the Storage-server and

transfer files using FTP to the playout directories on the playout nodes. Channel Packs are

transferred from the TX/MAM database or from Storage, depending on where they have been

stored with Channel Composer.

3) The sequencer interprets the active Playlist and sends commands to nexos, the K2 Edge

render engine [see the next diagram].

4) Nexos renders the commands and files.


8 Playout directories The table below lists the K2 Edge directories used by Cobalt and nexos.


Directory Usage

/system/objects/cobassets Root directory for Cobalt.

/system/objects/cobassets/bin Contains all executables and their settings.

/system/objects/cobassets/database Contains the database (= cobalt.fdb).

/system/objects/channelpack Contains Channel Packs.

/system/objects/cobassets/media Contains all media files that are under control of Cobalt. This directory is only used if the machine itself acts as an Asset Manager.

/system/objects/code Contains the executables required to run the K2 Edge environment, used to convert clips to the right format.

/system/objects/pictures Contains graphics.

/system/objects/mpegves Contains video files.

/system/objects/subtitles Contains subtitles.


9 The nexusproc script The Cobalt services are automatically started when the system is started up and are shut down before

the system itself is shutdown (warm shutdown) by the /system/nexusproc script.

Usage: nexusproc service start|stop|restart|status|version|enable|disable [all]

Example: /system/nexusproc sequencer0 restart

To show available nexusproc options on the command line, enter: /system/nexusproc

Service Explanation

dataserver : handles the cobalt databases communication

sequencer0 : handles command execution of scheduled Events for channel0




playout_distri : handles file/asset distribution, checking and management

schedulesync0 : handles schedule synching from the 'main' Channel for channel0 to the

backup Channel


backup Channel


backup Channel


backup Channel

ingest_distri : delete Assets (file and info).

settingd : manages and controls the K2 Edge front panel

pt_guard : watchdog for the dataserver

inbox : handles the dropfolder importer process (assetinboximporter)

jobhandler : handles asset jobs


10 dataserver The dataserver process provides all interaction with the TX/MAM (asset info) and Playout (schedule info) database files. The dataserver retrieves information from and updates information in the databases. The dataserver uses a watchdog process that checks the database connection. This service is called: pt_guard. As a default, pt_guard checks the connection every 10 seconds. When a 15 seconds timeout is reached, pt_guard will restart the dataserver process.

nexusproc script

Use the nexusproc script to manage the Cobalt services. Logs

To check the dataserver logs:

# tail –f /var/log/dsYYYYMMDD.log

(For example ds20110823.log.)

Configuration

The dataserver is not configured itself but uses configuration information from POC.

Applets

Retrieving data from the dataserver is done by means of XMLRPC calls. XMLRPC is an industry standard used to invoke functions across a network. A detailed description can be found on www.xmlrpc.com.

To access the dataserver using applets or Linux-applications, a library (libcobalt.so) is available. For more information, please contact Support.

If in POC an active Playlist's clock is displayed in red, the dataserver service is not available and needs to be restarted.

Example dataserver not running or accessible.

http://www.xmlrpc.com/


The watchdog process pt_guard interval and connection timeout can be changed in the nexusproc file.

pt_guard options:

Option Explanation

-h Show help.

-i <seconds> Interval between checks (default: 5).

-t <seconds> Timeout (default: 2).

-v Show version number.

Example: @pt_guard = “nice -n18 $SEQ_DIR/pt_guard -i 10 -t 15 >>/dev/null &”


11 sequencer The sequencers send commands to nexos and start applets. The sequencers will store main Events for the next 10 minutes in memory, including all secondary events for these main Events.

Each broadcast set has its own sequencer. The sequencers for broadcast sets can be identified by the seq_br[0..8] naming; [0..8] indicates the broadcast set. This means that the sequencer for broadcast set 0 is identified by the seq_br0 link. All seq_br[0..8] are linked to the sequencer file. This means that in case of an update, only the sequencer file needs to be overwritten.

The sequencers retrieve schedule information via a local dataserver.

nexusproc script

Use the nexusproc script to manage the Cobalt services.

Logs

To check the sequencer log:

# tail –f /var/log/seq_br0YYYYMMDD.log (0 is the sequencer number.)

The log will show Events that have been processed and all the commands that have been sent to nexos. Below you find an example playlist in POC and an example sequencer log.

Events are added to the top of the log.

Example playlist in POC.

Configuration

The sequencers look for a local dataserver to retrieve schedule information from the Playout database. Channel settings are retrieved from the TX/MAM database. The /system/blade.ini file (located on the main and backup playout node(s)) defines the TX/MAM server’s IP-address.

[COBALT]

system_db_ip=MAIN-DB

system_db_port=5020

Example excerpt from blade.ini.


Example sequencer log file.


12 ingest_distri Delete Assets (file and info)

nexusproc script


Logs

To check the ingest_distri log:

# tail –f /var/log/ingest_distri

Example ingest_distri log file.

The log will show if ingest_distri is active (timestamp every 10 seconds).


13 playout_distri The playout_distri process fetches media files and Channel Packs from storage and the TX/MAM database and transfers these files to the playout nodes for playout. Schedule info, including Events’ Asset and Channel Pack IDs (i.e. which media files and Channel Pack need to be fetched), is retrieved from the Playout database via the dataserver.

Playout_distri checks the next unchecked or error event and fetches content in playout order, based on (error) look ahead time as defined for the Channel in Asset Manager. If a current transfer operation is being handled and a more urgent transfer is required, the current transfer will automatically be slowed while the urgent transfer is handled.

nexusproc script


Log

To check the playout_distri log:

# tail –f /var/log/playout_distri.log

In POC, the status of Events and files is displayed via icons.

Applets

Playout_distri can trigger applets to check Events.

Configuration

The playout_distri process always looks for a local dataserver to retrieve schedule information from the Playout database and to the TX/MAM server (configured in blade.ini) for Channel information.

The look ahead time and alarm threshold for the playout_distri process are configured via Channel Management in Asset Manager.

The file /system/blade.ini (located on both the main and backup playout node(s)) specifies the

TX/MAM server’s IP-address.

[COBALT]

system_db_ip= MAIN-DB

system_db_port=5020

Example excerpt from blade.ini.



14 schedulesync The schedulesync process takes care of syncing the schedule from the main playout server to a backup playout server (if applicable). The schedulesync process will scan the main playout database, via the dataserver for any changes in the schedule (new items or items that were moved/deleted) and apply these changes to the backup playout database.

Schedulesync scans the schedule for changes every few seconds. A short term update process checks for changes in the next 30 minutes and a long term update process checks for changes in the look ahead time configured in the Channel settings in Asset Manager.

The schedulesync process is active on the backup playout system only. When the playout server starts up, the server itself is checked to see if this system is a backup system. If so, the schedulesync process is activated. A restart is required if a system is newly configured as a backup system to activate the schedulesync process.

The schedulesync process needs to be started with a low priority to ensure that it does not interfere with the real time processes in the system.

nexusproc script


Configuration

The schedulesync process is configured via Channel Management in Asset Manager. Channel settings are retrieved from the TX/MAM database. The /system/blade.ini file (located on the main and

backup playout node(s)) defines the TX/MAM server’s IP-address.

[COBALT]

system_db_ip= MAIN-DB

system_db_port=5020

Example excerpt from the blade.ini file.

The file /etc/hosts defines the (virtual) IP-address for MAIN-DB.


15 Workflow Assets and Ingest Creating Assets via TX/MAM

In this workflow:

1) Assets (Asset info) are created in TX/MAM. Until a file has been ingested, these Assets are

called empty Assets.

Processes: Asset info is written to the TX/MAM database by the assetinboximporter. The

assetinboximporter communicates with the TX/MAM database via the dataserver.


Creating Assets via Schedule Import, Ingest via the Inbox

a) Schedules are imported via POC. If Assets referenced in a schedule do not exist, an Asset with

an External reference is created and applicable custom metadata info is added (empty Asset).

Processes: the schedule importer in POC imports the schedule. The schedule importer writes

Asset info to the TX/MAM database via the dataserver.

Asset info can be created, but cannot be updated via schedule import. This should be done via the

TX/MAM interface.

Imported schedules and not-active Playlists are saved in POC (client). They can also be saved in

the TX/MAM database. When a Playlist is activated, Events are written (POC via dataserver) to

the playout database on the main playout node. When the Event is created, dataserver retrieves

all applicable Asset info from the TX/MAM database.

b) Files are ingested via the Inbox (via a share or FTP). Assets and files are linked based on External

reference. If an Asset does not yet exist in the TX/MAM database, an Asset is created.

Processes: the assetinboximporter checks the Inbox for files, creates Assets (Asset info in

TX/MAM database) if applicable and moves files from the Inbox to the TX/MAM controlled folders.

The dataserver is used for communication with the TX/MAM database.

Assets can be managed via TX/MAM and files can be ingested via TX/MAM [see the previous workflow].


Ingest via the Inbox, creating Assets via TX/MAM or Schedule Import

This is a combination of the previous two workflows: 1) Files are ingested via the Inbox. 2) Asset info is imported via a schedule, or created or updated via TX/MAM.


16 Manually configuring the TX/MAM main and backup

server

On the active (main) TX/MAM server, the file /system/STATUS should contain: active=yes

On the standby (backup) TX/MAM server, the file /system/STATUS should contain: active=no

Via samba (windows network share) the STATUS file can be found here: \\<TX/MAM server IP-address>\delta\STATUS

When working from command line: /system/STATUS

To change a TX/MAM server from main to backup:

On the main server, edit and safe the file /system/STATUS:

Change active=yes to active=no and save the file.

Run the /system/nexusproc restart all command.

To change a TX/MAM server from backup to main:

On the backup server, edit and safe the file /system/STATUS:

Change active=no to active=yes and save the file.

Run the /system/nexusproc restart all command.


17 Failover, manual backup and restore of the TX/MAM

servers

An automatic backup is created and restored from the active to the standby database every hour by the /etc/cron.backup/cob-bak and /etc/cron.restore/cob-restore commands.

Workflow Main TX/MAM server Backup TX/MAM server

Normal situation The main server is active and writes a backup to the backup server every hour.

The backup server is inactive. Database backups are written to the backup server.

Creating a manual backup from the main server (usually not needed).

# /etc/cron.backup/cob-bak

<enter> The database backup is written to the backup server.

Failover from the main to the backup TX/MAM server

Deactivate the main server. Deactivate the main first:

Stop all services: # /system/nexusproc stop all

Edit the file /system/STATUS, set yes to no: active=no

The backup server is inactive.

Restore the database on the backup.

The main is inactive. /etc/cron.restore/cob-

restore

Activate the backup server. Edit the file /system/STATUS, set no to yes: active=yes

Start all services: # /system/nexusproc

start all

The backup server is active.



Going back from the backup to the main TX/MAM server


The main server is inactive. The backup server is active and writes a database backup to the main server every hour.

To manually create a backup from the backup server (if no backup of the database is available on the main).

The database backup is written to the main server.

To manually create a backup on the backup server and write to the main: # /etc/cron.backup/cob-

bak <enter>

Restore the database on the main.

/etc/cron.restore/cob-

restore

Deactivate the backup server.

Stop all services: # /system/nexusproc

stop all

Edit the file /system/STATUS, set yes to no: active=no

Activate the main. Edit the file /system/STATUS, set no to yes: active=yes

Start all services: # /system/nexusproc start

all

Normal situation. The main is active. The backup server is inactive. Database backups are written to the backup server.


18 Log files overview

Linux: /var/log/messages

Applets: /var/log/applets

o Timed applets also log to the sequencer log.

o Non-timed applets (such as “pre-event”) also log to the playout_distri log.

ingest_distri: /var/log/ingest_distri.log

playout_distri: /var/log/playout_distri.log

nexos: /var/log/nexos

dataserver: /var/log/ds<date>.log

sequencer: var/log/seq<broadcast><date>.log


19 Connecting with PuTTY PuTTY is a software program that uses the secure shell protocol to connect to a remote computer and can be used to access the K2 Edge server. PuTTy can be downloaded from www.putty.org and is installed on a Windows workstation with connection the K2 Edge server.

To start Putty:

On a workstation with connection to the K2 Edge server, double-click the PuTTY icon to start.

The following (default) screen appears:

Once you set up a Putty session, in the Putty screen:

Enter the IP-address of the system that you want to connect to. The default Port is 22.

Select the Connection type: SSH.

Click Open.

The terminal window opens and you can log in. From the command prompt you will be able to enter Linux commands.

Example PuTTY terminal window.

To exit the Linux shell, on the command line enter: logout, exit or press [CTRL-D].

http://www.putty.org/


20 Appendix: K2 Edge network ports

FTP Default port 20 and 21

SSH/SCP Default port 22

Cobalt database access Default port 5020

Webbased interface Default port 80 on IP manager network/IP

ptsockse Default port 5000

nexos complex socket Default port 5001

UDP-monitoring Default port 4000

21 Appendix: TX/MAM server network ports

FTP Default ports 20 and 21

SSH/SCP Default port 22

Samba Default ports 137,138 and 139

Cobalt database access Default port 5020

Webbased interface Default port 80

TX/MAM hardware player Default ports 5000 and 5001


22 Appendix: Workflows Channels

The diagrams in this appendix include the sequencer. This concept has been added for engineers. The sequencer is a Cobalt process that translates the active Playlist to commands and sends these commands to nexos, the K2 Edge render engine. Channel Nexos channel nr. Broadcast set Sequencer

Single HD/SD 0 0 0

Simulcast 1 of 2 (HD) 0 0 0

Simulcast 2 of 2 (SD) 1 0 0

Preview 1 1 1

Record n/a 3 3

JIP 0 4 4

22.1.1 Single Channel


22.1.2 Simulcast


22.1.3 Join In Progress

Documents

K2 Edge Engineering Manual - Grass Valley