Cloud Slicer Live allows you to run a slicer in our cloud. This allows you to ingest and encode content without on-premise hardware. You may customize this slicer in the following ways:
Create and delete slicers as required by your business needs.
Set up a streaming workflow by performing the following steps:
Create an ingest pointAn ingest point identifies the URL and ports at which a CSL slicer may ingest your audio/video feed. in the region where your CSL slicer will be hosted.
The purpose of an ingest point is to persist your ingest URLs even when switching to a different CSL slicer. This means that you will not have to update your encoder's publishing configuration when switching to a different CSL slicer.
An ingest point identifies a URL and ports to which an encoder should push an audio / video feed.
Upon creating a CSL slicer, you must associate it with an ingest point from which it will ingest an audio / video feed.
Key information:
An ingest point can be in either of the following states:
To modify an ingest point
You may not reassign an ingest point to a different region. Create an ingest point if you require one for a different region.
To delete an ingest point
Check the ingest point's status.
Before creating a CSL slicer, you must first perform the following steps:
Identify the streaming protocol through which your feed will be published to a CSL slicer. A CSL slicer supports the following protocols:
The SRT streaming protocol requires slicer version 22060200 or higher.
Key information:
You may import settings from a file. We support the following formats:
Text File: You may import a file that uses the same format as a Live Slicer configuration file. Specify each desired setting on a separate line.
JSON: You may import a file that contains settings defined as key-value pairs using JSON notation.
To create a CSL slicer
From the Ingest Point section, select an ingest point that corresponds to the region where this slicer will be hosted and the streaming protocol for the feed that it will ingest.
RTP, SRT, and RIST
In the Source IP Address option, type the IP address from which your feed will be pushed. Our service will only ingest feeds served from this IP address.
Allow your feed to be pushed from any IP address by setting this option to 0.0.0.0.
Regardless of how this setting is configured, the encoder pushing the feed to our service must authenticate to our service by passing the CSL slicer's streaming key.
Learn more.
From the Slicer Software Version section, assign a slicer software version to the CSL slicer.
Select the desired slicer version.
If this CSL slicer's ingest point uses the SRT streaming protocol, then you must select slicer version 22060200 or higher.
Optional. From the Encoding Profile section, select the encoding profile that will be assigned to the CSL slicer.
Optional. From the Slicer Configuration section, import, add, or remove Slicer settings to your slicer configuration.
Define this slicer's ID through the slicerID setting.
From the Import Mode option, choose one of the following options:
Appending or prepending slicer configuration settings may result in duplicate settings. It is strongly recommended to avoid duplicate settings by immediately removing them from your slicer's configuration.
Add a setting by performing the following steps:
Clicking + Custom.
Alternatively, add a commonly used setting by clicking + Standard instead.
To modify a CSL slicer
Update this CSL slicer as needed.
Optional. From the Slicer Configuration section, review your slicer configuration. Import, add, or remove Slicer settings as needed.
Define this slicer's ID through the slicerID setting.
From the Import Mode option, choose one of the following options:
Appending or prepending slicer configuration settings may result in duplicate settings. It is strongly recommended to avoid duplicate settings by immediately removing them from your slicer's configuration.
Add a setting by performing the following steps:
Clicking + Custom.
Alternatively, add a commonly used setting by clicking + Standard instead.
Select the desired slicer version.
Changes to your CSL slicer's slicer configuration require restarting your CSL slicer. Restart your CSL slicer.
If you modified the CSL slicer's slicer version, then we will automatically restart the CSL slicer. No further action is required to apply changes to your CSL slicer's slicer configuration.
To delete a CSL slicer
Restarting a CSL slicer typically takes around 60 seconds.
Use a CSL slicer's status to find out whether it is ready to stream your content. Core CSL slicer statuses are described below.
You may not use the following settings with a CSL slicer:
You may import a slicer configuration file when defining your CSL slicer's slicer configuration. You may format this slicer configuration file using either colon-separated values or JSON.
You may not define a reserved slicer configuration setting within a slicer configuration file. Attempting to import a file that contains a reserved setting will generate an error.
Our service automatically detects the format when importing your slicer configuration file. It does not rely on the file extension when making this assessment.
You may define slicer configuration settings using the same format as a Live Slicer configuration file. Specify each desired setting on a separate line.
Syntax:
Example:
remote:on
description:Sports
input:rtmp
autoexpire_age:3
slicerID:sports_slicer
You may define slicer configuration settings using JSON format. Define each slicer configuration setting as a key-value pair using JSON notation.
Syntax:
Example:
{ "remote": "on", "description": "Sports", "input": "rtmp", "autoexpire_age": "3", "slicerID": "sports_slicer" }
Your encoder must push an audio / video feed to an ingest point. If you have assigned that ingest point to a CSL slicer, then that CSL slicer will automatically encode your content.
Our service will only ingest your feed when the following conditions are met:
Your encoder is configured to push an audio / feed to the CSL slicer's streaming URL.
Sample publishing URL:
RTP, SRT, and RIST
Your encoder's IP address matches the one defined in the ingest point's Source IP Address option.
You may bypass this restriction and allow your feed to be pushed from any IP address when this option is set to 0.0.0.0.
You must configure your encoder to pass the CSL slicer's streaming key along with your feed. This configuration varies by encoder. If your encoder does not provide a password option when defining a SRT publishing target, then you should include the passphrase query string parameter in the publishing URL.
Syntax:
You can find this streaming key by viewing the desired CSL slicer's Streaming Information section.
Sample publishing URL:
A link is established when an encoder starts pushing an audio / video feed to an ingest point. CSL slicer performance relies on this link and therefore we track key link health metrics. These metrics are measured by:
View these metrics from within the Link Monitor section of the desired CSL slicer.
Link health metrics are described below.
Name | Description |
---|---|
Round Trip Time |
Indicates the round trip time between the encoder and the CSL slicer in milliseconds. |
Link Uptime |
Indicates the duration, in hours, for the connection between the encoder and the CSL slicer. |
Latency Setting |
Indicates the length of time, in milliseconds, that the CSL slicer will wait before processing data packets. This delay provides time for packet correction to take place. |
Stream Bitrate |
Indicates the rate, in Kbps, at which data is being transferred from the encoder to the CSL slicer. |
Packets Inbound |
Indicates the number of data packets received by the CSL slicer. |
Packets Outbound |
Indicates the number of data packets sent to the encoder by the CSL slicer. |
Percent Link Success |
Indicates the percentage of data packets that were successfully received by the CSL slicer. |
Packets Errored |
Indicates the number of data packets that were not successfully delivered. |
Percent Errored |
Indicates the percentage of data packets that resulted in an error. |
Packets FEC Corrected |
Indicates the number of data packets that were successfully delivered after being corrected by Forward Error Correction (FEC). |
Percent Fixed by FEC |
Indicates the percentage of data packets that were successfully delivered after being corrected by Forward Error Correction (FEC). |
Packets ARQ Corrected |
Indicates the number of data packets that were successfully delivered as a result of automatic repeat request (ARQ). |
Percent Fixed by ARQ |
Indicates the percentage of data packets that were successfully delivered as a result of automatic repeat request (ARQ). |
ARQ Requests |
Indicates the number of requests that triggered ARQ. |
ARQ Fails |
Indicates the number of requests that were unsuccessful after triggering ARQ. |
Percent Failed ARQ |
Indicates the percentage of requests that were unsuccessful after triggering ARQ. |