@tencent-rtc/mcp 1.3.9 → 1.4.0

package/resource/doc/livekit/{voice → core-sdk/voice}/ios/voice-audience-list.md

@@ -1,8 +1,5 @@
 `LiveAudienceStore` is a module in `AtomicXCore` designed for managing audience information in live streaming rooms. With `LiveAudienceStore`, you can implement a comprehensive audience list and management system for your live streaming application.
 
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027182498/9013fb14c6b611f087ad52540099c741.png)
-
-
 ## Core Features
 - **Real-Time Audience List**: Fetch and display the list of users currently in the room.
 
@@ -14,72 +11,34 @@
 
 - **Room Management**: The host or administrator can remove specific viewers from 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 Responsibilities & Description**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`LiveUserInfo`</td>
-
-<td rowspan="1" colSpan="1" >`class`</td>
-
-<td rowspan="1" colSpan="1" >- Data model representing a viewer.<br>- Contains basic profile information such as userID, userName, and avatarURL.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`LiveAudienceState`</td>
-
-<td rowspan="1" colSpan="1" >`struct`</td>
-
-<td rowspan="1" colSpan="1" >- State container for the audience module.<br>- Exposes `audienceList` (StateFlow) for the real-time user list and `audienceCount` for the total viewer count.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`LiveAudienceEvent`</td>
-
-<td rowspan="1" colSpan="1" >`enum`</td>
-
-<td rowspan="1" colSpan="1" >- Event listener for audience changes.<br>- Provides callbacks like `.onAudienceJoined` and` .onAudienceLeft` to handle incremental list updates.</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`LiveAudienceStore`</td>
-
-<td rowspan="1" colSpan="1" >`class`</td>
-
-<td rowspan="1" colSpan="1" >- Primary interface for audience management.<br>- Used to fetch list snapshots, perform admin operations (e.g., kicking users), and subscribe to real-time events.</td>
-</tr>
-</table>
-
+| **Core Concept** | **Type** | **Core Responsibilities & Description** |
+| --- | --- | --- |
+| `LiveUserInfo` | `class` | - Data model representing a viewer.<br>- Contains basic profile information such as userID, userName, and avatarURL. |
+| `LiveAudienceState` | `struct` | - State container for the audience module.<br>- Exposes `audienceList` (StateFlow) for the real-time user list and `audienceCount` for the total viewer count. |
+| `LiveAudienceEvent` | `enum` | - Event listener for audience changes.<br>- Provides callbacks like `.onAudienceJoined` and` .onAudienceLeft` to handle incremental list updates. |
+| `LiveAudienceStore` | `class` | - Primary interface for audience management.<br>- Used to fetch list snapshots, perform admin operations (e.g., kicking users), and subscribe to real-time events. |
 
 ## 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: Initialize and Retrieve the Audience List
 
-Get a `LiveAudienceStore` instance linked to the `liveId` and fetch the initial audience snapshot. 
+Get a `LiveAudienceStore` instance linked to the `liveId` and fetch the initial audience snapshot.
 ``` swift
 import Foundation
-import AtomicXCore 
-import Combine     
+import AtomicXCore
+import Combine
 
 class AudienceManager {
     private let liveId: String
     private let audienceStore: LiveAudienceStore
     private var cancellables = Set<AnyCancellable>()
-    
+
     // Expose the [full] audience list publisher for UI layer subscription
     let audienceListPublisher = CurrentValueSubject<[LiveUserInfo], Never>([])
     // Expose the audience count publisher
@@ -89,11 +48,11 @@ class AudienceManager {
         self.liveId = liveId
         // 1. Get the LiveAudienceStore instance by liveId
         self.audienceStore = LiveAudienceStore.create(liveID: liveId)
-        
+
         // 2. Subscribe to state and events
         subscribeToAudienceState()
         subscribeToAudienceEvents()
-        
+
         // 3. Proactively fetch initial data for the first screen
         fetchInitialAudienceList()
     }
@@ -110,7 +69,7 @@ class AudienceManager {
             }
         }
     }
-    
+
     // ... subsequent code
 }
 ```
@@ -140,9 +99,9 @@ extension AudienceManager {
             .receive(on: DispatchQueue.main)
             .sink { [weak self] event in
                 guard let self = self else { return }
-                
+
                 var currentList = self.audienceListPublisher.value
-                
+
                 switch event {
                 case .onAudienceJoined(let newAudience):
                     print("Audience \(newAudience.userName) joined the live room")
@@ -151,7 +110,7 @@ extension AudienceManager {
                         currentList.append(newAudience)
                         self.audienceListPublisher.send(currentList)
                     }
-                    
+
                 case .onAudienceLeft(let departedAudience):
                     print("Audience \(departedAudience.userName) left the live room")
                     // Incremental update: remove the departed audience member from the current list
@@ -225,32 +184,32 @@ When a new audience member enters the live room, a welcome message is automatica
 
    ``` swift
    import Foundation
-   import AtomicXCore 
+   import AtomicXCore
    import Combine
-   
+
    class LiveRoomManager {
        private let liveId: String
        private let audienceManager: AudienceManager
        private let barrageManager: BarrageManager // Assume you have implemented BarrageManager as described in the barrage documentation
        private var cancellables = Set<AnyCancellable>()
-   
+
        init(liveId: String) {
            self.liveId = liveId
            // Initialize two core managers
            self.audienceManager = AudienceManager(liveId: liveId)
            self.barrageManager = BarrageManager(liveId: liveId)
-   
+
            // Set up linkage
            setupWelcomeMessageFlow()
        }
-   
+
        private func setupWelcomeMessageFlow() {
            // 1. Get the LiveAudienceStore instance
            let audienceStore = LiveAudienceStore.create(liveID: self.liveId)
-   
+
            // 2. Get the BarrageStore instance (thanks to internal mechanisms, this will be the same instance)
            let barrageStore = BarrageStore.create(liveID: self.liveId)
-   
+
            // 3. Subscribe to audience events
            audienceStore.liveAudienceEventPublisher
                .receive(on: DispatchQueue.main)
@@ -259,12 +218,12 @@ When a new audience member enters the live room, a welcome message is automatica
                    guard case .onAudienceJoined(let newAudience) = event else {
                        return
                    }
-   
+
                    // 5. Create a local tip message
                    var welcomeTip = Barrage()
-                   welcomeTip.messageType = .text 
+                   welcomeTip.messageType = .text
                    welcomeTip.textContent = "Welcome \(newAudience.userName) to the live room!"
-   
+
                    // 6. Call BarrageStore's API to insert it into the barrage list
                    barrageStore.appendLocalTip(message: welcomeTip)
                }
@@ -276,40 +235,11 @@ When a new audience member enters the live room, a welcome message is automatica
 ## API Documentation
 
 For detailed information on all public interfaces, properties, and methods of [LiveAudienceStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveaudiencestore) and its related classes, refer to the official API documentation included with the [AtomicX Core](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore) framework. The relevant Stores used in this document are as follows:
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >**Store/Component**</td>
-
-<td rowspan="1" colSpan="1" >**Feature Description**</td>
-
-<td rowspan="1" colSpan="1" >**API Documentation**</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >LiveCoreView</td>
-
-<td rowspan="1" colSpan="1" >Core view component for live video stream display and interaction: responsible for video stream rendering and view widget handling, supporting scenarios such as host streaming, audience co-hosting, and host-to-host connection.</td>
-
-<td rowspan="1" colSpan="1" >[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/livecoreview)</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >LiveAudienceStore</td>
-
-<td rowspan="1" colSpan="1" >Audience management: obtain real-time audience list (ID / name / avatar), count audience numbers, and listen for audience join/leave events.</td>
-
-<td rowspan="1" colSpan="1" >[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveaudiencestore)</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >BarrageStore</td>
-
-<td rowspan="1" colSpan="1" >Barrage feature: send text/custom barrage, maintain barrage list, and listen to barrage status in real time.</td>
-
-<td rowspan="1" colSpan="1" >[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestore)</td>
-</tr>
-</table>
-
+| **Store/Component** | **Feature Description** | **API Documentation** |
+| --- | --- | --- |
+| LiveCoreView | Core view component for live video stream display and interaction: responsible for video stream rendering and view widget handling, supporting scenarios such as host streaming, audience co-hosting, and host-to-host connection. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/livecoreview) |
+| LiveAudienceStore | Audience management: obtain real-time audience list (ID / name / avatar), count audience numbers, and listen for audience join/leave events. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveaudiencestore) |
+| BarrageStore | Barrage feature: send text/custom barrage, maintain barrage list, and listen to barrage status in real time. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestore) |
 
 ## FAQs
 
@@ -321,19 +251,13 @@ The `audienceCount` is a high-precision estimate. Updates occur based on specifi
 - **Unexpected Disconnection (Delayed)**:If a user disconnects abnormally (e.g., app crash, network loss), the system uses a heartbeat mechanism to verify status. The user is marked offline only after 90 seconds of inactivity, triggering a delayed count update.
 
 - **Frequency Control & Rate Limiting**: Audience count updates are broadcast as room messages. The system enforces a limit of 40 messages per second per room.
-   
 
    > **Note：**
-   > 
+   >
 
    > During high-traffic spikes (e.g., chat floods or rapid gifting), if the message rate exceeds this threshold, the system prioritizes core messages (like chat/barrage). Consequently, audience count update messages may be dropped to maintain stability.
-   > 
+   >
 
 - **What does this mean for developers?**
 
-
    Treat `audienceCount` as a metric for UI display purposes only. Do not rely on it for billing, critical statistics, or scenarios requiring 100% accuracy, as brief delays or data loss may occur during high-concurrency events.
-
-
-
-

package/resource/doc/livekit/{voice → core-sdk/voice}/ios/voice-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.