XSDK MEDIA ORCHESTRATION REFERENCE ARCHITECTURE

One media network.
Multiple node roles.

Compose video and audio workflows from XFlow, XCore AV and XNetwork.

Run them inside your application, as a standalone local process, or as a network of Media Nodes across hosts.

[ STATUS ] xMedia Next is currently in architecture redesign. The Flow-based XSDK foundation is available today through XFlow, XCore AV, XNetwork and the Flow Relay reference application.
ARCHITECTURE

One media network, clear roles at every node

DISTRIBUTED WORKFLOW ILLUSTRATIVE ARCHITECTURE XRegistry Discovery / resource visibility Media Node HOST A Capture Process Encode Mux Network output LOCAL BRANCH Preview Each node runs its own programmable media graph. Media Node HOST B Network input Demux Decode Convert Playout Receive, decode and output media. DEVICE OUTPUT DIRECT MEDIA Node to node over a suitable transport Commands / Configuration Status / Telemetry Logs / Events Commands / Configuration Status / Telemetry Logs / Events Web / Desktop / Automation Node control and status APIs AI Agents PLANNED Workflow control and orchestration Designed for AI-agent orchestration: planned workflow control with status, telemetry, logs and events as runtime feedback.

Every Media Node needs the same core capabilities: device I/O, codecs, routing, buffering, network transport, remote control and lifecycle management. Those capabilities already exist inside XFlow, XCore AV and XNetwork. The hard part is coordinating them into a predictable workflow — inside one node, and across a network of them.

xMedia is the orchestration layer built to do that.

01
Compose instead of rebuild.
One Flow-based graph replaces separate application and media-processing topologies. XFlow owns composition, routing, lifecycle, queues and backpressure — inside a single node.
02
Use media-native building blocks.
Decode, encode, convert, capture, playout and work with media containers through XCore AV, so the workflow layer does not need to invent another codec or device abstraction.
03
Connect without coupling to transport.
XNetwork handles discovery, Registry, RPC, signaling and physical connectivity between nodes — independent of whether a connection uses a local path, SRT, UDP, WebRTC or another supported transport.
DEPLOYMENT

One processing model. Three deployment options.

01
Embedded

Run workflows directly inside your product or application.

02
Local

Run a workflow as a standalone process on a single host.

03
Distributed

Connect media nodes across hosts using media and control channels.

INSIDE EVERY NODE

xMedia sits above the stack, not inside it

LAYER
XFlow
Composition and runtime behavior: graph topology, routing, bounded queues, fan-out/fan-in, lifecycle, backpressure.
LAYER
XCore AV
Media semantics and processing: formats, packets and frames, codecs, conversion, mux/demux, capture, playout.
LAYER
XNetwork
Connectivity and control: discovery, XRegistry, RPC, signaling, sessions, transports.
ORCHESTRATOR
xMedia
Application-level media intent: reusable workflows that coordinate the lower layers without duplicating them.

Applications can use XFlow, XCore AV and XNetwork directly for low-level control. xMedia adds a workflow surface for operations that would otherwise require repetitive orchestration, such as selecting a source, starting processing, creating a preview, starting a recording, maintaining a time-shift window and publishing the resource for remote consumers to attach to. It reuses the same underlying objects and lifecycle rather than introducing a second media engine.

Build the media product you need

Live production
Capture once. Create multiple outputs.
Input
Process
Playout
Preview
Record

For applications that combine real-time device I/O, processing and multiple delivery paths inside one controlled graph. Typical fit: broadcast tools, production appliances, channel systems, OEM video products.

Recording and time-shift
Turn live media into a bounded, seekable workflow.
Live source
Encode / mux
Rolling window
Live edge
Delayed playback

Build recorder and PVR-style applications without treating storage as an unrelated subsystem.

Remote media nodes
Discover a node first. Connect to it second.
Media Node
XRegistry
Direct Media

Useful when sources and processing nodes live on different hosts, networks or sites. See the full node topology in the architecture section above.

Browser and operator workflows
One control model, native and remote.

Expose media-system state and application operations through remote APIs instead of building a second control model for the UI. The native application lifecycle stays authoritative.

Browser / Operator UI
Native application
remote API · state stays authoritative on the native side
LIVE STATUS
WHAT EXISTS TODAY

We're validating the workflow pieces before introducing the next xMedia contract

Media I/O
DeckLink capture DeckLink playout File input
Processing
H.264 decode Conversion Transcoding Encode MPEG-TS mux/demux
Recording
File recording Bounded PVR / time-shift Delayed clip generation
Application
Real XFlow graph lifecycle Typed configure/start/status/stop Remote XNetwork RPC control Registry building blocks

We're stabilizing the lower layers before freezing the new high-level xMedia contract. That avoids duplicated abstractions and lets the future workflow API build on capabilities we've already proven independently. A stable public xMedia Next contract and release date haven't been announced yet.

Primary integration reference XSDK Flow Relay
REFERENCE APPLICATION

Meet XSDK Flow Relay

Flow Relay is the reference application used to assemble and validate the Flow-based media stack. Run real media pipelines, inspect the architecture and see how XFlow, XCore AV and XNetwork fit together before xMedia adds the higher-level workflow abstraction.