> 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/renderizando-con-ia/cloud-rendering.md).

# Renderizando en la nube

Presentamos la técnica de Renderizando en la nube de ACE Studio.

Renderizando en la nube permite a los usuarios procesar todas las tareas de renderizado a través de servidores en la nube, garantizando un rendimiento constante independientemente de las especificaciones del dispositivo local.

## Momento de Renderizando

El Renderizando en la nube comienza cuando se inicia la reproducción. Algunos parámetros, como AI-pitch, se renderizan previamente cuando se activan las herramientas de edición correspondientes.

## Estado de Renderizando

Los fragmentos no renderizados se marcan con una llave gris dentro de la regla de tiempo.

Un Clip pulsará si se está renderizando.

## Ámbito de Renderizando

{% tabs %}
{% tab title="Modelos V2" %}
El Modelo detecta dinámicamente el Rango de renderizado. Cuando se modifica un área pequeña, solo se volverá a renderizar el área modificada.
{% endtab %}

{% tab title="Modelos V1" %}
El Modelo renderiza pieza por pieza. La duración de cada pieza es aproximadamente equivalente a una frase musical (si la frase es más larga de 15 s, se usará Dividir). Cuando se realiza un cambio en una pieza o en una pieza conectada, se volverá a renderizar.
{% endtab %}
{% endtabs %}


---

# 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/renderizando-con-ia/cloud-rendering.md?ask=<question>&goal=<user_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.