Re: Installing 2.24

2022-12-16 Thread JxStarks
No, I haven't. Thank you for the direction.

Jerry

On Thu, Dec 15, 2022, 8:33 PM Jean Abou Samra  wrote:

> Le 16/12/2022 à 02:25, JxStarks a écrit :
> > Greetings,
> >
> > I'm feeling rather foolish. I'm running under Windows 10 and use
> > Frescobaldi (3.1.2) as my main interface with LilyPond. I have
> > downloaded LilyPond 2.24 and un-zipped the files.
> >
> > Where is the Go button? How do I install 2.24? I haven't found
> > anything like an install.exe. Am I missing the obvious?
>
> Have you read
> https://lilypond.org/doc/v2.24/Documentation/learning/installing?
>


Installing 2.24

2022-12-15 Thread JxStarks
Greetings,

I'm feeling rather foolish. I'm running under Windows 10 and use
Frescobaldi (3.1.2) as my main interface with LilyPond. I have downloaded
LilyPond 2.24 and un-zipped the files.

Where is the Go button? How do I install 2.24? I haven't found anything
like an install.exe. Am I missing the obvious?

Jerry


Re: Horizontal spacing for a few measures

2022-06-12 Thread JxStarks
Thanks David! I'll put these all in my 'toolbox'.

Jerry

On Sun, Jun 12, 2022 at 5:41 PM David Wright 
wrote:

> On Sun 12 Jun 2022 at 07:39:10 (-0700), Knute Snortum wrote:
> > On Sat, Jun 11, 2022 at 3:27 PM JxStarks  wrote:
> > >
> > > Thank you! The "page-count = 1" worked for this example, so I'll keep
> it in my toolbox.
> > > If I wanted to use the #(set-global-staff-size 19.8), where would I
> put it? I tried in the \paper { } section and LP told me it didn't belong
> there and ignored it.
> >
> > I usually put it near the top on the same level as the \version
> > command, that is, outside of any block.
>
> My positioning is similar for single scores, where I have:
>
>version
>language
>includes
>header
>  . miditempo (if used just for proofreading)
>  . global staff size
>  . paper
>  . default layout
>parts (global, SATB, lyrics)
>score
>
> which keeps the "tunables" together.
>
> But I often need multiple scores (a cappella choral, a piano reduction,
> or vocal on two and four staves) from the same parts. For those, I put
> each score in a \book, prefixed with its individual global staff size
> (and there may be specific layout options and extra headers added to
> the end of each type of score).
>
> Cheers,
> David.
>


Re: Horizontal spacing for a few measures

2022-06-12 Thread JxStarks
Got it. Thanks!

Jerry

On Sun, Jun 12, 2022 at 10:39 AM Knute Snortum  wrote:

> On Sat, Jun 11, 2022 at 3:27 PM JxStarks  wrote:
> >
> > Thank you! The "page-count = 1" worked for this example, so I'll keep it
> in my toolbox.
> > If I wanted to use the #(set-global-staff-size 19.8), where would I put
> it? I tried in the \paper { } section and LP told me it didn't belong there
> and ignored it.
>
> I usually put it near the top on the same level as the \version
> command, that is, outside of any block.
>
> --
> Knute Snortum
>


Re: Horizontal spacing for a few measures

2022-06-11 Thread JxStarks
Thank you! The "page-count = 1" worked for this example, so I'll keep it in
my toolbox.
If I wanted to use the #(set-global-staff-size 19.8), where would I put it?
I tried in the \paper { } section and LP told me it didn't belong there and
ignored it.

Thanks again for your help.
Jerry

On Sat, Jun 11, 2022 at 2:17 PM David Wright 
wrote:

> On Sat 11 Jun 2022 at 11:24:26 (-0400), JxStarks wrote:
> > I'm transcribing some hymns for use in my church (because I can make the
> > text larger), and I've noticed a problem. I like to make the introduction
> > as \tiny notes, then change to \normalsize for the body of the hymn.
> When I
> > first complete the transcription, the \tiny notes are compacted nicely,
> and
> > the hymn fits on one page. (See Example-1) If I transpose the hymn, the
> > \tiny notes become full-sized measures, and the hymn pushes one line onto
> > the next page. (See Example-2).
> >
> > Is there a way to force a compact horizontal spacing for the first 2 or 3
> > measures, then have standard spacing for the rest of the music?
>
> I added  \paper { ragged-right = ##t }  to the top of your code,
> copied the \score, and added  \transpose c ees  to one of them.
> The increase in width corresponds with the space taken by the
> key signature.
>
> So it appears that LP wanted just a little more space to set your
> hymn, and pushed onto a second page. You could try just replacing
> my ragged-right = ##t, above, with  page-count = 1  and seeing if
> LP will just manage to squeeze it in.
>
> If not, a tiny adjustment to \tiny might help, or even a line like:
>
>   #(set-global-staff-size 19.8)
>
> (rather than 20).
>
> Others may have some more heterogeneous solutions. These are final
> adjustments, after you've laid out the lines of the rest of the hymn.
> (For example, from what I can read of your hymn, I'd likely be
> breaking the line at the middle of measure 6, and so on.)
>
> Cheers,
> David.
>


Re: Concert pitch question (confused ex-tuba player)

2021-09-18 Thread JxStarks
I frequently speak in generalities, trying to show a pattern rather than an
exact example. Thank you for your clarification. I apologize for any
confusion I caused.

Jerry

On Sat, Sep 18, 2021, 1:47 AM Lukas-Fabian Moser  wrote:

> Hi Jerry,
>
> Am 18.09.21 um 00:22 schrieb JxStarks:
> > Hi Kenneth,
> >  I use LilyPond v 2.22.1 through Frescobaldi. When I'm dealing with
> > transposing instruments I arrange everything in C, then transpose the
> > parts. I would write a trumpet part like this:
> >
> > trumpet = \transpose c bes {
> >\global
> >notes, etc,
> >   }
> > }
> >
> > This way I can insert a % to comment out the transposition when I want
> > Lilypond's MIDI to play it for me:
> > trumpet = %\transpose c bes {
> >\global
> >notes, etc,
> >   %}
> > }
> >  When printing the parts, I remove the % signs, and they print out in
> > the transposed key.
>
> I think that's wrong in multiple ways.
>
> First: "c" and "bes" are from the same octave, so they are a 7th apart.
> This is not the usual transposition of a Bb trumpet: It should be c' and
> bes, for example.
>
> Second: Your description sounds as if "notes" are meant "in C" (concert
> pitch, "sounding") (because you do not want \transpose for MIDI
> generation). Then your transposition goes in the wrong direction: If
> \mus contains concert pitch music, it has to be printed by
>
> \transpose bes c' \mus
>
> or equivalently
>
> \transpose c d \mus
>
> in order to be played correctly by a player using a Bb trumpet, as
> explained by various people in this thread. (For a written "d", a Bb
> trumpet gives a "physical" "c"; so in order to get a "c", one has to
> write a "d", and so forth.)
>
> Lukas
>
>


Re: Concert pitch question (confused ex-tuba player)

2021-09-17 Thread JxStarks
Hi Kenneth,
 I use LilyPond v 2.22.1 through Frescobaldi. When I'm dealing with
transposing instruments I arrange everything in C, then transpose the
parts. I would write a trumpet part like this:

trumpet = \transpose c bes {
   \global
   notes, etc,
  }
}

This way I can insert a % to comment out the transposition when I want
Lilypond's MIDI to play it for me:
trumpet = %\transpose c bes {
   \global
   notes, etc,
  %}
}
 When printing the parts, I remove the % signs, and they print out in the
transposed key.

Hope this helps.
Jerry

On Fri, Sep 17, 2021 at 5:09 PM Kenneth Wolcott 
wrote:

> HI All;
>
>   I have a couple downloaded examples of brass quartet arrangements
> (theme excerpts mostly) forn 8notes.com, hosted by UK composer David
> Bruce, where each part is apparently NOT in concert pitch, but the
> parts are together, as they would be in a conductor's score.  The
> music, engraved as written, sounds AWFUL.  I suspect that I need to
> run transpose on each part to convert them to concert pitch, but I
> don't know for sure if that's the case and if so, exactly how to do
> that.  I have attached one example pdf to illustrate my question.
>
>   I know, as an ex-tuba player (and a very low-level amatuer tuba
> player), that tuba and trombone (bassoon?) don't require transposition
> as they are already in concert pitch (I never played a tuba in the key
> of C, F or Eb).  However most of the other wind instruments of an
> orchestra are not in concert pitch.  So when there is a trumpet in Bb,
> it certainly is not the same as a tuba in Bb, correct?  What about
> Horn in F?  What happens when the overall pitch of the piece in
> question is not C Major?
>
>   I've taken some church hymns, written for SATB (obviously) and
> converted them directly to a brass quartet (Soprano toTrumpet, Alto to
> French Horn, tenor to Trombone, and Bass to Tuba) and it doesn't sound
> bad, using the exact key the Hymn was written in.
>
>   Could someone clue me in on the basics here (I've read the Lilypond
> manuals on this topic, but I think I need a more rudimentary
> explanation).
>
> Thanks,
> Ken Wolcott
>


Re: Midi Instrument: change?

2021-09-04 Thread JxStarks
Thanks, David. This works a lot easier.
Jerry

On Sat, Sep 4, 2021 at 4:51 PM David Kastrup  wrote:

> Guy Stalnaker  writes:
>
> > See
> >
> http://lilypond.org/doc/v2.19/Documentation/notation/midi-channel-mapping
> >
> > Where the method is shown. Basically, you put the instrument into the
> > Voice context:
> >
> > %%% Code
> >
> >   \midi {
> > \context {
> >   \Staff
> >   \remove "Staff_performer"
> > }
> > \context {
> >   \Voice
> >   \consists "Staff_performer"
> > }
> >
> > %%% Code
> >
> > You'll see how it works. I do this all the time.
>
> Frankly, I have no idea what you all are talking about.
>
>
> Works fine without moving the Staff_performer.
>
> --
> David Kastrup
>


Re: Midi Instrument: change?

2021-09-04 Thread JxStarks
This is great! Thanks for your help.

Jerry

On Fri, Sep 3, 2021 at 8:46 PM Guy Stalnaker  wrote:

> See
> http://lilypond.org/doc/v2.19/Documentation/notation/midi-channel-mapping
>
> Where the method is shown. Basically, you put the instrument into the
> Voice context:
>
> %%% Code
>
>   \midi {
> \context {
>   \Staff
>   \remove "Staff_performer"
> }
> \context {
>   \Voice
>   \consists "Staff_performer"
> }
>
> %%% Code
>
> You'll see how it works. I do this all the time.
>
> Regards,
>
> GuyS
> On 9/3/21 7:36 PM, JxStarks wrote:
>
> Hi all,
> Is it possible to change the midi-instrument in the middle of a part? This
> is particularly useful for strings voices which do occasional pizzicato
> sections. It seems awfully cumbersome to write a whole part just for 5 or 6
> measures of pizzicato. How would the change (and the change back) be coded?
>
> Thanks in advance,
>
> Jerry
>
> --
> --
>
> “Happiness is the meaning and the purpose of life, the whole aim and end of 
> human existence.”
>
> ― Aristotle
>
>


Midi Instrument: change?

2021-09-03 Thread JxStarks
Hi all,
Is it possible to change the midi-instrument in the middle of a part? This
is particularly useful for strings voices which do occasional pizzicato
sections. It seems awfully cumbersome to write a whole part just for 5 or 6
measures of pizzicato. How would the change (and the change back) be coded?

Thanks in advance,

Jerry


Re: Stanzas and refrain

2021-08-26 Thread JxStarks
Hi Carlos,

I do a lot of this sort of thing for my church. I usually use the following
format:

\header { }
global { }
chordNames \ chordmode { \global chord, chord, chord, etc.}
melody = \relative c '' { \global   music, music, music, etc }
verse = \lyricmode { \set stanza = "1. " words, words, words, etc, chorus }

\score {
  <<
\new ChordNames \chordNames
\new Staff { \melody }
\addlyrics { \verse }
\addlyrics { \set stanza = "2. " words, words, words, etc (no chorus) }
\addlyrics { \set stanza = "3. " words, words, words, etc (no chorus) }
  >>

Ths words for the chorus only need to be in Verse 1, unless they change
each time. Also, because I'm old, I add this after the '\set stanza' at the
beginning of each word section:
\override LyricText font-size = 3
That makes it a lot easier for these old eyes to read.

Good luck with your work!

Jerry

On Thu, Aug 26, 2021 at 8:06 AM Carlos R Martinez <
car...@newsoundmusicstudio.com> wrote:

> Hi,
>
> How do I setup a lead sheet with 3 stanzas and 1 chorus/refrain.
>
> I need the refrain/chorus in the middle of the page after the verses
>
> Thanks
>
> --
>
>
>


Re: convert-ly

2021-06-03 Thread JxStarks
Thanks Hans: that did the trick. I guess I need to practice reading to the
end of the section before launching into trial-and-error. :-)

Jerry

On Thu, Jun 3, 2021 at 1:22 AM Hans Aikema  wrote:

>
> On 3 Jun 2021, at 02:34, JxStarks  wrote:
>
> 
> Some progress (cheers!):
> Re-naming the file to convert-ly.py enabled my system to treat it like an
> executable file. However, now it says it can't open the files:
> ===
> C:\Users\Jerry\Documents\RPC\Music\Christmas>convert-ly.py -e *.ly
> convert-ly.py (GNU LilyPond) 2.22.1
>
> convert-ly.py: error: *.ly: Unable to open file
> convert-ly.py: warning: There was 1 error.
>
> C:\Users\Jerry\Documents\RPC\Music\Christmas>
> ===
>
> There are 34 LilyPond files (all ending with .ly) in this folder. However,
> the multi-word names are separated by dashes, as in
> "It-Came-Upon-A-Midnight-Clear.ly". Does this confuse convert-ly?
> Am I missing something else?
>
> Jerry
>
>
> Jerry,
>
> the convert-ly script does not interpret wildcards, but requires the file
> explicitly. The way you call it makes it look for a file that is named *.ly
> (which can never be present as * is not an allowed character for a filename)
>
> As documented on
> https://lilypond.org/doc/v2.22/Documentation/usage/invoking-convert_002dly
> you need to use the 'forfiles' windows command to run the conversion for
> multiple files using a wildcard:
>
> forfiles /s /M *.ly /c "cmd /c convert-ly.py -e @file"
>
>


Re: convert-ly

2021-06-02 Thread JxStarks
Some progress (cheers!):
Re-naming the file to convert-ly.py enabled my system to treat it like an
executable file. However, now it says it can't open the files:
===
C:\Users\Jerry\Documents\RPC\Music\Christmas>convert-ly.py -e *.ly
convert-ly.py (GNU LilyPond) 2.22.1

convert-ly.py: error: *.ly: Unable to open file
convert-ly.py: warning: There was 1 error.

C:\Users\Jerry\Documents\RPC\Music\Christmas>
===

There are 34 LilyPond files (all ending with .ly) in this folder. However,
the multi-word names are separated by dashes, as in
"It-Came-Upon-A-Midnight-Clear.ly". Does this confuse convert-ly?
Am I missing something else?

Jerry

On Mon, May 31, 2021 at 10:44 PM Brian Barker 
wrote:

> At 15:18 31/05/2021 -0700, Knute Snortum wrote:
> >Then rename convert-ly to convert-ly.py. Windows won't be able to
> >know that it's a Python program otherwise.
>
> *Again*, I don't have this problem: I'm just trying to encourage
> accurate responses to others. Did you not notice that I suggested
> this renaming earlier? (Yes: really, I did!) You cannot "check that
> ... convert-ly.py ...[is] in that folder" when it isn't.
>
> Brian Barker
>
>
>


Re: convert-ly

2021-05-31 Thread JxStarks
or do I need to have some reference to Python in my PATH command?  If so,
what should it look like?

Jerry

On Mon, May 31, 2021 at 3:19 PM JxStarks  wrote:

> Hi all,
>
> Thanks for your many and informative responses. M.Tarenskeen correctly
> identified a typo in my PATH command ("C;" instead of "C:"). I corrected
> that, but the problem still persists. Here's my latest info from the
> Command Prompt:
> ===
> C:\Users\Jerry\Documents\RPC\Music\FILE>echo %PATH%
> C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
> Files
> (x86)\LilyPond\usr\bin;C:\Users\Jerry\AppData\Local\Microsoft\WindowsApps;
>
> C:\Users\Jerry\Documents\RPC\Music\FILE>convert-ly *.ly
> 'convert-ly' is not recognized as an internal or external command,
> operable program or batch file.
> ===
> Note: I tried both convert-ly and convert-ly.py, and neither one works for
> me.
>
> At some iteration in the past, the PATH command was "[pre-set
> paths];C:\Program Files (x86)\LilyPond\usr\bin;"
>
> Is it necessary to have the [pre-set paths] and the quotation marks?
>
> Jerry
>
> On Mon, May 31, 2021 at 2:27 PM Brian Barker 
> wrote:
>
>> At 11:04 31/05/2021 -0700, Knute Snortum wrote:
>> >I suggest you rename the file to that, ...
>>
>> For what it's worth, I didn't have this problem: that was Jerry
>> Starks. Is he now happy? I was merely concerned that I was watching a
>> conversation that seemed to include no doubt well-intentioned but
>> misleading responses, including simple reference to the inaccurate
>> documentation.
>>
>> Brian Barker
>>
>>
>>


Re: convert-ly

2021-05-31 Thread JxStarks
Hi all,

Thanks for your many and informative responses. M.Tarenskeen correctly
identified a typo in my PATH command ("C;" instead of "C:"). I corrected
that, but the problem still persists. Here's my latest info from the
Command Prompt:
===
C:\Users\Jerry\Documents\RPC\Music\FILE>echo %PATH%
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
Files
(x86)\LilyPond\usr\bin;C:\Users\Jerry\AppData\Local\Microsoft\WindowsApps;

C:\Users\Jerry\Documents\RPC\Music\FILE>convert-ly *.ly
'convert-ly' is not recognized as an internal or external command,
operable program or batch file.
===
Note: I tried both convert-ly and convert-ly.py, and neither one works for
me.

At some iteration in the past, the PATH command was "[pre-set
paths];C:\Program Files (x86)\LilyPond\usr\bin;"

Is it necessary to have the [pre-set paths] and the quotation marks?

Jerry

On Mon, May 31, 2021 at 2:27 PM Brian Barker 
wrote:

> At 11:04 31/05/2021 -0700, Knute Snortum wrote:
> >I suggest you rename the file to that, ...
>
> For what it's worth, I didn't have this problem: that was Jerry
> Starks. Is he now happy? I was merely concerned that I was watching a
> conversation that seemed to include no doubt well-intentioned but
> misleading responses, including simple reference to the inaccurate
> documentation.
>
> Brian Barker
>
>
>


Re: convert-ly

2021-05-30 Thread JxStarks
Thanks, Hans. I checked it out:
[image: image.png]
It appears that it's looking in the LilyPond/usr/bin folder, which is where
it should be looking, right?

Jerry

On Sun, May 30, 2021 at 6:51 PM Hans Aikema  wrote:

> check the your windows executable search path
>
> echo %PATH%
>
> most likely it's missing your lilypond binaries location
>
> On 31 May 2021, at 00:44, JxStarks  wrote:
>
> 
> Here's a screenshot:
> 
>
>
>
> On Sun, May 30, 2021 at 5:50 PM JxStarks  wrote:
>
>>
>> Hi Ralph,
>>
>> I read that documentation and tried it. I'm running Windows 10 Pro,
>> 10.0.19041 and I still get the same response: " 'convert-ly is not
>> recognized...". Am I missing something obvious?
>>
>> Jerry
>>
>>
>> On Sun, May 30, 2021 at 4:43 PM Ralph Palmer 
>> wrote:
>>
>>>
>>>
>>> On Sun, May 30, 2021 at 1:24 PM JxStarks  wrote:
>>>
>>>> What's the trick for using convert-ly in a Windows Command Prompt
>>>> window? I copied the convert-ly file into the directory where I want to
>>>> convert everything in it, and entered convert-ly *.ly. This produced the
>>>> error message " 'convert-ly' is not recognized as an internal or external
>>>> command, operable program or batch file".
>>>>
>>>> Then I entered convert-ly.py *.ly and it produced the same error
>>>> message.
>>>>
>>>> What's the trick?
>>>>
>>>
>>> Hi, Jerry -
>>>
>>> Please take a look at the entry in the documentation :
>>>
>>> https://lilypond.org/doc/v2.19/Documentation/usage/invoking-convert_002dly
>>>
>>> It tells how to run convert-ly on a single file, all files in a
>>> directory, or all files on the computer, for Linux, Apple, and Windows.
>>>
>>> All the best,
>>>
>>> Ralph
>>>
>>>
>>> --
>>> Ralph Palmer
>>> Seattle
>>> USA
>>> (he, him, his)
>>> palmer.r.vio...@gmail.com
>>>
>>


Re: convert-ly

2021-05-30 Thread JxStarks
Here's a screenshot:
[image: image.png]


On Sun, May 30, 2021 at 5:50 PM JxStarks  wrote:

>
> Hi Ralph,
>
> I read that documentation and tried it. I'm running Windows 10 Pro,
> 10.0.19041 and I still get the same response: " 'convert-ly is not
> recognized...". Am I missing something obvious?
>
> Jerry
>
>
> On Sun, May 30, 2021 at 4:43 PM Ralph Palmer 
> wrote:
>
>>
>>
>> On Sun, May 30, 2021 at 1:24 PM JxStarks  wrote:
>>
>>> What's the trick for using convert-ly in a Windows Command Prompt
>>> window? I copied the convert-ly file into the directory where I want to
>>> convert everything in it, and entered convert-ly *.ly. This produced the
>>> error message " 'convert-ly' is not recognized as an internal or external
>>> command, operable program or batch file".
>>>
>>> Then I entered convert-ly.py *.ly and it produced the same error message.
>>>
>>> What's the trick?
>>>
>>
>> Hi, Jerry -
>>
>> Please take a look at the entry in the documentation :
>> https://lilypond.org/doc/v2.19/Documentation/usage/invoking-convert_002dly
>>
>> It tells how to run convert-ly on a single file, all files in a
>> directory, or all files on the computer, for Linux, Apple, and Windows.
>>
>> All the best,
>>
>> Ralph
>>
>>
>> --
>> Ralph Palmer
>> Seattle
>> USA
>> (he, him, his)
>> palmer.r.vio...@gmail.com
>>
>


Re: convert-ly

2021-05-30 Thread JxStarks
Hi Ralph,

I read that documentation and tried it. I'm running Windows 10 Pro,
10.0.19041 and I still get the same response: " 'convert-ly is not
recognized...". Am I missing something obvious?

Jerry


On Sun, May 30, 2021 at 4:43 PM Ralph Palmer 
wrote:

>
>
> On Sun, May 30, 2021 at 1:24 PM JxStarks  wrote:
>
>> What's the trick for using convert-ly in a Windows Command Prompt window?
>> I copied the convert-ly file into the directory where I want to convert
>> everything in it, and entered convert-ly *.ly. This produced the error
>> message " 'convert-ly' is not recognized as an internal or external
>> command, operable program or batch file".
>>
>> Then I entered convert-ly.py *.ly and it produced the same error message.
>>
>> What's the trick?
>>
>
> Hi, Jerry -
>
> Please take a look at the entry in the documentation :
> https://lilypond.org/doc/v2.19/Documentation/usage/invoking-convert_002dly
>
> It tells how to run convert-ly on a single file, all files in a directory,
> or all files on the computer, for Linux, Apple, and Windows.
>
> All the best,
>
> Ralph
>
>
> --
> Ralph Palmer
> Seattle
> USA
> (he, him, his)
> palmer.r.vio...@gmail.com
>


convert-ly

2021-05-30 Thread JxStarks
What's the trick for using convert-ly in a Windows Command Prompt window? I
copied the convert-ly file into the directory where I want to convert
everything in it, and entered convert-ly *.ly. This produced the error
message " 'convert-ly' is not recognized as an internal or external
command, operable program or batch file".

Then I entered convert-ly.py *.ly and it produced the same error message.

What's the trick?

Thanks,
Jerry


Re: Change color of Lyrics?

2021-01-29 Thread JxStarks
Thank you! I thought I had tried that, but my syntax was incorrect.

Jerry


On Fri, Jan 29, 2021 at 11:33 AM Lukas-Fabian Moser  wrote:

> Hi Jerry,
>
> > Is there a way to change the color of Lyrics? The documentation tells
> how to change the color of almost everything except Lyrics. I have a
> 5-verse song that I want to change the color on verse 3 (to help singers
> keep their place). How is this done?
>
> Probably easiest way is to issue
>
> \override LyricText.color = #red
>
> This may be done inside the lyrics themselves, or in a \with block:
>
> \new Lyrics \with { \override LyricText.color = #red } ..
>
> or
>
> \addlyrics \with { \override LyricText.color = #red } ...
>
> in a recent LilyPond version, you may even write = red instead of = #red.
>
> Note that lyrics are made up not only of LyricText grobs, but also of
> LyricHyphen's, LyricExtender's etc., whose color has to be overriden
> separately as far as I know.
>
> Lukas
>
>
>


Re: Lyrics for ossia staff

2021-01-03 Thread JxStarks
Remy,

Thanks for the suggestion, but I have the same problem with this that I
have with the Documentation: it works fine as a snippet, but when I put it
in the entire piece, the ossia staff is below the bass staff, and the ossia
lyrics are beneath the soprano lyrics under the top staff. I need to have
the "ossia" staff above the top (soprano) staff, and the ossia lyrics
associated with the ossia staff.

Jerry

On Sun, Jan 3, 2021 at 2:58 PM JxStarks  wrote:

> Got it, thanks! I'll try it out now.
>
> On Sun, Jan 3, 2021 at 1:31 PM Remy CLAVERIE 
> wrote:
>
>> Hi Jerry,
>>
>>
>>
>> Here is a MWE with ossia/lyrics:
>>
>>
>>
>> \version "2.18.2"
>>
>> OssiaLyrics = \lyricmode {
>>   Ma -- gni -- fi -- cat
>> }
>>
>> \new Staff
>> <<
>>   \new Voice \relative c {
>> c''4 b d c
>> <<
>>   { c4 b d c }
>> \new Staff
>> <<
>>   \new Voice = "V" \relative c'' { e4 d f e }
>> >>
>> >>
>> c4 b c2
>>   }
>>   \new Lyrics \lyricsto "V" \OssiaLyrics
>> >>
>>
>>
>>
>> HTH,
>>
>>
>>
>> Rémy
>>
>> > Message du 03/01/21 18:22
>> > De : "JxStarks" 
>> > A : "lilypond-user" 
>> > Copie à :
>> > Objet : Lyrics for ossia staff
>> >
>> >
>> Hi all,
>>
>> >
>> I expect this has been solved somewhere, but I can't find it. The
>> documentation is good at explaining how to do something in isolation, but
>> not so good at explaining how to do something in the middle of a different
>> structure, such as a choir staff.
>>
>> >
>> Anyway, I have a choir staff to which I want to add an extra staff for
>> the Soprano I voices. I want the staff to appear at measure 27 and continue
>> until measure 41 and then stop. I want the extra staff to contain both
>> music and lyrics.
>> >
>>
>> >
>> I was able to get the staff and music to work fairly well using a
>> structure suggested in a previous discussion on ossia staves. How can I get
>> lyrics to go with it? The structure follows. Sorry it's so long: I'm not
>> sure where all the commands need to be placed. If there's a more elegant
>> solution, I'm all in favor of it, even if it means restructuring the whole
>> piece:
>> >
>>
>> >
>>
>> \version "2.18.2"
>>
>>
>>
>> \header { }
>>
>>
>>
>> global = {
>>
>>   \key d \major
>>
>>   \time 4/4
>>
>>   \tempo 4=69
>>
>>   \set Score.markFormatter = #format-mark-box-alphabet }
>>
>>
>>
>> sopI = \relative c'' {
>>
>>   \global
>>
>>   \dynamicUp
>>
>> *  Notes and rests.*
>>
>> }
>>
>>
>>
>> ossia = \relative c’’ { \stopStaff s1*25 \startStaff
>>
>>*Notes and rests for auxiliary staff *
>>
>>\stopStaff
>>
>> }
>>
>>
>>
>> verseSopranoVoice = \lyricmode {  *Lyrics here*. }
>>
>>
>>
>> olyrics = \lyricmode { *Auxiliary lyrics here.* }
>>
>>
>>
>> altoVoice = *same setup as sopI*
>>
>>   verseAltoVoice = *same setup as sopI*
>>
>> tenorVoice = *same setup as sopI*
>>
>>   verseTenorVoice = *same setup as sopI*
>>
>> bassVoice = *same setup as sopI*
>>
>>   verseBassVoice = *same setup as sopI*
>>
>>
>>
>> sopranoVoicePart = <<
>>
>>   \context Staff  = “top” \with {
>>
>> instrumentName = "Sopranos"
>>
>> shortInstrumentName = \markup \center-column { "S1" "S2" }
>>
>> midiInstrument = "choir aahs"
>>
>> }  { \new Voice = “1” \sopI }
>>
>>   <<
>>
>> \lyrics {
>>
>>\new Lyrics \lyricsto “1” \verseSopranoVoice }
>>
>>  \new Staff \with {
>>
>>alignAbove Context = #”top”
>>
>> \remove “Time_signature_engraver”
>>
>> \override Clef #’transparent = ##t
>>
>>} { \ossia }
>>
>>   >>
>>
>> }
>>
>> >>
>>
>>
>>
>> altoVoicePart = \new Staff \with {
>>
>>   instrumentName = “Altos”
>>
>>   shortInstrumentName \ \markup \center-column { “A1” “A2” }
>>
>>   midiInstrument = “choir aahs”
>>
>> } { \altoVoice }
>>
>>  \addlyrics { \verseAltoVoice }
>>
>>
>>
>> tenorVoicePart = *same setup as altoVoicePart*
>>
>> bassVoicePart = *same setup as altoVoicePart*
>>
>>
>>
>> \score {
>>
>>   <<
>>
>> \sopranoVoicePart
>>
>> \altoVoicePart
>>
>> \tenorVoicePart
>>
>> \bassVoicePart
>>
>>   >>
>>
>>   \layout { }
>>
>>   \midi { }
>>
>> }
>>
>>
>> >
>>
>> Thanks,
>>
>> Jerry Starks
>> >
>>
>>
>>
>>


Re: Lyrics for ossia staff

2021-01-03 Thread JxStarks
Got it, thanks! I'll try it out now.

On Sun, Jan 3, 2021 at 1:31 PM Remy CLAVERIE 
wrote:

> Hi Jerry,
>
>
>
> Here is a MWE with ossia/lyrics:
>
>
>
> \version "2.18.2"
>
> OssiaLyrics = \lyricmode {
>   Ma -- gni -- fi -- cat
> }
>
> \new Staff
> <<
>   \new Voice \relative c {
> c''4 b d c
> <<
>   { c4 b d c }
> \new Staff
> <<
>   \new Voice = "V" \relative c'' { e4 d f e }
> >>
> >>
> c4 b c2
>   }
>   \new Lyrics \lyricsto "V" \OssiaLyrics
> >>
>
>
>
> HTH,
>
>
>
> Rémy
>
> > Message du 03/01/21 18:22
> > De : "JxStarks" 
> > A : "lilypond-user" 
> > Copie à :
> > Objet : Lyrics for ossia staff
> >
> >
> Hi all,
>
> >
> I expect this has been solved somewhere, but I can't find it. The
> documentation is good at explaining how to do something in isolation, but
> not so good at explaining how to do something in the middle of a different
> structure, such as a choir staff.
>
> >
> Anyway, I have a choir staff to which I want to add an extra staff for the
> Soprano I voices. I want the staff to appear at measure 27 and continue
> until measure 41 and then stop. I want the extra staff to contain both
> music and lyrics.
> >
>
> >
> I was able to get the staff and music to work fairly well using a
> structure suggested in a previous discussion on ossia staves. How can I get
> lyrics to go with it? The structure follows. Sorry it's so long: I'm not
> sure where all the commands need to be placed. If there's a more elegant
> solution, I'm all in favor of it, even if it means restructuring the whole
> piece:
> >
>
> >
>
> \version "2.18.2"
>
>
>
> \header { }
>
>
>
> global = {
>
>   \key d \major
>
>   \time 4/4
>
>   \tempo 4=69
>
>   \set Score.markFormatter = #format-mark-box-alphabet }
>
>
>
> sopI = \relative c'' {
>
>   \global
>
>   \dynamicUp
>
> *  Notes and rests.*
>
> }
>
>
>
> ossia = \relative c’’ { \stopStaff s1*25 \startStaff
>
>*Notes and rests for auxiliary staff *
>
>\stopStaff
>
> }
>
>
>
> verseSopranoVoice = \lyricmode {  *Lyrics here*. }
>
>
>
> olyrics = \lyricmode { *Auxiliary lyrics here.* }
>
>
>
> altoVoice = *same setup as sopI*
>
>   verseAltoVoice = *same setup as sopI*
>
> tenorVoice = *same setup as sopI*
>
>   verseTenorVoice = *same setup as sopI*
>
> bassVoice = *same setup as sopI*
>
>   verseBassVoice = *same setup as sopI*
>
>
>
> sopranoVoicePart = <<
>
>   \context Staff  = “top” \with {
>
> instrumentName = "Sopranos"
>
> shortInstrumentName = \markup \center-column { "S1" "S2" }
>
> midiInstrument = "choir aahs"
>
> }  { \new Voice = “1” \sopI }
>
>   <<
>
> \lyrics {
>
>\new Lyrics \lyricsto “1” \verseSopranoVoice }
>
>  \new Staff \with {
>
>alignAbove Context = #”top”
>
> \remove “Time_signature_engraver”
>
> \override Clef #’transparent = ##t
>
>} { \ossia }
>
>   >>
>
> }
>
> >>
>
>
>
> altoVoicePart = \new Staff \with {
>
>   instrumentName = “Altos”
>
>   shortInstrumentName \ \markup \center-column { “A1” “A2” }
>
>   midiInstrument = “choir aahs”
>
> } { \altoVoice }
>
>  \addlyrics { \verseAltoVoice }
>
>
>
> tenorVoicePart = *same setup as altoVoicePart*
>
> bassVoicePart = *same setup as altoVoicePart*
>
>
>
> \score {
>
>   <<
>
> \sopranoVoicePart
>
> \altoVoicePart
>
> \tenorVoicePart
>
> \bassVoicePart
>
>   >>
>
>   \layout { }
>
>   \midi { }
>
> }
>
>
> >
>
> Thanks,
>
> Jerry Starks
> >
>
>
>
>


Lyrics for ossia staff

2021-01-03 Thread JxStarks
Hi all,

I expect this has been solved somewhere, but I can't find it. The
documentation is good at explaining how to do something in isolation, but
not so good at explaining how to do something in the middle of a different
structure, such as a choir staff.

Anyway, I have a choir staff to which I want to add an extra staff for the
Soprano I voices. I want the staff to appear at measure 27 and continue
until measure 41 and then stop. I want the extra staff to contain both
music and lyrics.

I was able to get the staff and music to work fairly well using a structure
suggested in a previous discussion on ossia staves. How can I get lyrics to
go with it? The structure follows. Sorry it's so long: I'm not sure where
all the commands need to be placed. If there's a more elegant solution, I'm
all in favor of it, even if it means restructuring the whole piece:

\version "2.18.2"



\header { }



global = {

  \key d \major

  \time 4/4

  \tempo 4=69

  \set Score.markFormatter = #format-mark-box-alphabet }



sopI = \relative c'' {

  \global

  \dynamicUp

*  Notes and rests.*

}



ossia = \relative c’’ { \stopStaff s1*25 \startStaff

   *Notes and rests for auxiliary staff *

   \stopStaff

}



verseSopranoVoice = \lyricmode {  *Lyrics here*. }



olyrics = \lyricmode { *Auxiliary lyrics here.* }



altoVoice = *same setup as sopI*

  verseAltoVoice = *same setup as sopI*

tenorVoice = *same setup as sopI*

  verseTenorVoice = *same setup as sopI*

bassVoice = *same setup as sopI*

  verseBassVoice = *same setup as sopI*



sopranoVoicePart = <<

  \context Staff  = “top” \with {

instrumentName = "Sopranos"

shortInstrumentName = \markup \center-column { "S1" "S2" }

midiInstrument = "choir aahs"

}  { \new Voice = “1” \sopI }

  <<

\lyrics {

   \new Lyrics \lyricsto “1” \verseSopranoVoice }

 \new Staff \with {

   alignAbove Context = #”top”

\remove “Time_signature_engraver”

\override Clef #’transparent = ##t

   } { \ossia }

  >>

}

>>



altoVoicePart = \new Staff \with {

  instrumentName = “Altos”

  shortInstrumentName \ \markup \center-column { “A1” “A2” }

  midiInstrument = “choir aahs”

} { \altoVoice }

 \addlyrics { \verseAltoVoice }



tenorVoicePart = *same setup as altoVoicePart*

bassVoicePart = *same setup as altoVoicePart*



\score {

  <<

\sopranoVoicePart

\altoVoicePart

\tenorVoicePart

\bassVoicePart

  >>

  \layout { }

  \midi { }

}


Thanks,

Jerry Starks


Re: compiling sonata with \include

2020-10-16 Thread JxStarks
I bypassed this problem by commenting out the Header information in each
file, then including the header information in the \include file like this:

\markup  { \fill-line {
  \line {  }
  \center-column { \abs-fontsize #18 { \bold "We Three Kings of Orient
Are"} }
  \line {  }
} }
\markup { \fill-line {
  \line { John H. Hopkins }
  \center-column {  }
  \line { John H. Hopkins }
} }
\include
"C:/Users/Jerry/Documents/Fam/Family-Carol-Book/We-Three-Kings-of-Orient-Are.ly"

That produced a satisfactory result for my purposes. Hope this helps.

Jerry

On Thu, Oct 15, 2020 at 12:23 PM Molly Preston 
wrote:

> I tried the print-all-headers = ##t and it didn't work.
> I also tried \bookpart around the \include and it gave me fatal errors.
>
> I have looked at the documents you reference, but I will have to look at
> the TitleMarkup I think.
>
> Thank you for directing me.
>
> On Thu, Oct 15, 2020 at 12:17 PM Xavier Scheuer 
> wrote:
>
>> On Thu, 15 Oct 2020 at 18:00, Molly Preston 
>> wrote:
>> >
>> > Hello. I am confused by the hierarchy of headings. I have read about it
>> in the manuals and still find it confusing.
>> >
>> > I am trying to use \include to compile my sonata. The score block and
>> headings are in each file.
>> >
>> > I basically just have this:
>> >
>> > \include "Circle_mvt1.ly"
>> > \pageBreak
>> > \include "Circle_mvt2.ly"
>> > \pageBreak
>> > \include "Circle_mvt3.ly"
>> >
>> > The third movement's heading is what's being shown on the first page.
>> That is why I ask about the hierarchy of headings. I tried putting the
>> headings in this file instead of in each individual file.
>>
>> Hello,
>>
>> Difficult to answer if you do not show us what is present in your files...
>> I guess it is each time a \score block and its corresponding \header
>> block.
>>
>> Anyway, I guess what you are looking for is
>> \paper {
>>   print-all-headers = ##t
>> }
>>
>> But instead of putting these manual \pageBreak it would be more
>> interesting to use \bookpart.
>> All this is documented in NR 3.2 Titles and headers and NR 3.1.5 File
>> structure.
>>
>> Personally for works with several movements I have customized the headers
>> (scoreTitleMarkup, see NR 3.2.2) and use a custom "movement" field.
>>
>> Cheers,
>> Xavier
>>
>> --
>> Xavier Scheuer 
>>
>>


Re: Combining roughly 70 separate files into a single book

2020-04-28 Thread JxStarks .
When I used this structure I did not use \book or \bookpart. I just used
the \include and \markup. I'll post an example when I get home from work.

-Jerry

On Tue, Apr 28, 2020, 12:51 PM Brent Annable  wrote:

> Hi Richard,
>
> Does that do page numbers as well?  I'd really like to eliminate any extra
> steps if possible; my goal is to have a master file that I can adjust as
> necessary, and then just press a button to spit the whole thing out every
> time I need a new version.
>
> Based on Jerry's suggestion I've done a little experimenting. Using a
> structure like this:
>
> \book {
> \bookpart {\include "O-Welt-ich-muss-dich.ly"}
> \bookpart {\include "O-Welt-ich-muss-dich.ly"}
> }
>
> does produce scores in sequence with headings, etc. in place, but the
> music processing is full of errors and the output is nonsensical (see
> attachment). Can someone explain to me why this approach doesn't work? I
> thought that anything in a \bookpart block should be independent of
> everything around it, is that not the case? I even tried it with multiple
> \book blocks, but that produced nothing at all.
>
> Brent.
>
> On Wed, 29 Apr 2020 at 02:18, Richard Shann 
> wrote:
>
>> On Tue, 2020-04-28 at 23:37 +1000, Brent Annable wrote:
>> > Hi all,
>> >
>> > I'm looking for some general advice on how to combine about 70 files
>> > into one, to turn multiple files into a single PDF.
>>
>> I guess you are aware that ghostscript can concatenate your pdfs?
>>
>> gs -dBATCH -dNOPAUSE -q -sDEVICE=pdfwrite -sOutputFile=merged.pdf *.pdf
>>
>> Richard Shann
>>
>> >
>> > Over the past two years or so I've been typesetting a collection of
>> > organ pieces for a friend. After doing the first few I created a
>> > template that I subsequently used to set the rest, adding to it as I
>> > went along whenever new problems presented themselves. Now the
>> > collection is finished and I need to put them all together, and I'm
>> > just wondering about the easiest way to go about it.
>> >
>> > Most of the Lilypond files contain multiple \score blocks (usually 2
>> > or 3) and the variables in each file all have the same names. I've
>> > attached a typical file to give an idea of what I'm dealing with
>> > (plus the file with my macros, for convenience).
>> >
>> > So I have about 70 files like this. How should I go about putting
>> > everything together? Can I do an 'include' for every file somehow? Or
>> > do I need to rename all the variables in each separate file to do
>> > that? I've never done this before, so would really appreciate being
>> > steered in the right direction to avoid having to reinvent the wheel.
>> >
>> > Many thanks,
>> >
>> > Brent.
>>
>


How can I link lyrics with a temporary counter-melody?

2020-02-24 Thread JxStarks .
This is probably documented somewhere, but I am miserably inept at
searching archives.
I'm writing up a Lead Sheet and the Bridge section has a counter-melody
with its own lyrics. I hacked it together using the _"" function, but I
hope there's a better way to do it. Please enlighten me or direct me to the
correct procedure. Attached is a sample of the coding and the results I've
been able to achieve. (The 'Counter-Melody-Coding.png is in case someone
can't open the .docx.)

Thanks.
Jerry


Counter-Melody.docx
Description: MS-Word 2007 document


Book Structure and Frescobaldi

2019-12-23 Thread JxStarks .
Hi,
I'm using LilyPond 2.18.2 and Frescobaldi 2.20.0.
When I create music with Frescobaldi, it generates this structure:

\version “2.18.2”

\header { … }

global = { \key f \major

   \time 4/4 … }



violin = \relative c’’ { \global … }

clarinet = \relative c’ { \global … }

cello = \relative c’ { \global … }



violinpart = \new Staff \with {

instumentName = “”

shortInstrumentName = “”

  } \violin



clarinetpart = [same structure]



cellopart = [same structure]



\score {

 <<

   \violinpart

   \clarinetpart

   \cellopart

>>

 \layout { }

 \midi {

\tempo 4=112|

 }

}

The (short) instructions in the LilyPond Notation Reference says to set up
a Book, use this structure:
\book {
  \score { ... }
  \markup { ... }
}

How can I transfer my Frescobaldi coding into a Book? Do I need to re-enter
everything from scratch? The Notation Reference assures me that a "\score"
can contain a musical expression of any complexity... but I can't get even
the printed example to work. I get error: syntax error, unexpected
NOTENAME_PITCH. What am I missing?

Jerry