> 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/de/notation/pitch/respell-pitches.md).

# Respell pitches

## Manually changing the enharmonic spelling of notes

To change the enharmonic spelling of a note, or notes, in both written *and* concert pitch views:

1. Select a note, or group of notes
2. Press `J`
3. Continue pressing `J` to cycle through the enharmonic equivalents.

To change the enharmonic spelling in the written pitch view, without affecting the concert pitch view, or vice versa:

1. Select a note, or group of notes
2. Press `Ctrl`+`J` (Mac: `Cmd`+`J`)
3. Continue pressing the same combination of keys to cycle through the enharmonic equivalents.

**Note:** If the pitches of selected notes are not all the same, the effect may be unpredictable.

## Automatically respelling all notes in a selection

### Respell pitches

* From the menu, select **Tool -> Respell Pitches**.


---

# 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/de/notation/pitch/respell-pitches.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.