Sixteenth notes connected to dotted eighths look like eighth notes, beam doesn't change, and triplet beams connect to eighth notes
When I connected a dotted eighth note to a sixteenth note, the sixteenth note displayed with the same single beam as an eighth note, rather than a double-beam. The last note in the picture below is actually a sixteenth note.
Also, when I used triplets and put eighth notes after them, their beams connected, as shown in the picture below.
Does anyone know how to fix any of these weird beam problems? Any help would be appreciated.
| Attachment | Size |
|---|---|
| Capture.PNG | 2.29 KB |
Comments
Could you attach a file with just this measure in it? The 16th note thing is something I've never seen before. As far a connected beams see: https://musescore.org/en/handbook/beams
In reply to Could you attach a file with… by mike320
"Also, when I used triplets and put eighth notes after them, their beams connected, as shown in the picture below."
![time sig.jpg]( "time sig.jpg")
I guess you are using a time signature kind 5/8 (or something like that ? your pic doesn't show the entire measure)
In this case, select the dotted eighth note and double-click on the first symbol in Beam properties palette.
Or, if preferred, or/and other similar cases in the score, redistribute the beaming of the note groupes in the Time signature properties (right-click on the time sig). See: https://musescore.org/en/handbook/time-signatures#change-default-beaming
In reply to "Also, when I used triplets… by cadiz1
Thanks for the links! It worked. All fixed now.
In reply to Could you attach a file with… by mike320
Sure, I should've done that in the first place - but I'm not sure that it has to do with the time signature.
Later, I tried just putting a dotted eighth and a sixteenth together, and it displayed correctly.
I think it may be because the dotted eighth and sixteenth are both for some reason connected to the beam of the triplet.
Thanks for the link!
In reply to Sure, I should've done that… by EYMusic
Like I said, the 16th should always be displayed as a 16th note. Don't attach a picture, attach an actual MuseScore file with that measure looking like that. I suspect there is something else going on or you found a bug that needs fixed.
In reply to Like I said, the 16th should… by mike320
Sorry - I'm new to this software, you can probably tell.
Also, it's already been fixed - I just didn't know how to manually change the beams. It worked fine.
Thank you for your suggestions.
In reply to Sure, I should've done that… by EYMusic
The algorithm for breaking beams in the presence of triplets is designed to be "sort of" clever but can be fooled. Basically, it rounds down to sixteenth and breaks the beam where sixteenths would be broken. So if you set your sixteenths to break every beat (in the Time Signature properties), then the triplet will separate there as well.
But indeed, there is no reason I can think why sixteenths wouldn't display as such, and I can't make this fail in my own attempts. As mentioned, it is difficult to help given only a picture - we need you to attach the actual score.
In reply to The algorithm for breaking… by Marc Sabatella
Actually, it's all fixed now. What I did was manually change the beams by using the "Beam Properties" and setting the dotted eighth as the start of a beam by dragging the icon to the note, and it detached from the triplets. Also, after I detached the dotted eighth from the triplets, the sixteenth displayed normally.
In reply to Actually, it's all fixed now… by EYMusic
Would still be useful for us to see the score though. If there truly was a sixteenth note that was not displaying correctly, that's a bug - one I've never seen or heard of before - and we'd love to be able to reproduce it so we can fix it. Seems there must be something very unique about your score that was triggering this bug, because nothing I have tried does anything but what it should.
In reply to Would still be useful for us… by Marc Sabatella
I tried to change it back such that the sixteenth note didn't display correctly, but for some reason it actually worked this time. I also made another score and tried to redo it, but it didn't work! My apologies for not posting the score before I fixed it, but I can tell you that all I did to fix it was use the "beam properties" to separate the triplets from the dotted eighth. Here's the fixed version: