This document describes how to get started with LEB. Before trying out LEB, you’re advised to read the Pricing Overview of LEB to get familiar with its billable items and prices.
- After the CSS service is activated, 20 GB of playback traffic for use in the Chinese mainland will be gifted.
- The steps to configure domain names for LEB are the same as those for LVB. If you have activated LVB, you can get started with LEB from Step 4. Get a playback URL.
To use CSS, you should have at least one push domain name, and one playback domain name. You cannot use one domain name for both push and playback.
You can add your own domain names.
Prepare your own domain names. For domain names in Chinese mainland regions, ICP filing is required.
Log in to the CSS console and enter Domain Management.
Click Add Domain.
- CSS provides a test domain name
xxxx.livepush.myqcloud.com. You can use it to test live push, but you're not advised to use it as the push domain name for business purposes.
- After the domain name is added successfully, you can view its information in the domain name list in Domain Management. For how to manage it, see Domain Management.
- For more information on live streaming domain names, please see Basic CSS Features.
Once your domain name is added, the system will assign it a CNAME domain name (suffixed with
.tlivepush.com), which cannot be accessed before you complete the CNAME configuration at your DNS service provider. After the CNAME configuration takes effect, you can use CSS. The following example shows you how to add a CNAME record by assuming Tencent Cloud is your DNS service provider:
- After a CNAME record is successfully added, it takes some time for the CNAME configuration to take effect. If the configuration fails, you cannot use CSS.
- After the CNAME configuration succeeds, you can see that the status symbol of the CNAME address in Domain Management in the CSS console has changed to .
- If the CNAME configuration failure persists, consult your DNS service provider.
- For more information on how to configure with other DNS service providers, see Configuring CNAME for Domain Name.
StreamName, such as
- In the push URL,
liveis the default
txSecretis the signature for playing back the stream, and
txTimeis the URL expiration time.
- Here is another way to generate a push URL: In Domain Management, find the push domain name you want use to generate a push URL, click Manage, select Push Configuration, enter an expiration time for the address and a custom
StreamName, and click Generate Push Address.
- You can create and configure a desired feature template before generating the push URL based on your business needs and bind it to the push domain name. For prices of CSS value-added features, see Pricing Overview.
You can enter the generated push URL into the push software as appropriate for your use cases.
StreamName, select a URL expiration time, turn the camera on, and click Start Push.
StreamNamein the push URL to play back the corresponding stream.
- WebRTC Live Demo supports the multi-definition feature. You can configure transcoding templates for HD and SD in Feature Configuration > Live Transcoding in the CSS console, enter a WebRTC stream address containing a transcoding template, test it, and then play it back. (If you don't need to test this feature, simply enter a WebRTC original stream in the demo.)
- For more information on live transcoding operations and billing, see CSS Transcoding.
LEB solution for mobile devices: supports B-frame decoding and AAC audio codec. This solution is integrated into the MLVB SDK. For how to use it, see LEB Playback.
The format of LEB playback URL is the same as that of LVB playback URL except that the former starts with
webrtc while the latter starts with
LEB playback URL format:
webrtc://domain/path/stream_id?txSecret=xxx&txTime=xxx (hotlink protection enabled). For how to generate a playback URL, please see Get playback URL.
You can also pull transcoded streams of different resolutions and bitrates. For information about generating playback URLs for transcoded streams, please see Live Remuxing and Transcoding.
The LEB solution for web does not support decoding and playing back B-frames. If the original stream contains B-frames, the backend will remove them by transcoding, which will result in latency and incur transcoding fees. We recommend not pushing streams with B-frames. You can also adjust the video codec parameter on push client software (such as OBS) to remove B-frames. If you use OBS for push, you can set to disable B-frames, as shown below:
Playback by web browser only supports standard WebRTC protocol and does not support AAC audio codec. If you push streams with audio in AAC format, the audio will be transcoded into Opus format, which will incur audio transcoding fees.