You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a problem in a specific score (posted on the bugs forum before and attached as a file there: link).
I have a problem in the attached score, measure 76 on the piano (lowest 2 staves). The piano melody is the accompaniment for the vocals in the upper staves and is displayed in a smaller format. The problem occurs with the 4th note (high "la" ("A")) in the left hand, which should (according to the original printout) be moved to the upper stave (right hand). When trying to move that note (with shortcut ctrl-shift-arrowup or with the button on the menu), it gets all messed up with some parts of the connection being drawn (in both upper and lower staves) and some not. The notehead itself however remains in the lower stave. Futhermore, the move of the note doesn't persist. Whenever changing tabs or saving the score, the note returns back to the lower stave.
The shortcut and the button do work cause I've used them throughout several other scores. It's just this one that is messed up.
This screenshot shows the current situation:
This one the messed up situation:
And finally what I want to achieve (done by drawing some manual lines for now):
The MuseScore file itself is attached on the linked bug forum: direct link to the file here.
Steps to reproduce
Try moving a note from the lower stave to the upper one or vice versa (on the piano staves). The fourth note in measure 76 needs to move to the upper stave by using ctrl-shift-arrowup or the button in the toolbar. The engraving gets messed up and the change is not persistent. This doesn't seem to work in other places either in this specific file.
Screenshots/Screen recordings
No response
MuseScore Version
4.1.1
Regression
I don't know
Operating system
Windows 10 and Windows 11 (also tested by a teacher of mine on MacOS with the same result)
Additional context
Before posting here, I made a post in the bug report forum (here). The MuseScore file that is causing the problem is attached in that post.
The text was updated successfully, but these errors were encountered:
Nasty! I can reproduce this in 4.0 and 4.1.
In master, it looks all right when I cross-stave the note (visually), but still the change doesn't persist over save/reload. Will investigate.
Issue type
Engraving bug
Bug description
I have a problem in a specific score (posted on the bugs forum before and attached as a file there: link).
I have a problem in the attached score, measure 76 on the piano (lowest 2 staves). The piano melody is the accompaniment for the vocals in the upper staves and is displayed in a smaller format. The problem occurs with the 4th note (high "la" ("A")) in the left hand, which should (according to the original printout) be moved to the upper stave (right hand). When trying to move that note (with shortcut ctrl-shift-arrowup or with the button on the menu), it gets all messed up with some parts of the connection being drawn (in both upper and lower staves) and some not. The notehead itself however remains in the lower stave. Futhermore, the move of the note doesn't persist. Whenever changing tabs or saving the score, the note returns back to the lower stave.
The shortcut and the button do work cause I've used them throughout several other scores. It's just this one that is messed up.
This screenshot shows the current situation:
This one the messed up situation:
And finally what I want to achieve (done by drawing some manual lines for now):
The MuseScore file itself is attached on the linked bug forum: direct link to the file here.
Steps to reproduce
Try moving a note from the lower stave to the upper one or vice versa (on the piano staves). The fourth note in measure 76 needs to move to the upper stave by using ctrl-shift-arrowup or the button in the toolbar. The engraving gets messed up and the change is not persistent. This doesn't seem to work in other places either in this specific file.
Screenshots/Screen recordings
No response
MuseScore Version
4.1.1
Regression
I don't know
Operating system
Windows 10 and Windows 11 (also tested by a teacher of mine on MacOS with the same result)
Additional context
Before posting here, I made a post in the bug report forum (here). The MuseScore file that is causing the problem is attached in that post.
The text was updated successfully, but these errors were encountered: