Grass Valley K2 AppCenter v.9.0 - Manual (Page 245)

Data track support on K2 Summit/Solo HD channels
On channels with the XDP (HD) license, the data track can contain ancillary data and other types
of data. Luma ancillary data packets are stored. Chroma ancillary data packets are not supported.
Supported as follows: Data
For record, selectable to use VITC or LTC ancillary timecode as timecode source. For
playout, selectable to insert recorded timecode track as ancillary data VITC or LTC timecode
packets. If the recorded timecode track is inserted as VITC ancillary timecode and VITC
ancillary timecode packets are already stored on the data track, then the recorded timecode
track overrides the stored VITC ancillary timecode packets. If the recorded timecode track
is inserted as LTC ancillary timecode and LTC ancillary timecode packets are already stored
on the data track, then the recorded timecode track overrides the stored LTC ancillary
timecode packets. Ancillary timecode
Extracted at input and stored on an ancillary data track. Upon playout, the data packets are
inserted into the video stream on specified lines. Maximum 8 packets per field. CC and TT
supported as native to format. Vertical interval
ancillary data packets
Captioning system support
An API is provided for access to captioning data, allowing Closed Captioning and Teletext systems
to produce timecode correlated captions for an existing K2 clip.
About FCC requirements
Federal Communications Commission (FCC) rules incorporate sections of industry standards EIA-708
and EIA-608. The K2 Summit/Solo system complies with the rules for EIA-608 to DTV Closed
Captioning (CC) transcoding. If SD material has EIA-608 CC present, the K2 Summit/Solo system
can be configured so that when it up-converts the material the EIA-708 packet contains the EIA-608
data plus the DTV CC transcoded from EIA-608.
This applies to up-conversion only. HD material should already have compliant EIA-708 packets.
Related Topics
Configuring data track settings on page 175
About privately defined data packets
In ancillary data, the K2 Summit/Solo system supports data defined by a private organization. This
is data that is not defined and registered with SMPTE.
For example, if a facility puts privately defined data as special "triggers" in their stream for
downstream devices, these triggers are preserved on record and transfer and played with field
accuracy when needed. SMPTE standard data is supported as well as the privately defined data, for
fully compliant, field accurate data track support.
Data bridging of VBI information on K2 Summit/Solo HD channels
On channels with the XDP (HD) license, data is bridged as follows:
29 October 2012 K2 AppCenter User Manual 245
Specifications