Compliance recording

What is ST2110 compliance recording?

ST2110 compliance recording is the continuous capture and archiving of SMPTE ST2110 IP media streams for regulatory compliance, legal evidence, and operational audit purposes. It provides a verifiable record of what was transmitted from ST2110 broadcast infrastructure.

SMPTE ST2110 is the professional standard for uncompressed IP video, audio, and ancillary data transport in modern broadcast facilities. As broadcast facilities transition from SDI-based to IP-based infrastructure, ST2110 is becoming the primary signal standard for studio, production, and transmission environments worldwide. The signal standard is changing, but the compliance recording obligation stays the same.

The FCC in the United States, Ofcom in the UK, TRAI in India, ACMA in Australia, and equivalent regulators in other major broadcast markets require broadcasters to keep verifiable records of transmitted content, whether that content is transported over SDI coaxial cable or SMPTE ST2110 IP infrastructure.

SyncWIZ is Tricube's GPU-accelerated broadcast compliance recording and monitoring platform, built for TV broadcasters, OTT providers, and media regulators worldwide. SyncWIZ accepts ST2110 as a native input source and records ST2110 streams directly to the compliance archive alongside SDI, NDI, SRT, and all other supported source types.

Why ST2110 compliance recording is different

Traditional broadcast compliance recording systems were designed for SDI infrastructure. They receive SDI signals from hardware capture cards, such as AJA, Blackmagic, Bluefish444 and Deltacast, and record them to a structured compliance archive.

ST2110 infrastructure delivers video differently. Uncompressed IP media is transported over facility networks, typically 10GbE or 25GbE, rather than physical SDI coaxial connections. Compliance recording systems that cannot accept ST2110 natively need intermediate ST2110 to SDI conversion at every compliance recording input.

This intermediate conversion approach has three operational problems:

Additional hardware at every input

An ST2110 to SDI converter appliance is required between each ST2110 source and each compliance recording input. A facility with 16 ST2110 channels requiring compliance recording needs 16 converter appliances and 16 sets of cabling, which adds 16 more points of failure.

Additional latency and signal degradation

Every conversion step introduces latency and a generation of signal processing between the ST2110 source and the compliance record. The recorded file is not a direct capture of the ST2110 signal but a converted version of it.

Operational complexity

Managing a hybrid infrastructure of ST2110 sources, ST2110 to SDI converters, and SDI-based compliance recorders creates operational complexity that increases with every additional channel. Troubleshooting a gap in the compliance record requires investigating the ST2110 source, the converter, and the recorder independently.

SyncWIZ removes this problem by recording ST2110 sources directly. There is no intermediate conversion hardware, and no conversion step to add latency or another point of failure.

How ST2110 compliance recording works in SyncWIZ

SyncWIZ records ST2110 sources through the same five-stage GPU processing pipeline used for all other source types:

  1. Stage 1: ST2110 ingest

    SyncWIZ receives the ST2110 IP media stream from the facility network: ST2110-20 video essence, ST2110-30 audio essence, and ST2110-40 ancillary data. ST2110 is treated as a native input source within the SyncWIZ multi-channel recording session alongside SDI, NDI, SRT, and all other configured sources.

  2. Stage 2: GPU decoding

    The received ST2110 signal passes into the GPU processing pipeline, where it is decoded and processed on NVIDIA, Intel, or AMD GPU hardware. GPU processing reduces CPU overhead and enables high channel density per server.

  3. Stage 3: GPU processing

    Format conversion, resolution scaling where required, and timestamp overlay all run on GPU hardware. The date and time are burned directly onto the recorded video, so the timestamp is embedded in the file and cannot be separated from the ST2110 content.

  4. Stage 4: GPU encoding

    The processed video is encoded to the configured compliance recording format, such as H.264, H.265/HEVC or another configured codec, using NVIDIA NVENC, Intel Quick Sync, or AMD hardware acceleration. Multiple encoding profiles per ST2110 source record proxy and archive quality simultaneously from the same ingest.

  5. Stage 5: Archive

    The encoded compliance recording is written to structured storage using the configured naming template, which embeds the source name, date, time, timecode, and chunk number in every filename. Post-capture file actions automatically copy completed files to secondary storage for backup and archive.

