@tencent-rtc/mcp 1.3.9 → 1.4.0

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

@@ -1,8 +1,5 @@
 This document provides guidance on integrating audio effect controls into your live streaming application using the `AudioEffectStore` and `DeviceStore` modules from the **AtomicXCore** framework. These modules enable features such as microphone volume control, ear monitoring, and a variety of voice changing and reverb effects.
 
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027182498/b6b61ae4c90111f0b011525400bf7822.png)
-
-
 ## Core Features
 
 By combining `AudioEffectStore` and `DeviceStore`, you can implement the following core features:
@@ -14,74 +11,22 @@ By combining `AudioEffectStore` and `DeviceStore`, you can implement the followi
 
 - **Reverb Effects**: Simulate different acoustic environments, such as KTV, metallic, deep, bright, and others.
 
-
 ## Core Concepts
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Core Concept**</td>
-
-<td rowspan="1" colSpan="1" >**Type**</td>
-
-<td rowspan="1" colSpan="1" >**Core Responsibility & Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`AudioChangerType`</td>
-
-<td rowspan="1" colSpan="1" >`enum`</td>
-
-<td rowspan="1" colSpan="1" >Enumerates available voice changing effects, such as "child", "man", etc.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`AudioReverbType`</td>
-
-<td rowspan="1" colSpan="1" >`enum`</td>
-
-<td rowspan="1" colSpan="1" >Enumerates available reverb effects, such as "ktv", "hall", etc.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`AudioEffectState`</td>
-
-<td rowspan="1" colSpan="1" >`struct`</td>
-
-<td rowspan="1" colSpan="1" >Represents the current state of the audio effect module, typically used for UI rendering. Includes voice changing effect state, reverb state, ear monitoring enabled state, and ear monitor volume.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`AudioEffectStore`</td>
-
-<td rowspan="1" colSpan="1" >`class`</td>
-
-<td rowspan="1" colSpan="1" >Singleton data management class for audio effects. Use it to invoke audio effect APIs. After calling an API, the corresponding state property is automatically updated. Subscribe to this reactive state to receive and monitor updates.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`DeviceState`</td>
-
-<td rowspan="1" colSpan="1" >`struct`</td>
-
-<td rowspan="1" colSpan="1" >Represents the current state of the device module, typically used for UI rendering. Core properties include camera and microphone status.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`DeviceStore`</td>
-
-<td rowspan="1" colSpan="1" >`class`</td>
-
-<td rowspan="1" colSpan="1" >Singleton data management class for device operations. Use it to control the camera and microphone. After calling an API, the corresponding state property is automatically updated. Subscribe to this reactive state to receive and monitor updates.</td>
-</tr>
-</table>
-
+| **Core Concept** | **Type** | **Core Responsibility & Description** |
+| --- | --- | --- |
+| `AudioChangerType` | `enum` | Enumerates available voice changing effects, such as "child", "man", etc. |
+| `AudioReverbType` | `enum` | Enumerates available reverb effects, such as "ktv", "hall", etc. |
+| `AudioEffectState` | `struct` | Represents the current state of the audio effect module, typically used for UI rendering. Includes voice changing effect state, reverb state, ear monitoring enabled state, and ear monitor volume. |
+| `AudioEffectStore` | `class` | Singleton data management class for audio effects. Use it to invoke audio effect APIs. After calling an API, the corresponding state property is automatically updated. Subscribe to this reactive state to receive and monitor updates. |
+| `DeviceState` | `struct` | Represents the current state of the device module, typically used for UI rendering. Core properties include camera and microphone status. |
+| `DeviceStore` | `class` | Singleton data management class for device operations. Use it to control the camera and microphone. After calling an API, the corresponding state property is automatically updated. Subscribe to this reactive state to receive and monitor updates. |
 
 ## Implementation
 
 ### Step 1: Component Integration
-- **Video Live Streaming**: Please refer to [Quick Start](https://write.woa.com/document/194571606121816064) to integrate **AtomicXCore**.
-
-- **Voice Chat Room**: Please refer to [Quick Start](https://write.woa.com/document/194571595685527552) to integrate **AtomicXCore**.
+- **Video Live Streaming**: Please refer to Quick Start to integrate **AtomicXCore**.
 
+- **Voice Chat Room**: Please refer to Quick Start to integrate **AtomicXCore**.
 
 ### Step 2: Obtain Store Instances
 
@@ -100,11 +45,10 @@ let deviceStore = DeviceStore.shared
 In-ear monitoring allows users to hear their microphone audio in real time. Manage in-ear monitoring by calling the interfaces described below.
 
 > **Note:**
-> 
+>
 
 > In-ear monitoring typically requires headphones to function properly.
-> 
-
+>
 
 #### Implementation
 1. **Toggle Ear Monitoring**: Use a `UISwitch` control to enable or disable in-ear monitoring.
@@ -113,7 +57,6 @@ In-ear monitoring allows users to hear their microphone audio in real time. Mana
 
 3. **Subscribe to State Updates**: Listen for real-time ear monitor state changes to update the UI.
 
-
 #### Code Example
 ``` swift
 // 1. Enable ear monitoring
@@ -137,44 +80,14 @@ audioEffectStore.state
 ```
 
 #### setVoiceEarMonitorEnable Parameters
-<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" >Whether to enable ear monitoring.<br>- true: Enable<br>- false: Disable</td>
-</tr>
-</table>
-
+| **Parameter Name** | **Type** | **Description** |
+| --- | --- | --- |
+| `enable` | `Bool` | Whether to enable ear monitoring.<br>- true: Enable<br>- false: Disable |
 
 #### setVoiceEarMonitorVolume Parameters
-<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 monitor volume.<br>- Value range: [0, 150]<br>- Default: 100</td>
-</tr>
-</table>
-
+| **Parameter Name** | **Type** | **Description** |
+| --- | --- | --- |
+| `volume` | `Int` | Ear monitor volume.<br>- Value range: [0, 150]<br>- Default: 100 |
 
 ### Step 4: Implement Microphone Volume Adjustment
 
@@ -185,7 +98,6 @@ To adjust the microphone (capture) volume, call the `setCaptureVolume(volume:)`
 
 2. **Subscribe to State Updates**: Listen for real-time volume state changes to update the UI.
 
-
 #### Code Example
 ``` swift
 // 1. Adjust capture volume
@@ -203,24 +115,9 @@ deviceStore.state
 ```
 
 #### setCaptureVolume Parameters
-<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" >Microphone (capture) volume.<br>- Value range: [0, 150]<br>- Default: 100</td>
-</tr>
-</table>
-
+| **Parameter Name** | **Type** | **Description** |
+| --- | --- | --- |
+| `volume` | `Int` | Microphone (capture) volume.<br>- Value range: [0, 150]<br>- Default: 100 |
 
 ### Step 5: Implement Voice Effects
 
@@ -235,24 +132,9 @@ audioEffectStore.setAudioChangerType(type: .none)
 ```
 
 #### setAudioChangerType Parameters
-<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`</td>
-
-<td rowspan="1" colSpan="1" >Voice changer effect enumeration.</td>
-</tr>
-</table>
-
+| **Parameter Name** | **Type** | **Description** |
+| --- | --- | --- |
+| `type` | `AudioChangerType` | Voice changer effect enumeration. |
 
 ### Step 6: Implement Reverb Effects
 
@@ -265,33 +147,17 @@ audioEffectStore.setAudioReverbType(type: .none)
 ```
 
 #### setAudioReverbType Parameters
-<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`</td>
-
-<td rowspan="1" colSpan="1" >Reverb effect enumeration.</td>
-</tr>
-</table>
-
+| **Parameter Name** | **Type** | **Description** |
+| --- | --- | --- |
+| `type` | `AudioReverbType` | Reverb effect enumeration. |
 
 ### Step 7: Reset Audio Effect Settings
 
 > **Note：**
-> 
+>
 
 > AudioEffectStore and DeviceStore are singletons, so audio effect and device settings apply globally. To prevent settings from one live room affecting others, reset the audio effect and device settings when the current live room ends.
-> 
-
+>
 
 Reset audio effect settings in the following scenarios:
 1. When the current live room ends.
@@ -299,7 +165,7 @@ Reset audio effect settings in the following scenarios:
 2. To provide a "one-click restore" feature, call the store's `reset()` method.
 
    ``` swift
-   class YourMainViewController: UIViewController {    
+   class YourMainViewController: UIViewController {
        func reset() {
            AudioEffectStore.shared.reset()
            DeviceStore.shared.reset()
@@ -310,32 +176,10 @@ Reset audio effect settings in the following scenarios:
 ## API Documentation
 
 For detailed information on all public interfaces and properties of [AudioEffectStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/audioeffectstore), [DeviceStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/devicestore), and related classes, refer to the official API documentation for the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore) framework.
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Store/Component**</td>
-
-<td rowspan="1" colSpan="1" >**Description**</td>
-
-<td rowspan="1" colSpan="1" >**API Reference**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >DeviceStore</td>
-
-<td rowspan="1" colSpan="1" >Controls audio/video devices: microphone (on/off, volume), camera (on/off, switch, quality), screen sharing, and real-time device status monitoring.</td>
-
-<td rowspan="1" colSpan="1" >[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/devicestore)</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >AudioEffectStore</td>
-
-<td rowspan="1" colSpan="1" >Audio effects: voice changing (child/male), reverb (KTV, etc.), ear monitoring adjustment, and real-time effect switching.</td>
-
-<td rowspan="1" colSpan="1" >[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/audioeffectstore)</td>
-</tr>
-</table>
-
+| **Store/Component** | **Description** | **API Reference** |
+| --- | --- | --- |
+| DeviceStore | Controls audio/video devices: microphone (on/off, volume), camera (on/off, switch, quality), screen sharing, and real-time device status monitoring. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/devicestore) |
+| AudioEffectStore | Audio effects: voice changing (child/male), reverb (KTV, etc.), ear monitoring adjustment, and real-time effect switching. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/audioeffectstore) |
 
 ## FAQs
 
@@ -350,7 +194,6 @@ This is a common point of confusion:
 
 - **Ear Monitor Volume**: Set via `AudioEffectStore.setVoiceEarMonitorVolume()`.  It only determines the volume level you hear in your in-ear monitor and does not affect the audience.
 
-
 ### Why does a newly created live room already have audio effects, or why is the volume too high or too low?
 
 Because `AudioEffectStore` and `DeviceStore` are singletons, audio effect and device settings are globally applied. If you previously set audio effects and did not reset them, those settings persist. Call the `reset()` method at the appropriate time to clear them.
@@ -364,7 +207,6 @@ Check the following:
 
 3. **Is the microphone enabled?** Confirm that the microphone is enabled in DeviceStore (i.e., openLocalMicrophone has been called).
 
-
 ### Can voice effects and reverb be enabled at the same time?
 
-Yes. `AudioChangerType` and `AudioReverbType` can be enabled simultaneously. For example, you can set both `AudioChangerType.LITTLE_GIRL`and `AudioReverbType.KTV` at the same time.
+Yes. `AudioChangerType` and `AudioReverbType` can be enabled simultaneously. For example, you can set both `AudioChangerType.LITTLE_GIRL`and `AudioReverbType.KTV` at the same time.

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

@@ -1,8 +1,5 @@
 This document provides a comprehensive guide for iOS developers to quickly integrate a feature-rich, high-performance live chat overlay (barrage/danmaku) system into your live streaming application using the `BarrageStore` module from the **AtomicXCore** framework.
 
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027182498/17934b0bc6e111f087ad52540099c741.png)
-
-
 ## Core Features
 
 `BarrageStore` delivers a complete barrage solution for your live streaming app. Core features include:
@@ -14,50 +11,19 @@ This document provides a comprehensive guide for iOS developers to quickly integ
 
 - Inserting system tips into the local message list (for example, "Welcome XX to the live room").
 
-
 ## Core Concepts
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Core Concept**</td>
-
-<td rowspan="1" colSpan="1" >**Type**</td>
-
-<td rowspan="1" colSpan="1" >**Core Responsibility & Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >[Barrage](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barrage)</td>
-
-<td rowspan="1" colSpan="1" >struct</td>
-
-<td rowspan="1" colSpan="1" >Represents the data model for a single barrage message. Contains all essential information such as sender (sender), message content (textContent or data), message type (messageType), and more.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >[BarrageState](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestate)</td>
-
-<td rowspan="1" colSpan="1" >struct</td>
-
-<td rowspan="1" colSpan="1" >Represents the current state of the barrage module. The main property, messageList, is an array of [Barrage] storing all barrage messages in chronological order for the current live room. This serves as the data source for UI rendering.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >[BarrageStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestore)</td>
-
-<td rowspan="1" colSpan="1" >class</td>
-
-<td rowspan="1" colSpan="1" >The core management class for barrage functionality. Use it to send messages (sendTextMessage, sendCustomMessage), and subscribe to its state property to receive all barrage message updates.</td>
-</tr>
-</table>
-
+| **Core Concept** | **Type** | **Core Responsibility & Description** |
+| --- | --- | --- |
+| [Barrage](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barrage) | struct | Represents the data model for a single barrage message. Contains all essential information such as sender (sender), message content (textContent or data), message type (messageType), and more. |
+| [BarrageState](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestate) | struct | Represents the current state of the barrage module. The main property, messageList, is an array of [Barrage] storing all barrage messages in chronological order for the current live room. This serves as the data source for UI rendering. |
+| [BarrageStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestore) | class | The core management class for barrage functionality. Use it to send messages (sendTextMessage, sendCustomMessage), and subscribe to its state property to receive all barrage message updates. |
 
 ## Implementation
 
 ### Step 1: Component Integration
-- **Video Live Streaming**: Please refer to [Quick Start](https://write.woa.com/document/194571606121816064) to integrate AtomicXCore. Quick Start to
-
-- **Voice Chat Room**: Please refer to [Quick Start](https://write.woa.com/document/194571595685527552) to integrate AtomicXCore.
+- **Video Live Streaming**: Please refer to Quick Start to integrate AtomicXCore. Quick Start to
 
+- **Voice Chat Room**: Please refer to Quick Start to integrate AtomicXCore.
 
 ### Step 2: Initialize and Listen for Barrage
 
@@ -71,10 +37,10 @@ class BarrageManager {
     private let liveId: String
     private let barrageStore: BarrageStore
     private var cancellables = Set<AnyCancellable>()
-    
+
     // Publisher for the complete message list, for UI layer subscription
     let messagesPublisher = PassthroughSubject<[Barrage], Never>()
-    
+
     init(liveId: String) {
         self.liveId = liveId
         // 1. Obtain the BarrageStore singleton for the given liveId
@@ -82,7 +48,7 @@ class BarrageManager {
         // 2. Start listening for barrage messages immediately after initialization
         subscribeToBarrageUpdates()
     }
-    
+
     private func subscribeToBarrageUpdates() {
         barrageStore.state
             .subscribe() // Subscribe to all BarrageState changes
@@ -109,7 +75,7 @@ extension BarrageManager {
             print("Barrage content cannot be empty")
             return
         }
-        
+
         // Send the message using the core API
         barrageStore.sendTextMessage(text: text, extensionInfo: nil) { result in
             // Handle the result in the callback, e.g., show a prompt to the user
@@ -125,40 +91,11 @@ extension BarrageManager {
 ```
 
 #### API Parameters
-<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 send.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`extensionInfo`</td>
-
-<td rowspan="1" colSpan="1" >`[String: String]?`</td>
-
-<td rowspan="1" colSpan="1" >Additional extension information for business customization.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`completion`</td>
-
-<td rowspan="1" colSpan="1" >`CompletionClosure?`</td>
-
-<td rowspan="1" colSpan="1" >Callback after sending is complete, containing the success or failure result.</td>
-</tr>
-</table>
-
+| **Parameter** | **Type** | **Description** |
+| --- | --- | --- |
+| `text` | `String` | The text content to send. |
+| `extensionInfo` | `[String: String]?` | Additional extension information for business customization. |
+| `completion` | `CompletionClosure?` | Callback after sending is complete, containing the success or failure result. |
 
 ### Step 4: Send Custom Barrage
 
@@ -169,7 +106,7 @@ extension BarrageManager {
     func sendGiftMessage(giftId: String, giftCount: Int) {
         // 1. Define a business-recognizable ID
         let businessId = "live_gift"
-        
+
         // 2. Encode business data as a JSON string
         let giftData: [String: Any] = ["gift_id": giftId, "gift_count": giftCount]
         guard let jsonData = try? JSONSerialization.data(withJSONObject: giftData),
@@ -177,7 +114,7 @@ extension BarrageManager {
             print("Failed to encode gift data as JSON")
             return
         }
-        
+
         // 3. Send the custom message using the core API
         barrageStore.sendCustomMessage(businessID: businessId, data: jsonString) { result in
             switch result {
@@ -192,40 +129,11 @@ extension BarrageManager {
 ```
 
 #### API Parameters
-<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" >Unique business identifier, e.g., "live_gift", used by the receiver 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, usually a JSON-formatted string.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`completion`</td>
-
-<td rowspan="1" colSpan="1" >`CompletionClosure?`</td>
-
-<td rowspan="1" colSpan="1" >Callback after sending is complete.</td>
-</tr>
-</table>
-
+| **Parameter** | **Type** | **Description** |
+| --- | --- | --- |
+| `businessId` | `String` | Unique business identifier, e.g., "live_gift", used by the receiver to distinguish different custom messages. |
+| `data` | `String` | Business data, usually a JSON-formatted string. |
+| `completion` | `CompletionClosure?` | Callback after sending is complete. |
 
 ### Step 5: Insert Local Tip Message
 
@@ -239,7 +147,7 @@ extension BarrageManager {
         welcomeTip.messageType = .text // Reuse the text type for display
         welcomeTip.textContent = "Welcome \(user.userName) to the live room!"
         // sender can be left empty or set to a system user identifier
-        
+
         // 2. Insert the message into the local list
         barrageStore.appendLocalTip(message: welcomeTip)
     }
@@ -247,24 +155,9 @@ extension BarrageManager {
 ```
 
 #### API Parameters
-<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" >message</td>
-
-<td rowspan="1" colSpan="1" >Barrage</td>
-
-<td rowspan="1" colSpan="1" >The message object to insert locally. The SDK appends this message to the messageList in BarrageState.</td>
-</tr>
-</table>
-
+| **Parameter** | **Type** | **Description** |
+| --- | --- | --- |
+| message | Barrage | The message object to insert locally. The SDK appends this message to the messageList in BarrageState. |
 
 ### Step 6: Manage User Speaking Permissions (Mute and Unmute)
 
@@ -305,7 +198,7 @@ import AtomicXCore
 let liveListStore = LiveListStore.shared
 
 // 2. Get the current live room info and modify the global mute status
-var currentLiveInfo = liveListStore.state.value.currentLive 
+var currentLiveInfo = liveListStore.state.value.currentLive
 currentLiveInfo.isMessageDisable = true // true to enable global mute, false to disable
 
 // 3. Call the update API and specify the modify flag
@@ -400,7 +293,7 @@ class BarrageUIManager {
 
     private func refreshUIIfNeeded() {
         guard let fullList = self.latestMessageList, let tableView = self.tableView else { return }
-        self.latestMessageList = nil 
+        self.latestMessageList = nil
 
         // Only keep the latest N messages
         let cappedList = Array(fullList.suffix(self.capacity))
@@ -468,7 +361,7 @@ For detailed information on all public interfaces, properties, and methods of [B
 
 ### In addition to basic text barrages, we also want to implement richer styles such as "colored barrages" and "gift barrages." How can we achieve this?
 
-You can implement these features using custom messages with `sendCustomMessage`. 
+You can implement these features using custom messages with `sendCustomMessage`.
 
 **Implementation Steps**
 1. **Define the Data Structure**: Collaborate with your client and server teams to define the JSON structure for custom messages. For example, a colored barrage can be defined as:
@@ -480,7 +373,6 @@ You can implement these features using custom messages with `sendCustomMessage`.
 
 3. **Receiver**: Upon receiving a barrage message, check whether its messageType is `BarrageType.CUSTOM` and whether the `businessID` matches. If so, parse the data string (usually as JSON), and render your custom UI style based on the parsed data (such as `color`, `text`).
 
-
 ### If I call BarrageStore.create(liveID = "some_id") in different classes or files, will this create multiple instances and cause confusion?
 
 No. The internal mechanism of **AtomicXCore** ensures that as long as you pass in the same liveID, you always get the same `BarrageStore` instance for that live room. You do not need to manage singletons manually.
@@ -496,7 +388,6 @@ No. The internal mechanism of **AtomicXCore** ensures that as long as you pass i
 
 4. **Network issues**: Ensure the device's network connection is normal. Message sending depends on network connectivity.
 
-
 ### How can new viewers see historical barrage messages sent before they joined the live room?
 
 `AtomicXCore` supports retrieving historical chat messages, but you need to enable this feature in the **server console**. Once configured, the SDK handles everything automatically—no additional client code is required.
@@ -506,12 +397,8 @@ No. The internal mechanism of **AtomicXCore** ensures that as long as you pass i
 
 2. On the Live Configuration page, select **View Past Messages**, and set Previous Messages Viewable to specify the number of messages (up to a maximum of 50) that new viewers can see.
 
-
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027202808/5ca7e8c2e20c11f095b0525400e889b2.png)
-
-
 #### **Step 2: Automatic Retrieval on the Client Side**
 
 After completing the above configuration, **no changes are needed** in your client code.
 
-When a new user joins the live room, `AtomicXCore` automatically retrieves the configured number of historical chat messages in the background. These messages are delivered to the UI layer through the `BarrageState` subscription channel, just like real-time messages. Your application will receive and display these historical chat messages in the same way as live messages.
+When a new user joins the live room, `AtomicXCore` automatically retrieves the configured number of historical chat messages in the background. These messages are delivered to the UI layer through the `BarrageState` subscription channel, just like real-time messages. Your application will receive and display these historical chat messages in the same way as live messages.