@tencent-rtc/mcp 1.3.9 → 1.4.0

package/resource/doc/livekit/{live → core-sdk/live}/flutter/live-audio-effect.md

@@ -1,8 +1,5 @@
 This document aims to guide you on how to use the `AtomicXCore` framework's `AudioEffectStore` and `DeviceStore` modules to quickly integrate audio effect control features for your live stream app, including Microphone Volume, listen, and add multiple fun voice-changing effects and reverb effects.
 
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032457995/5a187583f76311f0859b52540097cba1.png)
-
-
 ## Core Features
 
 By combining `AudioEffectStore` and `DeviceStore`, you can implement the following core features:
@@ -14,58 +11,20 @@ By combining `AudioEffectStore` and `DeviceStore`, you can implement the followi
 
 - **Reverb effect**: Simulates sound field effects in different environments, such as KTV, metallic sound, deep, and resonant.
 
-
 ## Conceptual Introduction
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Core Concept**</td>
-
-<td rowspan="1" colSpan="1" >**Type**</td>
-
-<td rowspan="1" colSpan="1" >**Core Responsibilities and Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >[AudioEffectState](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioEffectState-class.html)</td>
-
-<td rowspan="1" colSpan="1" >`class`</td>
-
-<td rowspan="1" colSpan="1" >Represents the current status of the audio effect module, usually used for UI rendering. Includes voice-changing status, reverberation status, ear return enabled status, ear return volume. All attributes are `ValueListenable` data type, support subscription listen.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >[AudioEffectStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioEffectStore-class.html)</td>
-
-<td rowspan="1" colSpan="1" >`class`</td>
-
-<td rowspan="1" colSpan="1" >Represents the **singleton data management class** of the audio effect module. Through it you can call the audio effect API to modify sound effects. When you call the API, the appropriate `audioEffectState` property will auto-update. You can subscribe to this state's responsive data to receive and listen for status updates.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >[DeviceState](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceState-class.html)</td>
-
-<td rowspan="1" colSpan="1" >`class`</td>
-
-<td rowspan="1" colSpan="1" >Represents the current status of the device module, usually used for UI rendering. Core attributes include device status of camera, microphone, capturing volume. All attributes are `ValueListenable` data type, support subscription listen.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >[DeviceStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceStore-class.html)</td>
-
-<td rowspan="1" colSpan="1" >`class`</td>
-
-<td rowspan="1" colSpan="1" >Represents the **singleton data management class** of the device module. Through it you can call the API to operate camera and microphone. When you call the API, the appropriate `state` property will auto-update. You can subscribe to this state's responsive data to receive and listen for status updates.</td>
-</tr>
-</table>
-
+| **Core Concept** | **Type** | **Core Responsibilities and Description** |
+| --- | --- | --- |
+| [AudioEffectState](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioEffectState-class.html) | `class` | Represents the current status of the audio effect module, usually used for UI rendering. Includes voice-changing status, reverberation status, ear return enabled status, ear return volume. All attributes are `ValueListenable` data type, support subscription listen. |
+| [AudioEffectStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioEffectStore-class.html) | `class` | Represents the **singleton data management class** of the audio effect module. Through it you can call the audio effect API to modify sound effects. When you call the API, the appropriate `audioEffectState` property will auto-update. You can subscribe to this state's responsive data to receive and listen for status updates. |
+| [DeviceState](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceState-class.html) | `class` | Represents the current status of the device module, usually used for UI rendering. Core attributes include device status of camera, microphone, capturing volume. All attributes are `ValueListenable` data type, support subscription listen. |
+| [DeviceStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceStore-class.html) | `class` | Represents the **singleton data management class** of the device module. Through it you can call the API to operate camera and microphone. When you call the API, the appropriate `state` property will auto-update. You can subscribe to this state's responsive data to receive and listen for status updates. |
 
 ## Implementation Steps
 
 ### Step 1: Integrating the Component
