xMedia SDK — Layer 02
xMediaStreams is a high-level runtime built on top of xMedia Core. It shifts the development model from composing handler graphs to working with structured stream objects — streams, groups, feeds, processors, and sinks.
Use Cases
xMediaStreams handles the workflows where structure and reliability matter. These are the scenarios it is designed to solve — not as extensions, but as first-class supported patterns.
Core Model
xMediaStreams introduces a structured object model on top of the handler layer. Every source, processing step, and output is a first-class runtime object — with defined lifecycle, time semantics, and a stable public interface. You no longer wire handlers together; you configure streams and let the runtime manage the rest.
Applications built against xMediaStreams interfaces remain stable as the underlying xMedia Core pipeline evolves. The abstraction boundary is intentional and maintained across releases.
Runtime objects
Interfaces
Workflow Model
xMediaStreams connects sources to outputs through a structured three-stage pipeline. Each stage has a defined role, clear API boundaries, and predictable behavior in production.
Readiness
xMediaStreams is the most stable and complete layer of the xMedia SDK. The core runtime model is defined, the public interfaces are stable, and the layer is actively used in real workflow integrations. This is the recommended starting point for any new project.
What is available today
Summary
xMediaStreams is not a toolkit of components — it is a runtime with a defined object model. It gives you the structure to build real products: monitoring systems, replay servers, ingest pipelines, and distributed media backends. The abstraction is intentionally high-level: your code describes what the workflow does, not how to wire handlers.