> 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-fr/outils-dia/exporting-metadata-into-your-nle.md).

# Exportation des métadonnées vers votre NLE

Comment exporter facilement n’importe quelle vue vers votre NLE

Shade prend en charge l’exportation des métadonnées au format CSV, TXT, ALE et TSV, ainsi que des préréglages pour **Premiere Pro**, **DaVinci Resolve**, et **Avid Media Composer** (les préréglages Premiere Pro et Avid exportent un fichier ALE ; le préréglage DaVinci Resolve exporte un CSV). Pour exporter, ouvrez la vue ou le dossier souhaité, cliquez sur le **Plus d’options** menu (…) , choisissez **Exporter**, puis choisissez un format. Dans une collection, les mêmes options d’export se trouvent dans le menu de téléchargement de la collection.

<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>

## Remarques spécifiques pour importer correctement des médias dans Davinci Resolve

Pour importer les métadonnées Shade dans Davinci Resolve, assurez-vous de désactiver « Match using clip start and end Timecode ». Cela se trouve en important d’abord les métadonnées dans l’ensemble du pool de médias (ou les clips sélectionnés)

<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>

Puis en décochant explicitement la case des timecodes de début et de 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-fr/outils-dia/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.