This article defines the concepts and objects in RMS live streaming. Understanding these terms will help you work effectively with the RMS API when building integrations or troubleshooting live streaming workflows.
| Name | Description |
| Live event |
A It creates an input endpoint that receives the live signal using a specified ingest protocol (RTMP, SRT, or RTSP). The ingest protocol and encoding type are set at creation and cannot be changed afterward - changing these settings requires deleting the live event and creating a new one. Attempting to modify For encoding type, passthrough events forward the single-bitrate stream from the encoder directly to packaging without transcoding. ABR (Adaptive Bitrate) events transcode the incoming stream into multiple quality levels for adaptive playback. See also: Live streaming quickstart, Live events API reference. |
| Asset |
An In live workflows, a The recorded asset persists even after the See also: Assets API reference, RMS Console: Media Asset upload. |
| Live output |
A It enables viewers to seek backward during the If you delete a See also: Live outputs API reference. |
| Streaming locator |
A It connects the asset to a To build a playback URL, combine the See also: Streaming locators API reference, RMS Concepts - Streaming Locators. |
| Streaming endpoint |
A RMS provides one built-in streaming endpoint per account for handling all content delivery through dynamic, just-in-time packaging. Creating additional endpoints is not supported. See also: Streaming Origin Endpoint: Best practices, CDN and custom domains in RMS. |
| Player clients |
Client applications that play back HLS or DASH streams delivered by RMS. RMS works with any standards-compliant video player, including browser-based libraries like hls.js, Shaka Player, and Video.js, as well as native players on mobile and desktop platforms. RMS also provides the Ravnur Player, which is optimized and tested for adaptive bitrate streaming and low-latency playback with RMS streams. See also: Ravnur Player, Configuring Ravnur Player for low latency live streaming. |
| DVR |
DVR (Digital Video Recording) allows viewers to rewind and time-shift during a live event by retaining recent media segments in the manifest window. When DVR is enabled, RMS continuously writes the live stream into an The default DVR window is 12 hours and is configurable in RMS Console. |
| Post-event encoding |
Post-event VOD encoding applies A live recording is not automatically re-encoded after the event ends - encoding is optional and only required when the archived stream does not already meet your playback or distribution requirements. See also: Transforms API reference, Jobs API reference. |
| RMS Console |
RMS Console is a web-based interface for managing RMS live events without calling the API directly. It provides common workflows such as creating live events, obtaining ingest URLs, starting and stopping streams, and accessing recordings. The RMS Console provides a subset of RMS API capabilities intended for common tasks and monitoring. See also: RMS Console: Start guide, RMS Console: API Key Management. |