Accessing the system via command line:
User: root
Password: proot123
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:
callcentre@grassvalley.com
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.
The K2 Edge Smart Playout Center Commissioning Manual describes how to commission a
De K2 Edge contains 8 bidirectional SDI-ports. A number of presets have been defined for the K2
Edge. These presets can be selected via the IP Manager.
Possible Channel configurations on a single K2 Edge server:
Single Channel HD
Single Channel SD
Single Channel HD + Preview Channel
Single Channel SD + Preview Channel
Simulcast
Note that available options depend on licenses purchased.
Single Channel SD
Preset 1
o Channel Single Inputs: IO1(SD),IO3(SD),IO5(SD),IO6(SD)
o Channel Single Outputs: IO2(SD),IO4(SD),IO7(SD), IO8(SD)
Preset 2
o Channel Single Inputs: IO1(SD),IO3(SD),IO5(HD),IO6(HD)
o Channel Single Outputs: IO2(SD),IO4(SD),IO7(SD),IO8(SD)
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.
8.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.
8.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.
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.
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.
8.7 System configuration > Time settings
Set the system date and time.
Current date: yyyy-mm-dd
Current time: hh:mm
8.8 System configuration > Licenses
Licenses are preconfigured.
8.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)
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 UDPprotocol. 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
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.
You need a license to enable the monitoring functionality.
Enable monitoring via the IP Manager > System monitoring > UDP Monitoring > Ethernet
Output: select On.
Settings:
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
To receive the stream at the client, you can use a media player such as VLC
(http://www.videolan.org/vlc/) on a local workstation to view the video and audio content contained
within the mpeg transport stream:
Start the VLC-player.
Select Media > Open Network Stream > Network.
Enter the network URL: udp://@:XXXX, where XXXX = the IP-port specified in the IP
Manager.
If applicable select Show more options and set Caching to 100 ms.
Click Play to start streaming.
To receive streams from multiple K2 Edge servers, in the IP Manager configure a unique target IP-port
for each K2 Edge. For example if your client PC IP is 10.250.51.60, set up as:
K2 Edge1: 10.250.51.60:4000
K2 Edge2: 10.250.51.60:4001
Verify with your network administrator that the routers in your network are multicast-enabled.
Verify with your network administrator which multicast addresses are available on the network.
In the IP Manager, specify the multicast destination IP-address available for network
Configure the Preview Channel via the IP Manager presets [see chapter 7].
Define a preview Channel in TX/MAM as described in the Commissioning and TX/Mam User
Manuals.
in Channel Composer create a Format and Template to play out the clip and activate on the
Preview Channel.
An example channel Preview1 and Channel Pack are preconfigured.
With the K2 Edge Recording option you can record a Live input and ingest as an Asset. MXF file types
can be recorded.
What is needed:
A default Recording Channel is preconfigured: Record1.
To enable, you need the K2-EDGE-SWLX-REC license.
You need the RecPack Channel Pack to work with the Recording function. The RecPack
Channel must be activated on the Recording Channel.
Enable recording via the IP Manager.
How to:
Enable recording via the IP Manager > Channel configuration > Enable recording channel:
select On.
Create a temporary Playlist. This Playlist is used to schedule Events with the recording
Formats attached.
In TX/MAM, create an empty Asset of the appropriate Asset Type.
Example.
You can also overwrite an existing Asset. In that case, in the LiveRecord Format set the StartLiveRec
> overwrite and CheckLiveAssetStatus > Overwrite options to 1.
Drag the (empty) Asset into a temporary Playlist and attach the LiveRecord Format to the
Event.
Double-click the Event and specify Duration. You do not have to specify an Event Tc in / Tc
You can also specify the Asset’s duration in TX/MAM, on the Spotcheck tab > Duration.
Activate the Event to the Record Channel, to the appropriate start date and time.
Make sure the LiveRec Channel Pack is activated on the Record Channel.
Example Recording Event.
If you do not know the recording Event’s duration in advance, schedule a LiveRecord Event
with a Duration that exceeds the estimated duration.
Schedule a manual Event after the recording Event with the IngestOnly Format attached;
recording will be stopped when the manual Event is triggered and the recording Event’s
duration is overruled. The IngestOnly Event ingests the recording.
o preset: the encoding preset, determines amongst others the container/codec
o mxf-d10-<bitrate>
Use for SD.
bitrate: 30/40/50
o xdcam-hd-<bitrate>
Use for HD.
bitrate: 30/40/50
o overwrite: 0 overwrite is not allowed, 1 is allowed
o vbirecord: 0 do not include vbi info, 1 include vbi info. Only supported for PAL-formats.
VBI is recorded in the visual area.
IngestRecording: starts ingesting the previous recording, if any, 6 seconds from start. Starts
ingesting the current recording, 6 seconds from end.
Event parameters can be modified in POC. If you want to work with different parameters than the ones
predefined, to avoid having to change parameters for each recording we advise to change the Format
in Channel Composer.
ACT
Adelaide
Brisbane
Broken_Hill
Canberra
Currie
Darwin
Eucla
Hobart
LHI
Lindeman
Lord_Howe
Melbourne
NSW
North
Perth
Queensland
South
Sydney
Tasmania
Victoria
West
Yancowinna
Brazil/
Acre
DeNoronha
East
West
Canada/
Atlantic
Central
East-Saskatchewan
Eastern
Mountain
Newfoundland
Pacific
Saskatchewan
Yukon
Gibraltar
Guernsey
Helsinki
Isle_of_Man
Istanbul
Jersey
Kaliningrad
Kiev
Lisbon
Ljubljana
London
Luxembourg
Madrid
Malta
Mariehamn
Minsk
Monaco
Moscow
Nicosia
Oslo
Paris
Podgorica
Prague
Riga
Rome
Samara
San_Marino
Sarajevo
Simferopol
Skopje
Sofia
Stockholm
Tallinn
Tirane
Tiraspol
Uzhgorod
Vaduz
Vatican
Vienna
Vilnius
Volgograd
Warsaw
Zagreb
Zaporozhye
Zurich
De K2 Edge contains 8 bidirectional SDI-ports. One video format can be configured per tile.
IO1 is always configured as input and IO2 as output to be able to use the bypass relay. A
number of presets have been defined for the K2 Edge. These presets are selected via the IP
Manager.
IOs and tiles.
14.2 Bypass
Ports IO1 (input) and IO2 (output) can be internally connected to bypass a Channel. When set
to bypass, the signal of the main Channel is ignored, and instead the feed received at IO1 is
made available at IO2. Bypass is enabled via the IP Manager.
14.3 Master and Slaves
To make a Channel's signal available on several SDI-outputs, one or more of the IO-ports can
be configured to become slave outputs. By default, the signal provided by a slave output is an
exact copy of the master output signal. A slave output uses the properties of the master
Output it refers to, and thus cannot introduce another broadcast format for the same Channel.
14.4 Genlock
If enabled, the SDI-output synchronizes to the frame rhythm of the genlock (blackburst) signal
connected to the blackburst BNC-socket on the back of the server. If disabled, or when no
genlock signal can be detected, the output will synchronize to an internal clock. Genlock can
only be set for master outputs.
From release 4.1 K2 Edge supports cross conversion between different broadcast signals.
This means that the system is capable of transforming a broadcast signal from one type
towards another. For example, a playout system renders and broadcasts a 720@59.94p
signal. When using a live-input of type NTSC the K2 Edge will detect that the input and output
formats are not compatible (but related) and will automatically insert a cross conversion filter.
This cross conversion filter will deinterlace/interlace the frames and correct the frame rate.
Cross conversion is automatically applied to clips, SDI-feeds and animations as indicated in
the tables in chapter 15.2.
A number of services embedded in clips and in the VBI-data in SDI-streams, such as AFD,
ATC and CDP, are extracted from the input source and made available in the output, possibly
converted to a suitable alternative format (for example ATC and VITC).
Different (but related) frame rate, automatically cross
converted from a progressive to an interlaced format. This
includes conversion of a selected set of services. Video is
scaled down via a Channel Composer template.
1080@50i
25
AR, Down
Close to native format in terms of video and audio, just
more pixels. Video is scaled down via a Channel
Composer template.
NTSC
SD, 720x480, interlaced, 29.97 frames/sec, AR 4:3
Accepted input
media formats
Fram
e rate
Conversions
Comments
NTSC
29.97
None
Native format.
720@5994p
59.94
AR, Cross, Down
Different (but related) frame rate, automatically cross
converted from progressive to interlaced format. This
includes conversion of a selected set of services. Video is
scaled down via a Channel Composer template.
1080@5994i
29.97
AR, Down
Close to native format in terms of video and audio, just
more pixels. Video is scaled down via a Channel
Composer template.
15.2 Supported broadcast formats
The following tables define the K2 Edge supported broadcast formats with their related
supported input media formats. For all of these tables we recognize the following conversion
types:
AR – Aspect Ratio conversion. Under user control via Channel Composer template.
Cross – Cross conversion between formats with different but related frame rates,
converting from interlaced to progressive format or vice versa. Fully automatic.
Down – Downscale of larger video format to fit smaller broadcast format. Under user
control via Channel Composer template.
Up – Upscale of smaller video format to fit larger broadcast format. Under user
control via Channel Composer template.
1
Frame rate for all tables is in frames per second.
Different (but related) frame rate, and automatically cross
converted from an interlaced to a progressive format. This
includes conversion of a selected set of services. Video is
scaled up via a Channel Composer template.
720@50p
50
None
Native format.
1080@50i
25
Cross, Down
Different (but related) frame rate, and automatically cross
converted from interlaced to progressive format. This
includes conversion of a selected set of services. Video is
scaled down via a Channel Composer template.
720@5994p
HD, 1280x720, progressive, 59.94 frames/sec, AR 16:9
Accepted input
media formats
Fram
e rate
Conversions
Comments
NTSC
29.97
AR, Cross, Up
Different (but related) frame rate, and automatically cross
converted from an interlaced to a progressive format. This
includes conversion of a selected set of services. Video is
scaled up via a Channel Composer template.
720@5994p
59.94
None
Native format.
1080@5994i
29.97
Cross, Down
Different (but related) frame rate, and automatically cross
converted from interlaced to progressive format. This
includes conversion of a selected set of services. Video is
scaled down via a Channel Composer template.
1080@50i
HD, 1920x1080, interlaced, 25 frames/sec, AR 16:9
Accepted input
media formats
Fram
e rate
Conversions
Comments
PAL
25
AR, Up
Close to native format in terms of video and audio, just
less pixels. Video is scaled up via a Channel Composer
template.
720@50p
50
Cross, Up
Different (but related) frame rate, automatically cross
converted from progressive to interlaced format. This
includes conversion of a selected set of services. Video is
scaled up via a Channel Composer template.
HD, 1920x1080, interlaced, 29.97 frames/sec, AR 16:9
Accepted input
media formats
Fram
e rate
Conversions
Comments
NTSC
29.97
AR, Up
Close to native format in terms of video and audio, but
less pixels. Video is scaled up via a Channel Composer
template.
720@5994p
59.94
Cross, Up
Different (but related) frame rate, automatically cross
converted from progressive to interlaced format. This
includes conversion of a selected set of services. Video is
scaled up via a Channel Composer template.
1080@5994i
29.97
None
Native format.
Input source
Condition
1
AFD-objects defined on the timeline of a Channel Composer template.
2
AFD ANC packets found in an MXF file, embedded in accordance with the SMPTE
436M-2006 specification, section 6: MXF Ancillary Data Packet wrapping specifications.
Main Player (*)
3
AFD-objects found embedded in the VBI-section of an SDI-stream of all supported
broadcast formats.
Main Player
15.3 Service extraction
A number of services embedded in clips and in the VBI-data in SDI-streams are extracted
from the input source and made available in the output, possibly converted to a suitable
alternative format. These extracted services will survive cross conversion, although some of
the conversions are lossy.
The following sections describe each of the services recognized by the extraction process,
with a list of the recognized sources.
15.3.1 AFD
The following input sources are supported for extraction of the Active Format Description
(AFD) service, in given order of priority:
(*) Input sources with the main Player condition are only recognized when the associated
Channel Composer Player object was assigned the main player role. At any given time, only
one Player can have this role.
A STL subtitle rendered in CEA-608 format. The 608 subtitle data will end up in the
CDP’s embedded 608 section.
This input source can co-exist with the next #2 source.
This input can also co-exist with #3 and #5. If present, 608 subtitle data from #3
and #5 will be overwritten.
2
CEA-608 XDS commands placed on the timeline of a Channel Composer template.
The XDS data will end up in the CDP’s embedded 608 section.
This input source can co-exist with the previous #1 source.
This input can also co-exist with #3 and #5. If present, 608 XDS data from #3 and
#5 will be overwritten.
3
CDP objects found embedded in VBI section of an incoming SDI stream.
Main Player
4
CDP objects created from CEA-608 metadata as a result of cross conversion from
SD to HD format. See the CEA-608 section below on how the 608 metadata came
into existence in the first place.
Main Player
5
CDP ANC packets found in an MXF file, embedded conform the SMPTE 436M2006 specification, section 6: MXF Ancillary Data Packet wrapping specifications.
Main Player
Input source
Condition
1
Any clip. The time code represents clip time.
Main Player
2
ATC objects found embedded in VBI section of HD SDI stream.
Main Player
15.3.2 CDP
The following input sources are supported for extraction of the Caption Distribution Packet
(CDP) service, in given order of priority:
15.3.3 ATC / VITC
The following input sources are supported for extraction of the Ancillary Time Code (ATC) and
Vertical Interval Time Code (VITC) services, in given order of priority:
That is, the ATC/VITC output reflects the time code of either the currently playing clip (if
playing with main player role) or the currently playing SDI stream (again, only if playing as
main player).
The extracted time code is emitted as VITC for SD-channels and ATC for HD channels.
An STL subtitle rendered in CEA-608 format.
This input source can co-exist with the next #2 source.
2
CEA-608 XDS commands placed on the timeline of a Channel Composer template.
This input source can co-exist with the previous #1 source.
3 CEA-608 objects found embedded in VBI section of an incoming SDI stream in
NTSC broadcast format.
Main Player
4
CEA-608 objects created from CDP metadata as a result of cross conversion from
HD to SD format.
Main Player
15.3.4 CEA-608
The following input sources are supported for extraction of the CEA-608 closed caption
service, in given order of priority:
15.4 The main Player
15.4.1 Introduction
In Channel Composer, Objects such as ‘Clip’, ‘Audio’ and ’Still’ use a Player to play out
content. Players can be used to control playout. Different actions can be defined. The default
is: Play. Players can be modified in the Object and Objects window.
One main Player can be active per Channel.
The main Player role has following properties:
The main Player has priority over other Players when resources are assigned.
If the main Player contains an embedded Closed Caption subtitle stream, this stream
will be played out. If other Clips contain subtitle streams, these streams will not be
played out. In other words, only the main Player’s subtitle stream will be played out.
The main Player is the source for the ATC (HD) or VITC (SD) timecode signal in the
SDI-output. Only one signal can be sent out, i.e. from the main Player.
If the main Player is a Live Player and this Player transfers VBI-data from the SDI-
input, this VBI-data will be transferred to SDI-out instead of any VBI-data generated
by the K2 Edge server. This means that VBI-data from the input such as subtitles and
teletext is passed to the output 'as is'.
The main Player role can be assigned at any point in time, but is only active if
After changing the playout nodes’, TX/MAM or FTP-servers’ IP-address, following
adjustments need to be made:
18.1 After changing the IP-address of the playout nodes
1) Change the playout node’s IP-address in the TX/MAM Channel settings.
18.2 After changing the virtual IP-address of the TX/MAM-servers
1) On the K2Edge nodes, in /etc/hosts adjust MAIN-DB. Specify the virtual IP of the
TX/MAM servers.
Example:
You can also set the IP-address of the TX/MAM server via the IP Manager.
2) On both the TX/MAM servers, in /usr/local/apache2/application/configs/txmam.ini,
adjust project_options.serverip. Specify the virtual IP of the TX/MAM servers.
Example:
3) On both the TX/MAM servers, in /usr/local/apache2/application/configs/txmam.ini,
adjust ingest.assetHostIp. Specify the virtual IP of the TX/MAM servers.
Example:
4) To change the IP-address in the POC desktop shortcut properties
Right-click the POC icon on your desktop > Properties > Shortcut.
In the Target field fill in the TX/MAM servers’ virtual IP-address.