> 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/guides/guides-zh/bian-ji-ji-cheng/jiang-shade-yuan-shu-ju-fa-song-dao-ni-de-jian-ji-ying-yong-cheng-xu.md).

# 将 Shade 元数据发送到你的剪辑应用程序

将标签、描述、状态和精选内容从 Shade 带入 Premiere Pro、Resolve 或 Avid 的素材箱。

**结果：** 在 Shade 中完成的日志工作，例如 AI 标签、描述、评分和状态，会作为列显示在你的剪辑软件的素材箱中，因此剪辑师无需切换应用即可对素材进行排序和搜索。

**适用对象：** 在 Shade 中做日志并在 Premiere Pro、DaVinci Resolve 或 Avid Media Composer 中剪辑的助理剪辑师和剪辑师。

**时间：** 大约 10 分钟。

## 开始之前

* 填写你想要保留的字段。AI 填充的字段也可以。参见 [元数据和自定义字段](https://academy.shade.inc/ai-tools/custom-and-automated-metadata).
* 从已挂载的 Shade 驱动器中将同一媒体导入到你的剪辑软件中。导出会与剪辑一一匹配，因此这些剪辑必须是相同的文件。

## 步骤

{% stepper %}
{% step %}

### 仅用你想要的列构建一个视图

创建一个视图，或打开现有视图，并只显示剪辑师需要的字段，例如描述、标签、镜头类型、评分和状态。按你正在处理的素材进行筛选。下一步你将从这个视图导出。
{% endstep %}

{% step %}

### 使用剪辑软件的预设导出

打开视图的 **更多选项** (**…**) 菜单，选择 **导出**，然后选择预设：

* **Premiere Pro**：导出 ALE 文件
* **Avid Media Composer**：导出 ALE 文件
* **DaVinci Resolve**：导出 CSV 文件

CSV、TXT、ALE 和 TSV 也可用于其他工具。在合集里，相同选项位于合集的下载菜单中。
{% endstep %}

{% step %}

### 导入到你的剪辑软件中

* **Premiere Pro 和 Avid：** 将 ALE 导入到项目中。元数据会合并到名称匹配的剪辑上。
* **DaVinci Resolve：** 在媒体池中选择剪辑，然后导入 CSV 元数据。在导入选项中，关闭 **使用剪辑起始和结束时间码进行匹配**，否则剪辑将无法匹配。
  {% endstep %}
  {% endstepper %}

## 变体

* **评论，而不是元数据：** 从评论面板菜单导出审阅评论。Resolve 用户可以选择 **导出到 Resolve（EDL）** 将注释作为时间线标记导入。参见 [客户审阅流程](/guides/guides-zh/shen-he-he-ke-hu-jiao-fu/ke-hu-shen-yue-liu-cheng.md).
* **字幕和脚本：** 从素材的 **转录** 面板中将转录内容导出为 SRT、VTT 或 ScriptSync。

## 相关指南

* [通过 ShadeFS 远程编辑](/guides/guides-zh/bian-ji-ji-cheng/tong-guo-shadefs-yuan-cheng-bian-ji.md)
* [设计可扩展的元数据架构](/guides/guides-zh/zi-ding-yi-dui-xiang-he-yuan-shu-ju/she-ji-ke-kuo-zhan-de-yuan-shu-ju-jia-gou.md)
* [构建可搜索的存档](/guides/guides-zh/sou-suo-ai-he-dang-an/gou-jian-ke-sou-suo-de-gui-dang.md)


---

# 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/guides/guides-zh/bian-ji-ji-cheng/jiang-shade-yuan-shu-ju-fa-song-dao-ni-de-jian-ji-ying-yong-cheng-xu.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.