> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/getting-started/add-lip-sync/create-a-lip-sync-profile.md).

# 创建口型同步配置文件

说明如何为超出 SDK 默认捆绑的三个配置文件之外的 BlendShape 格式创建自定义口型同步配置文件资源。

唇形同步配置文件定义了传输格式标识符——它告诉 SDK 应该从 Convai 期望哪些 blendshape 通道名称。

{% hint style="warning" %}
Convai 目前仅以三种格式流式传输 blendshape 数据： `arkit`, `metahuman`，以及 `cc4_extended`。只有在 Convai 明确为你的部署支持自定义格式时，自定义配置文件才有用。使用不受支持的格式 ID 创建配置文件将导致无法接收到任何 blendshape 数据。
{% endhint %}

对于所有标准设置，请使用三个内置配置文件之一，并将此页面留作高级或未来用途。

{% stepper %}
{% step %}

#### 创建资源

在 Project 窗口中，导航到你想存储该配置文件的文件夹。右键单击并选择 **创建 > Convai > Lip Sync > Profile**。请为该资源起一个具有描述性的名称——例如， `ConvaiLipSyncProfile_MyRig`.
{% endstep %}

{% step %}

#### 配置字段

选择新资源以在 Inspector 中打开它。

| 字段          | 说明                                      |
| ----------- | --------------------------------------- |
| **配置文件 ID** | 传输格式标识符。必须与 Convai 为此角色流式传输的格式 ID 完全匹配。 |
| **显示名称**    | 在 Inspector 中显示的人类可读名称。不会影响运行时行为。       |
| **传输格式**    | 网络传输格式字符串——通常与配置文件 ID 相同。               |

{% hint style="danger" %}
**配置文件 ID** 必须与 Convai 在流式传输 blendshape 数据时使用的标识符完全匹配。不匹配会导致 SDK 回退到空操作映射——不会驱动任何 blendshape。
{% endhint %}
{% endstep %}

{% step %}

#### 将配置文件 ID 分配给组件

设置 `ConvaiLipSyncComponent._lockedProfileId` 到 **配置文件 ID** 你定义的字符串。SDK 会在运行时从注册表中查找此配置文件。
{% endstep %}
{% endstepper %}

### 下一步

创建配置文件后，再创建一个映射，将其通道路由到你的绑定角色的 blendshape 名称。

{% content-ref url="/pages/0808b43e9ba988a5156bb5fb55261f1f67638b57" %}
[创建自定义口型同步映射](/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/getting-started/add-lip-sync/create-a-custom-blendshape-map.md)
{% endcontent-ref %}


---

# 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.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/getting-started/add-lip-sync/create-a-lip-sync-profile.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.