From c5ccf3bf6d26b886ecdb8553ee87daebc41cdbdf Mon Sep 17 00:00:00 2001 From: Cilla-luodan <85477033+Cilla-luodan@users.noreply.github.com> Date: Wed, 13 Nov 2024 18:25:41 +0800 Subject: [PATCH] New translations --- ...rameobserver_getvideoformatpreference.dita | 2 +- ...ideoframeobserver_oncapturevideoframe.dita | 6 +++- ...videoframeobserver_onrendervideoframe.dita | 3 ++ en-US/dita/RTC-NG/API/rtc_api_overview.dita | 32 +++++++++---------- 4 files changed, 25 insertions(+), 18 deletions(-) diff --git a/en-US/dita/RTC-NG/API/callback_ivideoframeobserver_getvideoformatpreference.dita b/en-US/dita/RTC-NG/API/callback_ivideoframeobserver_getvideoformatpreference.dita index 8e36f1add80..01aa1436f2a 100644 --- a/en-US/dita/RTC-NG/API/callback_ivideoframeobserver_getvideoformatpreference.dita +++ b/en-US/dita/RTC-NG/API/callback_ivideoframeobserver_getvideoformatpreference.dita @@ -32,7 +32,7 @@

You need to register the callback when calling the method. After you successfully register the video frame observer, the SDK triggers this callback each time it receives a video frame. You need to set your preferred video data in the return value of this callback.

The default types of pixel format () for the raw video are as follows:
    -
  • On the Android platform, the default video frame type may be I420Buffer or TextureBuffer. The cases where the video frame type is fixed as I420Buffer include but are not limited to:
      +
    • On the Android platform, the default video frame type may be I420Buffer or TextureBuffer. TextureBuffer 类型的纹理格式可能为 OES 格式或者 RGB 格式。 如果 返回的视频帧类型为 ，你需要在处理视频数据时增加对 I420Buffer 或 TextureBuffer 的适配。 The cases where the video frame type is fixed as I420Buffer include but are not limited to:
      • Specific devices, such as: LG G5 SE (H848), Google Pixel 4a, Samsung Galaxy A7, or Xiaomi Mi Max.
      • Image enhancement extension has been integrated and video noise reduction or low-light enhancement function has been enabled.
      • diff --git a/en-US/dita/RTC-NG/API/callback_ivideoframeobserver_oncapturevideoframe.dita b/en-US/dita/RTC-NG/API/callback_ivideoframeobserver_oncapturevideoframe.dita index a8c760ff7f5..b51e846f84f 100644 --- a/en-US/dita/RTC-NG/API/callback_ivideoframeobserver_oncapturevideoframe.dita +++ b/en-US/dita/RTC-NG/API/callback_ivideoframeobserver_oncapturevideoframe.dita @@ -35,6 +35,10 @@

      You can get raw video data collected by the local device through this callback and preprocess it as needed. Once the preprocessing is complete, you can directly modify videoFrame in this callback, and set the return value to to send the modified video data to the SDK.

      If you need to send the preprocessed data to the SDK, you need to call first to set the video processing mode to read and write mode ().

      You can get raw video data collected by the local device through this callback.

      + +

      该回调默认提供的视频数据格式为 I420Buffer 或 TextureBuffer，TextureBuffer 类型的纹理格式可能为 0ES 格式或者 RGB 格式。 如果你需要其他格式的视频数据，可在 回调的返回值中设置预期的数据格式。

      +

      该回调默认提供的视频数据格式为 I420 或 CVPixelBufferRef，如果你需要其他格式的视频数据，可在 回调中返回预期的数据格式。

      +

      该回调默认提供的视频数据格式为 YUV420，如果你需要其他格式的视频数据，可在 getVideoFormatPreference 回调的返回值中设置预期的数据格式。
Applicable scenarios @@ -45,7 +49,7 @@
Trigger timing

After the successful registration of the video data observer, each time the SDK captures a video frame.

-
+
Restrictions

After you successfully register the video frame observer, the SDK triggers this callback each time it receives a video frame. In this callback, you can get the video data sent from the remote end before rendering, and then process it according to the particular scenarios.

+

该回调默认提供的视频数据格式为 I420Buffer 或 TextureBuffer，TextureBuffer 类型的纹理格式可能为 0ES 格式或者 RGB 格式。 如果你需要其他格式的视频数据，可在 回调的返回值中设置预期的数据格式。

+

该回调默认提供的视频数据格式为 I420 或 CVPixelBufferRef，如果你需要其他格式的视频数据，可在 回调中返回预期的数据格式。

+

该回调默认提供的视频数据格式为 YUV420，如果你需要其他格式的视频数据，可在 getVideoFormatPreference 回调的返回值中设置预期的数据格式。