duplets triplets
having done the duplet a dot c I want the demisemiquaver triplet g d c, but both are each time connecting
whatever I do, always the same. What can I do ? This happens often ...
In the duplet a is not taking the dot.
having done the duplet a dot c I want the demisemiquaver triplet g d c, but both are each time connecting
whatever I do, always the same. What can I do ? This happens often ...
In the duplet a is not taking the dot.
Do you still have an unanswered question? Please log in first to post your question.
Comments
Highlight the first note of the triplet. Apple "beam start" property to it.
https://musescore.org/en/handbook/3/beams#change-note-beaming
In reply to Highlight the first note of… by jeetee
try that. thank you.
In reply to Highlight the first note of… by jeetee
ok, doing that, but I don't see "Time Signature Properties…;" anywhere. Workspace is advanced..
In reply to ok, doing that, but I don't… by Ja'hé
see https://musescore.org/en/handbook/3/time-signatures#change-default-beam…
In reply to see https://musescore.org/en… by Jojo-Schmitz
found it, bagpipe notation.....
thank you
In reply to found it, bagpipe notation… by Ja'hé
Pardon???
In reply to found it, bagpipe notation… by Ja'hé
I think you fond the wrong thing. BTW, the time signature properties link was to explain how to manually change a beam. You are not likely to set a good beam pattern in 4/4 time that would do what you wanted to break the beam between the duplet and triplet.
In reply to I think you fond the wrong… by mike320
can you explain, please ? Is it the time or the tuplets ? Presently doing another, I keep changing 6/8 and 4/4 but the problem remains.
In reply to can you explain, please ? Is… by Ja'hé
The picture above this reply looked like the triplet and duplet were on strange off beats. If you changed the beaming properties to do this automatically, you would probably end up with beams not being connected where they normally should be.
Your responses after this reply seem to indicate the problem was more related to improperly creating tuplets (generic for duplet, triplet...). You now seem to have a grasp on that, so perhaps if the tuplets start on normal beats, you could set default beaming to be helpful.
In reply to The picture above this reply… by mike320
thank you-that could explain why it often works or sometimes not.
In reply to found it, bagpipe notation… by Ja'hé
doing it again this time on simple quavers, nothing helps. In the middle of the score has been working fine all along, suddenly not any more. 2 duplets joining to a quadruplet . Choosing from the menue "duplet" does not help.
In reply to [inline:Cabar_Feidh.png] … by Ja'hé
I changed the workflow. Add tuplets is creating half the value intentioned. So I set to crotchet if I want quavers and choose duplet. It works, this time.
In reply to ok, doing that, but I don't… by Ja'hé
Highlight the first note of the triplet. Apple "beam start" property to it.
Nowhere does that mention Time Signature Properties. The included link pointed straight to the relevant page in the handbook, heading about how to apply the beam start to a selected note...