> For the complete documentation index, see [llms.txt](https://docs.acestudio.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acestudio.ai/docs/product-wiki-zh/gong-cheng/mixing/effects/room-effect.md).
# 房间效果
在虚拟房间中为人声轨道定位歌手。
该 **房间效果** 将 AI 声线置于共享的物理空间中，主要用于将多条声线一起定位。它是 **不** FX 链的一部分，并且仅适用于 **人声轨道** ——它独立于 [内置效果](/docs/product-wiki-zh/gong-cheng/mixing/effects/built-in-effects.md) 和 [第三方效果](/docs/product-wiki-zh/gong-cheng/mixing/effects/third-party-effects.md).
Room Effect 依赖一个单独安装的组件。首次使用时会提示你安装。
### 定位声线
在 Room Effect 的中心，你会看到虚拟录音空间。
每个彩色标记代表一条声线。
* 拖动标记即可在空间中移动对应的声线。
* 与虚线的距离决定了该声线离麦克风有多近。
### 选择房间大小
使用右上角的控制项切换房间大小：
* **8 米 × 8 米** ——录音棚。
* **16 米 × 16 米** ——合唱厅。
* **30 米 × 30 米** ——教堂。
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.acestudio.ai/docs/product-wiki-zh/gong-cheng/mixing/effects/room-effect.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
