After pushing a stream successfully, you can use the address generator of the CSS console to generate a playback URL (you need to enter the StreamName, which should be the same as the stream ID in the push URL).
1. Select Domain Management on the left sidebar and click the name of your playback domain or click Manage on the right.
2. Select Playback Configuration and, in Playback Address Generator, complete the following settings:
2.1 Select the type of stream to play, which can be the original stream, the transcoded stream, or adaptive bitrate streams. If you select Transcoded stream, you need to specify a transcoding template. If you select Adaptive bitrate streams, you need to specify an adaptive bitrate template.
2.2 Enter the StreamName, such as liveteststream. Make sure it’s the same as the StreamName in your push URL.
2.3 After you select an adaptive bitrate template, the names of the streams in the template will be listed in descending order by bitrate.
2.4 Select an expiration time, such as 2023-09-01 19:00:00.
3. Click Generate Address.
4. If you haven’t enabled authentication for your playback domain, in the Playback URL area on the same page, you can find playback URLs for RTMP, FLV, HLS, and UDP. Replace StreamName in the URLs with the stream ID in your push URL, and you can use the URLs to play the stream.
AppName: The live streaming application name, which is live by default and is customizable.
StreamName: The stream ID, which uniquely identifies a stream and is customizable.
txSecret: The authentication string generated after playback authentication is enabled.
txTime: The expiration timestamp of the playback URL configured in the console.
Note:
If you have enabled authentication, the actual expiration time of a URL will be txTime plus the validity period of the authentication key.
For the sake of convenience, the console allows you to specify the URL expiration time in human-readable format. If you enable authentication, when generating playback URLs, the system will convert it to a hex timestamp (the value of txTime).
As long as you start push or playback before the expiration time and the stream is not interrupted, the push or playback can continue even after the URL expires.
Playback URL for the transcoded stream
If a transcoding template is bound to your playback domain, and you want to play the transcoded stream, you need to append the template name (_transcoding template name) to the original playback URL.
For example, if the original playback URL is http://domain/AppName/StreamName.flv?txSecret=Md5(key+StreamName+hex(time))&txTime=hex(time) and the name of the transcoding template bound is hd, the playback URL of the transcoded stream would be http://domain/AppName/StreamName_hd.flv?txSecret=Md5(key+StreamName_hd+hex(time))&txTime=hex(time).
Adaptive bitrate playback URL
Only HLS and WebRTC are supported for adaptive bitrate playback. The URL formats for the two protocols are different.
To get an HLS adaptive bitrate URL, add the template name (_adaptive bitrate template name) after StreamName of the original playback URL.
For example, suppose the original playback URL is http://domain/AppName/StreamName.m3u8?txSecret=Md5(key+StreamName+hex(time))&txTime=hex(time) and the name of the adaptive bitrate template bound is autobitrate.
The HLS adaptive bitrate URL would be http://domain/AppName/StreamName_autobitrate.m3u8?txSecret=Md5(key+StreamName_autobitrate+hex(time))&txTime=hex(time).
The format of a WebRTC adaptive bitrate URL is ：
Playback domain (domain) + Application name (AppName, which is live by default), Stream ID (StreamName) + Authentication information + Adaptive bitrate stream names + Name of the initially played stream + Bitrate control mode.
Note:
The adaptive stream names are listed in descending order by bitrate.
Suppose the adaptive bitrate template bound has three streams. Their names are "test 1", "test 2", and "test 3", and their bitrates are 200 Kbps, 300 Kbps, and 400 Kbps respectively.The WebRTC adaptive bitrate URL would be:
CSS supports pushing and playing H.265 streams. If the original stream is an H.264 stream, you can configure a transcoding template to transcode it into an H.265 stream. For details about how to do this in the console or by calling an API, see Live Remuxing and Transcoding.
Yes
No
Was this page helpful?