Tuplet Voice Lock

• Apr 28, 2024 - 17:55

Hello.

In Musescore 4
(OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.2.1-240230937, revision: d757433)

I have a piece of music with a melody in voice 1. I'd like to transfer it to voice 2. It seems to work, except where I have triplets (other duplets are available). Triplets seemed to be stubbornly locked to the voice they were created in.

I've tried that with a brand new score, and any sort of duplet behaves exactly the same.

Are there any suggestions for how to transfer duplets to another voice? Or is the standard work around to re-enter them all the other voice manually?
Thanks

Dave

Comments

• Apr 28, 2024 - 18:06

How are you transferring the notes from voice 1 to voice 2?
When I use Tools->Voices->Exchange voice 1-2 option, then the results seem to be as expected.

Reply

• Apr 30, 2024 - 15:46

Hunh! It does the same for me. I can move notes entered in Voice 1 to Voice 2 by pressing Ctrl+Alt+2 or by clicking the Voice 2 button on the toolbar. But not tuplets (I tried several "sizes" of tuplets: triplets, septuplets, and quadruplets. The same for all.)

That said, ordinarily what I do is to enter notes directly into the Voice I want them in. For example ...

(I usually do this a system [3-10 measures] at a time.)
Press N to enable note entry; it defaults to Voice 1.
Enter the notes of Voice 1 to the whole system.
Move cursor back to the beginning of the system.
Press Ctrl+Alt+2 to switch to note entry in Voice 2.
Now enter the whole system's worth of notes to Voice 2.

In the event that notes are needed in Voices 3 and 4, I repeat this sequence for those notes after pressing Ctrl+Alt+3 or Ctrl+Alt+4.

If you want to you certainly can enter the Voice 2 notes first. Press N and then immediately press Ctrl+Alt+2 to switch to note entry in Voice 2. It will simply create rest(s) in Voice 1, placeholders until you are ready to enter notes into Voice 1. Leaving Voice 1 empty is usually undesirable and these rests cannot be deleted, only made invisible.

Reply

• Apr 30, 2024 - 18:21

OP said, "I have a piece of music with a melody in voice 1. I'd like to transfer it to voice 2. It seems to work, except where I have triplets (other duplets are available). Triplets seemed to be stubbornly locked to the voice they were created in."

Then they said, "I was using Ctrl + Alt + 2, or using the voice 2 icon from the toolbar."

That's what I was talking about in the first part of my note, and that's definitely what OP was talking about. It works on other notes, but not on tuplets, which seems a (very, very minor) bug.

The second part of my note, I was just generally talking about how to enter the notes into voices directly, which may have been the reason they were trying to move the notes to Voice 2. (Certainly, it may not have as well. I was just guessing.)

Reply

• Apr 30, 2024 - 19:17

This is not a bug, it was never implemented. The voice transfer was never designed to handle tuplets.
There was even a time (throughout Version 2, and some versions of V3) when it didn't work with tied notes either (see: https://musescore.org/en/node/273129, or https://musescore.org/en/node/269604, among many others. Same numerous posts with tuplets, like this one opened two days back)
The appropriate function, designed for this purpose, can be found at the menu Tools/Voices/Exchange voices
See: https://github.com/musescore/MuseScore/issues/13519

Reply

• May 1, 2024 - 23:25

When the same action has different effects, that's a bug. Sorry.

Selecting a note or range of notes, then pressing Alt++Ctrl+2 should either have no effect on any type of note (the correct response, IMO), or it should move the note(s) to Voice 2, regardless of the type of note. It should not respond differently to one sort of note versus another.

Reply

• May 2, 2024 - 02:50

At least if it moves everything but the duplet, that's something (IMO). Consider that when you C+P a range of measures that happen to contain a meter change, the meter change isn't copied. Bug? Maybe. Or maybe it isn't in the programing. Just like the duplet thing. It seems to me that a real bug is something that is supposed to work, But doesn't. Regardless of what we think is correct.
There are so many people complaining about MU4. Mainly because it doesn't work the same way MU3 does. And it surly doesn't. I get it. We can knit pick over details that are important to us. We can refuse to use MU4 until something important to us is restored. There is no reason to use MU4 in those cases. I get it. Fine, use 3.6 or 3.7. No problem.
But I write for playback. 99% of the time. Older versions don't come close for me. For things that don't work, I either find a workaround. Or I do something different.

Reply

• Apr 30, 2024 - 19:42

Thanks for your replies.

I was in the process of manually creating a grand staff of a four voice choir: SATB, where I'd originally created it on four staves, each voice in voice 1 on their own dedicated stave.

I'd not thought of using that exchange voice function, because I didn't think I wanted to exchange voices - I simply wanted to change the voice. But it works fine using exchange to change.

Reply

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