musescore / musescore/MuseScore

Expression text in grand staff does not offset above cresc. and decresc.

Open
#34,539 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

Using a grand staff instrument ie. Grand Piano,
Write a line of music in both staffs
Add a dynamic at the start of M1 and M2
Add a Cresc or decres over bar 1 into count 1 of bar 2
Add Expression text to beat 1 of M1
Incorrect behavior for placement. Should not move the Cresc or decresc but rather offset the grand staff for that line of music on the page and have the expression text above the cresc.
So offset from dynamic markings to the right, then offset up for hair pins.
The best way to implement this would be, let us be able to select if we want it in the center with the dynamics, above as per my earlier description, or below, if wanted. This can be implemented into the properties menu. This fix for behavior would go very far for cleaning up grand staff notation.

As of now, I don't believe MS4 can handle this use case. This is labeled as bug because expression text is an already an in place system.

Supporting files, videos and screenshots

Bar of MS4 that has this issue,

Image

Bar of notation found online with correct placement for expression text.

Image
In which versions of MuseScore Studio is this issue present?

4.7.4

Regression

I was unable to check

Operating system

Windows 10, presumed to be all current versions of MS4.7.4

Additional context

Conductors are very picky on how scores look. If this can be addressed as a simple implementation and pushed out to users, I would really appreciate it!

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
  • 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

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.

Research direction

Reproduce the issue in MuseScore Studio 4.7.4 using a Grand Piano staff, dynamics, a hairpin, and expression text as described. Inspect the notation layout and placement behavior; done means expression text is positioned above the crescendo or decrescendo without moving the hairpin, while the grand-staff spacing remains correct.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
design, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.