Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Octave-transposing Percussion Instruments (esp. Glockenspiel) and Concert Pitch representation #26354

Open
4 tasks done
paulalndwhr opened this issue Feb 5, 2025 · 0 comments
Assignees

Comments

@paulalndwhr
Copy link

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

Some orchestral instruments like the Double Bass or the Glockenspiel and some other percussion instruments sound octaves higher or lower than written.
Traditionally, orchestral scores in concert pitch and transposed scores both would display the notes written in the voice - even if there is an octave offset to what actually sounds.

There is an inconsistency in how Musescore deals with this at the moment: Double Basses are rendered identical in transposed and concert pitch mode. However, the Glockenspiel is rendered two octaves higher in concert pitch mode than in transposed mode.
My believe is that the way it is done on the double passes is correct.

steps to reproduce

  1. Notate music for double bass, notate music for glockenspiel
  2. switch around between concert pitch and transposed view
  3. observe inconsistency

Supporting files, videos and screenshots

Image Image

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

OS: macOS 13.1, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.4-243461245, revision: github-musescore-musescore-2232670

Regression

I was unable to check

Operating system

macOS 13.1

Additional context

I believe that this a regression compared to an earlier 4.x version, but I am unsure.

I have been composing in 4.3 in concert pitch mode a lot and this is the first time that I noticed the bug.

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants