> For the complete documentation index, see [llms.txt](https://rogodigital.gitbook.io/lipsync-pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rogodigital.gitbook.io/lipsync-pro/editor-windows-and-inspectors/project-settings.md).

# Project Settings

The **Project Settings** asset contains several project-specific settings for LipSync Pro. You can find the file in your Project panel in the *Rogo Digital/LipSync Pro* folder, or from the [Clip Editor](/lipsync-pro/editor-windows-and-inspectors/clip-editor.md) by clicking *File > Project Settings*.

![The default Project Settings asset is it comes in a clean installation](/files/-MKEy0HBTPJy8d6saOvp)

In the **Phoneme Set** field, you can assign a [Phoneme Set](/lipsync-pro/concepts-and-components/phoneme-sets.md) asset to control the available Phonemes. 

Under the **Animation Emotions** section you can add, remove or modify the [Emotions ](/lipsync-pro/concepts-and-components/lipsyncdata/markers.md#emotion-markers)that are available for use in your project. The name of an emotion can be changed by simply clicking on the name label in the list and typing, you can use the colour picker in the centre of the row to change the colour used for this emotion in the [Clip Editor](/lipsync-pro/editor-windows-and-inspectors/clip-editor.md).

The **Animation Gestures** section is similar, except for [Gestures](/lipsync-pro/concepts-and-components/lipsyncdata/markers.md#gesture-markers). The only difference is gestures don't have an associated colour, so only the name field is included.

{% hint style="warning" %}
**Warning:** changing the name of an emotion or gesture will break existing references to it in [LipSyncData ](/lipsync-pro/concepts-and-components/lipsyncdata.md)clips and on [LipSync ](/lipsync-pro/concepts-and-components/lipsync.md)components.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://rogodigital.gitbook.io/lipsync-pro/editor-windows-and-inspectors/project-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.