![]() As we keep explaining, the text works perfectly out of the box for all new new or relatively-recently-created created. The usefuyl end will come if you do as we have repeatedly asked and actually attach your score and give precise steps to reproduce the problem you are perceiving. If you do apply the predefined "pizz" text from the text-pallet, and then right-click on it and select "Staff Text Properties" you will see that it will assign voice 1 to the "pizz" sound. Not all staff texts will want to apply voice sound changes.Īnd it is not clear that you have tried method 2. It also has no voice selected for any of the channels, which I guess you think is OK. You would want it to say "pizz" in channel 1 if you previously on the staff did that change. It always shows a dialog where all channels have "arco" pre-selected. My understanding is that you John are using method 1 above, and are annoyed that when you do this for the second time on a staff, to switch back to arco, the predefined selection in the dialog-window does not show the "current" setting on the branch. These predefined text already are set up to change voice 1 to pizz/arco. Add predefined "pizz" and "arco" staff-texts from the "text" pallet on the left. Then right-click the text and select "Staff Text Properties", and define which voices should use which "sound".Ģ. Adding a staff text from the Add→Text→Staff Text menu. JoJo just wants to help.Īfter reading through the conversation I think the possible source of the confusion is that there are two ways to do this:ġ. I think there is no sarcasm involved here. I can't remember the last time I ever needed to resort to this dialog. Simply add the text from the palette and everything works perfectly right out of the box. Unless you are doing something unusual, you never need to open this dialog. Luckily, as mentioned, dealing with this dialog also completely unnecessary in most cases. We always welcome specific suggestions on these counts! No doubt it would be possible to design a dialog that worked different and didn't require this selection, and no doubt it would be possible to improve the documentation. It would be great indeed if somehow MuseScore could guess your intent, but unfortunately since this dialog is used for multiple different types of text, it's not possible in general to know. ![]() If you want it to be all voices, great, select all voices. If you want it to be voice 2, great, select voice 2. If you want it to be voice 1, great, select voice 1. The staff text properties does one thing here: it allows you to specify which voices the sound change will apply to. Don't think of it as being about whether you've "changed" voices or whether you have "selected" a voice or whether you are "affirming" or "reaffirming" anything.
0 Comments
Leave a Reply. |