tencent cloud

Cloud Streaming Services

Release Notes and Announcements
Announcements
User Guide
Product Introduction
Overview
CSS Products
Concepts
Features
Use Cases
Strengths
Use Limits
Purchase Guide
Billing Overview
Basic Service Fee
Value-Added Service Fee
Prepaid plan
Purchase Process
Changing Billing Modes
Refund Policy
Viewing Bills
Renewal
Processing for Overdue Payments
Billing FAQs
Live Video Broadcasting (LVB)
Overview
Use Cases
Getting Started
SDK Integration
Live Event Broadcasting (LEB)
Overview
LEB Versus LVB
Use Cases
Getting Started
SDK Integration
Live Video Caster
Overview
Application Scenarios
Feature Area Introduction
Managing Live Video Caster
General Cloud Director
Configuring Program Lists and Automated Broadcasting
Console Guide
Console Overview
Overview
Domain Management
Stream Management
Package Management
AI Features
Feature Configuration
Relay
Billing Usage Statistics
Monitoring
Toolkit
OOTB live
CAM-Based Access Control
Feature Guide
Push and Playback
Features
Practices in Typical Scenarios
Cloud Native Recording
Live Streaming Security
Global CSS Service
Callback Notifications
User Guides for Common Third-Party Tools
SDK Guide
0. SDK Integration Guide
1. Stream Push
2. Playback
3. Advanced Features
API Documentation
History
Introduction
API Category
Making API Requests
Live Pad APIs
Live Stream Mix APIs
Time Shifting APIs
Monitoring Data Query APIs
Billing Data Query APIs
Live Transcoding APIs
Delayed Playback Management APIs
Domain Name Management APIs
Watermark Management APIs
Certificate Management APIs
Stream Pulling APIs
Recording Management APIs
Live Callback APIs
Screencapturing and Porn Detection APIs
Authentication Management APIs
Live Stream Management APIs
Data Types
Error Codes
Ops Guide
Video Stuttering
Troubleshooting Push Failure
Troubleshooting Playback Failure
CLS Assists in Live Stream Troubleshooting
Troubleshooting High Latency
Troubleshooting Poor Quality of Pulled Video
Authorizing CSS to Store Screenshots in a COS Bucket
Troubleshooting
Live Stream Mixing Error `InvalidParameter.OtherError`
About Pushing
Generating Push URLs
PC Push
Playing Method
Web Player
Live Streaming Quiz
FAQs
Service Region
Live Streaming Basics
Push and Playback
CSS Billing
Global CSS Service
Live Recording
On-Cloud Stream Mix
Domain Configuration
Related to Live Video Caster
Compatibility with Apple ATS
Difference Between Stream Interruption and Stream Suspension
SLA
CSS Service Level Agreement
CSS Policy
Privacy Policy
Data Processing And Security Agreement
Glossary

SDK Integration

PDF
Focus Mode
Font Size
Last updated: 2024-09-18 21:45:51
As a lower-latency version of LVB, LEB provides superb live streaming experience with millisecond playback latency, far lower than that of live stream playback using traditional protocols. Before you use LEB, please read LEB Billing Overview to learn about its billable items and pricing.
Note:
LEB uses the WebRTC protocol to ensure low latency. It adopts the Opus codec and does not support B-frames. If the original stream contains B-frames or the codec is not Opus, the CSS backend will remove the B-frames and transcode the stream to Opus format, which will incur standard transcoding fees.

Integration into Application

Directions

You can integrate the MLVB SDK into your iOS or Android application to implement the live push and playback features.
Live push: Capture from the camera or phone screen and push the stream to CSS using the RTMP protocol. For details, see Publishing (Camera) and Publishing (Screen Recording).
Live playback: Play streams using WebRTC with ultra-low latency. For details, see Playback > LEB.
Note:
The MLVB SDK leverages the capabilities of CSS, IM, TRTC, and other services to implement low-latency audio/video communication for multiple parties, allowing participants to interact with each other while others watch. For details, see Mic Connect.

Free demo

TCToolkit is an open-source and comprehensive audio/video solution developed by Tencent Cloud. You can use it to try out LEB’s capability to play live streams with millisecond latency.
Platform
Demo
Push Demonstration (Android)
Playback Demonstration (Android)
Android












iOS
Under maintenance

Integration into Webpage

Directions

You can use the following ways to achieve live push and playback on your websites:
Live push on web: The push component is designed and packaged according to the WebRTC standard, which is supported by most browsers. You can enable the live push feature simply by importing the code we provide. For details, see WebRTC Push.
Note:
The Opus audio codec is used for the push of WebRTC streams. Therefore, if you use an LVB protocol (RTMP, HTTP-FLV, or HLS) for playback, the CSS backend will automatically convert the audio to AAC format to ensure successful playback, which will incur audio transcoding fees. For details, see Live Transcoding > Audio Transcoding. If you publish and play streams using the LEB protocol, CSS will not transcode the audio.
With WebRTC, each push domain can be used for up to 1,000 concurrent streams by default. If you want to push more streams, please submit a ticket.
Live playback on web: We recommend you use our web player SDK TCPlayerLite, which supports playing WebRTC streams on mobile and desktop browsers and delivers a superb streaming experience with millisecond latency, far lower than that of playback using traditional live streaming protocols.
Note:
If a browser does not support WebRTC, a WebRTC URL passed into the player will be converted to better support playback. By default, WebRTC is converted to HLS on mobile browsers and HTTP-FLV on desktop browsers.

Free demo

Live push on web: You can test the web push feature in Web Push of the CSS console.



Live playback on web: You can use the TCPlayer demo to test playback on web.
Note:
Both live push and playback on web use the standard WebRTC protocol. Web push does not generate B-frames, and audio is encoded in Opus format, so there will be no costs of audio transcoding or B-frame removal.

Implementing WebRTC Push Using OBS

LEB (ultra-low-latency live streaming) uses WebRTC to push live audio/video or video files to the CSS server. The following describes how to use OBS to push WebRTC streams.
OBS supports WebRTC protocol live streaming, which means you can easily and quickly push live streams to Tencent Cloud CSS using the WebRTC protocol on PC (Windows/Mac/Ubuntu), just like using the RTMP protocol. The following content mainly introduces how to use the OBS tool to implement WebRTC protocol live streaming functionality.
Note:
There are two schemes, new and old, to choose from when integrating OBS with WebRTC protocol live streaming:
New Scheme - OBS WebRTC Live Streaming (OBS v30.0 Beta 1 or higher): This scheme does not require a plugin, making the integration process more convenient. For specific operation guidance, please refer to:OBS WebRTC live streaming.
Old Scheme - Using OBS Plugin for WebRTC Live Streaming: If you are using an OBS version lower than v30.0 Beta 1 and cannot directly use the WebRTC protocol for live streaming, Tencent Cloud CSS provides an integrated OBS plugin solution for WebRTC live streaming. For specific operation guidance, please refer to: OBS Plugin for WebRTC Live Streaming.
Based on your actual requirements and OBS version, you can choose the appropriate WebRTC live streaming solution. Please note that the actual streaming performance may be affected by factors such as device performance, network conditions, and player buffering. During the usage process, you can adjust the streaming parameters and tools according to your needs to optimize the live streaming experience.

LEB playback

For how to use the MLVB SDK for LEB playback, see Playback > (LEB).

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback