Frame-Accurate SCTE Signaling. Anywhere.
AvailX delivers SCTE 104/35 signaling across the internet and places it on the correct video frame at the receiving end - no manual latency measurement, no static offsets.
Why Remote SCTE Signaling Breaks
The Problem
Most production trucks don't have SCTE 104/35 capability. Even those that do can only signal "break starts here, break ends here" - they can't build distributor-specific SCTE messages with each downstream partner's segmentation descriptors and UPID formats. And some transport paths like satellite may not carry SCTE correctly at all.
Network feeds arrive at affiliates with full SCTE decoration, but the affiliate's local playout doesn't preserve it. There's no standard way to restore it frame-accurately at scale.
How AvailX Solves It
The Transmitter accepts both SCTE 104 and SCTE 35 messages and delivers them frame-accurately to each Receiver. Each Receiver can apply its own signal processing rules to produce distributor-specific output - similar to an ESAM workflow but across the internet.
PhaseLock watches the video content itself to synchronize timing between origination and the receiving end. It doesn't matter what the transport latency is or how it changes - PhaseLock knows exactly which frame is which.
Predictive Pre-Roll
AvailX outruns the video transport. The Receiver gets the signaling message before the target frame arrives.
In TS mode, the Receiver places SCTE 35 in the transport stream with correct splice_time PTS ahead of the target frame - exactly how downstream splicers expect to receive it. SDI mode support (SCTE 104 in VANC) is coming soon.
The pre-roll window also provides resilience - if the first delivery attempt fails, the Transmitter retries while the target frame is still ahead.
Signal Processing
One trigger from the truck or automation system, different SCTE 35 output at each receiving point. Each Receiver's output is shaped by an ESAM rules engine configured for its distributor's requirements.
Built-In Rules Engine
Per-receiver SCTE 35 rules. Convert splice_insert() to time_signal(), rewrite segmentation descriptors and UPIDs, suppress signals, or pass through. Channel-level defaults with per-receiver overrides.
External POIS Integration
OC-SP-ESAM-API-I03 compliant Placement Opportunity Information Service connector for customers with existing ad decisioning infrastructure. Coming soon.
Splice Conditioning
AvailX can optionally analyze the video content near the target frame and choose the best splice point - a clean scene boundary or transition. The stream is conditioned at that point with a closed GOP and IDR frame, giving downstream splicers an ideal setup.
The search window is configurable. Turn it off entirely for exact-frame placement when that's what you need.
Standard SCTE 104 Injector Interface
The AvailX Transmitter presents a standard SCTE 104 injector interface over TCP. Any existing automation system - Imagine ADC, Harmonic Polaris, or anything else that speaks SCTE 104 - points its output at the Transmitter. It thinks it's talking to a normal injector. No code changes, no integration work.
The Transmitter collects responses from all downstream Receivers and returns a single aggregated response to the host application. The operator gets definitive confirmation - not fire-and-forget.
Architecture
AvailX Transmitter
Standard SCTE 104 injector over TCP for any existing automation system. Embedded module for tighter integration with BreakTime and AdIT. Passive reader for network-to-affiliate, reading existing SCTE directly from the stream. Associates each message with the exact video frame. Returns aggregated responses from all Receivers.
AvailX Receiver
Runs on your infrastructure. PhaseLock identifies the target frame. Signal processing rules produce distributor-specific SCTE 35 output with correct splice_time PTS. SDI mode coming soon. Video never touches AvailX. Primary/standby pairs.
AvailX Service
Management and orchestration. Web dashboard for streams, channels, and signal processing rules. Stream code generation and Transmitter pairing. Credential provisioning and lifecycle management.
AvailX Agent
Orchestrates Receivers on customer infrastructure. Receives stream configuration and signal processing rules from the Service, spins up the right Receivers, and keeps them healthy.
Use Cases
Remote Live Event Signaling
A production truck at a remote venue delivers video to a receiving location. An operator or automation system triggers ad breaks. Those break signals need to be placed frame-accurately in the output stream.
The operator triggers a break. Each Receiver places the correct distributor-specific SCTE output on the right frame with proper pre-roll. The operator gets confirmation it landed.
Network-to-Affiliate SCTE Re-Injection
Network feeds arrive at affiliates with full SCTE decoration, but the affiliate's local playout doesn't preserve it. AvailX restores it.
A Transmitter at the network origination point reads existing SCTE 104 or 35 and notes the precise video frame each message was associated with. At each affiliate, post-local-playout, the Receiver re-injects on the correct frames - frame-accurate re-injection, automatically.
PhaseLock lock state is the content detection. Locked on network content - inject. Loses lock on local content - stop. No configuration needed.
Simple Stream Pairing
Create a stream in AvailX. Get a stream code.
Hand the code to the truck crew or automation system.
The operator enters the code in BreakTime. PhaseLock establishes lock. Ready to go.
No manual configuration of endpoints, credentials, or routing. The stream code handles everything.
Built for Redundancy
Dual Bus Support
AvailX supports two independent messaging buses with independent credentials per bus. All components connect to both simultaneously. If one bus goes down, the other carries traffic with zero switchover delay.
Transmitter
Publishes to both buses simultaneously. Retries within the pre-roll window via request/reply.
Agent Pairs
Primary/secondary at each location. If the primary fails, the secondary takes over Receiver management.
Receiver Pairs
Primary/standby per stream. Both maintain PhaseLock lock continuously. Standby is already synchronized - promotion is immediate, no lock-up delay.
Every component except the human operator is redundancy-capable as a first-class feature.
Deployment
Cloud Service
Hosted at app.availx.tv. Per-concurrent-stream subscription. Schedule a meeting to get started.
Enterprise
Same codebase, same containers. Self-hosted option available for enterprise deployments. Perpetual license for a defined concurrent stream capacity. Schedule a meeting to discuss.
Security
Managed Credential Lifecycle
AvailX provisions scoped credentials per component, per stream. Each Transmitter, Receiver, and Agent gets only the permissions it needs. Each customer is fully isolated - complete namespace separation.
Instant Revocation
Credentials are killed immediately when a stream is torn down. No waiting for token expiry.
Video Stays on Your Infrastructure
Video is processed locally at the Transmitter and Receiver - it never transits AvailX cloud infrastructure. Only signaling data crosses the network. All connections are TLS-encrypted.