musescore / musescore/MuseScore

Incorrect pitch when using insert input mode in first measure with alto clef

Open
#26,029 6 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

engraving P3 UX/interaction
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
  1. Select "new score" on "Scores" page in home tab.
  2. Create a new score based on treble clef template
  3. Change treble clef to alto clef
  4. Change note input mode to "insert"
  5. Enter note input mode on the first beat of the first bar.
  6. Type "C" to enter C
  7. Expected: Note C is input and sounds.
  8. Actual: Note is drawn on Middle C (middle line of the stave), but it sounds B4 and is displayed as B4 on the bottom note property display area.
  9. Inserting more notes by typing "C" are consistently an octave above the previous one. See screenshot. These octaves are also indicated and sound as B, even though they are technically C.

Workaround: add first note in step time input mode.

Supporting files, videos and screenshots

image

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

4.5 prerelease 8 Jan 2025

Regression

No

Operating system

OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.0-, revision: github-musescore-musescore-

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.