Writing Tuplets Over the Barline

• Nov 22, 2018 - 08:54

Has anyone figured out a simple way to write tuplets over the barline WITHOUT a workaround?

Example: I'm in 4/4 time. I want to write a quintuplet (or any kind of tuplet, doesn't matter) in the space of 1 quarter-note that begins on the "and" of 4. This quintuplet would therefore extend into the next measure, and should end on the "and" of 1.

I can't do that because the program reads that I'm trying to fit something too large in too small of a space.

Currently, the only workaround I can think of is to make a measure of 5/4 (or longer) and write the tuplet that way, since the program will allow it to fit.


You mean this? I changed the real measure duration to 8/4 and then added the barlines using the "barlines" palette. You could write any tuplet over a barline you want this way, playback sounds the way it should also. Creating a 5/4 measure would change the way performers read the music so, at least to me, it wouldnt be a solution.

Attachment Size
t1uplet.png 138.63 KB

Joining the measures is definitely a good option as well, in some cases. Another is to work out the math on what part of the tuplet comes before the barline versus after, enter the two tuplets separately. Then hide extra flags or join beams or whatever might be required to make it look right.

In reply to by Marc Sabatella

Can you explain Option 1- Joining the Measures? Option 2 is a little convoluted, and all the suggestions in this thread are simply workarounds (though I'm grateful for the conversation and spirit of community!). I'm hoping with future releases there is something that can be done programming-wise to do all of the math for us :). Not that I don't like math, just that anything that detracts from the flow of the compositional process/output is seen as an obstacle.

In reply to by MHDrums

Joining measures means using Edit / Measure / Join Selected Measures to combine two 4/4 measures to create one 8/4 measure. It's basically the simple way to accomplish the workaround already mentioned.

And yes, some day it would be nice to figure out a good solution to this, right now it isn't obvious what that would even look like though, much less how to implement it.

In reply to by Marc Sabatella

Maybe there should be a "common workarounds" or similar section in the handbook. In many places in the internet you read often "musescore cant do this, and that, etc" and there are workarounds for almost everything, they just require a few more steps. I say this because i saw many support posts asking for common workarounds and they could be redirected to the handbook instead of explaining the workaround each time. I dont know if the developers would be ok with that though, maybe it looks like it points out missing features right in the handbook, but it would certainly be useful for users.

In reply to by [DELETED] 26799858

My hope was that this gringo that can barely speak Spanish would encourage someone whose first language is Spanish would take over and make the translation better. I'm glad you are doing this. The how to's can be translated to Spanish, but I would suggest that you concentrate on making the translation of the handbook better. This will help you when it comes to translating the version 3 handbook in a few months when that needs to be done.

We are off topic from the original post and there are an abundance of translators on these forums. If you want to continue this conversation or ask any questions concerning the translation, then the translation or documentation forum is perfect for this. I, like many others, monitor all forums.

Do you still have an unanswered question? Please log in first to post your question.