DC segno doesn't go all the back to the beginning.
In this piece, DC segno doesn't go all the back to the beginning. It doesn't repeat sections either; it just plays through them. What's more, it doesn't skip over the 1st ending and go directly to the second; it plays through the first ending into the second.
I must be notating it wrong. What is the right way to input this?
| Attachment | Size |
|---|---|
| p119 p120 p121a.jpg | 1.96 MB |
| p119 p120 p121a.mscz | 26.73 KB |
Comments
- Repeats are generally not taken after jumps. The next Major Version woll allow for this, there jumps have an extra property "with repeats".
- You confused the hell out of MuseScore:
* having an end repeat barline () with no matching start repeat barline
* having a an invisible D.C. and and a "D.C al fine" (with the text "al")
* having 2 Segnos, both named segno
* using voltas incorrectly (dragging with mouse rather than extending with shift+left)
In reply to - Repeats are generally not by Jojo-Schmitz
Ah. Confusion. I know it well. I've got copy and paste down, but that doesn't mean I know what I'm doing. ;)
The number one rule for Distributed Proofreaders is to not change what the author wrote. Typos in text are a little simpler to deal with than typos or errors in music transcription. Especially when what may have been logical to the original scribe is not applicable in the era of computer technology.
I'm guessing the reason the music returns to the second repeat instead of the first is because of the end repeat bar with the Segno. It finally returns to the first repeat and runs through again, this time going to the coda.
I'm having a problem with bar 21 not playing on the first repeat. I've deleted both bars 20 and 21 and then reinserted and rewritten them, hoping to get rid of a glitch somewhere. Bar 21 plays just fine on your example. It would be easy to just use your output and trash mine, but then I would never figure out the problem and be sure not to repeat it. Here's my current copy....
EDIT: Got it! Deleted the voltas and reinserted using shift left instead of just left. Everything works fine now. Not on this copy, but on the one in my computer. :) Thanks for all your help! LOVE this stuff! Most fun I've had in a long time. Glad to be here. And glad you're here too! <3
In reply to Ah. Confusion. I know it by judeeylander
It is the eand repeat barline in measure 24 that is throwing things off track (from there it jumps to what it thinks to be the matching start repeat, which in this case is the one in measure 5, not fixable playback wise without removing that end repeat barline), and the volta in measure 21, which has only grafically been extended to measure 24, not logically, see https://musescore.org/en/handbook/volta on how to extend a volta properly.
Also why using Staff text instead of Tempo text for "All.o mod.to" and "Più allegro"?
That use of f and p directly after one another, where the p is for the 2nd volta won't work playback wise.
In reply to It is the eand repeat barline by Jojo-Schmitz
Edits to correct glaring typos, or in this case music notation that doesn't work, are okay in Distributed Proofreaders. I just have to add a note that minor corrections have been made. It's okay to remove the repeat in measure 24 and replace it with a double bar to make it play right. Thank you for figuring it out! I read and play music, but my music theory is limited to my own experience at the church piano. Musescore is a whole new learning curve, and I love it!
I read the handbook on volta and watched the YouTube video suggested there. Wow! What wonderful information. I tend to learn as I go, researching things when an issue comes up. Reading without application never sticks with me. If I can apply it, I'll remember it. Even if I only remember where to look it up. ;)
When recreating music for an online book, I try to be as true to the original tempo as possible. Tempo is always a range. I use the actual note value to establish tempo and text to write the words. I want to be as close to what people expect to hear. In this book, there are several snippets used to illustrate motto variations. I want to make sure all of them play at the same speed so the listener will recognize them when they hear the full composition.
YouTube has several examples of La Media Caña, all played at 140bpm. I inserted hidden 140bpm on the snippets. "All.o mod.to" and "Più allegro" are ranges. I figured out the bpm for "All.o mod.to". I'll have to listen to the music again to figure out "Più allegro". Then I'll insert the actual bpm and hide it.
The f and p in measure 30 are what's written. It will play one or the other, but it won't play f and repeat p. Is there a way to silence this portion of the main composition and insert a hidden score that plays a continuous f then p instead?
In reply to Edits to correct glaring by judeeylander
For Tempi you still should better use tempo text and set the BMP for them manually via inspector rather than relying on 'follow text' and/or add invisible tempo texts
Dynamics and voltas discussed at https://musescore.org/en/node/218396
In reply to For Tempi you still should by Jojo-Schmitz
I found it. I didn't know I could set bpm through the Inspector. Thanks!