ST 2110¶

media.ingest.st2110

Description¶

Sapsan receives ST 2110 studio signals with separate tracks for uncompressed video, audio and ancillary data. Two configuration sources operate concurrently: central places the stream on a streamer and defines its input, while an external NMOS controller configures multicast addresses and receiver formats.

Configuration¶

Configure the stream through the central API. Stream configuration fragment:

streams:
- name: source1
  inputs:
  - st2110:
      network: studio
      receivers:
        video:
          enabled: true
        audio:
          enabled: true
        data:
          enabled: true

Parameters¶

Field	Description
`network`	media-network label configured on the streamer interface.
`receivers`	receive tracks; `enabled` enables reception.
`reduce_to_8bit`	reduce 10-bit video to 8 bits.
`recv_buffer_bytes`	socket buffer; `queue_max_bytes`: queue limit; `audio_frame_ms`: audio frame duration. Manual receiver addressing uses `host`, `port`, `source` and `format`; `sdp` supplies a transport description.

Authentication¶

The streamer serves IS-05 directly. Restrict NMOS controller access to the management network; NMOS configuration does not replace central API authorization.

Transport options¶

ST 2110-20 — video over RTP/UDP multicast.
ST 2110-30 — audio.
ST 2110-40 — ancillary data.

PTP synchronizes the timeline. SSM specifies the sender address.

Supported codecs¶

YCbCr 4:2:2 (8-bit)
YCbCr 4:2:2 (10-bit)
PCM L16
PCM L24

YCbCr describes uncompressed pixels; L16/L24 are uncompressed PCM samples. Video uses ST 2110-20 and audio uses ST 2110-30. AM824/AES3 (ST 2110-31) reception is not implemented in the current media path. SMPTE ST 291 for ANC packages ancillary data; it is not a video codec.

Error handling¶

Input state and failure cause are available in stream statistics. Connection loss or missing frames uses the shared retry and failover mechanisms.

Applying changes¶

Central changes and NMOS commands coexist: central owns placement and input composition, the controller owns track routing. The streamer applies IS-05 activation to receiver addressing. Address or format changes reconnect the affected receiver.

Counters¶

The tables give exact protocol statistics field names, including event counters and current-value gauges. Zero fields may be omitted. API and Prometheus expose different projections; the full list is not necessarily present in one Admin API response. Detailed statistics depend on the counter license.

Common input totals: bytes, frames, errors, warnings. They aggregate protocol data and must not be added to protocol counters again.

St2110¶

Field	Type
`declared_tracks`	`gauge`
`receiving_tracks`	`gauge`
`diverged_clock_tracks`	`gauge`
`clock_drift_ms`	`gauge`
`xdp_reopens`	`counter`

RtpChannel¶

Field	Type
`channel_id`	`label`
`rtp_packets`	`counter`
`rtcp_packets`	`counter`
`bytes`	`counter`
`frames`	`counter`
`pt_reject_count`	`counter`
`pt_reject_bytes`	`counter`
`ts_goes_backwards`	`counter`
`ts_jump_forward`	`counter`
`ts_stuck`	`counter`
`errors_dts_stuck`	`counter`
`sr_ts_stuck`	`counter`
`ts_stuck_restarts`	`counter`
`resync_sr`	`counter`
`marker_packets_count`	`counter`
`no_marker_mode_flag`	`gauge`
`errors_broken_payload`	`counter`
`errors_lost_packets`	`counter`
`errors_dropped_packets`	`counter`
`errors_late_packets`	`counter`
`errors_incomplete_frames`	`counter`
`nack_count`	`counter`
`onvif_buffer_overflow`	`counter`
`onvif_seq_gap`	`counter`
`onvif_marker_mismatch`	`counter`
`onvif_resync_dropped`	`counter`

Other details¶

NMOS IS-04 advertises receivers and IS-05 connects them. Without a controller, addresses and formats can be set manually through the central API. Uncompressed video requires sufficient network and memory bandwidth; add transcoding for HLS and other compressed outputs.