> 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/nl/idiomatic-notation/keyboard/cross-staff-notation.md).

# Notatie over meerdere notenbalken

## Notatie over meerdere notenbalken maken

1. Voer allereerst de notatie in op slechts één notenbalk.
2. Select a note in the [voice](/nl/basics/working-with-multiple-voices.md) that you wish to move up or down to the other staff, e.g.\
   ![](https://2553961276-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzCoPXZFszsH4FraEIMtt%2Fuploads%2Fgit-blob-e291ecef39d7a3227afe60da2b2342538bb17ceb%2Fcross-staff1.png?alt=media)
3. Press <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>Up</kbd>/<kbd>Down</kbd> (Mac: <kbd>Cmd</kbd>+<kbd>Shift</kbd>+<kbd>Up</kbd>/<kbd>Down</kbd>), to move the voice up or down to the other staff. Alternatively, you can click on the cross-staff icon in the toolbar and choose the same options from the context menu.\
   ![](https://2553961276-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzCoPXZFszsH4FraEIMtt%2Fuploads%2Fgit-blob-dca15db80e36dccfaff6c082f6e66a6c6295896a%2Fcross-staff2.png?alt=media)

**Opmerking**: Momenteel is het niet mogelijk om individuele noten van een akkoord van de ene notenbalk naar de andere te verplaatsen; als je één noot verplaatst, verplaatst het hele akkoord. Daarom moeten bepaalde noten, als je ze op de oorspronkelijke notenbalk wilt behouden, naar een andere stem worden verplaatst. Houd er ook rekening mee dat noten die op deze manier naar een andere notenbalk worden verplaatst, logischerwijs nog steeds bij de oorspronkelijke notenbalk horen – ze worden alleen op een andere notenbalk getekend. Dit is de reden waarom er geen rust wordt weergegeven op de notenbalk waar de noten vandaan zijn verplaatst.

## Zie ook

[Hoe maak je een akkoord of stok over twee notenbalken](https://musescore.org/en/node/8717)

<figure><img src="https://2553961276-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzCoPXZFszsH4FraEIMtt%2Fuploads%2Fgit-blob-527e4458eaa5052723f86d387e2d0c512bf140e3%2Flongstem2.png?alt=media" alt="Longstem2"><figcaption></figcaption></figure>


---

# 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/nl/idiomatic-notation/keyboard/cross-staff-notation.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.
