Live Media Core

Make every live source ready for its destination.

Receive live streams by push or pull, then relay, transcode, or convert them into the protocols and profiles required by each destination. Send the resulting stream to CloudTV services, your CDN, or another platform without building a separate media server.

Discuss your live workflow Explore common workflows
Connect either way
Push input, pull source, push output, or live pull address
Process per output
Relay, convert, or transcode only where required
CloudTV PlatformLive route control
Routes · Sources · Processing · Outputs · Health
Input
  • Standard push
  • RXT-accelerated push
  • Pull sources
ProcessLive Media Core
  • Relay
  • Transcode
  • Protocol conversion
Output
  • Push to a destination
  • Provide a live pull address
  • Send to a CDN
Route activePer-output processingHealth monitored

Real-world workflows

Turn the live source you have into the output your workflow needs.

Live systems do not always speak the same protocol, accept the same media profile, or connect in the same direction. Live Media Core sits between the source and destination and performs only the processing required by each output route.

01 · Protocol mismatch

Connect systems that use different streaming protocols.

When the source and destination cannot connect directly.

A camera may provide RTSP while a meeting application expects WebRTC. A broadcast source may deliver MPEG-TS while a downstream service expects HLS, fMP4, or another playback protocol. Even when the audio and video are already compatible, the two systems may still be unable to exchange the live stream.

Live Media Core accepts the source by push or pull, changes the protocol or container when the media tracks are compatible, and then pushes the result to its destination or provides a live address for a downstream system to pull.

Best suited to Video meetings, camera monitoring services, broadcast feeds moving to internet delivery, and integrations between streaming platforms.
  1. Source push or pull
  2. Live Media Core
  3. Protocol conversion
  4. Required output protocol
  5. Destination or pull endpoint
02 · Consistent outputs

Standardize mixed sources into consistent output profiles.

When several sources arrive with different media settings.

Live inputs may use different codecs, resolutions, bitrates, frame rates, or audio settings, while the platform, CDN, or player expects a consistent output. A high-bitrate source may also need lower-bitrate versions for different viewers and network conditions.

Live Media Core can transcode and normalize each source into one or more output profiles. Codec, resolution, bitrate, frame rate, audio, and other media settings are selected independently for each output.

Best suited to Broadcasters, live-stream aggregators, online education and meeting services, and operations that need several bitrate or resolution profiles from one source.
Mixed live sources

H.264 · 1080pH.265 · 4KVP9 · 720p

Transcode and normalize
  • 1080p · 6 Mbps
  • 720p · 3 Mbps
  • 480p · 1 Mbps
03 · Multi-destination relay

Relay one stream to multiple destinations.

When one encoder should not maintain every downstream connection.

One live event may need to reach several platforms, CDNs, partners, or regional systems at the same time. Those destinations may require different protocols, media profiles, and target addresses.

Push the source once, or let Live Media Core pull it once. Each output route then maintains its own destination, protocol, processing mode, and media profile without making the source encoder manage every remote connection.

Best suited to Simultaneous TikTok and YouTube publishing, broadcast syndication, live events, remote production, and workflows that use several CDNs or partner systems.
One pushed or pulled sourceLive Media Core
  • Destination platform
  • Customer or third-party CDN
  • Partner server
  • Additional output route
04 · Downstream pull

Provide a live output for downstream systems to pull.

When the destination expects to retrieve the stream itself.

A CDN, partner, or customer-operated system may require a stable pull address, while the original device can only push or cannot provide a publicly reachable live endpoint.

Live Media Core receives the source and exposes a continuous live output that the downstream system can pull. The address represents a live relay or processing route; it does not mean CloudTV stores source video files or maintains a video-on-demand media library.

Best suited to CDN origin pull, partner distribution, customer-operated delivery systems, and services that do not operate a separate live media server.
  1. Source push or pull
  2. Live Media Core
  3. Continuous live output address
  4. Downstream CDN, platform, or partner pulls

Ingest and output

Connect the source and destination in the direction each one expects.

Live Media Core accepts pushed streams, pulls from existing sources, pushes to remote destinations, and provides live outputs for players, CDNs, and downstream systems to pull. The available route depends on the media tracks, output protocol, processing mode, and customer configuration.

Push input