What ST2110 compliance recording must capture

A complete ST2110 compliance recording captures:

ST2110-20: video essence

The primary video content of each ST2110 source, recorded at compliance-grade quality alongside all other channels.

ST2110-30: audio essence

The audio content associated with each ST2110 source is recorded alongside the video in the same compliance file. Multi-channel audio tracks are preserved for loudness compliance evidence and audio quality verification.

ST2110-40: ancillary data

Timecode and ancillary data from ST2110-40 are embedded in the recorded file for post-production accuracy and compliance evidence. Timecode provides the authoritative temporal reference for the ST2110 compliance record.

Timestamp burn-in

The date and time are burned directly onto the recorded video, so they are embedded in the file and cannot be separated from the content. This provides strong timestamp evidence of when ST2110 content was transmitted, independent of file metadata that could in theory be altered.

Regulatory requirements for ST2110 compliance recording

ST2110 compliance recording obligations apply in the same way as SDI compliance recording obligations. The signal standard does not change the regulatory requirement.

United States (FCC)

Broadcasters transmitting programme content through ST2110 infrastructure must maintain compliance records that meet FCC retention requirements. Retaining general broadcast content for 60 to 90 days is standard practice, but check the current FCC rule. Political advertising records must be kept for a minimum of two years, and EAS activation records follow the specific EAS requirements.

United Kingdom (Ofcom)

Ofcom compliance obligations apply to transmitted content regardless of the internal signal standard used. Where ST2110 infrastructure is used for programme production and transmission, the transmitted output must be logged for compliance, with a minimum of 60 days' retention for television programming (the 42-day period applies to radio).

India (TRAI and MIB)

TRAI and Ministry of Information and Broadcasting compliance obligations apply to broadcasters using ST2110 infrastructure. Compliance recording of ST2110-based transmission is required under applicable Cable Television Networks Rules and TRAI directives.

Australia (ACMA)

ACMA compliance obligations apply to broadcasters operating ST2110 infrastructure for programme production and transmission. Retention periods depend on broadcaster category and content type under the Broadcasting Services Act.

European Union: national regulators

AVMS Directive obligations apply to broadcasters operating ST2110 infrastructure across EU member states. National regulators implement specific retention requirements that apply regardless of the internal signal standard used for programme production.

Middle East and Asia Pacific

National broadcast regulatory authorities across the UAE, Saudi Arabia, Qatar, Kuwait, Bahrain, Oman, Australia, New Zealand, and Singapore apply compliance recording requirements to broadcasters operating ST2110 infrastructure.

ST2110 compliance recording with SyncWIZ

SyncWIZ records ST2110 sources natively, as first-class recording channels in the same multi-channel compliance session as SDI, NDI, SRT, HLS, WebCapture, and all other supported sources.

Multi-channel synchronised recording

All ST2110 sources record simultaneously alongside all other source types in the same SyncWIZ session. A compliance session recording 16 ST2110 sources, 8 SDI sources, and 4 NDI sources records all 28 channels simultaneously, with every channel timestamped.

Multiple encoding profiles per ST2110 source

The same ST2110 ingest records simultaneously to a proxy format for fast compliance review and a high-resolution archive format for legal evidence. One ingest produces both recordings, with no additional hardware.

Scales by adding instances

Multiple SyncWIZ instances on a single NVIDIA, Intel, or AMD GPU server let you add ST2110 channels without changing hardware platforms. Channel density depends on the GPU server specification and licence.

SyncPlayer Web: browser-based ST2110 compliance review

ST2110 compliance recordings are accessible through SyncPlayer Web, the same browser-based, multi-channel synchronised review interface used for all other compliance recordings. It offers date navigation, a synchronised timeline, per-channel playback control, and variable speed playback from any authorised location, on a desktop, laptop, tablet or mobile browser. No client installation is required.

ST2110 compliance recording in mixed infrastructure environments

