@tencent-rtc/mcp 1.3.8 → 1.4.0

package/resource/doc/rtcengine/web/plugin/34-advanced-proxy.md

@@ -29,7 +29,7 @@ trtc.on(TRTC.EVENT.ERROR, error => {
   // User network firewall restrictions may cause audio and video calls to fail.
   // At this time, guide users to change networks or check network firewall settings.
   if (error.code === TRTC.ERROR_CODE.OPERATION_FAILED && error.extraCode === 5501) {
-    
+
   }
 });
 ```
@@ -44,7 +44,7 @@ trtc.on(TRTC.EVENT.ERROR, error => {
 | B        | Users can only access an internal proxy server on the network    | The proxy server is deployed on the internal network, and the internal network firewall needs to open a whitelist to allow the internal proxy server to access the external network.   |
 
 <div style="display: flex;justify-content: center;">
-  <img src="./assets/proxy-1.png"/>
+
 </div>
 
   <div style="display: flex;justify-content: center;">
@@ -52,7 +52,7 @@ trtc.on(TRTC.EVENT.ERROR, error => {
   </div>
 
 <div style="display: flex;justify-content: center;">
-	<img src="./assets/proxy-2.png" />
+
 </div>
 
 <div style="display: flex;justify-content: center;">Example of Solution 2-B</div>
@@ -62,7 +62,7 @@ trtc.on(TRTC.EVENT.ERROR, error => {
 After you have set up Nginx and Turn server, you can refer to the following example to set up a proxy server.
 
 ```javascript
-const trtc = TRTC.create(); 
+const trtc = TRTC.create();
 
 await trtc.enterRoom({
   ...,
@@ -72,7 +72,7 @@ await trtc.enterRoom({
     // Set up a turn server to relay media data packets between the SDK and the TRTC backend. 14.3.3.3:3478 is the IP address and port of the turn server.
     turnServer: { url: '14.3.3.3:3478', username: 'turn', credential: 'turn', credentialType: 'password' },
     // By default, the SDK will connect to trtc server directly, if connection failed, then SDK will try to connect the TURN server to relay the media data. You can set 'relay' to force the connection through the TURN server.
-    iceTransportPolicy: 'all', 
+    iceTransportPolicy: 'all',
     // By default, the SDK reports logs to the yun.tim.qq.com domain name. If this domain name cannot be accessed in your internal network, you need to whitelist the domain name or configure the following log proxy.
     // Set up a log reporting proxy. Logs are key data for troubleshooting, so be sure to set up this proxy.
     loggerProxy: 'https://proxy.example.com/logger/',
@@ -91,38 +91,36 @@ await trtc.enterRoom({
 2. Configure Nginx server
 
    ```sh
-   vi /etc/nginx/nginx.conf 
+   vi /etc/nginx/nginx.conf
    ```
 
    ```
    http {
-     server { 
+     server {
        # The access domain name of the Nginx server
-       server_name proxy.example.com; 
+       server_name proxy.example.com;
        # The access port of the Nginx server
-       listen 443; 
-   
-       ssl on; 
-   
+       listen 443;
+
+       ssl on;
+
        location /ws/ { # Corresponding to the websocketProxy parameter in setProxyServer
          proxy_pass https://signaling.rtc.qq.com/; # TRTC server
-         proxy_http_version 1.1; 
-         proxy_set_header Upgrade $http_upgrade; 
-         proxy_set_header Connection "upgrade"; 
+         proxy_http_version 1.1;
+         proxy_set_header Upgrade $http_upgrade;
+         proxy_set_header Connection "upgrade";
        }
        location /logger/ { # Corresponding to the loggerProxy parameter in setProxyServer
          proxy_pass https://yun.tim.qq.com/;
        }
-   
+
        # SSL certificate corresponding to the domain name, used for HTTPS, users need to apply for it themselves
-       ssl_certificate ./crt/1_proxy.trtcapi.com_bundle.crt; 
-       ssl_certificate_key ./crt/2_proxy.trtcapi.com.key; 
+       ssl_certificate ./crt/1_proxy.trtcapi.com_bundle.crt;
+       ssl_certificate_key ./crt/2_proxy.trtcapi.com.key;
      }
    }
 ```
 
-
-
 3. Reload Nginx
 
    ```sh
@@ -137,47 +135,46 @@ You can search for turn server setup tutorials on the Internet for setup, or you
 
 1. Create a script file `turn.sh` in the Linux server, and the script content is as follows:
 
-
    ```sh
    #!/usr/bin/env bash
-   
+
    # current file name is turn.sh
-   
+
    # ref:
    # https://gabrieltanner.org/blog/turn-server    STEP 3 testing turn server
    # https://medium.com/av-transcode/what-is-webrtc-and-how-to-setup-stun-turn-server-for-webrtc-communication-63314728b9d0
-   
+
    # as super-user
    # usage:  current_program <external-ip>
-   
+
    set -x
    set -e
-   
+
    ip a
    pwd
    whoami
-   
+
    display_usage() {
            echo "This script must be run with super-user privileges."
            echo -e "\nUsage: $0 <external-ip> \ne.g. $0 154.8.246.205"
    }
-   
+
    # if less than two arguments supplied, display usage
    if [ $# -lt 1 ]
    then
            display_usage
            exit 1
    fi
-   
+
    if [[ $1 =~ ^[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
      echo "get external ip $1"
    else
      echo "wrong external ip $1 , must not have whitespace, tab and other char"
      exit 2
    fi
-   
+
    yum install -y coturn
-   
+
    # $1 is <external-ip>
    cat <<EOF > /etc/coturn/turnserver.conf
    external-ip=$1
@@ -209,10 +206,10 @@ You can search for turn server setup tutorials on the Internet for setup, or you
 
    ```sh
    systemctl start coturn
-   
+
    # Check if turn is started successfully
    ps aux | grep coturn
-   
+
    # If you want to restart the service, execute
    service coturn restart 
    ```
@@ -225,9 +222,6 @@ You can search for turn server setup tutorials on the Internet for setup, or you
 
    Use this [test page](https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/) to test whether the turn server is accessible. If the result shows "done" as shown in the screenshot below, the turn server is working properly.
 
-   <img src="./assets/turn-test.png" alt="turn-test" style="zoom: 33%;" />
-
-
 ### Solution 2-B
 
 Solution B builds the Nginx proxy in the same way as Scenario A. There are two main differences:
@@ -245,4 +239,3 @@ sudo . /turn.sh 10.0.0.4
 
 - For the Nginx server, the domain name whitelist needs to be configured in the company's intranet firewall to allow the Nginx server to access TRTC's related domain names. Refer to: [TRTC Web SDK domain and port whitelist](https://trtc.io/document/59667?platform=web&product=rtcengine&menulabel=coresdk)
 - For the Turn Server, allow the Turn Server to access the external network.
-

package/resource/doc/rtcengine/web/plugin/36-advanced-virtual-background.md

@@ -4,7 +4,7 @@ This document will describe how to implement the virtual background feature duri
 
 | Original Camera | Background Blur | Background Image |
 | --- | --- | --- |
-| <img src="https://qcloudimg.tencent-cloud.cn/raw/28a9246a5e1071ea0200bfde6d2b110b.jpg" /> | <img src="https://qcloudimg.tencent-cloud.cn/raw/a605b69b39cea73a6ebfde6324e93fff.jpg" /> | <img src="https://qcloudimg.tencent-cloud.cn/raw/fec848fc9ff4a2b4dbfc49a5f4c2fb3d.jpg" /> |
+|  |  |  |
 
 ## Prerequisites
 
@@ -12,94 +12,18 @@ This document will describe how to implement the virtual background feature duri
 - [TRTC SDK](https://www.npmjs.com/package/trtc-sdk-v5) version must be >= 5.5.0
 - System and configuration requirements for various platforms are as follows:
 
-<table>
-<tr>
-<td rowspan="1" colspan="1">Platform</td>
+| Platform | Operating System | Browser Version | FPS | Recommended Configuration | Remarks |
+| --- | --- | --- | --- | --- | --- |
+| Web | Windows | Chrome 90+<br>Firefox 90+<br>Edge 97+ | 30 | Memory: 16GB<br>CPU: i5-10500<br>GPU: Dedicated 2GB | It is recommended to use the latest version of Chrome browser<br><b> (Enable hardware acceleration in the browser)</b> |
+| 15 | Memory: 8GB<br>CPU: i3-8300<br>GPU: Integrated Intel 1GB |  |  |  |  |
+| Mac | Chrome 98+<br>Firefox 96+<br>Safari 15+ | 30 | 2019 MacBook<br>Memory: 16GB (2667MHz)<br>CPU: i7 (6-core 2.60GHz)<br>GPU: AMD Radeon 5300M |  |  |
+| Android | Chrome<br>Firefox Browser
 
-<td rowspan="1" colspan="1">Operating System</td>
-
-<td rowspan="1" colspan="1">Browser Version</td>
-
-<td rowspan="1" colspan="1">FPS</td>
-
-<td rowspan="1" colspan="1">Recommended Configuration</td>
-
-<td rowspan="1" colspan="1">Remarks</td>
-</tr>
-
-<tr>
-<td rowspan="8" colspan="1">Web</td>
-
-<td rowspan="2" colspan="1">Windows</td>
-
-<td rowspan="2" colspan="1">Chrome 90+<br>Firefox 90+<br>Edge 97+</td>
-
-<td rowspan="1" colspan="1">30</td>
-
-<td rowspan="1" colspan="1">Memory: 16GB<br>CPU: i5-10500<br>GPU: Dedicated 2GB</td>
-
-<td rowspan="3" colspan="1">It is recommended to use the latest version of Chrome browser<br> <b> (Enable hardware acceleration in the browser)</b></td>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="1">15</td>
-
-<td rowspan="1" colspan="1">Memory: 8GB<br>CPU: i3-8300<br>GPU: Integrated Intel 1GB</td>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="1">Mac</td>
-
-<td rowspan="1" colspan="1">Chrome 98+<br>Firefox 96+<br>Safari 15+</td>
-
-<td rowspan="1" colspan="1">30</td>
-
-<td rowspan="1" colspan="1">2019 MacBook<br>Memory: 16GB (2667MHz)<br>CPU: i7 (6-core 2.60GHz)<br>GPU: AMD Radeon 5300M</td>
-</tr>
-
-<tr>
-<td rowspan="3" colspan="1">Android</td>
-
-<td rowspan="3" colspan="1">Chrome<br>Firefox Browser
-
-<td rowspan="1" colspan="1">30</td>
-
-<td rowspan="1" colspan="1">High-end devices (e.g., Qualcomm Snapdragon 8 Gen1)</td>
-
-<td rowspan="3" colspan="1">It is recommended to use Chrome, or Firefox browsers and other mainstream browsers<br>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="1">20</td>
-
-<td rowspan="1" colspan="1">Mid-range devices (e.g., MediaTek Dimensity 8000-MAX)</td>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="1">10</td>
-
-<td rowspan="1" colspan="1">Low-end devices (e.g., Qualcomm Snapdragon 660)</td>
-</tr>
-
-<tr>
-<td rowspan="2" colspan="1">iOS</td>
-
-<td rowspan="2" colspan="1">Chrome<br>Safari<br>Firefox</td>
-
-<td rowspan="1" colspan="1">30</td>
-
-<td rowspan="1" colspan="1">iPhone 13</td>
-
-<td rowspan="2" colspan="1">- Requires iOS 14.4 or above<br>- It is recommended to use Chrome or Safari browsers<br></td>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="1">20</td>
-
-<td rowspan="1" colspan="1">iPhone XR</td>
-</tr>
-
-</table>
+<td rowspan="1" colspan="1">30 | High-end devices (e.g., Qualcomm Snapdragon 8 Gen1) |  |  |  |
+| 20 | Mid-range devices (e.g., MediaTek Dimensity 8000-MAX) |  |  |  |  |
+| 10 | Low-end devices (e.g., Qualcomm Snapdragon 660) |  |  |  |  |
+| iOS | Chrome<br>Safari<br>Firefox | 30 | iPhone 13 | - Requires iOS 14.4 or above<br>- It is recommended to use Chrome or Safari browsers |  |
+| 20 | iPhone XR |  |  |  |  |
 
 ## Implementation Steps
 
@@ -203,7 +127,7 @@ Allows modification of virtual background parameters.
 | Name       | Type     | Attributes | Description                             |
 |------------|----------|------------|-----------------------------------------|
 | type       | `string` | Required   | - `image` for image background <br> - `blur` for background blur |
-| enableFaceCentering (Since v5.11.0)     | `boolean`        | Optional                   |`false`（default） 
+| enableFaceCentering (Since v5.11.0)     | `boolean`        | Optional                   |`false`（default）
 | blurLevel | `number` | Optional | - Set the level of blur when `type` is set to `blur`. Default value is 3, with a range from 1 to 10. |
 | src        | `string` | Required if type is `image`  | Image URL, such as `https://picsum.photos/seed/picsum/200/300` |
 
@@ -228,7 +152,6 @@ This plugin uses GPU acceleration, and you need to enable hardware acceleration
 
 **2. When device performance is insufficient, causing high latency and rendering issues**
 
-
 ```javascript
 async function onAbort(error) {
   await trtc.stopPlugin('VirtualBackground'); // Stop the plugin

package/resource/doc/rtcengine/web/plugin/37-advanced-voice-changer.md

@@ -44,7 +44,6 @@ await trtc.stopPlugin('VoiceChanger');
 await trtc.stopLocalAudio();
 ```
 
-
 ## API Reference
 
 ### trtc.startPlugin('VoiceChanger', options)
@@ -96,4 +95,4 @@ Disable voice changing effects
 // Disable the plugin before stopping microphone
 await trtc.stopPlugin('VoiceChanger');
 await trtc.stopLocalAudio();
-```
+```

package/resource/doc/rtcengine/web/plugin/39-advanced-video-decoder.md

@@ -19,7 +19,6 @@ The plugin relies on some static resource files. To ensure that the browser can
   > - If the host URL of the directory files is different from the host URL of the web application, you need to enable the CORS policy for the file domain.
   > - Do not place the directory files under an HTTP service, as loading HTTP resources under an HTTPS domain will be blocked by browser security policies.
 
-
 ### 2. Import and Register Plugin
 
 ```javascript
@@ -30,4 +29,4 @@ const trtc = TRTC.create({ plugins: [TRTCVideoDecoder], assetsPath: 'https://exa
 
 ## Plugin Activation
 
-The plugin functionality will automatically activate the fallback logic when SDK regular decoding fails, using software decoding method to decode. 
+The plugin functionality will automatically activate the fallback logic when SDK regular decoding fails, using software decoding method to decode.

package/resource/doc/rtcengine/web/plugin/40-advanced-video-mixer.md

@@ -2,8 +2,6 @@
 
 This document provides a detailed guide on how to use the TRTC Web SDK's VideoMixer plugin to composite multiple input sources including camera, screen sharing, text, images, and videos into a single video track for streaming with custom layouts. Developers can flexibly control the layout (position, size, layer zIndex) of each source.
 
-![The Workflow of Video Mixer](./assets/videomixer-workflow.png)
-
 ## Prerequisites
 
 - TRTC Web SDK version >= 5.12.0.
@@ -51,7 +49,7 @@ const { track } = await trtc.startPlugin('VideoMixer', options);
 The mixing plugin is only responsible for generating the mixed video track. Publishing operation is still controlled by the TRTC SDK. Pass the track returned by startPlugin as a parameter to the startLocalVideo interface to publish.
 
 ```js
-await trtc.startLocalVideo({ option: { 
+await trtc.startLocalVideo({ option: {
   videoTrack: track,
   profile: { width: 1920, height: 1080, bitrate: 2000 } // Set encoding parameters
 }});
@@ -64,7 +62,7 @@ Dynamically add, update, or remove mixing input sources by calling `trtc.updateP
 **Update Rules:**
 
 * **Input Source Description:** Input sources are divided into: `camera, screen, text, image, video`. All are arrays, each array element represents an input source, uniquely identified by the id attribute.
-* **Update Input Source:** Pass the same id and modify other parameters.  
+* **Update Input Source:** Pass the same id and modify other parameters.
 * **Add Input Source:** Pass a new id object.
 * **Remove Input Source:** Remove the object from the corresponding input source array.
 
@@ -73,7 +71,7 @@ Dynamically add, update, or remove mixing input sources by calling `trtc.updateP
 Control camera capture and layout.
 
 ```javascript
-// Update camera layout with id 'camera1'  
+// Update camera layout with id 'camera1'
 await trtc.updatePlugin('VideoMixer', {
   camera: [
     {
@@ -84,7 +82,7 @@ await trtc.updatePlugin('VideoMixer', {
   ]
 });
 
-// Remove all cameras  
+// Remove all cameras
 await trtc.updatePlugin('VideoMixer', { camera: [] });
 // If you only want to temporarily hide the input source on the canvas without physically closing capture, you can set hidden: true in the layout parameter. The same applies to other input sources.
 ```
@@ -102,7 +100,7 @@ await trtc.updatePlugin('VideoMixer', {
       y: 0,
       width: 1920,
       height: 1080,
-      zIndex: 0,      
+      zIndex: 0,
     }
   }],
   // If the user stops screen sharing via browser button instead of SDK, you can listen through this callback
@@ -142,13 +140,13 @@ Add images (such as logos) or local video files as mixing input sources.
 
 ```js
 await trtc.updatePlugin('VideoMixer', {
-  image: [{ 
-    id: 'img1', 
+  image: [{
+    id: 'img1',
     url: './image.png',
     layout: { x: 0, y: 500, width: 800, height: 400, zIndex: 4 }
   }],
-  video: [{ 
-    id: 'video1', 
+  video: [{
+    id: 'video1',
     url: './video.mp4',
     layout: { x: 0, y: 0, width: 1000, height: 500, zIndex: 5 }
   }]
@@ -189,11 +187,11 @@ try {
   })
   console.log(result.successOptions) // Successfully applied options for this update
 } catch (error: any) {
-  // Scenario 2: Error catching for all failures (catching thrown errors)  
+  // Scenario 2: Error catching for all failures (catching thrown errors)
   console.error(error);
   error?.data?.failedDetails.forEach(({ id, error }: { id: string, error: any }) => {
     console.error(`${id} mix failed`, error);
-  })  
+  })
 }
 ```
 
@@ -220,7 +218,6 @@ Used to start the mixing plugin and initialize canvas and input sources.
 | video             | [VideoSource](#videosource)[]       | Optional     | Parameters for controlling video input sources                                                                                                 |
 | onScreenShareStop | (id: string) => {}                | Optional     | Callback invoked when mixed screen sharing stops. May be used when user cancels screen sharing via browser button instead of SDK. The callback parameter is the id of the stopped screen capture |
 
-
 **Returns: Promise\<MixParseResult\>**
 
 `MixParseResult`
@@ -229,7 +226,10 @@ Used to start the mixing plugin and initialize canvas and input sources.
 | ------ | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | track  | [MediaStreamTrack](https://developer.mozilla.org/en-US/docs/Web/API/MediaStreamTrack)  | Mixed output video track                                                                                                                                                                                                                                                           |
 | systemAudioTrackList  | object | This returns a list of system audio tracks. After setting the ScreenSource parameter `systemAudio:true` and successfully capturing the audio, it will return the system audio tracks. The data format is: `{key: audioTrack}`, where `key` is the ID configured in the ScreenSource, for example: `{id1: audioTrack, id2: audioTrack}`.                                                                                                                                                                                                                                                         |
-| result | object            | Information about the success or failure of the parameters passed in this time, structured as follows:<table><tr><th>Name</th><th>Type</th><th>Description</th></tr><tr><td>successOptions</td><td>[Options](#options)</td><td>Successfully executed options for this update</td></tr><tr><td>failedDetails</td><td>MixFailedDetail[]</td><td>Detailed information about failed updates</td></tr></table> |
+| result | object            | Information about the success or failure of the parameters passed in this time, structured as follows:| Name | Type | Description |
+| --- | --- | --- |
+| successOptions | [Options](#options) | Successfully executed options for this update |
+| failedDetails | MixFailedDetail[] | Detailed information about failed updates | |
 
 `MixFailedDetail`
 
@@ -322,10 +322,10 @@ Stop mixing.
 
 ### 1. Frame Rate and Performance Optimization
 
-* **Frame Rate Settings:**  
-  * **Not Recommended**: manually setting canvasInfo.frameRate.  
-  * **Recommended**: let the plugin automatically calculate internally: when camera or screen sharing exists, take the maximum frame rate of the two; otherwise fixed at 15 fps. Manual specification may cause performance loss.  
-* **Performance Considerations:**  
+* **Frame Rate Settings:**
+  * **Not Recommended**: manually setting canvasInfo.frameRate.
+  * **Recommended**: let the plugin automatically calculate internally: when camera or screen sharing exists, take the maximum frame rate of the two; otherwise fixed at 15 fps. Manual specification may cause performance loss.
+* **Performance Considerations:**
   * The larger the canvas resolution and the more mixing input sources, the greater the rendering overhead. The business side should determine appropriate canvas parameters and number of input sources based on user device performance.
 
 ### 2. How to Set Resolution and Bitrate?

package/resource/doc/rtcengine/web/plugin/41-advanced-small-stream-auto-switcher.md

@@ -84,7 +84,7 @@ trtc.startPlugin('SmallStreamAutoSwitcher', {
 2. Frame rate conditions: Small stream frame rate is stable (difference between maximum and minimum frame rate does not exceed 1/3 of maximum frame rate)
 3. Limiting conditions: User is currently subscribed to small stream, and the user has only switched to small stream once, and not in sleep period
 
-> **Note:** 
+> **Note:**
 > - Detection frequency is once every 2 seconds
 > - The statistical window size for network quality and frame rate data automatically adapts to the maximum value of poorDuration and goodDuration
 > - After each switch, it enters a sleep period of `sleepTime` duration, during which automatic switching will not be triggered again

package/resource/doc/rtcengine/web/plugin/42-advanced-realtime-transcriber.md

@@ -90,7 +90,7 @@ const robotId = await trtc.startPlugin('RealtimeTranscriber', {
 trtc.on(TRTC.EVENT.REALTIME_TRANSCRIBER_MESSAGE, (data) => {
   console.log(`👤 ${data.speakerUserId}:`);
   console.log(`  Original: ${data.sourceText}`);
-  
+
   if (data.translationTexts) {
     Object.entries(data.translationTexts).forEach(([lang, text]) => {
       console.log(`  ${lang.toUpperCase()}: ${text}`);
@@ -204,10 +204,10 @@ Transcription message event, triggered when new transcription results are availa
 ```javascript
 trtc.on(TRTC.EVENT.REALTIME_TRANSCRIBER_MESSAGE, (event) => {
   const { speakerUserId, sourceText, translationTexts, isCompleted } = event;
-  
+
   // Display real-time transcription result
   console.log(`[${isCompleted ? 'Completed' : 'In Progress'}] ${speakerUserId}: ${sourceText}`);
-  
+
   // Display translation results
   if (translationTexts) {
     translationTexts.forEach(({ language, text }) => {
@@ -301,7 +301,7 @@ const subtitleMap = new Map();
 
 trtc.on(TRTC.EVENT.REALTIME_TRANSCRIBER_MESSAGE, (event) => {
   subtitleMap.set(event.segmentId, event);
-  
+
   if (event.isCompleted) {
     // Speech segment completed, can be archived
     archiveSubtitle(subtitleMap.get(event.segmentId));
@@ -312,4 +312,3 @@ trtc.on(TRTC.EVENT.REALTIME_TRANSCRIBER_MESSAGE, (event) => {
 **3. How to save bandwidth?**
 
 When you don't need to receive transcription messages, remove all listeners for the `REALTIME_TRANSCRIBER_MESSAGE` event, and the plugin will automatically pause receiving messages to save bandwidth. When listeners are added again, message receiving will automatically resume.
-

package/resource/doc/rtcengine/web/plugin/43-advanced-face-detection.md

@@ -34,8 +34,8 @@ The plugin relies on static resource files. To ensure the browser can load and r
 ```javascript
 import { FaceDetection } from 'trtc-sdk-v5/plugins/video-effect/face-detection';
 
-const trtc = TRTC.create({ 
-  plugins: [FaceDetection], 
+const trtc = TRTC.create({
+  plugins: [FaceDetection],
   assetsPath: 'https://xxxx/assets'  // Replace with your static resource address
 });
 ```
@@ -177,4 +177,4 @@ Adjust sensitivity by combining these parameters:
 
 **2. Do I need to restart detection after the video stream recovers?**
 
-No. The plugin automatically handles video stream state changes and resumes detection upon recovery.
+No. The plugin automatically handles video stream state changes and resumes detection upon recovery.