PVirtual tuner platform
A modular broadcast operations platform for remote tuners, channel intelligence, secure delivery and managed media services.
About productOverview
SAT>IP Client Pro goes far beyond a remote tuner bridge. It combines virtual reception, OrbitScan inventory, OTA/XMLTV EPG, browser delivery, DVR, media libraries, conditional access, network policy and auditable operations in one licensed Linux platform.
For operators who need one control plane for remote reception, channel inventory, programme data, protected delivery and media operations.
Features
Connect reception hardware across routed networks and expose it to local Linux applications or downstream services. Each remote source can choose TCP or UDP transport independently, while the optional proxy module provides transparent upstream SAT>IP pass-through with controlled listener and firewall handling.
Discover satellite networks from NIT/BAT data, analyze real transport streams and maintain a service inventory keyed by DVB ONID, TSID and SID—not fragile channel names. Health evidence, scheduled recovery, lifecycle changes and bounded public inventory feeds turn tuner scans into a durable operational data set.
Preserve specialist broadcast identities through acquisition, analysis and delivery. The client supports T2-MI PLP extraction, MPS inner-service selection and raw BBFrame reconstruction for compatible multistream reception, carrying the required tuning evidence through OrbitScan, EPG and streaming workflows.
Combine XMLTV feeds with tuner-bound over-the-air EPG collection, reload and browse programme data, then launch playback, one-off recording or series rules from the same context. Source-scoped scheduling, identity reconciliation and bounded history help prevent stale or cross-multiplex guide data.
The integrated streamer manages live television plus VOD, TV-show and music libraries. Tokenized HTTP, HLS and DASH outputs support browser and application clients, while encrypted SRT covers resilient contribution. Per-session monitoring, transport-health evidence and cleanup protect long-running delivery nodes.
DVBAPI, structured Newcamd profiles, DDCI and hardware CI cover authorized access workflows. Authenticated HTTPS administration, API keys, user/token management, fixed-port firewall policy and per-client delivery controls keep operational access and media access deliberately separated.
The Control Center brings tuner state, bandwidth, sessions, signal, EPG, storage and add-on status together. Signed in-app releases, controlled update channels, health supervision and automation APIs support repeatable fleet operation across bare metal, Proxmox and LXC environments.
Integrated modules
Licensed modules share reception identity, access control and operational evidence instead of behaving like disconnected utilities.
Bring remote SAT>IP capacity into Linux applications, choose TCP or UDP per source, and operate across bare metal, Proxmox or LXC with topology-appropriate permissions.
Expose multiple controlled proxy tuners as transparent pass-through routes to upstream receivers, with automatic listener allocation, firewall integration and watchdog recovery.
Discover NIT/BAT networks, analyze services, retain DVB ONID/TSID/SID identity, track mux health and publish bounded channel inventories and confirmed change events.
Collect standard and platform-specific over-the-air guide data, merge XMLTV sources, protect source identity, retain bounded history and coordinate acquisition with tuner availability.
Operate live TV, VOD, television-series and music libraries; provide browser playback, recording and series rules; import remote live sources and keep media catalogues synchronized.
Create tokenized segmented and direct outputs, preserve channel identity in playlists, monitor per-feed transport health and manage concurrent client sessions.
Support authorized DVBAPI and Newcamd profiles alongside DDCI and hardware CI, with structured profile control, key activity visibility and recovery safeguards.
Use authenticated HTTPS, API keys, users and delivery tokens, fixed-port firewall policy, signed update channels, system health supervision and auditable release management.
Architecture
The client connects remote reception to local applications while keeping transport and output choices explicit.
SAT>IP servers and tuner sources
Transport and virtual tuners
DVB adapters · RTSP · HTTP · SRT
Linux applications and operator workflows
Platforms
Deployments can run on bare metal and supported virtualized Linux environments, including Proxmox and LXC, with the network and adapter permissions required by the chosen design.
Manual
This deployment sequence keeps reception, transport, access and operational acceptance in one technical plan.
Document each SAT>IP server, the routed network path and the local applications that need tuner capacity. Automatic discovery should not be assumed across routed networks.
Define the remote tuners explicitly and choose TCP or UDP independently for each connection. The right transport depends on the network and the behavior of the remote server.
Choose the virtual DVB-adapter and redistribution workflow required by the consuming Linux applications. Confirm device permissions and virtualization constraints for bare metal, Proxmox or LXC.
Use RTSP, HTTP or SRT according to the consumer and path. For SRT, choose whether to deliver a service, a PID list or a complete transponder instead of moving more data than the workflow requires.
Restrict operator access, authentication and management APIs to the intended network. Separate operational metadata and control from any public-facing delivery path.
Test source acquisition, signal reporting, virtual-adapter behavior, output stability and recovery with representative traffic. Record the working source and transport choices for ongoing operation.
Support
Ask about compatibility, access, troubleshooting or deployment requirements.
Downloads
Public packages appear in the download centre. Customer-specific releases require an authorized account.