Push into Live Media Core.

  • RTMP / RTMPS
  • RTSP / RTSPS
  • SRT
  • WebRTC / WHIP
  • HTTP / HTTPS MPEG-TS ingest
  • MPEG-TS over TCP
  • MPEG-TS over UDP unicast or multicast
  • RTP over UDP
  • RTP over TCP
  • RTP over HTTP
  • RTP multicast
  • RTP carrying ES, PS, TS or EHOME
  • RTSP-TS
  • RTP-TS
  • GB28181
Pull input

Pull from an existing source.

  • RTMP / RTMPS
  • RTMPT / RTMPTS
  • RTSP / RTSPS
  • SRT
  • WebRTC / WHEP
  • HLS with MPEG-TS segments
  • HLS with fMP4 segments
  • Encrypted HLS
  • DASH
  • HTTP / HTTPS FLV
  • HTTP / HTTPS MPEG-TS
  • HTTP / HTTPS fMP4
  • MPEG-TS over TCP
  • MPEG-TS over UDP unicast or multicast
  • RTP over UDP or TCP
  • RTP multicast
  • RTSP-TS
  • RTP-TS
  • GB28181 active pull
  • MMS / MMSH / MMST
  • Icecast / SHOUTcast audio streams
Push output

Push to a destination.

Live Media Core establishes and maintains the outbound connection.

  • RTMP / RTMPS
  • RTSP / RTSPS
  • SRT
  • WebRTC / WHIP
  • MPEG-TS over TCP
  • MPEG-TS over UDP unicast or multicast
  • RTP over UDP
  • RTP over TCP
  • RTP multicast
  • RTP carrying ES, PS, TS or EHOME
  • GB28181
Pull / playback output

Provide an output for downstream pull or playback.

The player, CDN, or downstream system initiates the connection.

  • RTSP / RTSPS
  • RTMP / RTMPS
  • SRT
  • WebRTC / WHEP
  • HLS with MPEG-TS segments
  • HLS with fMP4 segments
  • Encrypted HLS
  • DASH
  • DASH with DRM when Rights Protection is enabled
  • HTTP / HTTPS FLV
  • WebSocket / Secure WebSocket FLV
  • HTTP / HTTPS MPEG-TS
  • WebSocket / Secure WebSocket MPEG-TS
  • HTTP / HTTPS fMP4
  • WebSocket / Secure WebSocket fMP4

CloudTV RXT is an accelerated transport path, not a media protocol. Encrypted HLS and DASH with DRM require the corresponding Rights Protection configuration. Protocol availability depends on media compatibility and the processing selected for the route.

Live Media Core processes live routes. CloudTV does not provide video file hosting or maintain a customer video-on-demand media library.

Live processing paths

Process each output only as much as it needs.

A single live input can feed several independent outputs. Keep one route unchanged, convert another to a different protocol, and transcode a third into the codec or profile required by its destination.

Live inputPush or pullTrack and compatibility inspection
Relay

Keep the original media when no conversion is required.

Relay compatible audio, video, and additional tracks without unnecessary decoding or re-encoding. This reduces processing delay, avoids unnecessary quality loss, and uses fewer compute resources. The route can push to a destination or provide a live pull address.

Protocol conversion

Change how the stream is delivered without changing the media itself.

Compatible tracks can be repackaged into another streaming protocol or container without a full transcode.

  • RTSP → HLS
  • RTMP → HTTP-FLV
  • MPEG-TS → fMP4
  • RTSP with compatible tracks → WebRTC
Transcode

Create the media profile required by each destination.

Change video or audio codecs, resolution, bitrate, frame rate, audio settings, or filters. One input can produce several independent output profiles, using software or hardware acceleration as configured.

Input exampleRTMP · H.264/AAC · 1080p
One input · independent decisions per output
Live Media Core
YouTubeRTMP · Original profileRelay
WebRTC application720p · Lower bitrateTranscode
Customer CDNHLS / fMP4Protocol conversion
DestinationOutput protocolProcessing modeCodec and profilePush or pull

Route continuity

Recover the source without restarting playback.

Live Media Core keeps the downstream route alive while an upstream publisher reconnects or a fallback source takes over. Viewers remain connected to the same playback address without client-side source switching or a new playback session.

Downstream route retained
Upstream reconnect

Keep the route while the publisher reconnects.

A temporary upstream disconnect does not require the downstream workflow to be rebuilt. The publisher can reconnect to the same live route within its configured continuity window while existing viewers remain attached to the same playback address.

  1. Upstream publisher
  2. Temporary disconnect
  3. Live route retained
  4. Publisher reconnects

