Bug report
I'm not really sure if this is a bug. As you can see, the beam is not at the right location.
| Attachment | Size |
|---|---|
| Screenshot (19).png | 295.03 KB |
Do you still have an unanswered question? Please log in first to post your question.
I'm not really sure if this is a bug. As you can see, the beam is not at the right location.
| Attachment | Size |
|---|---|
| Screenshot (19).png | 295.03 KB |
Do you still have an unanswered question? Please log in first to post your question.
Comments
Can you attach the actual MSCZ file?
In reply to Can you attach the actual by Isaac Weiss
Yes. If possible can you please help me fix this?
In reply to Yes. If possible can you by bumble02_omit@…
When I load this into 2.0.3, the stems run all the way down the page, so the problem is worse than what the picture shows. So something definitely went wrong here - do you have any idea how this happened? What the last thing you did before things went crazy?
Best thing I know to do is delete the problem beat - click the high B at the beginning of the triplet, then shift+right to extend the selection, then delete. Then re-enter it.
In reply to When I load this into 2.0.3, by Marc Sabatella
I really have no clue what's wrong with it. I will try that. Thanks
In reply to When I load this into 2.0.3, by Marc Sabatella
Already fixed it! I fixed by deleting the measure and then create a new one. Anyway, it's something Musescore has to work with.
My guess is that you have (perhaps inadvertently) tried to force these notes to be beamed across the barline to notes in the previous measure. this works for measures on the same system, but not for measures on different systems, leading to results like this. The musical context makes it look like this was n accident. To reset, click the notes on the system below that are missing the beam and reset their beaming to automatic (Layout / Reset Beam Mode).