Ooops! Wrong thread. Sorry.
On Wed, 2021-10-27 at 22:28 +0100, J Martin Rushton wrote:
> Kevin,
> Just a tiny typo: in the last verse of "Go where the glory waits
> thee"
> you have "Draw_w_ one tear from thee;"
>
> Regards,
> Martin
>
>
Sorry, this was posted to the wrong thread yesterday:
Kevin,
Just a tiny typo: in the last verse of "Go where the glory waits thee"
you have "Draw_w_ one tear from thee;"
Regards,
Martin
On Wed, Oct 27, 2021 at 12:32 PM Kevin Cole wrote:
> I've mentioned before that I (a) don't read music, and (b) am pretty
> much a beginner with LilyPond.
>
...
> I'm really only concerned here with how to better grok LilyPond.
>
>
- For full measure rests I saw you use 'r2.' In the song of the
On Wed 27 Oct 2021 at 14:59:43 (-0400), Kevin Cole wrote:
> I've mentioned before that I (a) don't read music, and (b) am pretty
> much a beginner with LilyPond.
>
> Before I make TOO many mistakes, and make a royal mess of things, I
> thought I'd offer up the three wee songs I've entered thus far
On Wed, Oct 27, 2021 at 5:14 PM Ralph Palmer wrote:
>
> It looks to me like an excellent job so far!
On Wed, Oct 27, 2021 at 5:15 PM Guy Stalnaker wrote:
>
> With LP, the output is the goal. There are multiple approaches to such goals
> depending on experience, etc. My LP now looks much differe
Kevin,
Just a tiny typo: in the last verse of "Go where the glory waits thee"
you have "Draw_w_ one tear from thee;"
Regards,
Martin
On Wed, Oct 27, 2021 at 12:33 PM Kevin Cole wrote:
> I've mentioned before that I (a) don't read music, and (b) am pretty
> much a beginner with LilyPond.
>
> Before I make TOO many mistakes, and make a royal mess of things, I
> thought I'd offer up the three wee songs I've entered thus far. The
With LP, the output is the goal. There are multiple approaches to such
goals depending on experience, etc. My LP now looks much different from the
LP I first wrote 10+ years ago. Yet that 10 year old code still works. And
were LP experts to attempt the same no doubt their code would be different.
On 26/10/2021 08:46, Lukas-Fabian Moser wrote:
While this is technically perfect, I'd strongly advise against doing it
this way: It's a recipe for disaster regarding the start of the 2nd
alternative. Half of your cellists (or whatever instrument uses tenor
and bass clef here) is going to play a
On Wed, Oct 27, 2021 at 3:52 PM Guy Stalnaker wrote:
> Kevin, I get 404 Not Found errors fir the .ly source links. But the
> engravings and audio pages all work well. Very nicely done!!
Oops. The source repo was set to "private". I've changed that. the
links to the sources *should* now work.
I
Le 27/10/2021 à 09:23, Lukas-Fabian Moser a écrit :
but I admit that your solution gives better spacing. (The
extra-spacing-width of both Staff.Clef and Staff.BarLine doesn't seem
to be able to increase the space between clef and barline.)
Even though this behavior may not be clearly
document
[Valentin]
The first one is in fact a feature of whole bar percent repeats.
Basically you just need to set countPercentRepeats to #t
Have a look at
https://lilypond.org/doc/v2.23/Documentation/notation/short-repeats.html
Thanks, I didn't know about that!
[Lukas]
I have a branch on my c
Kevin, I get 404 Not Found errors fir the .ly source links. But the
engravings and audio pages all work well. Very nicely done!!
Regards.
On Wed, Oct 27, 2021, 2:31 PM Kevin Cole wrote:
> I've mentioned before that I (a) don't read music, and (b) am pretty
> much a beginner with LilyPond.
>
> B
I've mentioned before that I (a) don't read music, and (b) am pretty
much a beginner with LilyPond.
Before I make TOO many mistakes, and make a royal mess of things, I
thought I'd offer up the three wee songs I've entered thus far. The
sources:
https://codeberg.org/ubuntourist/celtic_song_book/sr
On Tue, Oct 26, 2021 at 1:52 PM Jefferson Felix wrote:
> it's not generating doubleSlurs, but when I remove the pair of numbers
> after \partCombine, doubleSlurs works.
>
> Am I doing something wrong?
I also live in a music tradition with joined-notes hymnals. I use
\partcombine #'(2 . 9)
In you
Thomas fantastic work as always. I found a potential limitation. Can you
confirm if this is possible with the current code?
I'd like a bit more control on the stem attachment of the splited stems
ideally on each note.
I've seen some cases where the stem is attached at the right side of the
altered
Lukas-Fabian Moser writes:
>> \version "2.22.1"
>>
>> {
>> \clef tenor
>> \repeat volta 2 {
>> c'1
>> \clef bass
>> c'1
>> }
>> \alternative {
>> {
>> c'1
>> \set Staff.clefGlyph = "clefs.C"
>> }
>> { c'1 }
>> }
>> c'1
>> }
>
> While this is technic
Lukas-Fabian Moser writes:
>> { \startMeasureCount s1*2\< s\> s\< s\> <>\! }
>
> Somehow I was never happy with this use of spacer rests for dynamic
> parts (even though it is recommended in the documentation).
>
> My issue is that the "natural" way of reading/writing/speaking would be:
>
> "St
Hello Greg,
The first one is in fact a feature of whole bar percent repeats. Basically you
just need to set countPercentRepeats to #t
Have a look at
https://lilypond.org/doc/v2.23/Documentation/notation/short-repeats.html[1]
Cheers,
Valentin
[1] https://lilypond.org/doc/v2.23/Documenta
Hi Valentin,
Am 27.10.21 um 09:09 schrieb Valentin Petzel:
Hello Lukas, hello Jean, hello David,
Maybe something like this could do the trick.
Yes, maybe (even though I still read f' after the bar line for a second
and had to look in the source to find out what the intended pitch was). :-)
{ \startMeasureCount s1*2\< s\> s\< s\> <>\! }
Somehow I was never happy with this use of spacer rests for dynamic
parts (even though it is recommended in the documentation).
My issue is that the "natural" way of reading/writing/speaking would be:
"Start a crescendo, then wait two bars;
Hello Lukas, hello Jean, hello David,
Maybe something like this could do the trick.
Cheers,
Valentin
Am Dienstag, 26. Oktober 2021, 09:46:57 CEST schrieb Lukas-Fabian Moser:
> > \version "2.22.1"
> >
> > {
> > \clef tenor
> > \repeat volta 2 {
> > c'1
> > \clef bass
> > c'1
> >
22 matches
Mail list logo
