> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/shade-academy/shade-academy-es/herramientas-de-ia/exporting-metadata-into-your-nle.md).

# Exportar metadatos a tu NLE

Cómo exportar fácilmente cualquier vista a tu NLE

Shade admite la exportación de metadatos como archivos CSV, TXT, ALE y TSV, además de preajustes para **Premiere Pro**, **DaVinci Resolve**, y **Avid Media Composer** (los preajustes de Premiere Pro y Avid exportan un archivo ALE; el preajuste de DaVinci Resolve exporta un CSV). Para exportar, abre la vista o carpeta que desees, haz clic en el **Más opciones** menú (…), elige **Exportar**, y elige un formato. En una colección, las mismas opciones de exportación están en el menú de descarga de la colección.

<figure><img src="https://450378260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUNq6h2Bfw7aAK0J2ffnZ%2Fuploads%2F6BjhOfQyIiP08w6orLrO%2FScreenshot%202025-02-19%20at%2011.38.33%E2%80%AFAM.png?alt=media&#x26;token=a1836d12-190f-43b9-9b94-956bef56c44d" alt=""><figcaption></figcaption></figure>

## Notas específicas para importar correctamente medios en DaVinci Resolve

Para importar metadatos de Shade en DaVinci Resolve, asegúrate de desactivar "Coincidir usando el código de tiempo de inicio y fin del clip". Esto se puede encontrar primero importando metadatos a todo el grupo multimedia (o a los clips seleccionados)

<figure><img src="https://450378260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUNq6h2Bfw7aAK0J2ffnZ%2Fuploads%2F2Km5GqnFM2fzIZdcXYKA%2FScreenshot%202025-02-19%20at%2011.39.20%E2%80%AFAM.png?alt=media&#x26;token=e6c41288-bd64-401f-b786-ad0b8f71f6b1" alt="" width="375"><figcaption></figcaption></figure>

Y luego desmarcando explícitamente la casilla del código de tiempo de inicio y fin.

<figure><img src="https://450378260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUNq6h2Bfw7aAK0J2ffnZ%2Fuploads%2FCF0x4bsjY5v4P7nZCz5v%2FScreenshot%202025-02-19%20at%2011.41.00%E2%80%AFAM.png?alt=media&#x26;token=af6a2a59-ffc1-448a-ac19-0afeef662df9" alt=""><figcaption></figcaption></figure>


---

# 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://academy.shade.inc/shade-academy/shade-academy-es/herramientas-de-ia/exporting-metadata-into-your-nle.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.
