musescore / musescore/MuseScore

Walker noteheads do not mirror correctly

Open
#26,299 0 comments 0 reactions 2 assignees 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

**Edited with better pictures, and 2 more errors found

In the inspector panel, under Note and Head scheme, the 7 shape (Walker) shape note heads are implemented incorrectly in 6 instances:

  1. Re (the crescent) with a down stem ought to be faced with the points away from the stem
  2. Re (the crescent) as a whole note (that is, with no stem) ought to be faced with points to the right instead of left
  3. Ti (the isosceles triangle) with an up stem ought to be pointed toward the stem
  4. Do (The rhombus) ought to have a stem centered on the notehead
  5. Do (The rhombus) ought to naturally have the long edge on the bottom, both without a stem and with a down stem
  6. Fa (The acute triangle) as a whole note (no stem) needs to be rotated 180 degrees.

The notehead mirroring function doesn't actually mirror the notehead--it simply moves it to the other side of the stem without changing the direction it faces.

I'm including pictures of Musescore's engraving and Walker's style from his tunebook.

Thanks in advance,
Robert McIntyre

Supporting files, videos and screenshots

Image

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

I am using:
MuseScore version (64-bit): 3.6.2.548021803, revision: github-musescore-musescore-3224f34

This problem persists in:
MuseScore Studio version (64-bit): 4.4.3-242971445, revision: eb6b367

Regression

I was unable to check

Operating system

OS: Windows 10 (10.0), Arch.: x86_64

Additional context

No response

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.