musescore / musescore/MuseScore
Incorrect horizontal alignment of palm mute text
Nobody has claimed this yet.
- 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 guitar staff with notes in it.
- Apply palm mute (P.M.) to a note.
- Observe the palm mute alignment.
Actual behavior: Palm mute is aligned to start from the left edge of the note. In the case of palm mutes, this is incorrect and often results in the text crossing over to the next note making distinguishing between muted and unmuted notes harder. (See attached example file)
Expected behavior: The palm mute text should be centered around the wanted note, making it a more sane default and reducing manual adjustments.
Workaround: manually adjust every single palm mute element separately (Style... > Text styles > Palm mute has no effect. https://github.com/musescore/MuseScore/issues/25585 )
Supporting files, videos and screenshots
What is the latest version of MuseScore Studio where this issue is present?
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.0-250721848, revision: github-musescore-musescore-7c55023
Regression
No.
Operating system
Windows 10
Additional context
Manually setting a x-offset in Style... > Text styles > palm mute did not work:
[Guitar] Offsets in text styles don't work for Let-ring and Palm mute #25585
https://github.com/musescore/MuseScore/issues/25585 )
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.