> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/performance-cdn/static-content-delivery/stream-management.md).

# Stream Management

Stream Management allows you to create and manage adaptive bitrate (ABR) stream definitions for live streaming resources. A stream definition combines multiple encoded video renditions into a single logical stream, enabling compatible media players to switch between quality levels automatically based on network conditions and device capabilities.

After a stream is configured, Medianova packages the incoming live stream and delivers it using supported adaptive streaming protocols through the global CDN network.

{% hint style="info" %}
Stream Management is available only for live streaming resources configured to receive an RTMP ingest. Before creating a stream, ensure that your streaming resource is active and your encoder is configured to publish to the assigned RTMP endpoint.
{% endhint %}

A stream definition represents a live channel and contains one or more quality profiles. Each profile corresponds to a different encoded bitrate or resolution of the same live stream.

When a viewer starts playback, the media player retrieves the stream manifest and automatically selects the most appropriate rendition based on available bandwidth and playback conditions.

Typical use cases include:

* Live television
* Sports broadcasting
* Webcasts and webinars
* OTT platforms
* Corporate live events

### How Stream Management Works

The following workflow describes how a live stream is processed and delivered.

1. A live encoder publishes the stream using RTMP.
2. Medianova receives the incoming stream through the configured ingest endpoint.
3. Stream Management associates the incoming stream with the configured stream definition.
4. Medianova packages the stream into adaptive streaming formats.
5. Manifest files and media segments are generated.
6. The CDN caches and delivers the content from edge locations to viewers.

The CDN distributes streaming content but does not perform video encoding. Video encoding and bitrate generation are completed by the encoder before the stream reaches the CDN.

### Supported Streaming Protocols

Stream Management supports multiple streaming protocols to provide compatibility across different playback environments. While live streams are ingested using RTMP, viewers receive adaptive HTTP-based streams through one or more playback protocols.

| Protocol                                | Purpose                             | Typical Usage                                                            |
| --------------------------------------- | ----------------------------------- | ------------------------------------------------------------------------ |
| **HLS (HTTP Live Streaming)**           | Primary adaptive streaming protocol | Apple devices, Safari, Smart TVs, OTT platforms, and most modern players |
| **MPEG-DASH**                           | Standards-based adaptive streaming  | Web browsers, Android devices, Smart TVs, and OTT applications           |
| **Microsoft Smooth Streaming**          | Legacy adaptive streaming protocol  | Legacy Microsoft streaming environments                                  |
| **RTMP (Real-Time Messaging Protocol)** | Live stream ingest                  | Used by encoders to publish live streams to Medianova                    |
| **HDS (HTTP Dynamic Streaming)**        | Legacy Adobe streaming protocol     | Legacy Adobe Flash-based deployments                                     |

#### Protocol Roles

Streaming protocols serve different purposes throughout the delivery workflow.

* **RTMP** is used only to ingest the live stream from the encoder.
* **HLS**, **MPEG-DASH**, and **Smooth Streaming** are generated from the incoming stream and delivered to viewers.
* **HDS** is available only for legacy compatibility.

This architecture allows a single live stream to be delivered simultaneously using multiple playback protocols without requiring multiple encoder outputs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://clients.medianova.com/products/performance-cdn/static-content-delivery/stream-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.