Redundant Beam
Redundant beam appears for the reason I don’t know, if I delete note G4, Voice 2, at Bar 15 beat 2.75 stave1, this beam can be then deleted.
Similar situation happened before a few times, not only for the hidden notes, or 1/16th notes.
| Attachment | Size |
|---|---|
| 3-04 Humoresque Bar 15-16.png | 131.22 KB |
| 3-04 Humoresque.mscz | 50.25 KB |
Comments
Smells like a corruption to me, how did you manage to get there?
In reply to Smells like a corruption to… by Jojo-Schmitz
The way to get there:
0. Delete all notes in bar 15;
1. Enter in this bar eight 16th notes, and a grace note for the last note, by default they are voice 1;
2. Untick “play” for the grace note and the ones before and after, three notes are then muted;
3. Enter voice 2 into the bar, as the newer attached pngs. Once the last 16th is entered, the redundant appears.
This happened before not only following these steps, which I forget. Sorry.
And now it’s 12:38am in Sydney, good night!
In reply to (No subject) by Jojo-Schmitz
I made it work with OP's score, but I couldn't make it happen from scratch. I added hidden staves, put the measure with the extra beam as the last on the system, made it the second system in the score with no duplication. I've only previously seen this in the last measure of a system where the beam shows up in the first. hmmm.......
Now,
0. "Shift+i" to show all invisibles;
1. Delete title and composer;
2. “i” to remove two pianos;
3. “Ctrl+Del” to delete all the bars in front and behind bar 15 of violin, the redundant is still there, right hand down, as attached;
4. Save score and reopen;
5. It’s gone. Good game to be continued to play …
(Refresh screen display with above steps 0-3 dose not get rid of the redundant.)
That still don't seem to be steps to reproduce the problem, but steps to fix the broken score, right?
Either or both, I'm trying to corner the bug if there is any to a smallest possible area.
What interesting is when saved and reopen, it's gone..... better leave it to programmers.
This beam is displaying because you have notes in voice 2 at the end of bar 23 (!) that are set to "middle of beam" and they are trying to extend the beam back to the previous note in that voice, which is bar 15. Set those notes back to Auto and the glitch disappears.
Of course, setting those notes to middle of beam should have created a beam all the way back to bar 15. Not that you'd have wanted that, but that would have been the correct behavior given your beam settings. But you weren't seeing that because of #16278: Beaming notes over barlines and line breaks.
In reply to This beam is displaying… by Marc Sabatella
@Marc,
Just a thought, there is no way to tell the current beam setting without adding additional notes or rests. Perhaps there should be some sort of feedback in the inspector (similar to note heads). I'm not sure if this is already planned for version 3 or not. What do you think?
Well,, there is one way: Open the Beams palette, then select the note, now the beam palette will show the type.
But agreed, this should better (additionaly) be in the Inspector.
And no, so far that is not in 3.0
In reply to Well,, there is one way:… by Jojo-Schmitz
I just tested this with various notes. I realize it only works if you have changed the beaming. It doesn't show if auto is in effect or what the default beaming would be for the specific note.
edit: I continued testing and see that the current beaming is only shown if you use the palette. It does not show this in a custom workspace.
I did two tests confirmed your investigation result: the “redundant beam” came from crossing barline beam broken by a “Line Break”.
In reply to I just tested this with… by mike320
new testing score, if you delete bar 5 voice 2 beat 4 rest, as arrow shows.... it's not the crossing bar beams this time.
In reply to new testing score, if you… by Xianyue賢越
If you are referring to the beam the arrow is pointing at here:
That is the beam for voice 2, which has not been made invisible. I don't see anything else unusual in that measure.
In reply to If you are referring to the… by mike320
show hidden, and then delete the rest of voice 2 green before it as the jpg I uploaded with the score and c.
In reply to show hidden, and then delete… by Xianyue賢越
That was strange. I deleted the rest you pointed at, and the beam jumped up to the staff above it.
In reply to That was strange. I deleted… by mike320
have fun
In reply to have fun by Xianyue賢越
After further testing, if these beams are set to auto, they jump when the rest is deleted. If the three notes have beam set to start, middle, middle, the beam does not jump. The "beam" on the rest does not affect the behavior.
This issue is still marked as a duplicate of #16278: Beaming notes over barlines and line breaks, if it is, fine, but better supply the added infos there, if it is not, this here needs to get marked active again
In reply to This issue is still marked… by Jojo-Schmitz
sorry, my limited brain memory took me here. thanks for your efforts, and have a cup of tea.
In reply to After further testing, if… by mike320
More programming fun now, with this score, go to the second line from the end, i.e. Status showing bar number 125, click highlight top treble measure, and on palettes click beam “auto”. You should see the captured.
I was thinking to post there on #16278, and then found the tile there was “crossing bar beam” which diffs from this. Have fun.
This is something different indeed. The problem here is that by selecting the entire measure, that is including the rests that are present in voice 1 (the actual notes are in voice 2, for whatever reason). So you are actually setting the beaming for the rests to auto as well. Don't do that, this has the effect of trying to beam across the rests. Instead, since you don't really want to include the rests in the beaming, use the Inspector to limit the selection to just the Notes within the region (or use right click, Select / All Similar Elements in Range Selection). Or, better yet, move your notes to voice 1.
In reply to This is something different… by Marc Sabatella
I understand the reasons you told here and totally agree with you. But users wouldn’t have this complete logic brains, they would just simply think “auto” should fix/do anything perfect, they would think here whatever had happened was “broken”.
I agree. See #52151: "Auto" beam setting for *Rests* should not beam (if no stemlets). Hopefully that will be fixed at some point as well.
In reply to I understand the reasons you… by Xianyue賢越
Hi, pls help edit this song bar 11.
Please use the forum for support requests rather than closed (or duplicate) issues
In reply to Hi, pls help with this song… by Xianyue賢越
Workaround for this bug:
input a hidden 8'th on the 2nd voice in the 12th measure.
(and untick "play" on inspector.)
see attachment:
It's a similar issue, the beam belongs to the two eighths at the end of bar 45. Because the first of these was set to "middle of beam" for some reason, MuseScore is trying to connect it to the preceding eighths in that voice, which are the ones in bar 11.
In reply to It's a similar issue, the… by Marc Sabatella
Thanks, I was tricked again - at a remote distance of them. I was thinking it's another new case of the Redundant Beam.
And now, this one: at bar 5, staff 2, beat 6? Redundant beam new case?
No, but elements of the chord (noteheads, stem) moved separately via the elements offset, rather than the chord as a whole for the chord offset
In reply to No, but elements of the… by Jojo-Schmitz
is it possible to fix it?
Sure, just remove the erroneous Note adjustments and make them to the Choed instead.
And as mentioned, in the future if you have questions, please ask for help by starting new threads in the Support forum rather than adding replies to closed issues.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.