Most broadcast facilities transitioning to ST2110 operate mixed infrastructure, with ST2110 for new IP deployments alongside legacy SDI equipment. Compliance recording in these environments must handle both signal standards simultaneously.

SyncWIZ records SDI sources from AJA, Blackmagic, Bluefish444, Deltacast, Magewell, and Yuan capture hardware alongside ST2110 sources, in the same multi-channel compliance session, on the same synchronised timeline, and in the same compliance archive. Facilities transitioning from SDI to ST2110 do not need separate compliance recording systems for each signal standard, because SyncWIZ handles both natively.

BridgeWIZ, Tricube's live video gateway, converts ST2110 sources to NDI or SRT for facilities where the compliance recorder receives converted protocol outputs rather than ST2110 directly. BridgeWIZ converts ST2110 to NDI on the local network, and SyncWIZ records the NDI stream as a standard compliance recording channel. This approach enables ST2110 compliance recording in environments where the compliance recorder is not on the same network segment as the ST2110 infrastructure.

How SyncWIZ differs from legacy ST2110 compliance recording approaches

Traditional compliance recording approaches for ST2110 infrastructure need dedicated hardware at every step, with ST2110 to SDI converter appliances feeding SDI-based compliance recorders. Each extra hardware layer adds points of failure and a significant hardware investment per compliance recording channel.

SyncWIZ provides complete ST2110 compliance recording in software. It accepts ST2110 natively, records it directly to the compliance archive, and makes it accessible through SyncPlayer Web from any authorised location, with no dedicated ST2110 converter appliances or intermediate SDI conversion hardware.

The full GPU video processing pipeline runs on NVIDIA, Intel, or AMD hardware, with decoding, conversion, encoding, overlay, and preview all on the GPU. Multiple instances on a single GPU server record ST2110 channels, depending on server specification and licence, without dedicated hardware appliances per channel.

FAQs

What is ST2110 compliance recording?

ST2110 compliance recording is the continuous capture and archiving of SMPTE ST2110 IP media streams for regulatory compliance, legal evidence, and operational audit purposes. As broadcast facilities transition from SDI to ST2110 IP infrastructure, compliance recording systems must handle ST2110 sources natively, providing the same verifiable, retrievable compliance records that regulators require regardless of the signal standard used in the broadcast chain. SyncWIZ records ST2110 sources directly as native input channels in the same multi-channel compliance session as SDI, NDI, and SRT sources.

Does SMPTE ST2110 infrastructure require broadcast compliance recording?

Yes. Regulatory compliance obligations apply to broadcasters using ST2110 infrastructure in exactly the same way they apply to SDI and other IP broadcast infrastructure. The FCC, Ofcom, TRAI, ACMA, and equivalent bodies in other major markets require broadcasters to keep verifiable records of transmitted content, whatever internal signal standard is used. A change in how the signal is transported does not change the regulatory obligation.

Can SyncWIZ record ST2110 sources directly without intermediate SDI conversion?

Yes. SyncWIZ accepts ST2110 as a native input source and records ST2110 streams directly to the compliance archive, without requiring ST2110 to SDI converter hardware at each recording input. ST2110 sources record in the same multi-channel session as SDI, NDI, SRT, and all other supported sources.

How does ST2110 compliance recording scale for large channel counts?

Multiple SyncWIZ instances on a single GPU server record ST2110 channels, with capacity depending on hardware specification and licence. Expansion means running additional instances on existing server hardware rather than buying additional hardware appliances per channel.

Can SyncWIZ record ST2110 and SDI sources in the same compliance session?

Yes. SyncWIZ records ST2110, SDI, NDI, SRT, HLS, WebCapture, and all other supported source types simultaneously in the same multi-channel compliance session, regardless of source type. Broadcast facilities operating mixed ST2110 and SDI infrastructure record all sources from a single platform with a unified compliance archive.

Get started

See how SyncWIZ fits your compliance workflow

Book a demo with our broadcast engineers. We will demonstrate SyncWIZ using your sources, channel count, and compliance requirements.