Can't copy and paste with local time signature? Guess I did the time signatures backwards

• Oct 4, 2018 - 00:01

So I decided to go with the local time signature method. I can get the notes and pedal marks into the score just fine, until I try to copy and paste the left hand. It says an error message like this:

Please select the entire tuplet/tremolo and try again

From what I can guess, this means that I put in 12/8 as the local time signature when I should have written it in 12/8 and put in 4/4 as the local time signature in the right hand. So I would need to cut the entire right hand, put the 12/8 time signature in as a global time signature, put in 4/4 as a local time signature and then paste the right hand back in in order to not have to redo the whole score and solve this issue of not being able to cut and paste the left hand, right?

Also I installed the tempo changes plugin to get a smooth ritardando instead of a choppy one or a time intensive one.

Here is the score I am having issues with:
Nocturne in B flat.mscz


MuseScore will not allow you to paste into a local time signature. If you try, it will give an error message that says, "Cannot paste in local time signature". And, as you have already found out, MuseScore will not allow you to copy from a local time signature, although the error message it gives is not so clear. I cannot say for sure why copy/paste is prohibited for local time signatures, but you will have to be content with being able to copy/paste one hand and not the other.

Given MuseScore's limitations with local time signatures, and also the fact that it is rather uncommon to have a different time signature for each hand, it is probably better to write your nocturne with both hands in 4/4 after all. If you think that making all those triplets will be a pain, try this:
1. Select the first full measure rest in the left hand.
2. Press "N" to enter Note Input mode.
3. Press "5" to select quarter note duration.
4. Hold down the "0" key to start filling the left hand with quarter note rests. Keep the "0" key down as long as you like, or until each measure in the left hand is filled with quarter note rests.
5. Press "N" (or ESC) to leave Note Input mode.
6. Select all of the quarter note rests, and press Ctrl+3.
7. Right-click one of the tuplet numerals, and choose "Select->All Similar Elements".
8. Press "V" to make the tuplet numerals invisible.
9. Go back and enter the pitches.
Using this method, I was able to rewrite your score in no time, after copying and pasting the right hand. Here is the result:
Nocturne in B flat.mscz

Indeed, the local time signature feature is quite limited, and in any event, I strongly recommend against using for simple cases like this. Unless there is an extremely compelling reason to do otherwise, you should notate it in 4/4 using triplets in the LH (you can always hide the numbers / brackets) or in 12/8 with occasional duplets in the RH. Don't confuse people by making it look more complicated than it actually is.

In reply to by Marc Sabatella

I ran into this transcribing Corelli's La Folia (as arranged by Suzuki) , which has a section/movement with the violin in 12/8 and piano in 4/4. In this case it really is pretty complicated so just not doing it is not a great option. I guess there are no near-term plans to fix this limitation?

In reply to by mcx

FYI, the limitation still exists in version 3, it has not been fixed. I fear the fix will not appear before version 4, which hasn't even been discussed yet, because it will likely require changing the internal format of the .mscz file, which will not happen in any version 3.x release. I, as a fellow MuseScore user only, hoped this would be fixed in version 3. I've put projects on hold because of all of the problems with local time signatures.

In reply to by mike320

The slightly good news is I don't think any file format changes would be needed. But really fixing all the problems with local time signatures is a big undertaking, probably not easily done one bug at a time. I have hope we'll get to the point where this rises to the top of the priority list and someone finds the time and energy to deal with it.

In reply to by Marc Sabatella

Thanks for the updates. In the meantime, I'm working around it using 12/8 as global (instead of 12/8 local, 3/4 global). It's manageable, but I'm looking forward to this getting fixed eventually. Thanks for all your hard work on this awesome tool. I hope by reporting these issues I'm helping to make it a bit better (since I don't have time to code on it myself, at least for now).

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