-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Note highlighting on the piano keyboard ignores ottavas #21900
Comments
I guess, also alternate tunings is related to this (where results can be even more stange). |
Hi! I'm working on a fix for this issue regarding note highlighting on the piano keyboard during ottavas. Could you please assign me? |
davidfaianunes
added a commit
to davidfaianunes/MuseScore
that referenced
this issue
Apr 5, 2024
davidfaianunes
added a commit
to davidfaianunes/MuseScore
that referenced
this issue
Apr 15, 2024
…ottava\nIn the class Note there are multiple computations for pitch.\n I've used the playback pitch (ppitch) instead of the effective pitch (epitch),\nbecause the audio was using the pitch i wanted shown on the keyboard.
davidfaianunes
added a commit
to davidfaianunes/MuseScore
that referenced
this issue
Apr 15, 2024
…ottava In the class Note there are multiple computations for pitch. I've used the playback pitch (ppitch) instead of the effective pitch (epitch), because the audio was using the pitch i wanted shown on the keyboard.
davidfaianunes
added a commit
to davidfaianunes/MuseScore
that referenced
this issue
Apr 15, 2024
…ottava. I've used the playback pitch (ppitch) instead of the effective pitch (epitch) in pianokeyboardcontroller.cpp.
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue type
UI bug (incorrect info or interface appearance)
Bug description
When one or more notes are selected, the note(s) in the selection get highlighted on the piano keyboard. This highlighting does not account for ottavas, so the wrong key gets highlighted for any note affected by one.
Tested on 4.2.1 and on the most recent nightly build.
Steps to reproduce
Expected result: the key corresponding to the selected note gets highlighted
Actual result: the highlighted key is off by an octave, as if the ottava didn't exist
Screenshots/Screen recordings
No response
MuseScore Version
MuseScore version (64-bit): 4.3.0-240710504, revision: github-musescore-musescore-5be2b33
Regression
I don't know
Operating system
Arch Linux x86_64
Additional context
No response
The text was updated successfully, but these errors were encountered: