This 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 publishing" in some cases.
The pull (LVB playback) video source is generated in real time. It is only meaningful if someone pushes a live stream. Once the host stops streaming, the LVB 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.
It refers to the domain name used to push live streams, which is required. It must be registered and get an ICP filing before you can use the LVB service. After a push domain name is configured, LVB will generate the corresponding push address.
It refers to the domain name used to play back live streams, which is required. It must be registered and get an ICP filing before you can use the LVB service. After a playback domain name is configured, LVB will generate the corresponding playback address.
A CNAME domain name is a domain name suffixed with
.liveplay.myqcloud.com that is assigned by the system to the connected acceleration domain name configured in the LVB Console. You need to configure a CNAME record at your domain name service provider. After the record takes effect, LVB will take care of domain name resolution, and all requests made to this domain name will be forwarded to the edge servers of LVB.
StreamName is the ID of a stream, which is usually used to uniquely identify the stream together with a domain name.
AppName is an LVB application name used to identify the storage path of a live streaming media file. It is
live by default and customizable.
Transcoding is an offline task that converts a video bitstream. It changes parameters of the source bitstream, such as codec, resolution, and bitrate, to adapt it to different devices and network conditions. The following benefits can be achieved with transcoding:
It refers to the process where an event notification is triggered by a live stream during push, Tencent Cloud proactively 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, a JSON packet containing the callback information can be obtained for parsing and information logging.
It refers to the
txSecret field in the push and playback URLs, which can prevent attackers from forging your backend for push URL generation or stealing your playback address for illegal profit.
During the push, video files generated by muxing original streams (without modifying such information 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.
To avoid your video copyright from being infringed during LVB push, you can add a configured watermark to the video stream during transcoding to output a watermarked video stream. The watermark can be either text or image.
You can capture screenshots of videos in a pushed live stream at a fixed interval and store the generated image files into COS. To enable the screencapturing feature, you must first grant LVB the permission to write to your COS bucket. For more information, please see Granting LVB Access to COS Bucket for Screenshot Storage.
Based on the screencapturing feature, the system can identify whether a host are presenting non-compliant live content in LVB push based on the screencapturing and porn detection template associated with the push domain name. For more information, please see Screencapturing and Porn Detection Configuration.