New YiCAT updates (#3910)

* New translations

* New translations

* New translations

* New translations

* New translations

* New translations

* New translations

* New translations

* New translations

* New translations

* New translations

* New translations

* New translations

* New translations

* New translations

* New translations

* New translations

* New translations

* New translations

* New translations

* New translations

* 4.5.1 framework (#3907)

* update unity&unreal keysmap

* add bp&unreal props

* Update release_notes.dita

* Update keys-rtc-ng-api-flutter.ditamap

* Electron/RN: add keys

* Update keys-rtc-ng-api-blueprint.ditamap

* RN/Electron: add ai keys CN

* Update keys-rtc-ng-links.ditamap

---------

Co-authored-by: Nero-Hu <[email protected]>

* New translations

* New translations

* New translations

* New translations

* New translations

* delete rte api

* Update api_imediaengine_pushvideoframe.dita

---------

Co-authored-by: Suri539 <[email protected]>
Co-authored-by: Nero-Hu <[email protected]>
Co-authored-by: Suri539 <[email protected]>

Author: 3 people

en-US/dita/RTC-NG/API/api_imediaengine_pushvideoframe.dita

@@ -39,7 +39,7 @@
             </dlentry>
             </dl>
             <p id="desc1">To publish a custom video source, see the following steps:<ol>
-            <li>Call <xref keyref="createCustomVideoTrack"/> to create a video track and get the video track ID.</li>
+            <li>Call <xref keyref="createCustomVideoTrack"/> to create a video track and get the video track ID.<note type="note">If you only need to push one custom video source to the channel, you can directly call the <xref keyref="setExternalVideoSource"/> method and the SDK will automatically create a video track with the <parmname>videoTrackId</parmname> set to 0.</note></li>
             <li>Call <xref keyref="joinChannel2"/> to join the channel. In <xref keyref="ChannelMediaOptions"/>, set <parmname>customVideoTrackId</parmname> to the video track ID that you want to publish, and set <parmname>publishCustomVideoTrack</parmname> to <codeph><ph keyref="true"/></codeph>.</li>
             <li>Call this method and specify <parmname>videoTrackId</parmname> as the video track ID set in step 2. You can then publish the corresponding custom video source in the channel.</li></ol></p>
             <note type="danger" id="desc2">After calling this method, even if you stop pushing external video frames to the SDK, the custom video stream will still be counted as the video duration usage and incur charges. Agora recommends that you take appropriate measures based on the actual situation to avoid such video billing.<ul>
@@ -63,8 +63,8 @@
             </plentry>
             <plentry id="videotrackid">
                 <pt>videoTrackId</pt>
-                <pd>The video track ID returned by calling the <apiname keyref="createCustomVideoTrack"/> method. The default value is 0.</pd>
-            </plentry>    
+                <pd>The video track ID returned by calling the <apiname keyref="createCustomVideoTrack"/> method.<note type="note">If you only need to push one custom video source, set <parmname>videoTrackId</parmname> to 0.</note></pd>
+            </plentry>
             </parml>
         </section>
         <section id="return_values">

en-US/dita/RTC-NG/API/api_irtcengine_enablevirtualbackground.dita

@@ -48,6 +48,7 @@
             <p>Call this method after calling <xref keyref="enableVideo"/> or <xref keyref="startPreview2"/>.</p>
             <note type="attention" id="hardware_req">
             <ul>
+            <li>Using a video as a your virtual background will lead to continuous increase in memory usage, which may cause issues such as app crashes. Therefore,it is recommended to reduce the resolution and frame rate of the video when using it.</li>
             <li>This feature has high requirements on device performance. When calling this method, the SDK automatically checks the capabilities of the current device. Agora recommends you use virtual background on devices with the following processors:<ul>
                 <li props="android unity cpp unreal bp rn flutter cs">Snapdragon 700 series 750G and later</li>
                 <li props="android unity cpp unreal bp rn flutter cs">Snapdragon 800 series 835 and later</li>

en-US/dita/RTC-NG/API/api_irtcengine_sendstreammessage.dita

@@ -45,7 +45,7 @@
             <note type="attention">
             <ul>
             <li>This method needs to be called after <xref keyref="createDataStream2" /> and joining the channel.</li>
-            <li>In live streaming scenarios, this method only applies to hosts.</li>
+            <li>This method applies to broadcasters only.</li>
             </ul></note> </section>
         <section id="parameters">
             <title>Parameters</title>

en-US/dita/RTC-NG/API/api_irtcengine_setremoterendermode2.dita

@@ -69,9 +69,11 @@
                 <pt props="ios mac">mirror</pt>
                 <pd>
                     <p props="ios mac cpp unreal bp unity flutter rn electron cs">The mirror mode of the remote user view. See <xref keyref="VIDEO_MIRROR_MODE_TYPE" />.</p>
-                    <p props="android hmos">The mirror mode of the remote user view.<ul conkeyref="setLocalRenderMode2/videomirrormodetype">
-                    <li />
-                    </ul> </p>
+                    <p props="android hmos">The mirror mode of the remote user view.<ul>
+                    <li><ph keyref="VIDEO_MIRROR_MODE_AUTO" />(0): The SDK determines whether to enable the mirror mode. The SDK disables mirror mode by default.</li>
+                    <li><ph keyref="VIDEO_MIRROR_MODE_ENABLED" />(1): Enables the mirror mode for remote user's view.</li>
+                    <li><ph keyref="VIDEO_MIRROR_MODE_DISABLED" />(2): Disables the mirror mode for remote user's view.</li>
+                    </ul></p>
                     <note conkeyref="setLocalRenderMode2/mirror" props="unreal bp"/>
                 </pd>
             </plentry>

en-US/dita/RTC-NG/API/api_irtcengine_setvideoscenario.dita

@@ -72,7 +72,7 @@
                         </li>
                     </ul>
                 </p>
-                <p id="1v1"><apiname keyref="APPLICATION_SCENARIO_1V1"/>(2) This is applicable to the <xref keyref="one-to-one-live"/> scenario. To meet the requirements for low latency and high-quality video in this scenario, the SDK optimizes its strategies, improving performance in terms of video quality, first frame rendering, latency on mid-to-low-end devices, and smoothness under weak network conditions.</p>
+                <p id="1v1"><apiname keyref="APPLICATION_SCENARIO_1V1"/>(2) This is applicable to the <xref keyref="one-to-one-live"/> scenario. To meet the requirements for low latency and high-quality video in this scenario, the SDK optimizes its strategies, improving performance in terms of video quality, first frame rendering, latency on mid-to-low-end devices, and smoothness under weak network conditions.<note type="attention">This enumeration value is only applicable to the broadcaster vs. broadcaster scenario.</note></p>
                 <p id="liveshow"><apiname keyref="APPLICATION_SCENARIO_LIVESHOW"/>(3) This is applicable to the <xref keyref="showroom"/> scenario. In this scenario, fast video rendering and high image quality are crucial. The SDK implements several performance optimizations, including automatically enabling accelerated audio and video frame rendering to minimize first-frame latency (no need to call <xref keyref="enableInstantMediaRendering"/>), and B-frame encoding to achieve better image quality and bandwidth efficiency. The SDK also provides enhanced video quality and smooth playback, even in poor network conditions or on lower-end devices.</p>
                 </pd>
             </plentry>

en-US/dita/RTC-NG/API/api_irtcengineex_sendstreammessageex.dita

@@ -44,7 +44,6 @@
             <li props="android apple cpp unity flutter">If you need a more comprehensive solution for low-latency, high-concurrency, and scalable real-time messaging and status synchronization, it is recommended to use <xref keyref="rtm2"/>.</li>
             <li>Call this method after <xref keyref="joinChannelEx"/>.</li>
             <li>Ensure that you call <apiname keyref="createDataStreamEx2" /> to create a data channel before calling this method.</li>
-            <li>This method applies only to the COMMUNICATION profile or to the hosts in the LIVE_BROADCASTING profile. If an audience in the LIVE_BROADCASTING profile calls this method, the audience may be switched to a host.</li>
             </ul></note> </section>
         <section id="parameters">
             <title>Parameters</title>