> For the complete documentation index, see [llms.txt](https://handbook.musescore.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.musescore.org/fr/notation/pitch/ambitus.md).

# Ambitus

An ambitus indicates the range of notes included within a staff. It is used to indicate the appropriate voice for a particular part. (See [Ambitus](https://en.wikipedia.org/wiki/Ambitus_\(music\)) on Wikipedia.)

## Adding an ambitus to your score

To create an ambitus, use either of these methods:

* Select the desired start clef and click on the ambitus symbol in either the **Pitch** or **Lines** palette
* Drag the ambitus symbol from either the **Pitch** or **Lines** palette and drop it onto the desired start clef.

## Changing the range of an ambitus

You can change the range of an ambitus via the **Properties** panel.

To update manually, set the values for **Top note** and **Bottom note** as required.

To do so automatically, click the **Update to match the notes on the staff** button.

## Ambitus properties

These properties are also available in the **Properties** panel (under **Show more**):

* **Direction**
* **Notehead type** and **Notehead duration**
* **Line thickness**


---

# 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://handbook.musescore.org/fr/notation/pitch/ambitus.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.