> 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/3/sound-and-playback/dynamics.md).

# Dynamics

[Dynamics of a piece](https://w.wiki/8Jpm) is the variation in loudness and timbre between notes or phrases. This chapter covers **Dynamics** [Text](/3/text/text-types.md) that can change note playback loudness inside the program. [Hairpin](/3/notation/hairpins.md) and [Articulations](/3/notation/articulations-and-ornaments.md) (eg Accent >, Marcato ^) score objects also affect dynamics. [Overriding setting can be assigned](#loudness-of-a-note) to note directly.

## Adding a dynamic to the score

<figure><img src="/files/RpYaE2VUGXxGQbWMWRCU" alt="Dynamics palette (Advanced)"><figcaption></figcaption></figure>

Dynamics symbols can be found in **Dynamics** [**palette**](/3/basics/palettes.md). Additional symbols are available in the [Master Palette](/3/advanced-topics/master-palette.md) (<kbd>Shift</kbd>+<kbd>F9</kbd>). To apply a dynamic to the score, either,

* Select a note and click a dynamic symbol in a palette (double-click in versions prior to 3.4),
* Drag a dynamic symbol from a palette onto a note, or
* Set up and use keyboard shortcuts with the [Dynamics actions](https://musescore.org/en/project/dynamics-actions) plugin.

**NOTE:**

* Applying new symbol does not replace exisiting score item.
* Placing multiple symbols on voices at the same time position does not create desired playback, because the minimal area of effect ([**Dynamic Range** property](#properties-and-global-settings)) is staff, not voice. Try utilizing multiple [Instruments](/3/basics/instruments.md).

## Creating a custom dynamic

## Editing text

*Does not affect* [*playback*](#properties-and-global-settings)*.*

Double-click a score item to edit text content. See also the [Text editing](/3/text/text-editing.md) chapter.

## Professional glyphs for engraving

Musescore is shipped with professional glyphs eg the florin sign (the curvy hooked f, ƒ), which is different from an italic plain character f. Add them in [*Text editing mode*](/3/text/text-editing.md#enterexit-text-edit-mode) using the [special characters palette](/3/text/text-editing.md#symbols-and-special-characters), or one of the following shortcuts ( MacOS use <kbd>Cmd</kbd> in place of <kbd>Ctrl</kbd> ),

* Piano *p*: <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd>
* Forte *f*: <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>F</kbd>
* Mezzo *m*: <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>M</kbd>
* Rinforzando *r*: <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>R</kbd>
* Sforzando *s*: <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>S</kbd>
* Niente *n*: <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>N</kbd>
* Z *z*: <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>Z</kbd>

## Properties and global settings

[Selected](/3/basics/selecting-elements.md) score items can be edited with [Inspector](/3/basics/inspector.md),

Under the "Text" section,

* **Fontface**: Ignored by [glyphs](#professional-glyphs-for-engraving). All default symbols under Dynamics [palette](/3/basics/palettes.md) use glyphs. Glyphs use fontface selected under **Format → Style → Score : Musical text font**. See the [Fonts](/3/advanced-topics/fonts.md) chapter.
* **Remove Custom Formatting**: Very rarely used. Removes \<sym> internal codings and makes glyphs inside incompatible with the "Musical text" global styling functionality. See the [Fonts](/3/advanced-topics/fonts.md) chapter.
* See also the [Text basics](/3/text/text-basics.md) chapter.

Under the "Dynamic" section,

* **Dynamic range**: Area of effect of the symbol:
  * *System*: every instrument in the score.
  * *Part*: one instrument (all of its staffs), default.
  * *Staff*: one staff (eg one hand in piano) regardless of voices. As of MuseScore 3.6.2, this option is incompatible with the [Staff / Part properties: single note dynamics](/3/advanced-topics/staff--part-properties.md#snd) playback mechanism, see [forum discussion](https://musescore.org/en/node/351268).
* **Velocity**: 0 to 127. Use a higher number to make notes sound louder, use lower number to make notes sound softer. For more info, see [Loudness of a note](#loudness-of-a-note).
* **Velocity change**: -127 to 127. The change in **Velocity** from the dynamic's parent note to the following one. It is ignored by some instruments. For more information, see [SND](#single-note-dynamics-snd).
* **Change speed**: *Slow*, *Normal*, *Fast*. The speed of the change indicated by **Velocity change**, in real time. This is unaffected by the current Tempo. The default value is *Normal*.
* **Style**: "Text Style" profile applied. See the [Text styles and properties](/3/text/text-styles-and-properties.md) chapter.
* **Placement**: Position on score, above or below staff. Press <kbd>X</kbd> to flip.

Global settings are covered in the [Layout and formatting](/3/formatting/layout-and-formatting.md) chapter.

## Reusing custom symbol

To save and reuse a custom symbol, see [Add an existing score element to a palette](/3/basics/palettes.md#add-from-an-opened-score).

## Loudness of a note

**IMPORTANT:** When a dynamics symbol is added to the score, it affects playback from the parent note onward until the next dynamic symbol. Final barlines or rests do not reset the loudness to default.

The [Synthesizer](/3/sound-and-playback/synthesizer.md) creates audio for each note based on its assigned MIDI velocity value, ranging from 0 (softest) to 127 (loudest). The possible range of actual loudness is determined by the [soundfont](https://musescore.org/en/handbook/developers-handbook/references/instrumentsxml-documentation) creator. A dynamics symbol uses its **Velocity** property ([table of default values](https://musescore.org/en/handbook/developers-handbook/references/instrumentsxml-documentation)) to assign a basic MIDI velocity to the current note and all following notes til another symbol is encountered. [Hairpin](/3/notation/hairpins.md) and [Articulations](/3/notation/articulations-and-ornaments.md) (eg Accent >, Marcato ^) score objects may modify MIDI velocity then. User can also [assign velocity to notes directly in the Inspector](/3/basics/inspector.md).

Not specifing any dynamics symbols in a score is similar to using a ***mf*** (mezzoforte) through out. This is because Musescore assigns MIDI velocity 80 to notes that are not affected by any dynamics symbol, which is equal to the default **Velocity** of ***mf***.

There is no interface to adjust individual [voice](/3/basics/working-with-multiple-voices.md) volume. However, the [Voice Velocity plugin](https://musescore.org/en/project/voice-velocity) can batch adjust *existing* note's **Velocity** properties based on their voice. Notes added after plugin execution will not be automatically adjusted, the user need to run the plugin again.

The following sliders adjust volume broadly but have nothing to do with MIDI velocity,

* changing the volume of instrument (or channel / playing technique) in [Mixer](/3/sound-and-playback/mixer.md), and
* changing the overall volume of whole score, with slider in the [Play Panel](/3/sound-and-playback/play-mode.md#play-panel) or the [Synthesizer](/3/sound-and-playback/synthesizer.md).

Lastly, using [reverb effect in Synthesizer](/3/sound-and-playback/synthesizer.md#effects) may boost volume.

## Single Note Dynamics (SND)

(After Musescore 3.1)

A dynamic symbol with a non-zero **Velocity change** property can simulate Attack envelope effect ([wikipedia](https://en.wikipedia.org/wiki/Envelope_\(music\))) if the [Instrument](/3/advanced-topics/staff--part-properties.md#snd), [Synthesizer](/3/sound-and-playback/synthesizer.md) and [Soundfont](https://musescore.org/en/handbook/developers-handbook/references/instrumentsxml-documentation#sndsetting) is setup correctly, such symbol is called Single Note Dynamics (SND), SND also has [several different meanings](/3/appendix/glossary.md#single-note-dynamic) due to continuous software development. SNDs also use **Change speed** property.

**sfz** (sforzando) and **fp** (fortepiano) are designed to work on certain instruments only; e.g. **sfz** symbol's effect on the violin does not exist on piano.

For more information, see [How to setup Musescore for correct playback for all dynamics and hairpins](https://musescore.org/en/node/290616).

## See Also

* [Text types](/3/text/text-types.md)
* [Fonts](/3/advanced-topics/fonts.md)
* [Hairpin](/3/notation/hairpins.md)
* [Articulations](/3/notation/articulations-and-ornaments.md)
* [How to setup Musescore 3.x for correct playback for all dynamics and hairpins](https://musescore.org/en/node/290616)

## External links

* [How to restore correct playback of dynamics and hairpins in an imported MIDI file](https://musescore.org/en/node/277424)


---

# 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://handbook.musescore.org/3/sound-and-playback/dynamics.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.
