As broadcast facilities move from SDI to ST2110 IP infrastructure, compliance logging must evolve with the signal standard. The regulatory obligations that govern broadcast compliance recording do not change because the signal travels over ST2110 rather than SDI. Regulators such as the FCC in the United States, Ofcom in the UK, TRAI in India, and ACMA in Australia, along with equivalent bodies in other major markets, require broadcasters to keep verifiable records of transmitted content, whatever signal standard the broadcast chain uses.
Compliance logging systems designed only for SDI cannot capture ST2110 signals without intermediate conversion. BridgeWIZ, Tricube's live video gateway, and SyncWIZ, its compliance recording platform, together provide a complete ST2110 compliance logging workflow on standard GPU server hardware, without dedicated ST2110 compliance recording appliances.
The ST2110 compliance logging challenge
Traditional broadcast compliance logging systems were designed for SDI infrastructure. They accept SDI signals from capture hardware made by vendors such as AJA, Blackmagic, Bluefish444, and Deltacast, and record them to a structured compliance archive.
ST2110 infrastructure delivers video differently, as uncompressed IP media over facility networks rather than through physical SDI coaxial connections. Compliance logging systems that cannot accept ST2110 natively need intermediate ST2110 to SDI conversion at every compliance recording input. Each conversion step adds hardware and cost, and introduces another potential point of failure in the compliance chain.
The ideal ST2110 compliance logging workflow accepts ST2110 sources directly and records them to a structured compliance archive with the same capabilities as SDI-based compliance logging, without intermediate hardware conversion.
Two approaches to ST2110 compliance logging
BridgeWIZ and SyncWIZ together support two complementary approaches to ST2110 compliance logging:
Approach 1: direct ST2110 compliance recording via SyncWIZ
SyncWIZ, Tricube's broadcast compliance recording platform, accepts ST2110 as a native input source. ST2110 streams from IP media infrastructure record directly to the SyncWIZ compliance archive alongside SDI, NDI, SRT, and all other supported source types.
This is the simplest approach to ST2110 compliance logging, because ST2110 sources record directly to SyncWIZ without any intermediate conversion. The complete SyncWIZ compliance workflow applies to ST2110 sources exactly as it does to SDI and NDI sources, including multi-channel recording, a date-based archive, synchronised multi-channel playback in SyncPlayer Web, and all other compliance recording capabilities.
Approach 2: ST2110 via BridgeWIZ conversion to SyncWIZ
For deployments where the compliance recording system receives converted protocol outputs rather than ST2110 directly, BridgeWIZ converts ST2110 to NDI or SRT, and SyncWIZ records the converted stream for compliance.
BridgeWIZ converts ST2110 to NDI and outputs it to the local network. SyncWIZ records the NDI stream, receiving it as a standard NDI source for compliance logging. This approach enables ST2110 compliance logging where the compliance recorder is not on the same network segment as the ST2110 infrastructure.
Alternatively, BridgeWIZ converts ST2110 to SRT for transport across network boundaries, and SyncWIZ records the SRT feed at the receiving end for compliance logging.
What ST2110 compliance logging must capture
A complete ST2110 compliance logging workflow captures:
ST2110-20 video essence
The video content of each ST2110 source, recorded continuously at compliance-grade quality alongside all other channels.
Audio
The audio content associated with each ST2110 source, recorded alongside the video in the compliance archive. Multi-channel audio tracks are preserved for loudness compliance evidence and audio quality verification.
Timecode and metadata
Timecode and ancillary data embedded in recorded files. These provide the time reference for compliance evidence and allow precise retrieval of specific moments from the archive.
Timestamp burn-in
Date and time are burned directly onto the recorded video, so the timestamp is embedded in the file and cannot be separated from the content. This provides timestamp evidence of when ST2110 content was transmitted.
Regulatory requirements for ST2110 compliance logging
Regulatory compliance obligations apply to ST2110 broadcast infrastructure in the same way they apply to SDI and IP broadcast infrastructure. The signal standard does not change the regulatory obligation.
United States (FCC)
Broadcasters transmitting programme content over ST2110 infrastructure must keep compliance records that meet FCC retention requirements: 60 to 90 days for general content (check the current rule) and two years for political advertising. ST2110 compliance logging provides the required evidence.
United Kingdom (Ofcom)
Ofcom compliance obligations apply to transmitted content regardless of the internal signal standard. ST2110 infrastructure used for programme production and transmission requires compliance logging of the transmitted output.
India (TRAI)
TRAI compliance obligations apply to broadcasters using ST2110 infrastructure. Compliance recording of ST2110-based transmission is required under applicable broadcasting regulations.
Australia (ACMA)
ACMA compliance obligations apply to broadcasters operating ST2110 infrastructure for programme production and transmission.
International markets
National broadcast regulators in all major markets require compliance records of transmitted content. ST2110 infrastructure does not exempt broadcasters from these obligations.
SyncWIZ for ST2110 compliance recording
SyncWIZ, Tricube's broadcast compliance recording platform, provides the complete compliance recording workflow for ST2110 infrastructure:
Direct ST2110 ingest
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 sources.
Synchronised multi-channel review
ST2110 channels record in the same session as all other sources, regardless of protocol, and play back together on one synchronised timeline in SyncPlayer Web.
Multi-format recording
ST2110 sources record to proxy and archive quality simultaneously from one ingest, giving a fast review format alongside an archive format for compliance evidence.
Date and time overlay
The timestamp is burned directly onto recorded ST2110 video and embedded in the file as compliance evidence.
SyncPlayer Web
Browser-based archive access with date navigation, a synchronised multi-channel timeline, per-channel playback control, and variable speed playback. ST2110 compliance recordings are accessible from any authorised location without client installation.
Scalable channel architecture
Multiple SyncWIZ instances on a single GPU server record ST2110 channels, depending on server specification and licence, without dedicated hardware recorders per channel.
BridgeWIZ for ST2110 protocol conversion in compliance workflows
BridgeWIZ supports ST2110 compliance logging workflows in several ways:
ST2110 to NDI for SyncWIZ recording
BridgeWIZ converts ST2110 sources to NDI, making them available to SyncWIZ for compliance recording where the compliance recorder is not on the same ST2110 network segment.
ST2110 to SRT for remote compliance recording
BridgeWIZ converts ST2110 sources to SRT for transport to remote locations, where SyncWIZ records the SRT feed for compliance logging at remote playout centres, affiliate stations, and distribution hubs.
ST2110 ISO recording alongside compliance outputs
BridgeWIZ records ST2110 ISO files concurrently with all other outputs. This provides individual source-level archive records alongside programme-level compliance logging from SyncWIZ.
Complete ST2110 compliance workflow on GPU server hardware
The complete ST2110 compliance logging workflow using BridgeWIZ and SyncWIZ runs on standard server hardware with NVIDIA, Intel, or AMD GPU acceleration, without dedicated compliance recording appliances or dedicated ST2110 gateway hardware:
Single server deployment
One GPU server runs both BridgeWIZ and SyncWIZ instances simultaneously. BridgeWIZ handles ST2110 protocol conversion and ISO recording. SyncWIZ handles compliance logging of ST2110 sources, either directly or via BridgeWIZ conversion.
Separate server deployment
BridgeWIZ runs on one GPU server, handling ST2110 conversion and ISO recording. SyncWIZ runs on a second server, handling compliance logging and receiving ST2110 directly or via NDI or SRT from BridgeWIZ.
Both deployment models run entirely in software on standard GPU server hardware, in place of dedicated hardware appliances for compliance recording and protocol conversion.
How this differs from legacy ST2110 compliance recording approaches
Legacy compliance recording approaches for ST2110 infrastructure need dedicated hardware at every step, with ST2110 to SDI converter appliances feeding SDI-based compliance recorders. This means multiple hardware layers, multiple points of failure, and significant hardware investment per compliance recording channel.
BridgeWIZ and SyncWIZ together provide complete ST2110 compliance logging in software. SyncWIZ accepts ST2110 natively, or BridgeWIZ converts it for transport to SyncWIZ, all on standard GPU server hardware. No dedicated ST2110 compliance appliances or intermediate SDI conversion hardware are needed, and GPU-accelerated processing scales by adding instances on the same server.
FAQs
Does ST2110 infrastructure require broadcast compliance logging?
Yes. Regulatory compliance obligations apply to broadcasters using ST2110 infrastructure in the same way they apply to SDI and IP broadcast infrastructure. Regulators such as the FCC, Ofcom, TRAI, and ACMA, along with equivalent bodies in other major markets, require broadcasters to keep verifiable records of transmitted content, whatever internal signal standard is used.
Can SyncWIZ record ST2110 sources directly for compliance?
Yes. 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 sources. The complete SyncWIZ compliance recording workflow applies to ST2110 sources exactly as it does to SDI and NDI sources.
How does BridgeWIZ support ST2110 compliance logging workflows?
BridgeWIZ converts ST2110 sources to NDI or SRT for transport to SyncWIZ compliance recording in deployments where the compliance recorder is not on the same ST2110 network segment. BridgeWIZ also records ST2110 ISO files concurrently, providing individual source-level archive records alongside programme-level compliance logging from SyncWIZ.
Can ST2110 compliance logging run on standard server hardware?
Yes. BridgeWIZ and SyncWIZ together provide complete ST2110 compliance logging on standard server hardware with NVIDIA, Intel, or AMD GPU acceleration, without dedicated ST2110 compliance recording appliances or dedicated gateway hardware.
How does ST2110 compliance logging scale for large channel counts?
Multiple SyncWIZ instances on a single GPU server handle ST2110 compliance recording, depending on server specification and licence. Multiple BridgeWIZ instances handle ST2110 protocol conversion and ISO recording at the same time. Both scale by adding instances on existing server hardware, without dedicated hardware appliances per channel.