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

Concepts

PDF
Focus Mode
Font Size
Last updated: 2024-07-30 17:07:34

Push

Refers to the process in which the host pushes local video and audio sources to Tencent Video Cloud servers. It is also known as "RTMP push" in some cases.

Playback

Refers to live playback in which the source video and audio are pulled from the Tencent Video Cloud servers and played back at the specified address after live push is implemented. The video source is generated in real time. It is only meaningful if someone pushes a live stream. Once the host stops streaming, the live streaming URL will become invalid, and since the live streams are played back in real time, no progress bar will be displayed on the player during the playback.

Push domain name

The domain name used to push live streams, which is a required setting. You must register the domain name before you can use it for live streaming. After a push domain name is configured, CSS will generate the corresponding push URL. For details, see Splicing Live Stream URLs.

Playback domain name

The domain name used to play back live streams, which is a required setting. You must register the domain name before you can use it for live streaming. After a playback domain name is configured, CSS will generate the corresponding playback URL. For details, see Splicing Live Stream URLs.

Domain CNAME

A domain name that is suffixed with .liveplay.myqcloud.com and is assigned by the system to the acceleration domain name configured in the CSS console. You need to configure a CNAME record with your domain name service provider. After the record takes effect, CSS will be responsible for the domain name resolution, and all requests made to this domain name will be forwarded to the edge servers of CSS.

StreamName

The ID of a stream. StreamName and the domain name together are used to uniquely identify a stream.

AppName

The live streaming application name used to identify the storage path of a live streaming media file. The application name is live by default and is customizable.

Transcoding

Transcoding is an offline task that converts one video bitstream into another. It changes the codec, resolution, bitrate, and other parameters of the bitstream for playback on different devices in varying network environments. This feature can achieve the following:
Increase compatibility: Transcode a source video to formats that are compatible with multiple types of devices for smooth playback.
Increase bandwidth adaptability: Transcode a source video to outputs in Smooth, SD, HD, and UHD. End users can select the bitrates as needed for their network conditions.
Reduce bandwidth usage: Use advanced codecs for transcoding to substantially reduce the bitrate of a video with the original quality retained, thus lowering the payback bandwidth usage.

H.264

A codec standard for highly-compressed digital video. H.264 is developed by ITU-T Video Coding Experts Group (VCEG) and ISO/IEC Moving Picture Experts Group (MPEG). It has the following advantages in transcoding:
It allows SD digital image (at a resolution below 1280 x 720) to transfer at a speed below 1 Mbps.
It delivers better image quality than other video codecs under the same bandwidth.

H.265

H.265 is optimized based on the H.264 video codec while still having some of the same features as H.264. It has the following advantages in transcoding:
It allows general HD audio/video (720p at a resolution of 1280 x 720) to be transferred at 1-2 Mbps.
It achieves the optimal balance between the bitstream, encoding quality, latency, and algorithm complexity.

Event message notification

When an event notification is triggered during a live push, Tencent Cloud sends the request to your server according to the configured message template, and your server authenticates and responds to the request. For more information on the response protocol, please see Event Message Notification Protocol. After the authentication is passed, your server will obtain a JSON packet containing the callback information to parse and record.

Referer

The txSecret field in the push and playback URLs. Referer is used to prevent attackers from forging your backend to generate push URLs and from stealing your playback URLs.

Live recording

During the push, video files generated by muxing original streams (without modifying information such as audio and video data and corresponding timestamps) can be stored on the VOD platform. To use this feature, you need to activate VOD first.

Watermark

To avoid your video copyright from being infringed during live push, you can add a watermark to the video stream during transcoding. The watermark can be either text or an image.

Screencapture

This feature captures video images of pushed live streams at specified intervals and then stores generated image files in COS. To enable screencapture, you must first grant CSS the permission to write to your COS bucket. For more information, see Authorizing CSS to Store Screenshots in a COS Bucket.

95th percentile bandwidth

During the billing period, the peak bandwidth every 5 minutes is taken as a sample point. All sample points of the current month are sorted in descending order, and the top 5% are removed. The highest value of the remaining sample points is used as the 95th percentile of the monthly peak bandwidth.


Help and Support

Was this page helpful?

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

Feedback