The TXLivePusher SDK is mainly used to publish streams for LEB (ultra-low latency streaming). It can publish audio and video the browser captures from the camera, screen, or a local media file to live streaming servers via WebRTC.
Note：
With WebRTC, each domain name can be used for the publishing of up to concurrent 100 streams by default. If you want to publish more streams, please submit a ticket.
Basics
Below are some basics you need to know before integrating the SDK.
Splicing publishing URLs
To use Tencent Cloud live streaming services, you need to splice publishing URLs in the format required by Tencent Cloud, which consists of four parts.
An authentication key is not required. You can enable publishing authentication if you need hotlink protection. For details, please see Splicing CSS URLs.
Browser support
Publishing for LEB relies on WebRTC and therefore can only be used on OS and browsers that support WebRTC.
The audio/video capturing feature is poorly supported on mobile browsers. For example, mobile browsers do not support screen recording, and only iOS 14.3 and above allow requesting camera access. Therefore, the publishing SDK is mainly used on desktop browsers. The latest version of Chrome, Firefox, and Safari all support publishing for LEB.
To publish streams on mobile browsers, use the MLVB SDK.
SDK Integration
Step 1. Prepare the page
Add an initialization script to the (desktop) page from which streams are to be published.
The script needs to be imported into the body part of the HTML code. If it is imported into the head part, an error will be reported.
Step 2. Add a container to the HTML page
Add a player container to the section of the page where local video is to be played. This is achieved by adding a div and giving it a name, for example, id_local_video. Local video will be rendered in the container. To adjust the size of the container, style the div using CSS.
1. Generate an instance of the publishing SDK:
Generate an instance of the global object TXLivePusher. All subsequent operations will be performed via the instance.
var livePusher =newTXLivePusher();
2. Specify the local video player container:
Specify the div for the local video player container, which is where audio and video captured by the browser will be rendered.
livePusher.setRenderView('id_local_video');
Note：
The video element generated via setRenderViewis unmuted by default. To mute video, obtain the video element using the code below.
3. Set audio/video quality:
Audio/video quality should be set before capturing. You can specify quality parameters if the default settings do not meet your requirements.
// Set video quality
livePusher.setVideoQuality('720p');// Set audio quality
livePusher.setAudioQuality('standard');// Set the frame rate
livePusher.setProperty('setVideoFPS',25);
4. Capture streams:
You can capture streams from the camera, mic, screen and local media files. If capturing is successful, the player container will start playing the audio/video captured.
// Turn the camera on
livePusher.startCamera();
// Turn the mic on
livePusher.startMicrophone();
5. Publish streams:
Pass in the LEB publishing URL to start publishing streams. For the format of publishing URLs, please see Splicing CSS URLs. You need to replace the prefix rtmp:// with webrtc://.
Before publishing, make sure that audio/video streams are captured successfully, or you will fail to call the publishing API. You can use the code below to publish streams automatically after audio/video is captured, that is, after the callback for capturing the first audio or video frame is received. If both audio and video are captured, publishing starts only after both the callback for capturing the first audio frame and that for the first video frame are received.
The SDK provides a static method to check whether a browser supports WebRTC.
TXLivePusher.checkSupport().then(function(data){
// Whether WebRTC is supported
if(data.isWebRTCSupported){
console.log('WebRTC Support');
}else{
console.log('WebRTC Not Support');
}
// Whether H.264 is supported
if(data.isH264EncodeSupported){
console.log('H264 Encode Support');
}else{
console.log('H264 Encode Not Support');
}
});
Event callbacks
The SDK supports callback event notifications. You can set an observer to receive callbacks of the SDK’s status and WebRTC-related statistics. For details, see TXLivePusherObserver.
livePusher.setObserver({
// Warnings for publishing
onWarning:function(code, msg){
console.log(code, msg);
},
// Publishing status
onPushStatusUpdate:function(status, msg){
console.log(status, msg);
},
// Publishing statistics
onStatisticsUpdate:function(data){
console.log('video fps is '+ data.video.framesPerSecond);
}
});
Device management
You can use a device management instance to get the device list, switch devices, and perform other device-related operations.
var deviceManager = livePusher.getDeviceManager();// Get the device list
deviceManager.getDevicesList().then(function(data){
data.forEach(function(device){
console.log(device.deviceId, device.deviceName);
Yes
No
Was this page helpful?