tencentcloud-sdk-nodejs-intl-en 3.0.1349 → 3.0.1350

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -35,6 +35,7 @@ const SetUserBlockedRequest = models.SetUserBlockedRequest;
35
35
  const DescribeUserEventRequest = models.DescribeUserEventRequest;
36
36
  const DeleteCloudModerationRequest = models.DeleteCloudModerationRequest;
37
37
  const SetUserBlockedResponse = models.SetUserBlockedResponse;
38
+ const McuBackgroundCustomRender = models.McuBackgroundCustomRender;
38
39
  const WaterMarkChar = models.WaterMarkChar;
39
40
  const DescribeTrtcRoomUsageResponse = models.DescribeTrtcRoomUsageResponse;
40
41
  const StopPublishCdnStreamResponse = models.StopPublishCdnStreamResponse;
@@ -295,18 +296,14 @@ This API is used to achieve the following goals:
295
296
  }
296
297
 
297
298
  /**
298
- * **API Description**
299
+ * API description:.
300
+ Start a mixed stream forwarding task to mix multiple audio and video streams in a TRTC room into one media stream, transcode it, and push it to live stream CDN or back to the TRTC room. It also supports directly forwarding a single stream from the TRTC room without transcoding. After startup successful, it will return a task ID (TaskId) unique to the SdkAppid dimension. You need to save this TaskId, as it will be relied on to update and end the task subsequently. See document: [Feature Description](https://www.tencentcloud.comom/document/product/647/84721?from_cn_redirect=1#b9a855f4-e38c-4616-9b07-fc44e0e8282a) and [Common Issues](https://www.tencentcloud.comom/document/product/647/62620?from_cn_redirect=1).
299
301
 
300
- This API starts a stream mixing and relaying task. This API mixes multiple audio/video streams from a TRTC room into a single stream, encodes it, and then pushes it to CDN server or publishs it into the TRTC room. It also supports relaying a single stream from a TRTC room directly without transcoding.
301
-
302
- After success, the API returns a globally unique TaskID. You will need this TaskId in later operations such as updating or stopping the task.
303
-
304
- For more details, refer to the document: [Feature Description](https://trtc.io/zh/document/47858?product=rtcengine ) and [FAQs](https://trtc.io/zh/document/36058?product=rtcengine&menulabel=core%20sdk&platform=web) .
305
-
306
- Note: You can enable the relay to CDN in the console to monitor events under the CDN relay status. For callback details, see: [Relay to CDN Callback Description](https://trtc.io/zh/document/54913?product=rtcengine&menulabel=core%20sdk&platform=web ) .
307
-
308
- Starting a relay task may incur the following fees:
309
- MCU stream mixing and transcoding fees: [See Cloud Stream Mixing and Transcoding Pricing](https://trtc.io/zh/document/47631 ) .
302
+ Note:.
303
+ You can enable bypass relay callback through console activation for monitoring events of CDN state. Refer to the documentation for callback: [Bypass Relay Callback Description](https://www.tencentcloud.comom/document/product/647/88552?from_cn_redirect=1).
304
+ Initiating a mixed stream push task may incur the following fees:.
305
+ For MCU mix transcoding fees, refer to the documentation: On-Cloud MixTranscoding billing (https://www.tencentcloud.comom/document/product/647/49446?from_cn_redirect=1).
306
+ For forwarding expenses of non-Tencent Cloud CDN, refer to the documentation: [Cloud-based forwarding billing explanation](https://www.tencentcloud.comom/document/product/647/82155?from_cn_redirect=1).
310
307
  * @param {StartPublishCdnStreamRequest} req
311
308
  * @param {function(string, StartPublishCdnStreamResponse):void} cb
312
309
  * @public
@@ -478,7 +475,8 @@ Note: For details about how to use this API, see the `StartPublishCdnStream` doc
478
475
  }
479
476
 
480
477
  /**
481
- * This interface can be used to initiate a web-page recording task. In the interface parameters, specify the recording URL, recording resolution, recording result storage and other parameters. If there are parameter or API logic problems, the result will be returned immediately. If there are page problems, such as the page cannot be accessed, the result will be returned in the callback. Please pay attention.
478
+ * This API is used to trigger a page recording task. Specify parameters such as the recording URL, recording resolution, and recording result storage in the API parameter.
479
+ Because parameter or API logic issues will return immediate results. For page issues such as page unreachable, results will be returned in the callback, stay tuned.
482
480
  * @param {StartWebRecordRequest} req
483
481
  * @param {function(string, StartWebRecordResponse):void} cb
484
482
  * @public
@@ -557,7 +555,7 @@ Note:
557
555
  /**
558
556
  * API description:.
559
557
  Start on-cloud recording to complete audio and video recording in the room and upload to designated cloud storage. This API is used to record each audio and video stream in the TRTC room separately or merge multiple video images into one stream.
560
- Before official online operation, pay attention to the recording best practices (https://www.tencentcloud.com/document/product/647/76497?from_cn_redirect=1#e7e2f04c-6cde-43c9-9cd0-0f8d22dee68c). In conjunction with best practices, it can greatly improve API recording availability.
558
+ Before official online operation, pay attention to the recording best practices (https://www.tencentcloud.comom/document/product/647/76497?from_cn_redirect=1#e7e2f04c-6cde-43c9-9cd0-0f8d22dee68c). In conjunction with best practices, it can greatly improve API recording availability.
561
559
 
562
560
  This API is used to achieve the following goals:.
563
561
  Specify the subscription stream parameter (RecordParams) to specify the blocklist or allowlist of anchors that need to be recorded.
@@ -1,3 +1,3 @@
1
1
  module.exports = {
2
- v20240718: require("./v20240718"), v20180717: require("./v20180717"),
2
+ v20180717: require("./v20180717"), v20240718: require("./v20240718"),
3
3
  };
@@ -1,3 +1,3 @@
1
1
  module.exports = {
2
- v20250806: require("./v20250806"), v20210820: require("./v20210820"),
2
+ v20210820: require("./v20210820"), v20250806: require("./v20250806"),
3
3
  };