tencent cloud



Last updated: 2023-09-27 11:28:11

    Ear Monitor-related Issues

    In Karaoke scenarios, ear monitoring is likely to be used. How can I enable the ear monitoring function?


    What if there is no effect after enabling the ear monitoring function?

    Due to the high hardware latency of Bluetooth headsets, please try to prompt the host to wear wired headphones on the user interface. At the same time, please note that not all phones can achieve excellent ear monitoring effects after enabling this feature. The TRTC SDK has already blocked this effect on some phones with poor ear monitoring performance.

    Is the ear monitoring latency too high?

    Please check if you are using a Bluetooth headset. Due to the high hardware latency of Bluetooth headsets, please try to use wired headphones as much as possible.
    In addition, you can try to improve the high latency of ear monitoring by enabling hardware ear monitoring through the experimental interface setSystemAudioKitEnabled. Currently, for Huawei and Vivo devices, the SDK uses hardware ear monitoring by default, while other devices use software ear monitoring by default.
    // Enable hardware ear monitoring
    mTRTCCloud.callExperimentalAPI("{\\"api\\":\\"setSystemAudioKitEnabled\\", \\"params\\": {\\"enable\\":1}}");

    NTP Time Synchronization Issues

    Reminder: “NTP time sync finished, but result maybe inaccurate”?

    NTP time synchronization is successful, but the deviation may be more than 30ms, reflecting poor client network environment and continuous rtt jitter.

    Reminder: “Error in AddressResolver: No address associated with hostname”?

    NTP time synchronization failure may be due to temporary anomalies in the local carrier DNS resolution under the current network environment. Please try again later.

    NTP service retry processing logic?


    Network Speed Test Recommendations

    Online Karaoke scenarios have high network requirements for users, especially real-time chorus. A high-quality and stable network environment is necessary for a good Karaoke experience. Therefore, it is recommended to perform a network speed test on the user before entering the room, and give a UI layer reminder to users who do not meet the network requirements, prohibiting them from joining the Karaoke room or participating in chorus.
    Initiating network speed test with TRTC SDK:
    TRTCCloudDef.TRTCSpeedTestParams speedTestParams = new TRTCCloudDef.TRTCSpeedTestParams();
    speedTestParams.sdkAppId = SDK_APP_ID;
    speedTestParams.userId = userId;
    speedTestParams.userSig = userSig;
    // If the actual bandwidth is higher than the expected value, the test result is the expected value;
    // if the actual bandwidth is lower than the expected value, the test result is the actual bandwidth value.
    speedTestParams.expectedDownBandwidth = 3000; // Expected downstream bandwidth, ranging from 10 to 5000 kbps
    speedTestParams.expectedUpBandwidth = 3000; // Expected upstream bandwidth, ranging from 10 to 5000 kbps
    Expected upstream bandwidth, ranging from 10 to 5000 kbps
    Please perform the network speed test before entering the room. Network speed testing in the room will affect the normal audio and video transmission effects, and due to too much interference, the network speed test results will also be inaccurate.
    TRTC SDK network speed test result callback:
    public void onSpeedTestResult(TRTCCloudDef.TRTCSpeedTestResult result) {
    String tquality = "Unknown";
    switch (result.quality) {
    case 0:
    tquality = "Unknown";
    case 1:
    tquality = "The current network is very good";
    case 2:
    tquality = "The current network is good";
    case 3:
    tquality = "The current network is average";
    case 4:
    tquality = "The current network is poor";
    case 5:
    tquality = "The current network is very poor";
    case 6:
    tquality = "The current network does not meet TRTC's minimum requirements";
    if (result.success) {
    mTextTestResult.append("Speed test successful!" + "\\n");
    mTextTestResult.append("IP address: " + result.ip + "\\n");
    mTextTestResult.append("Uplink packet loss rate: " + result.upLostRate + "\\n");
    mTextTestResult.append("Downlink packet loss rate: " + result.downLostRate + "\\n");
    mTextTestResult.append("Network latency: " + result.rtt + "ms\\n");
    mTextTestResult.append("Downlink bandwidth: " + result.availableDownBandwidth + "kbps\\n");
    mTextTestResult.append("Uplink bandwidth: " + result.availableUpBandwidth + "kbps\\n");
    mTextTestResult.append("Network quality: " + tquality + "\\n");
    } else {
    mTextTestResult.append("Speed test failed!" + "\\n");
    mTextTestResult.append("Error message: " + result.errMsg + "\\n");

    Joining a Chorus Midway

    The real-time chorus solution theoretically has no limit on the number of chorus participants, supporting multiple people to participate in the chorus simultaneously, as well as joining the chorus midway.
    The following are the key actions for joining a chorus midway:
    NTP time synchronization
    Enable chorus experimental interface
    Enter the room and start streaming on the microphone
    Receive chorus signaling, obtain accompaniment resources and chorus agreed time
    Calculate the difference between the agreed time and the current time, preload and seek accompaniment
    Start participating in the chorus and synchronize accompaniment progress and lyrics progress in real-time
    For the specific implementation process and code implementation of the above key actions, please refer to the documentation onsong synchronization, lyrics synchronization, vocal synchronization.
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support