TRTC supports four room entry modes. Video call (VideoCall) and audio call (VoiceCall) are the call modes, and interactive video streaming (Live) and interactive audio streaming (VoiceChatRoom) are the live streaming modes.
The call modes allow a maximum of 300 users in each TRTC room, and up to 50 of them can speak at the same time. The call modes are suitable for scenarios such as one-to-one video calls, video conferencing with up to 300 participants, online medical consultation, remote interviews, video customer service, and online Werewolf playing.
How It Works
TRTC services use two types of server nodes: access servers and proxy servers.
Access server
This type of nodes use high-quality lines and high-performance servers and are better suited to drive low-latency end-to-end calls, but the unit cost is relatively high.
Proxy server
This type of servers use mediocre lines and average-performance servers and are better suited to power high-concurrency stream pulling and playback. The unit cost is relatively low.
In the call modes, all users in a TRTC room are assigned to access servers and are in the role of “anchor”. This means the users can speak to each other at any point during the call (up to 50 users can send data at the same time). This makes the call modes suitable for use cases such as online conferencing, but the number of users in each room is capped at 300.
Sample Code
You can obtain the sample code used in this document at GitHub.
Directions
Step 1. Run the official SimpleDemo
We recommend that you read Demo Quick Start > Electron first and follow the instructions to run the official SimpleDemo.
If you run SimpleDemo successfully, then you know how to install Electron in your project.
If not, there may be a problem in the download or installation process. Try troubleshooting the problem by following the instructions in Electron's installation document.
Step 2. Integrate trtc-electron-sdk into your project
If you can run SimpleDemo successfully, then you know how to set up the Electron environment.
You can develop your project based on the demo we provide to get started quickly.
You can also run the following command to install trtc-electron-sdk in your project.
npminstall trtc-electron-sdk --save
Step 3. Initialize an SDK instance and configure event callbacks
1. Create a trtc-electron-sdk instance:
import TRTCCloud from'trtc-electron-sdk';
let trtcCloud =newTRTCCloud();
2. Listen for the onError event:
// Error events must be listened for and captured, and error messages should be sent to users.
letonError=function(err){
console.error(err);
};
trtcCloud.on('onError',onError);
Step 4. Assemble the room entry parameter TRTCParams
When calling the enterRoom() API, you need to pass in a key parameter TRTCParams, which includes the following required fields:
Parameter
Type
Description
Example
sdkAppId
Number
Application ID, which can be found in Application Management > Application Info in the console
1400000123
userId
String
Can contain only letters (a-z and A-Z), digits (0-9), underscores, and hyphens. We recommend you set it based on your business account system.
test_user_001
userSig
String
userSig is calculated based on userId. For the calculation method, see UserSig.
eJyrVareCeYrSy1SslI...
roomId
Number
Numeric room ID. For string-type room ID, use strRoomId in TRTCParams.
29834
import{
TRTCParams,
TRTCRoleType
}from"trtc-electron-sdk/liteav/trtc_define";
let param =newTRTCParams();
param.sdkAppId =1400000123;
param.roomId =29834;
param.userId ='test_user_001';
param.userSig ='eJyrVareCeYrSy1SslI...';
Note:
In TRTC, users with the same userId cannot be in the same room at the same time as it will cause a conflict.
The value of appScene must be the same on each client. Inconsistent appScene may cause unexpected problems.
Step 5. Create and enter a room
1. Call enterRoom() to enter the room specified by the roomId field in TRTCParams. If the room does not exist, the SDK will create a room whose number is the value of roomId.
2. Set the appScene parameter according to your actual application scenario. Inappropriate appScene values may increase stutter or reduce video clarity.
For video calls, set it to TRTCAppScene.TRTCAppSceneVideoCall.
For audio calls, set it to TRTCAppScene.TRTCAppSceneAudioCall.
Note:
For more information about TRTCAppScene, see TRTCAppScene .
3. You will receive the onEnterRoom(result) callback. If result is greater than 0, room entry succeeds, and the value of result indicates the time (ms) room entry takes; if result is less than 0, room entry fails, and the value is the error code for the failure.
The SDK supports two subscription modes: automatic subscription and manual subscription. The former allows instant streaming and is suitable for calls with a small number of participants, while the latter reduces bandwidth usage and is suitable for conferences with a large number of participants.
Automatic subscription (recommended)
After room entry, the SDK will automatically pull audio streams from other users in the room. This enables instant streaming.
1. If other users in the room are sending audio data, you will receive the onUserAudioAvailable() notification, and the SDK will play their audio automatically.
3. If a remote user in the room is sending video data, you will receive the onUserVideoAvailable() notification, but since the SDK has not received instructions on how to display the video, it will not process the video data. You need to call startRemoteView(userId, view, streamType) to associate the remote user’s video data with view.
TRTCVideoFillMode.TRTCVideoFillMode_Fill: aspect fill. The image may be scaled up and cropped, but there are no black bars.
TRTCVideoFillMode.TRTCVideoFillMode_Fit: aspect fit. The image may be scaled down to ensure that it’s displayed in its entirety, and there may be black bars.
5. You can call stopRemoteView(userId) to block the video of a specified userId or stopAllRemoteView() to block the video of all remote users. The SDK will stop pulling the video data of the user(s).
If you do not call startRemoteView() to subscribe to the video stream immediately after receiving the onUserVideoAvailable() callback, the SDK will stop pulling the remote video within 5 seconds.
Manual subscription
You can call setDefaultStreamRecvMode(autoRecvAudio, autoRecvVideo) to switch the SDK to the manual subscription mode. In this mode, the SDK will not pull the audio/video data of other users in the room automatically. You have to start the process manually via APIs.
2. If other users in the room are sending audio data, you will receive the onUserAudioAvailable() notification, and you need to call muteRemoteAudio(userId, false) to manually subscribe to the users’ audio. The SDK will decode and play the audio data received.
3. If a remote user in the room is sending video data, you will receive the onUserVideoAvailable(userId, available) notification, and you need to call startRemoteView(userId, view) to manually subscribe to the user's video data. The SDK will decode and play the video data received.
Step 7. Publish the local stream
1. Call startLocalAudio() to enable mic capturing and encode and publish the audio captured.
2. Call startLocalPreview() to enable camera capturing and encode and publish the video captured.
TRTCVideoFillMode.TRTCVideoFillMode_Fill: aspect fill. The image may be scaled up and cropped, but there are no black bars
TRTCVideoFillMode.TRTCVideoFillMode_Fit: aspect fit. The image may be scaled down to ensure that it’s displayed in its entirety, and there may be black bars.
Call exitRoom() to exit the room. The SDK disables and releases devices such as cameras and mics during room exit. Therefore, room exit is not an instant process. It completes only after the onExitRoom() callback is received.
// Please wait for the `onExitRoom` event callback after calling the room exit API.
letonExitRoom=function(reason){
console.log(`onExitRoom, reason: ${reason}`);
};
trtcCloud.exitRoom();
trtcCloud.on('onExitRoom', onExitRoom);
Note:
If your Electron application integrates multiple audio/video SDKs, please wait after you receive the onExitRoom callback to start other SDKs; otherwise the device busy error may occur.
Yes
No
Was this page helpful?