> 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/instrumentos/create-instrument-sounds/expression-controls.md).
# Controles de expresión
Descubre los Controles de expresión del Instrumento AI de ACE Studio.
## ¿Qué son los Controles de expresión?
Los Controles de expresión son Parámetros que puedes automatizar a lo largo del tiempo para añadir matices y realismo, permitiéndote "pintar" dónde debe estar activo un efecto.
### Controles disponibles
Vibrato
Vibrato es una fluctuación sutil y rápida en la altura de una nota, que añade calidez, expresión y riqueza al sonido.
Dividir-tonos
Dividir-tonos es una técnica avanzada que crea un sonido áspero y texturizado al producir múltiples alturas simultáneamente. Es perfecta para añadir un carácter crudo y contundente o una sensación de Tensión a tu melodía.
## Edición de Controles de expresión
1. Selecciona el Control de expresión debajo de Piano Roll.
2. Haz clic y arrastra para "pintar" las regiones que deseas activar.
3. Simplemente haz clic derecho y arrastra sobre una región activa para borrarla.
---
# 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/instrumentos/create-instrument-sounds/expression-controls.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.