The continuity window and fallback sources are configured for each route. Source recovery preserves the downstream route, but it does not promise that every frame survives an upstream or network interruption.

Independent outputs

One destination can recover without stopping the others.

Each output maintains its own destination, protocol, processing mode, connection, and health state. A failure or reconnect on one output does not require the source or other healthy outputs to restart.

  • Output A Healthy
  • Output B Reconnecting
  • Output C Healthy
On-demand processing

Use processing resources only while a route needs them.

Pulling, protocol conversion, and transcoding can remain inactive until a viewer or configured output makes the route active. This reduces CPU and GPU use for live routes with no current consumer or downstream output.

No active route Inactive

Viewer or output active Processing

Native live engine

Built for sustained live-stream processing.

The native C++ engine uses asynchronous network I/O and multi-threaded processing for sustained streaming traffic, concurrent live routes, and multi-track audio, video, and subtitle handling.

  • Native C++ media processing
  • Asynchronous network I/O
  • Multi-threaded live processing
  • Multi-track handling

Codec and track handling

Keep compatible tracks. Transcode only when the output requires it.

Codec compatibility is evaluated for each output route. Compatible tracks can be relayed or repackaged without re-encoding, while incompatible tracks can be transcoded into the profile required by the selected output protocol.

Broad protocol-conversion support

Common media tracks that can be relayed or converted across a broad range of live protocols when the route is compatible.

Video

  • H.264 / AVC
  • H.265 / HEVC
  • VP8
  • VP9
  • AV1

Audio

  • AAC
  • Opus
  • G.711 A-law / μ-law
  • MP3
Additional passthrough or transcoding support

Additional codecs the commercial media core can preserve or transcode when the selected route supports them.

Video

  • H.266 / VVC
  • MPEG-2 Video
  • MJPEG / JPEG
  • SVAC

Audio

  • MP2
  • G.722
  • G.722.1
  • G.723
  • G.726
  • G.729
  • ADPCM

These codec groups describe processing support, not universal compatibility with every output protocol. The result for a route also depends on its input container, output protocol, track combination, and required media profile.

Route explainer

See why an output is relayed, converted, or transcoded.

This explainer illustrates common processing decisions. The exact route is validated against its complete media and output configuration.

Likely processing pathProtocol conversion

The media codec can be preserved while the live stream is repackaged for HLS.

Per-output transcode controls

Video codec · Audio codec · Resolution · Video bitrate · Frame rate · Audio bitrate · Sample rate · Channel layout · Filters · Software or hardware acceleration

Multi-track handling

Preserve the tracks the selected output can carry.

Compatible output formats can preserve multiple audio, video, and subtitle tracks. When Live Subtitles is enabled, generated subtitle tracks join the same live processing route as an optional product.

  • Multiple video tracks
  • Multiple audio tracks
  • Subtitle tracks

Fit your existing stack

Connect Live Media Core to the systems you already use.

Keep your encoder, destination platforms, CDN, and playback applications. Live Media Core handles only the ingest, relay, conversion, or transcoding stages enabled for each route.

SourceYour sourceStandard push or pull · Optional CloudTV RXT
ProcessLive Media CoreIngest · Relay · Protocol conversion · Transcoding
Existing deliveryYour CDN, platform, or destinationKeep the player and downstream systems already in place

Global Edge CDN is not required. Live Media Core can deliver processed streams directly to a customer-operated or third-party system.

CloudTV PlatformSourcesRoutesProcessingOutputsHealthUsage
Before ingestResilient TransportRXT-accelerated publishing or source transfer During processingLive SubtitlesSpeech recognition and multilingual subtitle tracks Before deliveryRights ProtectionEncrypted HLS · DASH with DRM · Invisible watermarking DeliveryGlobal Edge CDNGlobal live-stream distribution ApplicationsNative SDK & ApplicationsPlayback integration · RXT endpoints · Generated or custom apps OperationsBusiness ManagementContent · Packages · Plans · Subscriptions · Customers · Devices

CloudTV Platform manages the shared configuration, routing, health, and usage for every enabled route. Business Management supports the business side of the service and does not sit in the live media path. Standard protocols remain available without Native SDK & Applications. Optional products are not required processing steps.

Map the live route

Tell us what the source sends and what the destination expects.

Share the source protocols, codecs, destinations, output profiles, and whether each route should be relayed, converted, or transcoded. We can help map the right workflow through Live Media Core.

Discuss your live workflow