> 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-es/proyecto/mixing/effects/room-effect.md).
# Efecto de sala
Sitúa a los cantantes en una sala virtual sobre las Pistas vocales.
El **Efecto de sala** coloca Voces de IA en un espacio físico compartido, principalmente para posicionar varias voces juntas. Es **no** parte de la cadena de FX y está disponible en **solo Pistas vocales** — se sitúa aparte de [Efectos integrados](/docs/product-wiki-es/proyecto/mixing/effects/built-in-effects.md) y [Efectos de terceros](/docs/product-wiki-es/proyecto/mixing/effects/third-party-effects.md).
Room Effect depende de un componente instalado por separado. Se te pedirá instalarlo la primera vez que lo uses.
### Posicionar voces
En el centro de Room Effect, ves el espacio de grabación virtual.
Cada marcador de color representa una Voz.
* Arrastra un marcador para mover esa Voz por la sala.
* La distancia respecto a la línea discontinua controla lo cerca que esa Voz está del micrófono.
### Elige un tamaño de sala
Usa el control de la esquina superior derecha para cambiar el tamaño de la sala:
* **8 m × 8 m** — Sala de estudio.
* **16 m × 16 m** — Sala de Coro.
* **30 m × 30 m** — Iglesia.
---
# 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-es/proyecto/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.
