Publish processed media with a streaming locator using the RMS Console.

The RMS Console converts processed content into streaming-ready formats and generates endpoints for playback. Create streaming locators to connect encoded media to playback endpoints. This enables viewers to access the media.

This page explains how to publish and validate media delivery through the RMS Console.

In this article:

Create a streaming locator

Retrieve media playback and download URLs

Access playback URLs

Download URLs

Understand content key policies

Validate playback & Troubleshoot issues

Validate media playback

Troubleshoot publishing issues

Before you begin

• Set up your RMS Console usage environment
• Upload media assets into the storage
• Process media to create an output asset

If you skip processing the media and create a Streaming Locator for input assets (instead of output assets), playback URLs will not be generated.

Create a streaming locator

Streaming locators generate access points to your media content. They provide a bridge between your stored media asset and the streaming endpoints. Locators are secure paths for content distribution. By generating streaming locators, you transform processed media assets into playable content.

Steps to сreate a streaming locator:

1. Open the output Asset Details page.

2. Click one of the buttons to add a new streaming locator:

• Create locator on the top right corner
• button next to Streaming locators

3. Complete the fields in the form that appears:

• Name: Use the auto-generated name (locator_{timestamp}) or enter a custom name.

• Streaming policy: select from available options based on distribution needs, see Understand content key policies.
• Content key policy: select if using encryption such as ClearKey or DRM (Digital Rights Management) policies.
• Expiration time (optional): set when the streaming URLs should stop working. After that, the media will not play until a new locator is created.
• Streaming locator ID (optional): customize ID formatted as GUIDs if you need a specific locator ID.

4. Click Add.

After creating a locator, it immediately appears in the Streaming locators list. Multiple locators can be created for a single asset to support different access policies. You may switch between locators for playback using the Select streaming locator dropdown.

Retrieve media playback and download URLs

Access playback URLs

You can access streaming URLs using the Show URLs button.

The URLs are a pathway for media distribution that combines three essential components:

• Streaming endpoint hostname {rms-hostname}: this is your Streaming endpoint hostname which can be found in Account Settings > Streaming endpoints:

• Locator ID {locator-id}: a unique identifier for the access path, generated when you create a streaming locator.
• Asset Name {asset-name}: a distributed media asset.

When these components are composed in the URL structures for DASH (Dynamic Adaptive Streaming over HTTP) and HLS (HTTP Live Streaming), they manifest your media content.

Structure of Dash URL:

https://{rms-hostname}/{locator-id}/{asset-name}.ism/manifest(format=mpd-time-cmaf)

Structure of HLS URL:

https://{rms-hostname}/{locator-id}/{asset-name}.ism/manifest(format=m3u8-cmaf)

Download URLs

URLs are available for individual asset blobs in the Streaming URLs window.

Download URLs for individual asset blobs are available with these policies::

• Predefined_DownloadAndClearStreaming
• Predefined_DownloadOnly

Understand content key policies

Known limitations

The RMS Console interface has the following limitations:

• Custom streaming policies cannot be added
• Locator filtering is not available
• Once created, locators cannot be deleted

Workaround: find step-by-step API guides for deleting locators and locator filtering. Custom streaming policies can be added via an API request or backend configuration logicAPI requests as well.

Validate playback & Troubleshoot issues

Validate media playback

To confirm successful media publishing:

1. Verify the streaming locator has generated playback URLs.

2. Check that the media plays correctly in the RMS Console Player.

3. Optionally, test playback using standard HLS and DASH-compatible external players.

Troubleshoot publishing issues

Encountering issues? Here are common troubleshooting steps to resolve playback problems:

Missing URLs

• Ensure you created the Streaming Locator on the output asset. Locators on input assets don’t generate playback URLs

No playback

If you're using a custom-built preset and experiencing no playback:

• Verify that the output asset blob contains media files.

• Review the job processing history for any errors. Troubleshoot and reprocess the media if there are job failures.

Contact us

If you've exhausted these troubleshooting steps and still cannot resolve the issue, contact Ravnur.