-- **Live streaming**: Refer to [quick integration](https://write.woa.com/document/200455640177692672) to integrate **AtomicXCore** and complete service access.
-
-- **Voice chat room**: Refer to [quick integration](https://write.woa.com/document/200555778169073664) to integrate **AtomicXCore** and complete service access.
+- **Live streaming**: Refer to quick integration to integrate **AtomicXCore** and complete service access.
 
+- **Voice chat room**: Refer to quick integration to integrate **AtomicXCore** and complete service access.
 
 ### Step 2: Obtain a Store Instance
 
@@ -85,11 +44,10 @@ class _AudioEffectPanelWidgetState {
 Ear monitoring function allows users to monitor their own microphone sound in real time. Calling the API introduced in this section can manage the ear monitoring function.
 
 > **Note:**
-> 
+>
 
 > The in-ear monitoring feature typically needs to connect to headphones to work properly.
-> 
-
+>
 
 #### Implementation Method
 1. **Enable/Disable Ear Monitoring**: You can use the `Switch` control to implement the ear monitoring function.
@@ -98,7 +56,6 @@ Ear monitoring function allows users to monitor their own microphone sound in re
 
 3. **Listen for Status Updates to Update UI**: You can subscribe to real-time ear monitoring status value updates to refresh the UI.
 
-
 #### Sample Code
 ``` java
 import 'package:flutter/material.dart';
@@ -155,44 +112,14 @@ class EarMonitorWidget extends StatelessWidget {
 ```
 
 #### SetVoiceEarMonitorEnable API Parameter
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Parameter Name**</td>
-
-<td rowspan="1" colSpan="1" >**Type**</td>
-
-<td rowspan="1" colSpan="1" >**Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`enable`</td>
-
-<td rowspan="1" colSpan="1" >`bool`</td>
-
-<td rowspan="1" colSpan="1" >Enable earpiece feedback.<br>-  true: Enable<br>-  false: Disable</td>
-</tr>
-</table>
-
+| **Parameter Name** | **Type** | **Description** |
+| --- | --- | --- |
+| `enable` | `bool` | Enable earpiece feedback.<br>-  true: Enable<br>-  false: Disable |
 
 #### SetVoiceEarMonitorVolume API Parameter
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Parameter Name**</td>
-
-<td rowspan="1" colSpan="1" >**Type**</td>
-
-<td rowspan="1" colSpan="1" >**Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`volume`</td>
-
-<td rowspan="1" colSpan="1" >`int`</td>
-
-<td rowspan="1" colSpan="1" >Ear return volume.<br>- Value ranges from 0 to 150.<br>- Default value: 100.</td>
-</tr>
-</table>
-
+| **Parameter Name** | **Type** | **Description** |
+| --- | --- | --- |
+| `volume` | `int` | Ear return volume.<br>- Value ranges from 0 to 150.<br>- Default value: 100. |
 
 ### Step 4: Implement Vocal Volume Adjustment
 
@@ -203,7 +130,6 @@ When the Anchor hopes to adjust their own uplink capturing volume, call the `Dev
 
 2. **Listen for Status Updates to Update UI**: You can subscribe to real-time volume level status value updates to refresh the UI.
 
-
 #### Sample Code
 ``` java
 import 'package:flutter/material.dart';
@@ -240,24 +166,9 @@ class CaptureVolumeWidget extends StatelessWidget {
 ```
 
 #### SetCaptureVolume API Parameter
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Parameter Name**</td>
-
-<td rowspan="1" colSpan="1" >**Type**</td>
-
-<td rowspan="1" colSpan="1" >**Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`volume`</td>
-
-<td rowspan="1" colSpan="1" >`int`</td>
-
-<td rowspan="1" colSpan="1" >Capture volume size.<br>- Value ranges from 0 to 150.<br>- Default value: 100.</td>
-</tr>
-</table>
-
+| **Parameter Name** | **Type** | **Description** |
+| --- | --- | --- |
+| `volume` | `int` | Capture volume size.<br>- Value ranges from 0 to 150.<br>- Default value: 100. |
 
 ### Step 5: Implement Voice-Changing Effects
 
@@ -328,24 +239,9 @@ class VoiceChangerWidget extends StatelessWidget {
 ```
 
 #### SetAudioChangerType API Parameter
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Parameter Name**</td>
-
-<td rowspan="1" colSpan="1" >**Type**</td>
-
-<td rowspan="1" colSpan="1" >**Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`type`</td>
-
-<td rowspan="1" colSpan="1" >[AudioChangerType](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioChangerType.html)</td>
-
-<td rowspan="1" colSpan="1" >Voice-changing effects enumeration.</td>
-</tr>
-</table>
-
+| **Parameter Name** | **Type** | **Description** |
+| --- | --- | --- |
+| `type` | [AudioChangerType](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioChangerType.html) | Voice-changing effects enumeration. |
 
 ### Step 6: Implement Reverb Effect
 
@@ -424,33 +320,17 @@ class ReverbWidget extends StatelessWidget {
 ```
 
 #### SetAudioReverbType API Parameter
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Parameter Name**</td>
-
-<td rowspan="1" colSpan="1" >**Type**</td>
-
-<td rowspan="1" colSpan="1" >**Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`type`</td>
-
-<td rowspan="1" colSpan="1" >[AudioReverbType](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioReverbType.html)</td>
-
-<td rowspan="1" colSpan="1" >Reverb effects enumeration.</td>
-</tr>
-</table>
-
+| **Parameter Name** | **Type** | **Description** |
+| --- | --- | --- |
+| `type` | [AudioReverbType](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioReverbType.html) | Reverb effects enumeration. |
 
 ### Step 7: Reset Sound Effect Settings
 
 > **Important:**
-> 
+>
 
 > AudioEffectStore and DeviceStore are singletons, so audio effects and device settings take effect globally. If you do not want the settings of the current live streaming room to affect other live streaming rooms created later, you need to reset the audio effects and device settings when the current live streaming room ends.
-> 
-
+>
 
 You may need to reset sound effect settings in the following two scenarios:
 1. **When the current live streaming room ends**, call the `store`'s `reset()` method to reset sound effects.
@@ -460,16 +340,16 @@ You may need to reset sound effect settings in the following two scenarios:
    ``` java
    import 'package:flutter/material.dart';
    import 'package:atomic_x_core/atomicxcore.dart';
-   
+
    /// Sound effect reset component
    class AudioEffectResetWidget extends StatelessWidget {
      const AudioEffectResetWidget({super.key});
-   
+
      void _resetAudioEffect() {
        AudioEffectStore.shared.reset();
        DeviceStore.shared.reset();
      }
-   
+
      @override
      Widget build(BuildContext context) {
        return ElevatedButton(
@@ -681,32 +561,10 @@ class AudioEffectPage extends StatelessWidget {
 ## API documentation
 
 For detailed information about all public interfaces and attributes of [AudioEffectStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioEffectStore-class.html), [DeviceStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceStore-class.html) and its related classes, see the official API documentation of the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_Flutter/index.html) framework.
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Store/Component**</td>
-
-<td rowspan="1" colSpan="1" >**Feature Description**</td>
-
-<td rowspan="1" colSpan="1" >**API Reference**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >**AudioEffectStore**</td>
-
-<td rowspan="1" colSpan="1" >Audio effect management: Perform audio effect settings and obtain real-time audio effect status.</td>
-
-<td rowspan="1" colSpan="1" >[API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioEffectStore-class.html)</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >**DeviceStore**</td>
-
-<td rowspan="1" colSpan="1" >Device management: perform camera and microphone operations and obtain real-time device status.</td>
-
-<td rowspan="1" colSpan="1" >[API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceStore-class.html)</td>
-</tr>
-</table>
-
+| **Store/Component** | **Feature Description** | **API Reference** |
+| --- | --- | --- |
+| **AudioEffectStore** | Audio effect management: Perform audio effect settings and obtain real-time audio effect status. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioEffectStore-class.html) |
+| **DeviceStore** | Device management: perform camera and microphone operations and obtain real-time device status. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceStore-class.html) |
 
 ## FAQs
 
@@ -721,7 +579,6 @@ This is a very important and confusing concept. The difference is as follows:
 
 - **Ear Return Volume (EarMonitorVolume):** Set via `AudioEffectStore.shared.setVoiceEarMonitorVolume()`. It only determines the Anchor's headphone monitoring volume and **does not** impact the audience.
 
-
 ### Why Does a Newly Created Live Streaming Room Have Sound Effects Directly or Issues Like Very High or Low Volume?
 
 `AudioEffectStore` and `DeviceStore` are singletons, which means audio effects and device settings take effect globally. This situation probably occurs because you set audio effects earlier but did not reset them. You need to call the `reset()` method in an appropriate place.
@@ -735,8 +592,6 @@ Please check by the following steps:
 
 3. **Is the microphone enabled**: Confirm that the microphone in `DeviceStore` is enabled (the `openLocalMicrophone()` call has been made).
 
-
 ### Can Voice-Changing Effects and Reverb Effects Take Effect at the Same Time?
 
 Yes. `AudioChangerType` and `AudioReverbType` can take effect in superposition. For example, you can simultaneously set `AudioChangerType.girl` voice-changing and `AudioReverbType.ktv` reverb.
-

package/resource/doc/livekit/{live → core-sdk/live}/flutter/live-barrage.md

@@ -1,8 +1,5 @@
 This document aims to guide Flutter developers on how to use the `BarrageStore` module in the `AtomicXCore` framework to quickly integrate a bullet screen system with various features and outstanding performance for your live stream app.
 
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032457995/e62bfa87f76211f0822d525400074c32.png)
-
-
 ## Core Features
 
 `BarrageStore` provides a complete bullet screen solution for your live stream app. Core features include:
@@ -14,54 +11,22 @@ This document aims to guide Flutter developers on how to use the `BarrageStore`
 
 - Insert a system prompt in the local message list (for example, "Welcome XX to enter live room").
 
-
 ## Core Concept Analysis
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Core Concept**</td>
-
-<td rowspan="1" colSpan="1" >**Type**</td>
-
-<td rowspan="1" colSpan="1" >**Core Responsibility and Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >[Barrage](https://tencent-rtc.github.io/TUIKit_Flutter/api_barrage_barrage_store/Barrage-class.html)</td>
-
-<td rowspan="1" colSpan="1" >`class`</td>
-
-<td rowspan="1" colSpan="1" >Represents a data model for a Danmu Message. It contains all key information such as sender information (`sender`), message content (`textContent` or `data`), and message type (`messageType`).</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >[BarrageState](https://tencent-rtc.github.io/TUIKit_Flutter/api_barrage_barrage_store/BarrageState-class.html)</td>
-
-<td rowspan="1" colSpan="1" >`class`</td>
-
-<td rowspan="1" colSpan="1" >Represents the current status of the bullet screen module. Its core attribute `messageList` is a `ValueListenable<List<Barrage>>`, storing all Danmu messages in the live streaming room in chronological order, serving as the data source for UI rendering.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >[BarrageStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_barrage_barrage_store/BarrageStore-class.html)</td>
-
-<td rowspan="1" colSpan="1" >`class`</td>
-
-<td rowspan="1" colSpan="1" >This is the core management class for danmu function interaction. Through it, you can send messages (`sendTextMessage`, `sendCustomMessage`) and receive and listen to ALL Danmu Message updates by listening to its `barrageState.messageList` property.</td>
-</tr>
-</table>
-
+| **Core Concept** | **Type** | **Core Responsibility and Description** |
+| --- | --- | --- |
+| [Barrage](https://tencent-rtc.github.io/TUIKit_Flutter/api_barrage_barrage_store/Barrage-class.html) | `class` | Represents a data model for a Danmu Message. It contains all key information such as sender information (`sender`), message content (`textContent` or `data`), and message type (`messageType`). |
+| [BarrageState](https://tencent-rtc.github.io/TUIKit_Flutter/api_barrage_barrage_store/BarrageState-class.html) | `class` | Represents the current status of the bullet screen module. Its core attribute `messageList` is a `ValueListenable<List<Barrage>>`, storing all Danmu messages in the live streaming room in chronological order, serving as the data source for UI rendering. |
+| [BarrageStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_barrage_barrage_store/BarrageStore-class.html) | `class` | This is the core management class for danmu function interaction. Through it, you can send messages (`sendTextMessage`, `sendCustomMessage`) and receive and listen to ALL Danmu Message updates by listening to its `barrageState.messageList` property. |
 
 ## Implementation Steps
 
 ### Step 1: Integrating the Component
-- **Live streaming**: Refer to [quick integration](https://write.woa.com/document/200455640177692672) for seamless integration with **AtomicXCore** and service access.
-
-- **Voice chat room**: Refer to [quick integration](https://write.woa.com/document/200555778169073664) for seamless integration with **AtomicXCore** and service access.
+- **Live streaming**: Refer to quick integration for seamless integration with **AtomicXCore** and service access.
 
+- **Voice chat room**: Refer to quick integration for seamless integration with **AtomicXCore** and service access.
 
    Return to the current project after integration.
 
-
 ### Step 2: Initialize and Listen to the Bullet Screen
 
 Retrieve a `BarrageStore` instance bound to the current live streaming room `liveId`, and set a listener to receive the latest **Full** barrage message list in real time.
@@ -75,7 +40,7 @@ class BarrageManager {
   late final VoidCallback _messageListChangedListener = _onMessageListChanged;
 
   // Expose message list change notification to the public
-  final ValueNotifier<List<Barrage>> messagesNotifier = 
+  final ValueNotifier<List<Barrage>> messagesNotifier =
       ValueNotifier<List<Barrage>>([]);
 
   BarrageManager({required this.liveId}) {
@@ -134,32 +99,10 @@ extension BarrageManagerSend on BarrageManager {
 ```
 
 **API parameter:**
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Parameter**</td>
-
-<td rowspan="1" colSpan="1" >**Type**</td>
-
-<td rowspan="1" colSpan="1" >**Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`text`</td>
-
-<td rowspan="1" colSpan="1" >`String`</td>
-
-<td rowspan="1" colSpan="1" >The text content to be sent.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`extensionInfo`</td>
-
-<td rowspan="1" colSpan="1" >`Map<String, String>?`</td>
-
-<td rowspan="1" colSpan="1" >Attach extra extended information applicable to business customization.</td>
-</tr>
-</table>
-
+| **Parameter** | **Type** | **Description** |
+| --- | --- | --- |
+| `text` | `String` | The text content to be sent. |
+| `extensionInfo` | `Map<String, String>?` | Attach extra extended information applicable to business customization. |
 
 ### Step 4: Send Custom Barrage Item
 
@@ -196,32 +139,10 @@ extension BarrageManagerCustom on BarrageManager {
 ```
 
 **API parameter:**
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Parameter**</td>
-
-<td rowspan="1" colSpan="1" >**Type**</td>
-
-<td rowspan="1" colSpan="1" >**Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`businessID`</td>
-
-<td rowspan="1" colSpan="1" >`String`</td>
-
-<td rowspan="1" colSpan="1" >Business unique identifier, such as "live_gift", used for recipient to distinguish different custom messages.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`data`</td>
-
-<td rowspan="1" colSpan="1" >`String`</td>
-
-<td rowspan="1" colSpan="1" >Business data, typically strings in JSON format.</td>
-</tr>
-</table>
-
+| **Parameter** | **Type** | **Description** |
+| --- | --- | --- |
+| `businessID` | `String` | Business unique identifier, such as "live_gift", used for recipient to distinguish different custom messages. |
+| `data` | `String` | Business data, typically strings in JSON format. |
 
 ### Step 5: Insert Prompt Message Locally
 
@@ -480,7 +401,7 @@ class BarrageUIManager {
     if (newList == null) return;
 
     _latestMessageList = null; // Clear flags to avoid repeated refresh
-    
+
     // Update data source and refresh UI
     onUpdate(newList);
   }
@@ -513,7 +434,7 @@ void _refreshUIIfNeeded() {
 
   // Key point: Take the latest N messages
   const capacity = 500; // The client keeps the latest 500 messages only
-  final cappedList = fullList.length > capacity 
+  final cappedList = fullList.length > capacity
       ? fullList.sublist(fullList.length - capacity)
       : fullList;
 
@@ -541,7 +462,6 @@ This is actually achieved by the custom message `sendCustomMessage`. `BarrageSto
 
 3. **Receiver**: After receiving the Danmu Message, check whether its `messageType` is `.custom` and whether `businessId` matches. If matched, parse the `data` string (usually parsing JSON), and render your custom UI style based on the parsed data (such as `color, text`).
 
-
 ### Different Classes and Files Call `BarrageStore.create("some_id")`. Will This Create Multiple Instances and Cause Chaos?
 
 No worries at all. `AtomicXCore`'s internal mechanism will underwrite that as long as the `liveId` passed in is identical, the `BarrageStore` instance obtained will always be the same one bound to the live streaming room. You can use it wherever required without manually managing the singleton.
@@ -557,7 +477,6 @@ No worries at all. `AtomicXCore`'s internal mechanism will underwrite that as lo
 
 4. **Network issue**: Check whether the current network connection of the device is normal. Sending messages depends on the network.
 
-
 ### How to Show New Audience the History Danmu Messages When They Enter the Live Room
 
 `AtomicXCore` supports pulling history Danmu Messages, but this requires you to perform one simple configuration in the **server console**. Once configured, the SDK will automatically handle everything subsequently with no need to write additional code.
@@ -567,15 +486,8 @@ No worries at all. `AtomicXCore`'s internal mechanism will underwrite that as lo
 
 2. On the Live configuration page, select **new member pull historical messages**, modify **new member viewable latest message count**, supports a maximum of **50**.
 
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032457995/f7e29319f76211f0831c52540073fd3b.png)
-
-
    **Step 2: Client Seamless Retrieval**
 
-
-   After completing the above configuration, your client-side code **requires no modification**. 
-
+   After completing the above configuration, your client-side code **requires no modification**.
 
    When a new user joins the live room, the `AtomicXCore` underlying layer will automatically pull your configuration history message count. These historical messages will be pushed to your UI layer through your realized `BarrageStore.barrageState` subscription channel, just like real-time messages. Your application will naturally receive and show these historical bullet screens, same as receiving real-time bullet screens.
-
-