musescore / musescore/MuseScore

Dynamics collides with cross-staff arpeggio

Open
#23,615 0 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

engraving P2
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

When adding text dynamics between the staffs with cross-staff arpeggio, it [text dynamics] collides with the arpeggio line, while not adjusting its horizontal position in order not to intersect with the line.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/5ec10d12-743f-4e34-9440-d9e9a9394945

Expected behavior

The dynamic had to be positioned in such a way that it did not intersect with the arpeggio line (either the arpeggio line or the dynamic had to move).
Снимок экрана (456)

Or the arpeggio line should have become invisible in the area where the dynamic is located.
Снимок экрана (457)

What is the latest version of MuseScore Studio where this issue is present?

MuseScore Studio version (64-bit): 4.3.2-241630831, revision: github-musescore-musescore-22b46f2

Regression

No.

Operating system

Windows 11

Additional context

It would also be nice to be able to allow the user to apply arpeggios to chords in a cross-staff style. Currently, in order to connect arpeggios between the staffs, the user will first have to add an arpeggio to one of several staffs, and then drag it [arpeggio] with the key combination Shift + ↓ (Shift + ↑ to drag from bottom to top). Wouldn't it be better to simplify this method? For example, so that the arpeggio is automatically stretched when it is added to the chord range selected after several staffs:

https://github.com/user-attachments/assets/8393c61a-def5-4474-8e83-49a53c2099b0

Checklist

  • ✅ This report follows the guidelines for reporting bugs and issues
  • ✅ I have verified that this issue has not been logged before, by searching the issue tracker for similar issues[^1]
  • ✅ I have attached all requested files and information to this report
  • ✅ I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

[^1]: I am aware that issue #17719 exists, but I am not sure exactly whether the approach described in it is appropriate to address the issue of the relative position of dynamics and arpeggios? It seems to me that if you make the arpeggio lines invisible in the area where they can intersect with dynamics, then it may seem that the arpeggio does not actually cover several staffs, that each arpeggio is separate for each staff. @oktophonie, please correct me if that's not the case.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.