I cannot move the beams up
Reported version
3.0
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
Please take a look on my file from bar 124 - I can't seem to edit the beams.
| Attachment | Size |
|---|---|
| Rondo.mscz | 71.08 KB |
| Rondo.png | 49.38 KB |
Comments
Try this. Better use the forum though. (was generated with 3.0.2)
In reply to Try this. Better use the… by Shoichi
I still can't move the beams
Did you update to 3.6.2?
And double click the beam, then grab the left handle and move it?
In reply to Did you update to 3.6.2? by Jojo-Schmitz
Yes I am fully updated and I tried doing that and it still won't move
This is the issue tracker, for reporting bugs, for getting usage support please use the forum (as had been said earlier).
In reply to This is the issue tracker,… by Jojo-Schmitz
But this is a bug - see my post here: https://musescore.org/en/node/322411#comment-1085303, where they also say it's likely a bug.
In reply to But this is a bug - see my… by jamesmayhew
But to be clear, they (me that is) say it was probably a bug in the older version of Musescore that was used to create the score or to create that section of the score. Removing and replacing the beam in the current version (3.6.2). Fixes the problem.
There have been very many bugs fixed since version 3.0.2 which was reported to have been used to create the score. Moral: make sure you are using the latest version
There it was said that this might have been a bug in an older version.
And even here you've been told to update.
Oops just saw the other reply...
And you said there that you got it to work meanwhile.
In reply to There it was said that this… by Jojo-Schmitz
My fault, I didn't realise I reported it as version 3.0 (a bit dumb, I know). I am actually using the latest version, so the problem must be a bug in the latest version.
Your score was from annolder version, 3.0.2.
In reply to Your score was from annolder… by Jojo-Schmitz
"so the problem must be a bug in the latest version."
No! It works fine if you create that notation in the current version. If it was created in an earlier bugged version that introduced something odd into the score, the current unbuggy version probably doesn't understand the gobbledegook that the earlier version put there. As I said, it works fine if you remove the existing beams that were presumably created with version 3.0.2 and with bugs from that version and recreate them with the current version 3.6.2 that doesn't have that particular bug.