|
From: | Mats Bengtsson |
Subject: | Re: lyrics following split voices |
Date: | Wed, 06 Aug 2008 14:26:47 +0200 |
User-agent: | Thunderbird 2.0.0.5 (X11/20070716) |
Trevor Daniels wrote:
So, for the example in question, the NR should certainly state categorically what the voice names are in the various constructs, and examples showing the differences would be fine. But I don't think there is any need to put lengthy explanations in the NR - it's a reference document - they really need to go in the LM.So maybe we need an explanation of using voice naming in this way somewhere in the LM. Any suggestions? And the NR should certainly list all the context names that are assigned by default somewhere. Perhaps I'll work that into the section on Contexts. What do you think?
Note that the use of the trick \new Voice = "1" { ... <<{...} \\ {...}>> ... }only works if you have a single Staff (or at most one Staff with polyphony), since otherwise you would have several \new Voice = "1" in the same score, which doesn't work. Therefore, it's fairly esoteric and perhaps something that shouldn't be taught in the LM.
/Mats
Trevor----- Original Message ----- From: "Francisco Vila" <address@hidden>To: "Mats Bengtsson" <address@hidden>; <address@hidden>Cc: "Paul Scott" <address@hidden>; "LilyPond User" <address@hidden>Sent: Wednesday, August 06, 2008 12:47 AM Subject: Re: lyrics following split voices2008/8/5 Mats Bengtsson <address@hidden>:I'm surprised that nobody answered exactly this question. If you name your main voice "1", then the upper voice of the <<{...} \\ {...} >> constructwill stay the same Voice context as the single voice.That's true, it is explained in LM 3.2.1 I'm hearing Voices ...tangentially. One has to deduct this when he reads 'The Voice contexts bear the names "1", "2", etc.' I propose: to add some lines explaining this very case: how to make the single voice to keep being the same, although a second voice arrives. LM 3.2.2 Explicitly instantiating voices does explain that (the red diamonds example), but does not mention the trick of calling the voice "1" ! It rather uses a simple << .. \new Voice>> construct.Note, though that the<<{...} \\ {...} >> construct will add property settings equivalent to the \voiceOne command, so you have to explicitly insert a \oneVoice afterwardsto revert to the default settings:Again, this is only tangentially explained in LM 3.2.2 because the \oneVoice command is used with no previous <<\\>>construct ! I could not have figured this, without your help. Thanks! Now I suppose I have to take the compromise to write this down in NR Simultaneous Notes. -- Francisco Vila. Badajoz (Spain) http://www.paconet.org _______________________________________________ lilypond-devel mailing list address@hidden http://lists.gnu.org/mailman/listinfo/lilypond-devel_______________________________________________ lilypond-user mailing list address@hidden http://lists.gnu.org/mailman/listinfo/lilypond-user
-- ============================================= Mats Bengtsson Signal Processing School of Electrical Engineering Royal Institute of Technology (KTH) SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: address@hidden WWW: http://www.s3.kth.se/~mabe =============================================
[Prev in Thread] | Current Thread | [Next in Thread] |