musescore / musescore/MuseScore
Enabling invisible staff lines in 2 staves instruments will change the dynamics position on top of the notes
@DmitryArefiev is already working on this.
Since Mar 6, 2026.
- 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
- create a score for piano in 4/4
- write 2 half notes in the treble cleff
- Put dynamics PPP (crescendo scissors) to FF from note to note (this is important)
- Go to the layout pallet and select "Insert staff type change" for that measure
- Click the new square that appeared on the measure and go to properties
- Check the box "Invisible staff lines"
Actual behavior: The dynamics move upwards colliding with the notes written and are unable to move up or down even with the "Auto-place" setting off. They can only move horizontally and they end up together with the notes.
Expected behaviour: The expected behaviour is that the dynamics stay in place and can still be moved freely like in any other instance
Supporting files, videos and screenshots
In which versions of MuseScore Studio is this issue present?
4.6.5
Regression
I was unable to check
Operating system
Windows 10
Additional context
If you do the same steps but instead of putting the dynamics in the treble clef you put them in the bass clef and change their position to "above" in the properties you get a similar issue where the dynamics can't move upwards.
See Screenshot Bass clef alt
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.