Managing the Encoder
Configuring Metadata Capture
Makito
X User’s Guide, v2.2, Issue 02
102
Configuring Metadata Capture
IMPORTANT
Metadata processing is a licensed feature which may be installed at the
factory or via a field upgrade by installing a license file.
From the Metadata pages, you can configure the Makito
X to capture either KLV (Key
Length Value) or CoT (Cursor on Target) metadata and then incorporate data information
within the metadata elementary stream of the standard MPEG Transport Stream.
You can set up multiple metadata inputs to include in Transport Streams. The Makito
X
supports up to three metadata input types:
●
Serial port (
Makito
X SDI only)
:
The Makito
X SDI extracts either KLV or CoT
metadata packets from the COM1 serial port. See
●
SDI (
Makito
X
SDI
only)
:
The Makito
X SDI extracts KLV metadata packets from the
HD-SDI interface as per MISB RP 0605.2. See
●
Network:
The Makito
X captures metadata from a user definable network port (up to
eight UDP inputs). The encoder can receive either (a) KLV payload encapsulated in
UDP or (b) CoT inside UDP that is converted to KLV and then streamed. See
“Configuring Network Metadata Sources”
The Makito
X auto-detects the hardware setup of the encoder. If the serial port or SDI video
is connected, the serial or SDI metadata source is created automatically at startup by the
system. For Serial input, the COM Port Mode must also be set to Metadata (see
196). UDP sources must be manually created by the user. The Makito
supports
insertion of multiple metadata sources into the same KLV Elementary Stream.
The Makito
X supports both synchronous and asynchronous KLV metadata stream
signaling and AU (Access Unit) transport support. When configuring a stream, you can
select the encapsulation type to use for the associated KLV metadata source. For technical
specifications, see
“Asynchronous KLV Metadata Support”
CoT/UDP and CoT/Serial metadata sources can also be retransmitted to other IP destina-
tions for follow-up analysis by third party systems. For more information, see
You can define a small set of static KLV objects (i.e., mission IDs and security classifica-
tion) for KLV and CoT metadata sources. For more information, see