Arpeggios and chords across clefs.

• Nov 22, 2019 - 03:29

Arpeggios across clefs are some of the most common features in music, especially in the Romantic period. However, it seems I can't do that directly on Musescore. As a result, every time I want to make these, I need to extend two separate arpeggio lines to merge them and edit the notes manually on the pianoroll editor. This can be frustrating if I need to do these for hundreds of time in a single piece. The following picture demonstrates what I meant by arpeggios across clefs.
Musescore 1.png

Similarly, despite being a common feature, I couldn't create chords across barlines either. This will be a convenient feature if there are a lot of chords in the middle registers as we no longer need to utilize a lot of ledger lines below the treble clef/above the bass clef. The following picture is an example of chords across clef in Liszt's Transcendental Etudes No.2
Musescore 2.png


That first one is a known limitation, but the second one can be done. Press Ctrl+Shift+Up/Down to move notes to a different stave.

In reply to by Howard-C

The second one is not quite fixed by cross staff notation because it is limited. You cannot simply select the bottom note of a chord and press ctrl+alt+down arrow to move it to the bottom clef because the entire chord will move. You must put the note you want moved into another voice and use ctrl+alt+down arrow, select the stem and disable auto placement then double click the stem to extend it to the other clef. It's essentially the same limitation as with arpeggios with a similar solution.

In reply to by mike320

Exactly. That's why I am posting this in the feature request subforum. Even though there are indirect ways to do arpeggios or chords across staff, I think Musescore should add additional features that can create these features directly, given their frequent occurance in music.

In reply to by Steven_Wan

If you follow Howard C's link, you will see there is an official suggestion that I am talking about. Howard said that it's a bug, but it is a design decision. Howard C added a comment to the issue linking it to this discussion so programmers can see discussions concerning it. In short, you have done exactly as you should have, thank you.

Do you still have an unanswered question? Please log in first to post your question.