[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-user
Subject:    Re: Lirics in repeated multi-voice bar
From:       Jogchum Reitsma <j.reitsma () hccnet ! nl>
Date:       2022-03-31 10:55:23
Message-ID: 8ce5949c-0c17-688b-faef-6030673c6053 () hccnet ! nl
[Download RAW message or body]

Op 30-03-2022 om 04:42 schreef David Wright:
> On Tue 29 Mar 2022 at 10:55:01 (-0600), Carl Sorensen wrote:
>> On Tue, Mar 29, 2022 at 5:08 AM Jogchum Reitsma<j.reitsma@hccnet.nl>  wrote:
> <...>
> The song has three (double-)verses, and the underlay is trivially
> different for the altos in verse one around measure 7, which might
> be a reason for setting it separately.
>
> (Three lines of German might also be difficult for some.)
Yes, I agree, although I don't think three German lines would pose a 
real problem to our (Dutch) choir
> However, the split bass at the end causes no problems at all: just
> add a new voice for one part, and let the lyrics carry through in
> the other (ie no change for them), eg:
>
>    fs1 fs4( gs) gs( fs)
>    cs\breve
>    < fs, cs' >\breve
>    << { \voiceTwo fs\breve ~ fs1 fs } \new Voice { \voiceOne cs'\breve ~ cs1 ds } >>
>    < gs, cs, >\breve

I'm not sure how to interpret this code. If I insert it on the pace at 
hand in my score, I get error messages saying "fs is not a note name", 
and so on. Or is the mail system distorting your message?

Deleting all the 's'-es (fs, gs, and so on) of course removes that error 
messages. But than I'm not sure why you are coding \breve notes here - 
Iḿ not surprised that inserting that in my code gives strange results... 
Besides that, the f's should be f-sharp, an the compiler complains about 
ties not being able to end.

As I see it, the high bass-line should read (after the half note rest)
g2 | f-sharp1(~ |   f-sharp4 e) e2 |

and the lower bass-line
g,2 | f-sharp2( b4 g-sharp | a2) a

The last bar is one voice again, <d d,>2 \fermata r2

See the "original", after which I coded the piece

But maybe I don't understand you correctly?

I think that what you mean by "just add a new voice for one part, and 
let the lyrics carry through in the other" is, at least for placing the 
lyrics, what I did in my answer to Carl's message (see my reaction to 
him above)

> (In case you wonder why there are two parts here, and not chords,
> it is of course because it's   \voiceOne cs'\breve cs1( ds)
> in the original score.)
No, I didn't wonder :-)
> Cheers,
> David.

many thanks, and regards, Jogchum

[Attachment #3 (multipart/related)]

[Attachment #5 (text/html)]

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">Op 30-03-2022 om 04:42 schreef David
      Wright:<br>
    </div>
    <blockquote type="cite" cite="mid:20220330024204.GA16667@axis.corp">
      <pre class="moz-quote-pre" wrap="">On Tue 29 Mar 2022 at 10:55:01 (-0600), Carl \
Sorensen wrote: </pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">On Tue, Mar 29, 2022 at 5:08 AM Jogchum \
Reitsma <a class="moz-txt-link-rfc2396E" \
href="mailto:j.reitsma@hccnet.nl">&lt;j.reitsma@hccnet.nl&gt;</a> wrote: </pre>
      </blockquote>
      &lt;...&gt;
      <pre class="moz-quote-pre" wrap="">The song has three (double-)verses, and the \
underlay is trivially different for the altos in verse one around measure 7, which \
might be a reason for setting it separately.

(Three lines of German might also be difficult for some.)</pre>
    </blockquote>
    Yes, I agree, although I don't think three German lines would pose a
    real problem to our (Dutch) choir
    <blockquote type="cite" cite="mid:20220330024204.GA16667@axis.corp">
      <pre class="moz-quote-pre" wrap="">However, the split bass at the end causes no \
problems at all: just add a new voice for one part, and let the lyrics carry through \
in the other (ie no change for them), eg:

  fs1 fs4( gs) gs( fs)
  cs\breve
  &lt; fs, cs' &gt;\breve
  &lt;&lt; { \voiceTwo fs\breve ~ fs1 fs } \new Voice { \voiceOne cs'\breve ~ cs1 ds \
} &gt;&gt;  &lt; gs, cs, &gt;\breve
</pre>
    </blockquote>
    <br>
    <p>I'm not sure how to interpret this code. If I insert it on the
      pace at hand in my score, I get error messages saying "fs is not a
      note name", and so on. Or is the mail system distorting your
      message?</p>
    <p>Deleting all the 's'-es (fs, gs, and so on) of course removes
      that error messages. But than I'm not sure why you are coding
      \breve notes here - Iḿ not surprised that inserting that in my
      code gives strange results... Besides that, the f's should be
      f-sharp, an the compiler complains about ties not being able to
      end.</p>
    <p>As I see it, the high bass-line should read (after the half note
      rest)<br>
      g2 | f-sharp1(~ |   f-sharp4 e) e2 | <br>
    </p>
    <p>and the lower bass-line<br>
      g,2 | f-sharp2( b4 g-sharp | a2) a <br>
    </p>
    <p>The last bar is one voice again, &lt;d d,&gt;2 \fermata r2</p>
    <p>See the "original", after which I coded the piece</p>
    <p>But maybe I don't understand you correctly?<br>
    </p>
    <p><img src="cid:part1.lmMD3cTU.vtrVHcjv@hccnet.nl" alt=""></p>
    <p>I think that what you mean by "just add a new voice for one part,
      and let the lyrics carry through in the other" is, at least for
      placing the lyrics, what I did in my answer to Carl's message (see
      my reaction to him above)<br>
    </p>
    <blockquote type="cite" cite="mid:20220330024204.GA16667@axis.corp">
      <pre class="moz-quote-pre" wrap="">
(In case you wonder why there are two parts here, and not chords,
it is of course because it's   \voiceOne cs'\breve cs1( ds)
in the original score.)</pre>
    </blockquote>
    No, I didn't wonder :-)
    <blockquote type="cite" cite="mid:20220330024204.GA16667@axis.corp">
      <pre class="moz-quote-pre" wrap="">Cheers,
David.
</pre>
    </blockquote>
    <p>many thanks, and regards, Jogchum<br>
    </p>
  </body>
</html>


["AW5SrHWSMcaFYEHN.png" (image/png)]

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic