Re: simple problem: my first text spanner starts too early?

[Kenneth Wolcott]

Thank you Xavier!

You gave me the hint I needed.

I need to specify that the text spanner should start below (not
default, which is above).

Problem solved.

Ken

On Mon, Apr 22, 2024 at 1:18 PM Xavier Scheuer  wrote:
>
> On Mon, 22 Apr 2024 at 21:48, Kenneth Wolcott  
> wrote:
> >
> > Hi;
> >
> >   I've made a simple mistake but I can't figure out what I did wrong.
> >
> > At bar #36 the first text spanner starts. I think that's correct.  But
> > the piano articulation should be a bar earlier? But that also seems
> > correct.  How can all of these three "facts" be true without a
> > contradiction? Perhaps it is a spacing issue that needs to be tweaked?
> >
> > The original pdf, my engraving and the Lilypond source are attached.
>
> Hello,
>
> Your TextSpanner starts at the beginning of bar #37 and is displayed above 
> the staff, that's what you have in your code as well.
> Is there a particular reason why you don't use a DynamicTextSpanner (command 
> \cresc) for these cresc. ?
> And why you put your dynamics in a separate variable but not these textual 
> crescendi ?
> And using a Dynamics context seems an overkill for me in this case (I use 
> them only for PianoStaff-likes).
>
> Kind regards,
> Xavier
>

Re: LilyPond 2.25.14

[Kenneth Wolcott]

Hi Jonas;

  I hope that the following information is useful:

Lilypond performance stats for the engraving of one very small and one
medium sized pieces

native = Apple Silicon build
foreign = x86_64
other = MacPorts LP 2.24.3

~/Downloads/native_lilypond-2.25.14/bin/lilypond
./Danny_Boy_updated.ly  0.53s user 0.06s system 87% cpu 0.683 total
~/Downloads/foreign_lilypond-2.25.14/bin/lilypond
./Danny_Boy_updated.ly  0.93s user 0.09s system 101% cpu 1.010 total
/opt/local/bin/lilypond ./Danny_Boy.ly  0.48s user 0.06s system 104%
cpu 0.515 total

~/Downloads/native_lilypond-2.25.14/bin/lilypond
./Waltz_Nr2_updated.ly  1.07s user 0.10s system 102% cpu 1.145 total
~/Downloads/foreign_lilypond-2.25.14/bin/lilypond
./Waltz_Nr2_updated.ly  1.76s user 0.15s system 100% cpu 1.907 total
/opt/local/bin/lilypond ./Waltz_Nr2.ly  1.06s user 0.12s system 103%
cpu 1.140 total

for i in ./Danny_Boy.ly ./Danny_Boy_updated.ly ./Waltz_Nr2.ly
./Waltz_Nr2_updated.ly
for> do
for> wc $i
for> done
 232 8144641 ./Danny_Boy.ly
 232 8144642 ./Danny_Boy_updated.ly
 9393892   19981 ./Waltz_Nr2.ly
 9393892   19982 ./Waltz_Nr2_updated.ly

Ken Wolcott

On Sat, Mar 23, 2024 at 12:09 PM Jonas Hahnfeld  wrote:
>
> On Sat, 2024-03-23 at 11:39 -0700, Kenneth Wolcott wrote:
> > Hi Jonas;
> >
> >   I've tried engraving a couple of randomly chosen previous engravings
> > (using LP 2.24.x) using the new LP 2.25.14 version on my Mac (Apple
> > Silicon).
> >
> >   Since none of my engravings are large, most of them are one to two
> > pages in length, I thought there would be no noticable decrease in
> > engraving time, but I was wrong!  It IS noticably faster for even
> > small files :-)
> >
> >   One thing I noticed is what one of my engravings had significant
> > change in apperance in the second and third page, as if I had inserted
> > a forced page break in two or three places.  There were no conversion
> > errors or warnings in any of my engravings.
> >
> >   I don't know what was the cause of the speedup, but it is
> > appreciated! I have been using the MacPorts version of Lilypond 2.24.3
> > compared to this recent test release.
>
> Thanks for testing! The performance advantage probably comes from Guile
> 3.0 in our binaries of 2.25.14 versus Guile 2.2 with the MacPorts
> version, having a faster startup time which matters especially for
> smaller files. If you have some time, I would be really interested in
> seeing a comparison with LilyPond 2.25.14 from
> https://gitlab.com/lilypond/lilypond/-/packages/23923980 when the
> x86_64 executable is run through Rosetta on Apple Silicon...
>
> Jonas

Re: LilyPond 2.25.14

[Kenneth Wolcott]

Hi Jonas;

  I've tried engraving a couple of randomly chosen previous engravings
(using LP 2.24.x) using the new LP 2.25.14 version on my Mac (Apple
Silicon).

  Since none of my engravings are large, most of them are one to two
pages in length, I thought there would be no noticable decrease in
engraving time, but I was wrong!  It IS noticably faster for even
small files :-)

  One thing I noticed is what one of my engravings had significant
change in apperance in the second and third page, as if I had inserted
a forced page break in two or three places.  There were no conversion
errors or warnings in any of my engravings.

  I don't know what was the cause of the speedup, but it is
appreciated! I have been using the MacPorts version of Lilypond 2.24.3
compared to this recent test release.

Thanks to all who have made this an awesome product!

Ken Wolcott

On Sat, Mar 23, 2024 at 10:20 AM Kenneth Wolcott
 wrote:
>
> WOW!!! Apple Silicon support!!!
>
> On Sat, Mar 23, 2024 at 8:03 AM Jonas Hahnfeld via LilyPond user
> discussion  wrote:
> >
> > On Sat, 2024-03-23 at 14:25 +0100, Jonas Hahnfeld wrote:
> > > We are happy to announce the release of LilyPond 2.25.14. This is
> > > termed a development release, but these are usually reliable for
> > > testing new features and recent bug fixes.
> >
> > Following this release, I made two special builds with the changes
> > proposed in https://gitlab.com/lilypond/lilypond/-/merge_requests/2283
> > that would be great to get more widespread testing:
> >
> > Native Apple Silicon build: https://cloud.hahnjo.de/s/x9D62eASSn6Ng7D
> > This is a native arm64 version for macOS 12+; if you have a Mac, please
> > test and (hopefully) confirm the performance advantage over running the
> > x86_64 build via Rosetta 2 
> >
> > Windows build with Guile JIT: https://cloud.hahnjo.de/s/Ek5x9rybpiPNtoj
> > This turns on just-in-time compilation that was added in Guile 3.0, but
> > we had to keep disabled on Windows until now. Please test, especially
> > on larger scores where this should provide a performance advantage.
> >
> > Cheers
> > Jonas
>

Re: LilyPond 2.25.14

[Kenneth Wolcott]

WOW!!! Apple Silicon support!!!

On Sat, Mar 23, 2024 at 8:03 AM Jonas Hahnfeld via LilyPond user
discussion  wrote:
>
> On Sat, 2024-03-23 at 14:25 +0100, Jonas Hahnfeld wrote:
> > We are happy to announce the release of LilyPond 2.25.14. This is
> > termed a development release, but these are usually reliable for
> > testing new features and recent bug fixes.
>
> Following this release, I made two special builds with the changes
> proposed in https://gitlab.com/lilypond/lilypond/-/merge_requests/2283
> that would be great to get more widespread testing:
>
> Native Apple Silicon build: https://cloud.hahnjo.de/s/x9D62eASSn6Ng7D
> This is a native arm64 version for macOS 12+; if you have a Mac, please
> test and (hopefully) confirm the performance advantage over running the
> x86_64 build via Rosetta 2 
>
> Windows build with Guile JIT: https://cloud.hahnjo.de/s/Ek5x9rybpiPNtoj
> This turns on just-in-time compilation that was added in Guile 3.0, but
> we had to keep disabled on Windows until now. Please test, especially
> on larger scores where this should provide a performance advantage.
>
> Cheers
> Jonas

Re: FYI: recent MacPorts ghostscript upgrade causes Lilypond 2.24.2 warning from Guile

[Kenneth Wolcott]

Thanks, Jean, I wasn't sure that this was a different thing with
ghostscript or not, just thought I'd mention it.  Yes, I am using the
Lilypond tarball now in place of the MacPorts Lilypond.  I am looking
forward to the new Lilypond release...

Thanks,
Ken

On Wed, Nov 15, 2023 at 11:41 AM Jean Abou Samra  wrote:
>
> Thanks, but we already know about this. See 
> https://gitlab.com/lilypond/lilypond/-/issues/6675 and the various recent 
> threads about Homebrew on this list.
>
> We are unfortunately unlikely to convince package maintainers to downgrade 
> Ghostscript to 10.02.0 since the change that broke LilyPond was a security 
> fix.
>
> LilyPond 2.24.3 is going to be released quite soon with a workaround on our 
> side that should fix this issue. Meanwhile, it's best to use binaries from 
> lilypond.org.

FYI: recent MacPorts ghostscript upgrade causes Lilypond 2.24.2 warning from Guile

[Kenneth Wolcott]

FYI:

gs --version
10.02.1

GNU LilyPond 2.24.2 (running Guile 2.2)
Changing working directory to: `[redacted]/tmp/lilypond/target'
Processing `low_organ_notes.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Interpreting music...
MIDI output to `low_organ_notes.midi'...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Converting to `low_organ_notes.pdf'...
warning: `(gs -q -dNODISPLAY -dNOSAFER -dNOPAUSE -dBATCH
-dAutoRotatePages=/None -dPrinted=false
/var/folders/w6/y2gky19s1mbcg5cgwj4512q4gn/T//lilypond-tmp-4188220)'
failed (256)

/opt/local/share/lilypond/2.24.2/ly/init.ly:65:2: error: Guile
signaled an error for the expression beginning here
#
 (let ((book-handler (if (defined? 'default-toplevel-book-handler)
Throw to key `ly-file-failed' with args `()'.

Ken Wolcott

Re: what is the musical ornament called that looks like a mordent but has curl in front of it?

[Kenneth Wolcott]

Ah! a \downmordent :-) I was looking right at it on the Lilypond list
of ornaments...

On Thu, Oct 26, 2023 at 8:28 PM Kenneth Wolcott
 wrote:
>
> Hi;
>
> what is the musical ornament called that looks like a mordent but has
> curl in front of it?
>
> I'm engraving a 8notes.com Tuba+Piano arrangement of the Aria from the
> Goldberg Variations.
>
> Attached is a screenshot.
>
> Thanks,
> Ken Wolcott

what is the musical ornament called that looks like a mordent but has curl in front of it?

[Kenneth Wolcott]

Hi;

what is the musical ornament called that looks like a mordent but has
curl in front of it?

I'm engraving a 8notes.com Tuba+Piano arrangement of the Aria from the
Goldberg Variations.

Attached is a screenshot.

Thanks,
Ken Wolcott

Re: How to "guarantee" Lilypond pdf (letter) output with sufficient margins for 3-hole punch?

[Kenneth Wolcott]

Hi Knute;

  Thanks for the tips.

  I'm in the midst of engraving a one-page sheet of music now using
your suggestions, hopefully it will be correct for three-hole-punching
or easy for me to fiddle with the values of the settings.

Thanks,
Ken

On Mon, Oct 23, 2023 at 1:30 PM Knute Snortum  wrote:
>
>
> On Mon, Oct 23, 2023 at 11:09 AM Kenneth Wolcott  
> wrote:
>>
>> Hi;
>>
>>   How to "guarantee" Lilypond pdf (letter) output with sufficient
>> margins for 3-hole punch?
>
>
> It's no guarantee, but I put the following in my paper block:
>
>   two-sided = ##t
>   inner-margin = 12\mm
>   outer-margin = 8\mm
>
> --
> Knute Snortum
>
>

How to "guarantee" Lilypond pdf (letter) output with sufficient margins for 3-hole punch?

[Kenneth Wolcott]

Hi;

  How to "guarantee" Lilypond pdf (letter) output with sufficient
margins for 3-hole punch?

  I'm looking forward to having a method of "guaranteeing" Lilypond
pdf output for letter (not a4) of my engravings such that the
resulting printout can be three-hole punched (on both sides
potentially) without making adversely affecting the visibility of the
pdf.

  This "procedure" or "process" might be needed retroactively as well
as for a new engraving project.

  I know that this might be a proportionate value so I'd have to
adjust it if I specified (or changed) a global font size.

  I guess what I'm looking for is the equivalent of "indent" but for
every system.

  I'll look again to see if I understand "margin"-related settings...

Thanks for hints...

Ken Wolcott

Re: Is there a glyph? (or something) to indicate a clap in a vocal piece?

[Kenneth Wolcott]

Veddy veddy funny :-)

On Mon, Oct 16, 2023 at 1:28 PM David Kastrup  wrote:
>
> Kenneth Wolcott  writes:
>
> > Hi;
> >
> >   On a related note (pun not intended!) I have seen a Tuba solo score
> > where there is a notation to "slap" the instrument, shown as literally
> > a "slap" like a "rit." or ".cresc.". I was wondering how to engrave
> > that...other than the obvious...
>
> For tuba solo I think it would be important to indicate that one is
> supposed to slap the instrument rather than the player.
>
> --
> David Kastrup

Re: Is there a glyph? (or something) to indicate a clap in a vocal piece?

[Kenneth Wolcott]

Hi;

  On a related note (pun not intended!) I have seen a Tuba solo score
where there is a notation to "slap" the instrument, shown as literally
a "slap" like a "rit." or ".cresc.". I was wondering how to engrave
that...other than the obvious...

Thanks,
Ken Wolcott

On Mon, Oct 16, 2023 at 1:01 PM Kevin Cole  wrote:
>
> On Mon, Oct 16, 2023 at 1:47 PM Karlin High  wrote:
>
> > I have seen choral works use "X" note heads to indicate claps or
> > foot-stomps.
> >
> > The commands \xNotesOn and \xNotesOff seem worth trying.
> >
> > 
>
> Aaaand, we have a winner! ;-)
>
> (At least until I get to the MIDI, but I'm feeling confident that I
> know how to accomplish that part.)
>
> Just what the doctor ordered.
>
> Thanks!
>

what is an articulation that looks like a marcato but is shaped like a half-moon?

[Kenneth Wolcott]

what is an articulation that looks like a marcato but is shaped like a
half-moon?

This is from an arrangement of the Marcello Oboe Concerto (Adagio
movement) by way of Bach and/or Vivaldi, re-arranged for two trumpets,
french horn and tuba.

The articulation in question is from the first trumpet part.

I don't see anything like this in the list of articulations in the
Notation Reference.

LP 2.24.2

See attachment.

Thanks,
Ken Wolcott

Re: having trouble with a segno repeat

[Kenneth Wolcott]

AHA!  Thank you!

On Mon, Sep 11, 2023 at 7:31 PM Colin Campbell  wrote:
>
> At line 102 or so, you have an extra curly brace. When I take that out,
> all is good. I found it by folding section by section till I saw your
> coda was not folded when it should have been.
>
> HTH,
>
> Colin
>
> On 2023-09-11 19:10, Kenneth Wolcott wrote:
> > Hi;
> >
> >I'm trying to follow the segno repeat with coda instructions in the
> > Notation Reference, but apparently I am not successful :-(
> >
> > Summary: The original pdf has:
> >
> > 1. four bars followed by a segno sign at bar #5
> > 2. a "to Coda" at bar #21;
> > 3. a D.S.al Coda at bar #46
> > 4. a Coda sign (and separated) three bars.
> >
> > Lilypond 2.24.2 (from MacPorts).
> >
> > I was able to engrave all the notes ok, but could not get the segno
> > repeat correct.
> >
> > Processing `Mission_Impossible.ly'
> > Parsing...
> > [redacted]/source/Mission_Impossible.ly:103:3: error: syntax error,
> > unexpected NOTENAME_PITCH
> >
> >c4^^ r8 c4^^ r8 df4^^ ef^^  | % m47
> > Interpreting music...
> > [redacted]/source/Mission_Impossible.ly:103:31: warning: skipping
> > zero-duration score
> >c4^^ r8 c4^^ r8 df4^^ ef^^
> >| % m47
> > [redacted/source/Mission_Impossible.ly:103:31: warning: to suppress
> > this, consider adding a spacer rest
> >c4^^ r8 c4^^ r8 df4^^ ef^^
> >| % m47
> >
> > I have attached the original pdf from which I am engraving andmy
> > Lilypond source. I don't think that the attachments will be too
> > large... I don't want to attach my pdf because it might be too
> > large...
> >
> > du -k ../origin/Schifrin_MissionImpossible-TV_TubaDuet.pdf
> > ../target/Mission_Impossible.pdf .
> > /Mission_Impossible.ly
> > 36 ../origin/Schifrin_MissionImpossible-TV_TubaDuet.pdf
> > 84 ../target/Mission_Impossible.pdf
> > 12 ./Mission_Impossible.ly
> >
> >
> > Thanks,
> > Ken Wolcott

having trouble with a segno repeat

[Kenneth Wolcott]

Hi;

  I'm trying to follow the segno repeat with coda instructions in the
Notation Reference, but apparently I am not successful :-(

Summary: The original pdf has:

1. four bars followed by a segno sign at bar #5
2. a "to Coda" at bar #21;
3. a D.S.al Coda at bar #46
4. a Coda sign (and separated) three bars.

Lilypond 2.24.2 (from MacPorts).

I was able to engrave all the notes ok, but could not get the segno
repeat correct.

Processing `Mission_Impossible.ly'
Parsing...
[redacted]/source/Mission_Impossible.ly:103:3: error: syntax error,
unexpected NOTENAME_PITCH

  c4^^ r8 c4^^ r8 df4^^ ef^^  | % m47
Interpreting music...
[redacted]/source/Mission_Impossible.ly:103:31: warning: skipping
zero-duration score
  c4^^ r8 c4^^ r8 df4^^ ef^^
  | % m47
[redacted/source/Mission_Impossible.ly:103:31: warning: to suppress
this, consider adding a spacer rest
  c4^^ r8 c4^^ r8 df4^^ ef^^
  | % m47

I have attached the original pdf from which I am engraving andmy
Lilypond source. I don't think that the attachments will be too
large... I don't want to attach my pdf because it might be too
large...

du -k ../origin/Schifrin_MissionImpossible-TV_TubaDuet.pdf
../target/Mission_Impossible.pdf .
/Mission_Impossible.ly
36 ../origin/Schifrin_MissionImpossible-TV_TubaDuet.pdf
84 ../target/Mission_Impossible.pdf
12 ./Mission_Impossible.ly


Thanks,
Ken Wolcott


Schifrin_MissionImpossible-TV_TubaDuet.pdf
Description: Adobe PDF document


Mission_Impossible.ly
Description: Binary data

QUIBBLE: Interesting use (mis-matched) of left and right quotes of quoted strings in Lilypond output

[Kenneth Wolcott]

Hi;

QUIBBLE: Interesting use (mis-matched) of left and right quotes of
quoted strings in Lilypond output

Processing `Were_You_There.ly'...
...
MIDI output to `Were_You_There.midi'...
...
Converting to `Were_You_There.pdf'...

  Note that the left quote looks like a grave, or back-quote, while
the right quote looks like a regular quote.

  Is this deliberate?

  It's not that it really matters to me, just that I am pointing out
that I just noticed it and I thought it was interesting.

Thanks,
Ken Wolcott

Re: Trying and failing to engrave a segno repeat with coda: More alternatives than repeats.

[Kenneth Wolcott]

Hi Valentin;

  Wow, that's a lot to digest; thanks, I'll try to work through that.

Ken

On Fri, Jun 9, 2023 at 2:02 AM Valentin Petzel  wrote:
>
> Hello Ken,
>
> please try to give a MWE and to describe what you actually want to achieve. It
> is hard to get what you want from just a handful of screenshots of jump marks.
>
> I suppose this is supposed to be something like
>
> A [SEGNO] B [Fine→Coda] C [Dal segno al Fine e poi la coda] [Coda] D
>
> So essentially A → B → C → B → D
>
> What you are doing is something like
>
> {
>   c'1 c'
>   \repeat segno 2 {
> d' d'
>   }
>   \alternative {
> \volta 1 { }
> \volta 2 { e' e' }
> { f' f' }
>   }
> }
>
> instead you should be doing something like this
>
> {
>   c'1 c'
>   \repeat segno 2 {
> d' d'
>   }
>   \alternative {
> { e' e' }
> { f' f' }
>   }
> }
>
> Or as given in the documentation
>
> {
>   c'1 c'
>   \repeat segno 2 {
> d' d'
>   }
>   \alternative {
> { e' e' }
> { \section \sectionLabel "Coda" }
>   }
>   f' f'
> }
>
> Now, Lilypond will then produce marks that are more inspired by classical use
> of codas, while this is more a pop-style use of coda marks (where you will 
> find
> interesting instructions like this "D.S. al coda" (lit. from the sign to the
> Coda, so start playing repeat from the segno and stop once you reach the
> Coda).
>
> Now, if you want you can simply tell Lilypond to do this thing by simple
> styling directives:
>
> {
>   c'1 c'
>   \repeat segno 2 {
> d' d'
>   }
>   \alternative {
> { e' e' }
> { f' f' }
>   }
> }
>
> \layout {
>   \context {
> \Score
> dalSegnoTextFormatter =
> #(lambda (context return-count marks)
>(let* ((start-markup (car marks))
>   (end-markup (cadr marks))
>   (next-markup (caddr marks))
>   (result (if start-markup "D.S." "D.C.")))
>  (if next-markup
>  (markup result "al Coda")
>  (if end-markup
>  (markup result "al" end-markup)
>  result
> \override CodaMark.self-alignment-X = ##f
> \override CodaMark.font-size = #0
> codaMarkFormatter =
> #(lambda (count context)
>(let* ((coda-markup (format-coda-mark (ceiling (/ count 2)) context)))
>  (if (= (remainder count 2) 1)
>  (markup #:put-adjacent X LEFT #:center-align coda-markup
> #:fontsize -1 "To Coda ")
>  (markup #:put-adjacent X RIGHT #:center-align coda-markup
> #:fontsize -1 " Coda"
>   }
> }
>
> Cheers,
> Valentin

Re: Trying and failing to engrave a segno repeat with coda: More alternatives than repeats.

[Kenneth Wolcott]

HI Jean;

  Thank you so much.

  It works now.

On Fri, Jun 9, 2023 at 12:51 AM Jean Abou Samra  wrote:
>
> Le jeudi 08 juin 2023 à 22:56 -0700, Kenneth Wolcott a écrit :
> > Hi;
> >
> > Trying and failing to engrave a segno repeat with coda:
> >
> > warning: More alternatives than repeats.  Junking excess alternatives
> >
> > Attachments:
> >
> > I have screenshots for the following from the original pdf I am
> > transcribing from:
> > (i) sego;
> > (ii_ the "to coda";
> > (iii) combined "ds al coda" and "Coda" [combined]
> >
> > (iv) the resulting pdf;
> >
> > (v) I have the output from Lilypond;
> >
> > (vi) My Lilypond source;
> >
> >   Again, must be missing something trivial and obvious :-(
>
>
> You have things like this:
>
> rh = {
>   \global
>   \clef treble
>   \rh_i
>   \repeat segno 2 {
> \rh_ii
>   }
>   \alternative {
> \volta 1 {
>   \rh_iii
> }
> \volta 2 \volta #'() {
>   \section
>   \sectionLabel "Coda"
> }
> \rh_iv
>   } \fine
> }
>
> Each element of the \alternative block is an alternative. Therefore, you
> have three alternatives: \volta 1 { ... }, \volta 2 { ... }, and \rh_iv.
> For a \repeat segno **2**, that is illogical.
>
> Instead, you should put \rh_iv outside of the \alternative block.
>
> Best,
> Jean

Re: Lilypond v 2.24.1, segno repeat question where segno and coda sign are adjacent

[Kenneth Wolcott]

Oh, darn :-)

I forgot to attach my Lilypond source code.

Thanks,
Ken

On Mon, May 29, 2023 at 3:16 PM Kenneth Wolcott
 wrote:
>
> HI;
>
>   Lilypond v 2.24.1, segno repeat question where segno and coda sign
> are adjacent in the original.
>
>   How to engrave this (screenshot attached)?  The only segno sign is
> at this location and the only coda sign is also at this location. I'd
> like to engrave the music so that the midi output represents the segno
> in action.  What I don't understand in this case is where my \volta 1
> and \volta 2 are to be placed when the segno and coda signs are
> adjacent.
>
> Thanks,
> Ken Wolcott


Raindrops_Keep_Fallin_on_my_Head_before_introducing_segno_repeat.ly
Description: Binary data


Raindrops_Keep_Fallin_on_my_Head.ly
Description: Binary data

Re: Problem understanding 2.24.1 segno repeat for a fine+dc_al_fine repeat

[Kenneth Wolcott]

Thank you Jean!

On Sat, May 13, 2023 at 7:19 AM Jean Abou Samra  wrote:
>
> Le vendredi 12 mai 2023 à 20:42 -0700, Kenneth Wolcott a écrit :
>
> Hi;
>
>   I'm converting a 2.22.2 Lilypond engraving where I manually implemented a 
> fine+dc_al_fine repeat into a 2.24.1 repeat segno and I run into difficulties.
>
> Since the fine ends at beat 3 of 4 (well, 2/2 meter), I run into issues with 
> partials and bar checks.
>
>   I also run into problems with the voltas.
>
>   Please show me where I screwed up.
>
>   I am looking at the Notation Reference for LIlypond 2.24.1, but obviously I 
> am missing something.
>
>   I have attached a screenshot and my Lilypond source.
>
>   I get two copies of each of the two errors (one for each score section).
>
> You have misplaced braces. The syntax is
>
> \repeat segno 2 {
>   ...
>   \volta 1 \fine
>   \volta 2 { ... }
> }
>
> and not
>
> \repeat segno 2 {
>   ...
> }
> \volta 1 \fine
> \volta 2 { ... }

Re: Problem understanding 2.24.1 segno repeat for a fine+dc_al_fine repeat

[Kenneth Wolcott]

Forgot to include screenshots of the origin that I'm using as a sample
to engrave from...

On Fri, May 12, 2023 at 8:42 PM Kenneth Wolcott
 wrote:
>
> Hi;
>
>   I'm converting a 2.22.2 Lilypond engraving where I manually
> implemented a fine+dc_al_fine repeat into a 2.24.1 repeat segno and I
> run into difficulties.
>
> Since the fine ends at beat 3 of 4 (well, 2/2 meter), I run into
> issues with partials and bar checks.
>
>   I also run into problems with the voltas.
>
>   Please show me where I screwed up.
>
>   I am looking at the Notation Reference for LIlypond 2.24.1, but
> obviously I am missing something.
>
>   I have attached a screenshot and my Lilypond source.
>
>   I get two copies of each of the two errors (one for each score section).
>
> one error:
> All_Things_Bright_And_Beautiful.ly:45:12: warning: found music after \fine
>   \volta 2
>\fine
>
> second error:
> All_Things_Bright_And_Beautiful.ly:33:33: warning: barcheck failed at: 3/4
> c''4^5 e'^1 f'^2 a'^4
>
> Thanks,
> Ken Wolcott

Problem understanding 2.24.1 segno repeat for a fine+dc_al_fine repeat

[Kenneth Wolcott]

Hi;

  I'm converting a 2.22.2 Lilypond engraving where I manually
implemented a fine+dc_al_fine repeat into a 2.24.1 repeat segno and I
run into difficulties.

Since the fine ends at beat 3 of 4 (well, 2/2 meter), I run into
issues with partials and bar checks.

  I also run into problems with the voltas.

  Please show me where I screwed up.

  I am looking at the Notation Reference for LIlypond 2.24.1, but
obviously I am missing something.

  I have attached a screenshot and my Lilypond source.

  I get two copies of each of the two errors (one for each score section).

one error:
All_Things_Bright_And_Beautiful.ly:45:12: warning: found music after \fine
  \volta 2
   \fine

second error:
All_Things_Bright_And_Beautiful.ly:33:33: warning: barcheck failed at: 3/4
c''4^5 e'^1 f'^2 a'^4

Thanks,
Ken Wolcott


All_Things_Bright_And_Beautiful.ly
Description: Binary data

Re: flageolet is not listed in the index portion of the Notation Reference

[Kenneth Wolcott]

Nevermind :-(

I was searching in the Index for 'flageolet' instead of '\flageolet'.
I global search of 'flageolet' and following every result determined
this.

Sorry for the noise, me lazy :-(

Thanks,
Ken

On Tue, Apr 18, 2023 at 11:51 AM Kenneth Wolcott
 wrote:
>
> Hi;
>
> The term 'flageolet' is not listed in the index portion of the
> Notation Reference.
>
> Thanks,
> Ken Wolcott

flageolet is not listed in the index portion of the Notation Reference

[Kenneth Wolcott]

Hi;

The term 'flageolet' is not listed in the index portion of the
Notation Reference.

Thanks,
Ken Wolcott

Re: Anybody else playing with GPT4 and Lilypond?

[Kenneth Wolcott]

I'm currently using "ChatGPT Mar 14 Version."

Ken

On Wed, Mar 29, 2023 at 5:15 PM Saul Tobin  wrote:
>
> A practical follow up question: what is currently the largest repertoire of 
> publicly available Lilypond scores? Ideally, something like the complete Bach 
> chorales or Mozart piano sonatas.
>
> On Wed, Mar 29, 2023 at 3:43 PM Saul Tobin  wrote:
>>
>> I've seen some examples of other people succeeding in getting ChatGPT with 
>> GPT4 to compose simple music in other text based music formats. I've had 
>> limited success getting it to output Lilypond code. It is able to correctly 
>> structure the code with a score block, nested contexts, and appropriately 
>> named variables, and bar checks at the end of each measure. It seems to 
>> struggle to create rhythms that fit within the time signature beyond 
>> extremely simple cases. It also seems to struggle a lot to understand what 
>> octave pitches will be in when using relative mode.
>>
>> It also seems to have a lot of trouble keeping track of the relationship 
>> between notes entered in different simultaneous expressions. Just asking it 
>> to repeat back which notes appear in each voice on each beat, GPT4 
>> frequently gives stubbornly incorrect answers about the music it generated. 
>> This makes it very difficult to improve its output by giving feedback.
>>
>> I'm curious whether anybody else has tried playing with this. I have to 
>> imagine that GPT4 has the potential to produce higher quality Lilypond 
>> output, given some of the other impressive things it can do. Perhaps it 
>> needs to be provided with a large volume of musical repertoire in Lilypond 
>> format.

Re: Anybody else playing with GPT4 and Lilypond?

[Kenneth Wolcott]

Correction: I don't think I'm using ChatGPT4, I'm using
https://chat.openai.com/chat.
Ken

On Wed, Mar 29, 2023 at 4:06 PM Kenneth Wolcott
 wrote:
>
> HI Saul;
>
>   I asked ChatGPT to write some ABC notation.  The result was...'okay'.
>
>   I then asked for a very simple arrangement of some children's tune
> and it got very confused about relative pitches.  Since the rhythm for
> the piece of music I requested was so simple it didn't have a problem
> generating the score.  I argued with ChatGPT about relative pitches in
> Lilypond, I told it to go back and read the manuals :-)  I gave up
> asking ChatGPT about generating Lilypond scores after that.
>
> Ken Wolcott
>
> On Wed, Mar 29, 2023 at 3:44 PM Saul Tobin  wrote:
> >
> > I've seen some examples of other people succeeding in getting ChatGPT with 
> > GPT4 to compose simple music in other text based music formats. I've had 
> > limited success getting it to output Lilypond code. It is able to correctly 
> > structure the code with a score block, nested contexts, and appropriately 
> > named variables, and bar checks at the end of each measure. It seems to 
> > struggle to create rhythms that fit within the time signature beyond 
> > extremely simple cases. It also seems to struggle a lot to understand what 
> > octave pitches will be in when using relative mode.
> >
> > It also seems to have a lot of trouble keeping track of the relationship 
> > between notes entered in different simultaneous expressions. Just asking it 
> > to repeat back which notes appear in each voice on each beat, GPT4 
> > frequently gives stubbornly incorrect answers about the music it generated. 
> > This makes it very difficult to improve its output by giving feedback.
> >
> > I'm curious whether anybody else has tried playing with this. I have to 
> > imagine that GPT4 has the potential to produce higher quality Lilypond 
> > output, given some of the other impressive things it can do. Perhaps it 
> > needs to be provided with a large volume of musical repertoire in Lilypond 
> > format.

Re: Anybody else playing with GPT4 and Lilypond?

[Kenneth Wolcott]

HI Saul;

  I asked ChatGPT to write some ABC notation.  The result was...'okay'.

  I then asked for a very simple arrangement of some children's tune
and it got very confused about relative pitches.  Since the rhythm for
the piece of music I requested was so simple it didn't have a problem
generating the score.  I argued with ChatGPT about relative pitches in
Lilypond, I told it to go back and read the manuals :-)  I gave up
asking ChatGPT about generating Lilypond scores after that.

Ken Wolcott

On Wed, Mar 29, 2023 at 3:44 PM Saul Tobin  wrote:
>
> I've seen some examples of other people succeeding in getting ChatGPT with 
> GPT4 to compose simple music in other text based music formats. I've had 
> limited success getting it to output Lilypond code. It is able to correctly 
> structure the code with a score block, nested contexts, and appropriately 
> named variables, and bar checks at the end of each measure. It seems to 
> struggle to create rhythms that fit within the time signature beyond 
> extremely simple cases. It also seems to struggle a lot to understand what 
> octave pitches will be in when using relative mode.
>
> It also seems to have a lot of trouble keeping track of the relationship 
> between notes entered in different simultaneous expressions. Just asking it 
> to repeat back which notes appear in each voice on each beat, GPT4 frequently 
> gives stubbornly incorrect answers about the music it generated. This makes 
> it very difficult to improve its output by giving feedback.
>
> I'm curious whether anybody else has tried playing with this. I have to 
> imagine that GPT4 has the potential to produce higher quality Lilypond 
> output, given some of the other impressive things it can do. Perhaps it needs 
> to be provided with a large volume of musical repertoire in Lilypond format.

Re: Benefits of Cairo backend over Ghostscript for PDF

[Kenneth Wolcott]

+infinity

On Sun, Mar 19, 2023 at 3:41 AM David Kastrup  wrote:
>
> Andrew Bernard  writes:
>
> >> On 18/03/2023 11:44 pm, Werner LEMBERG wrote:
>  Hi Werner, With NBN in Australia, the speeds are amazing.  [...]
> >>> Well, a great percentage of the world does not have such amazing
> >>> circumstances...
> >
> > Well as I said, I don't know. I thought America would be way ahead.
>
> The political system in the U.S. considers bribes by lobbyists a First
> Amendment protected variant of free speech.  As a consequence, cable
> companies receiving government subsidies for implementing broadband
> coverage save a lot of money if instead of increasing broadband coverage
> they bribe the politicians responsible for implementing oversight or at
> least ensuring there is a reasonable chance for competitors to get
> access to the market.
>
> The FCC government agency responsible for regulating cable companies has
> currently spent more than a year headless, with lobbyists sabotaging an
> appointment for the leadership position after the last one had left.
>
> Sometimes it is not sufficient to be good at developing technology...
>
> --
> David Kastrup
>

Re: Message size limit

[Kenneth Wolcott]

Hard disagree on rich text :-)

Rich text and other kinds of formatting issues all occur when there is
no formatting standard required to be met.  Having everyone use
exactly the same formatting rules would be overly burdensome.  Getting
everyone to agree to a set of formatting rules would be nearly
impossible.  When person A uses a formatting style best suited to
them, person B may have extreme difficulty understanding what is being
expressed when their formatting style is significantly different.
Some people really do not like having a rich text environment forced
on them (perhaps the person is using a text-based interface,
text-based email app, text-based editor, etc).

  What I think is best if the specific desired formatting of the crux
of the issue (not the entire email content) is best placed in an
attachment, just like pdf, png, jpeg, gif, etc files.

  Well, that's my two cents on the issue :-)

Thanks,
Ken Wolcott

On Sat, Mar 4, 2023 at 1:03 PM Saul Tobin  wrote:
>
> Hard disagree on plain text emails.
>
> I didn't really have a strong opinion re the whole discussion about message 
> boards vs. email, but IMO the world has moved on to rich text email with 
> embedded media. I think the reliance on plain text email as the standard for 
> this mailing list detracts significantly from the conversation. Inlining 
> images makes it much easier to communicate typesetting questions and also 
> much easier to quickly respond, especially when viewing messages on a cell 
> phone.
>
> Rich text emails with embedded media should IMO be supported as first class 
> citizens of the mailing list.
>
> Saul
>
>
> On Sat, Mar 4, 2023 at 12:18 PM Valentin Petzel  wrote:
>>
>> Hi Jean,
>>
>> I think Robin is talking about embedded images that are quoted on reply,
>> resulting in the same attachment being sent back and forth over and over
>> again.
>>
>> Of course this does not matter when you send plain text emails, which should
>> be the sensible choice ...
>>
>> Cheers,
>> Valentin
>>
>> Am Samstag, 4. März 2023, 16:53:11 CET schrieb Jean Abou Samra:
>> > Le samedi 04 mars 2023 à 16:45 +0100, Robin Bannister a écrit :
>> > > Jean Abou Samra wrote:
>> > > > Hi,
>> > > >
>> > > > We've been informed that the size of messages to this list containing
>> > > > large attachments is occasionally clogging up the GNU list server's
>> > > > mail delivery queue, causing distribution delays (not just for this
>> > > > list, but for everyone on the hundreds of other gnu.org lists).
>> > > >
>> > > > To avoid this, your friendly list admins have configured a max message
>> > > > size of 512KB.>
>> > > Is there any specific advice for users taking screenshots?
>> >
>> > Not sure I understand the question. Why would they differ from other kinds
>> > of attachments?
>> > > Especially inline ones: those get copied when quoted, cf 2021-09.
>> >
>> > What are you referring to precisely? There are lots of messages in the list
>> > archives for September 2021.
>>

Re: Lilypond 2.24.1 convert-ly writes version 2.24.0 to the converted file(s)?!

[Kenneth Wolcott]

Now how did I miss that? Face-palm :-)

Thanks,
Ken

On Wed, Mar 1, 2023 at 11:40 PM Mark Knoop  wrote:
>
>
> At 17:41 on 01 Mar 2023, Kenneth Wolcott wrote:
> > Hi;
>
> > I think that convert-ly should write the current version to the
> > converted file(s).
>
> > If that statement is correct, then Lilypond version 2.24.1 writes the
> > older version (2.24.0) to the converted file(s).
>
> Please see the -c, --current-version option to convert-ly.
>
>
> --
> Mark Knoop

Re: Lilypond 2.24.1 convert-ly writes version 2.24.0 to the converted file(s)?!

[Kenneth Wolcott]

Thanks, Jean.

That makes sense.

But the implication is it should based on the fact that the conversion
history shows all the minor versions along the way...

Thanks,
Ken

On Wed, Mar 1, 2023 at 6:05 PM Jean Abou Samra  wrote:
>
> Le mercredi 01 mars 2023 à 17:41 -0800, Kenneth Wolcott a écrit :
>
> Hi;
>
> I think that convert-ly should write the current version to the
> converted file(s).
>
> If that statement is correct, then Lilypond version 2.24.1 writes the
> older version (2.24.0) to the converted file(s).
>
> I believe it's intentional. The syntax never changes within a stable release 
> by definition of a stable release, so convert-ly will never make any 
> modifications between 2.24.0 and 2.24.1. In other words, converting to 2.24.0 
> and converting to 2.24.1 is the same thing. Perhaps it could output \version 
> "2.24" to avoid this kind of confusion.

Lilypond 2.24.1 convert-ly writes version 2.24.0 to the converted file(s)?!

[Kenneth Wolcott]

Hi;

I think that convert-ly should write the current version to the
converted file(s).

If that statement is correct, then Lilypond version 2.24.1 writes the
older version (2.24.0) to the converted file(s).

Here's my test script invocation:

./test_conversion_version.bash | tee ./test_conversion_version.log

See attached files.

Perhaps I'm imagining things

Thanks,
Ken Wolcott


test_conversion_version.bash
Description: Binary data


test_conversion_version.log
Description: Binary data


test_try1.ly
Description: Binary data


test_try1_converted.ly
Description: Binary data


test_try1_converted.log
Description: Binary data

Re: Policy for posts from non-members

[Kenneth Wolcott]

Hi Jean;

  I've been following this thread for some while.  I really applaud
your intentions and efforts with regards to this mailing list
management; your dedication is impressive and appreciated.

Ken Wolcott

On Wed, Feb 22, 2023 at 2:25 PM Jean Abou Samra  wrote:
>
> Le mardi 21 février 2023 à 23:36 +0100, Jean Abou Samra a écrit :
>
> Hi,
> I've not been an admin of this list for very long, yet I'm already weary of 
> telling people who post without being subscribed to the list that they should 
> subscribe in order to avoid each of their messages being manually approved. I 
> wonder what you (meaning everyone, but especially Mark, the other admin) 
> would think about changing the list configuration to reject post from 
> non-members instead of holding them on moderation, with a message such as
> “Welcome to the lilypond-user mailing list. We apologize, but in order to 
> prevent spam, we need you to subscribe to the list before you post. Please 
> fill out the subscription form on 
> https://lists.gnu.org/mailman/listinfo/lilypond-user.
> Once you are subscribed, you will receive all posts to the list, so you can 
> help out other people as well. However, if you only wish to interact with 
> this list infrequently, you may disable mail subscription in your membership 
> preferences after you have subscribed.
> If you believe you are already subscribed to the list, it probably means that 
> you accidentally posted from a different email address than the one you are 
> subscribed with.
> If you have any question or encounter problems, feel free to contact the list 
> admins at lilypond-user-ow...@gnu.org”
> On the plus side, this means that instead of delaying the message until Mark 
> or me looks at it, the feedback will come instantly.
>
> An update on this:
>
> It turned out to be a really bad idea. Fortunately, Bob Proulx, an admin on 
> GNU's Mailman server, noticed the change and explained why.
>
> The problem is backscatter. If a spammer sends a spam while making it look 
> like it comes from a real address that is not subscribed to the list, the 
> person this real address belongs to receives an automated message from the 
> list, which is viewed as unsolicited. Not only is that bad for this person, 
> but it leads to DNS blacklisting for lists.gnu.org, which affects all GNU 
> lists badly.
>
> I apologize for this; I didn't realize this implication at all. The change 
> has been rolled back and things will just remain as they were before. Thank 
> you Bob!
>
> Jean

Re: spurious second treble clef sign, what did I do wrong this time?

[Kenneth Wolcott]

Ah!!! Got it.

Thanks to you all.

Ken

On Tue, Feb 21, 2023 at 12:52 PM Mats Bengtsson
 wrote:
>
>
> On 2023-02-21 21:33, Kenneth Wolcott wrote:
>
> Hi Leo;
>
>   Thanks again for your help.
>
>   I have the "\grace s8." now in all three of the voices that do not
> have the "\acciaccatura", yet the problem persists.
>
>   I'm not sure how I would insert the "\grace s8." into my \global
> variable.  I'm sure that is obvious, but I don't grok it.
>
>   I have attached my current Lilypond source, pdf output from Lilypond
> and the original pdf file.
>
> Thanks,
> Ken
>
> If you look carefully, you will see that it's no longer the clef, but the 
> time signature that's duplicated. The reason is that you have included the 
> time signature setting in your \global variable and that you have included 
> the \global variable into your \piano_dynamics variable, without a matching 
> \grace{s8.}. Since there's no reason to include \global in \piano_dynamics, 
> it's easiest to simply remove it there. Otherwise add \grace {s8.} there as 
> well.
>
>/Mats

Re: spurious second treble clef sign, what did I do wrong this time?

[Kenneth Wolcott]

Thank you, Leo.

I already had "\grace {s16*3} s1" in the second lh voice, apparently
needed in the the second rh voice?

Thanks,
Ken

On Mon, Feb 20, 2023 at 11:42 PM Leo Correia de Verdier
 wrote:
>
> I haven’t been able to open your  .ly file since   I’m on the telephone, but 
> that should be an issue 34. Add s8. right after the clef and time signature 
> in the right hand, so that the grace note timing matches between the 
> different staves and voices and the extra clefs and time signatures will 
> disappear.
>
> HTH
> /Leo
>
> > 21 feb. 2023 kl. 08:33 skrev Kenneth Wolcott :
> >
> > Hi;
> >
> >  I'm engraving a piece of music arranged for Piano that (later) has
> > polyphony in the right hand and left hand.
> >
> >  This is Lilypond 2.24.1 on MacOS.
> >
> >  There is a spurious second treble clef (and spurious time signature)
> > in the first bar of the right hand (upper) staff.
> >
> >  What am I doing wrong that causes this?
> >
> >  I am attaching the example pdf which I am engraving from, my
> > Lilypond source and the pdf Lilypond creates.
> >
> > Thanks,
> > Ken Wolcott
> > 
> > 
> > 

Re: I did not previously realize that Lilypond would automatically update pre-existing scores

[Kenneth Wolcott]

Thanks to all for the clarification.

Ken

On Sat, Feb 18, 2023 at 6:14 AM Sven Axelsson  wrote:
>
> On Sat, 18 Feb 2023 at 09:03, Kenneth Wolcott  
> wrote:
>>
>> I have some LIlypond code (from someone on the list) which is at
>> Lilypond version:
>>
>> grep version ./only_even_bars.ly
>> \version "2.22.0"
>>
>> ~/Downloads/lilypond-2.24.1/bin/lilypond ./only_even_bars.ly
>> GNU LilyPond 2.24.1 (running Guile 2.2)
>> Processing `./only_even_bars.ly'
>> Parsing...
>> Interpreting music...[8]
>> Preprocessing graphical objects...
>> Finding the ideal number of pages...
>> Fitting music on 1 page...
>> Drawing systems...
>> Converting to `only_even_bars.pdf'...
>> Success: compilation successfully completed
>>
>> No big fat warning.
>>
>> ~/Downloads/lilypond-2.24.1/bin/lilypond --version
>> GNU LilyPond 2.24.1 (running Guile 2.2)
>>
>> The resultant pdf is at Lilypond version 2.24.1 (attached).
>>
>> Hmmm...
>
>
> The version number in the footer just shows what version of Lilypond you 
> compiled with.
> It does not mean that your score was changed in any way, and if it contains 
> features that
> have been changed or deprecated the compilation will still fail and you need 
> to run
> convert-ly as usual.
>
> --
> Sven Axelsson
> ++[>++>+++>++>++
> ><<<<<-]>.+..>+.>+.<<-.>>+.>.<<.
> +++.>-.<<++.>>.<++.>>>++.<<<<.>>.<.

Re: I did not previously realize that Lilypond would automatically update pre-existing scores

[Kenneth Wolcott]

I have some LIlypond code (from someone on the list) which is at
Lilypond version:

grep version ./only_even_bars.ly
\version "2.22.0"

~/Downloads/lilypond-2.24.1/bin/lilypond ./only_even_bars.ly
GNU LilyPond 2.24.1 (running Guile 2.2)
Processing `./only_even_bars.ly'
Parsing...
Interpreting music...[8]
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Converting to `only_even_bars.pdf'...
Success: compilation successfully completed

No big fat warning.

~/Downloads/lilypond-2.24.1/bin/lilypond --version
GNU LilyPond 2.24.1 (running Guile 2.2)

The resultant pdf is at Lilypond version 2.24.1 (attached).

Hmmm...

Ken

On Fri, Feb 17, 2023 at 11:52 PM Werner LEMBERG  wrote:
>
>
> > Well, that’s what you get if the LilyPond version is too old. The
> > question was for a version that is “too new”.
>
> D'oh, right :-)
>
>
> Werner


only_even_bars.ly
Description: Binary data


only_even_bars.pdf
Description: Adobe PDF document

Re: I did not previously realize that Lilypond would automatically update pre-existing scores

[Kenneth Wolcott]

Hi Werner;

  Then as usual, I'm very confused.

  I'm not using Frescobaldi; the user interface is using a much too
small a font for me to use and I saw no way to enlarge it.

  What is expected to happen when Lilypond 2.24.1 encounters a score
with a version of 2.22.2 in it? Well, I'll try to carefully reproduce
(or not!) my experience!

  I guess my fingers were running faster than my eyes and my brain :-)

Thanks,
Ken

On Fri, Feb 17, 2023 at 10:50 PM Werner LEMBERG  wrote:
>
>
> > I did not previously realize that Lilypond would automatically update
> > pre-existing scores.
>
> It doesn't.  Are you using Frescobaldi?  Maybe this front-end can be
> set to automatically run `convert-ly`.
>
>
> Werner

I did not previously realize that Lilypond would automatically update pre-existing scores

[Kenneth Wolcott]

Hi;

I did not previously realize that Lilypond would automatically update
pre-existing scores.

I was surprised when I noticed that LIlypond 2.24.1 (locally installed
by download) automatically updated my 2.22.1 Lilypond score.  Usually
I run the convert script before engraving, but this time I forgot to
do that.

That's a nice feature I was not expecting. I usually carefully read
the Changes document and I did not see this feature.  How long has
this been the case?  Is there a way to tell Lilypond not to do this?
In general, I think that this is a great feature, but sometimes I'd
like to preserve what I have prior to conversion.

BTW, thanks to all who have contributed to this awesome Lilypond
project; it really is awesome.

Thanks,
Ken Wolcott

Re: The "R.H." instruction with 45 degree slope down and up from treble to bass clef: How?

[Kenneth Wolcott]

Thank you, Werner!

On Sun, Jan 29, 2023 at 11:17 PM Werner LEMBERG  wrote:
>
>
> > The "R.H." instruction with 45 degree slope down and up from treble
> > to bass clef: How?
>
> Look up 'staff-change lines' in the Notation Reference index to get
> details on the `\showStaffSwitch` command.
>
>
> Werner

Re: LP 2.24.0 segno repeat where coda break is in the middle of a repeat volta block

[Kenneth Wolcott]

Hi David;

  Thank you so much for reminding me that there are ways to reduce the
size of the pdf, decreasing the size to reduce the pain of downloading
a huge attachment.

Ken

On Sun, Jan 22, 2023 at 8:35 AM David Wright  wrote:
>
> On Sat 21 Jan 2023 at 15:51:16 (-0800), Kenneth Wolcott wrote:
> > Using Lilypond 2.24.0, I engraved "Memory" (from "Cats") using the
> > example published in the Hal Leonard Easy Piano Songs book (the pdf
> > file generated from photos from this book are huge).
>
> I displayed your PDF at 60% size, and took screenshots of the pages.
> The structure of the score is still plainly visible, but five pages
> like this would take about 750KB to post instead of 14MB: of great
> benefit to many.
>
> I won't post them here, but I can send you pages privately.
>
> Cheers,
> David.

Re: sustain to-barline? LP 2.24.0

[Kenneth Wolcott]

Hi Martin;

  I really did not think that I could have another Dynamics Context;
wonderful idea.

Thanks,
Ken

On Thu, Jan 12, 2023 at 12:10 AM Martín Rincón Botero
 wrote:
>
> Hi Kenneth,
>
> you can add another Dynamics context below the lower staff and use it only 
> for pedalling.
>
> Martín.
>
> www.martinrinconbotero.com
>
>
> On Jan 12, 2023 at 7:07 AM,  wrote:
>
> Hi;
>
>   However, placing the sustain pedal actions in the Dynamic Context
> means that the pedal actions show up below the treble clef rather than
> below the bass clef.  This, of course, interferes with hairpins and
> dynamics.  I'd like an RFE to have a sustainContext that pairs with
> the lower staff :-)
>
> Thanks,
> Ken
>
> On Wed, Jan 11, 2023 at 9:32 PM Kenneth Wolcott
>  wrote:
> >
> > Hi;
> >
> >   Now that's weird :-)
> >
> >   Now the sustain pedal bracket style is working as desired.
> >
> > Thanks,
> > Ken
> >
> > On Wed, Jan 11, 2023 at 9:04 PM Kenneth Wolcott
> >  wrote:
> > >
> > > Hi;
> > >
> > >   Placing the sustain pedal actions in the Dynamics Context results in
> > > the sustain pedal bracket style being ignored, reverting to the
> > > default style.
> > >
> > > Thanks,
> > > Ken
> > >
> > > On Wed, Jan 11, 2023 at 8:50 PM Kenneth Wolcott
> > >  wrote:
> > > >
> > > > Hi;
> > > >
> > > >   I decided to place my sustain pedal commands in the Dynamics
> > > > Context; I hope that solves the problem.
> > > >
> > > > Thanks,
> > > > Ken
> > > >
> > > > On Wed, Jan 11, 2023 at 7:29 PM Kenneth Wolcott
> > > >  wrote:
> > > > >
> > > > > Hi;
> > > > >
> > > > > sustain to-barline? LP 2.24.0
> > > > >
> > > > >   I'd like to have the sustain pedal terminate at the bar line, not at
> > > > > the last note in the staff.
> > > > >
> > > > >   Is there a "to-barline" setting for the sustain pedal?  I searched
> > > > > for "to-barline" and found nothing regarding the sustain pedal.
> > > > >
> > > > >   I looked at the mailing list archive and found something in 2015 
> > > > > mentioning:
> > > > >
> > > > > \override Staff.PianoPedalBracket.to-barline = ##t
> > > > >
> > > > >   I tried this but it seems to be ignored.
> > > > >
> > > > > Thanks,
> > > > > Ken Wolcott
>

Re: bar check problems with a repeat volta whose first ending is an incomplete bar

[Kenneth Wolcott]

Thank you Michael and Pierre for some good ideas.

Ken

On Thu, Jan 12, 2023 at 1:18 AM Michael Hendry  wrote:
>
> On 12 Jan 2023, at 07:17, Pierre Perol-Schneider 
>  wrote:
>
>
> Hi Kenneth
>
> Le jeu. 12 janv. 2023 à 07:30, Kenneth Wolcott  a 
> écrit :
> ...
>>
>> It is bar #8 that is the incomplete bar in the first repeat volta,
>
> ...
>
> Two possibilities:
> a) ignore the warning, since it compiles OK;
> b) Change the measure length for each voice for this specific measure:
> \set Timing.measureLength = #(ly:make-moment 2/8)
>  (see: 
> https://lilypond.org/doc/v2.23/Documentation/notation/special-rhythmic-concerns.fr.html)
>
> HTH, cheers,
> Pierre
>
>
> …or you could work around the problem by starting the repeat at the beginning 
> of the first full bar, and including the E and D# lead-in at the end of bar 8.
>
> Or you could make bar 8 a 2/8 bar.
>
> The former would be easier to read, IMHO, but I’m (very much) an amateur 
> musician!
>
> Michael
>
>
>

Re: sustain to-barline? LP 2.24.0

[Kenneth Wolcott]

Hi;

  However, placing the sustain pedal actions in the Dynamic Context
means that the pedal actions show up below the treble clef rather than
below the bass clef.  This, of course, interferes with hairpins and
dynamics.  I'd like an RFE to have a sustainContext that pairs with
the lower staff :-)

Thanks,
Ken

On Wed, Jan 11, 2023 at 9:32 PM Kenneth Wolcott
 wrote:
>
> Hi;
>
>   Now that's weird :-)
>
>   Now the sustain pedal bracket style is working as desired.
>
> Thanks,
> Ken
>
> On Wed, Jan 11, 2023 at 9:04 PM Kenneth Wolcott
>  wrote:
> >
> > Hi;
> >
> >   Placing the sustain pedal actions in the Dynamics Context results in
> > the sustain pedal bracket style being ignored, reverting to the
> > default style.
> >
> > Thanks,
> > Ken
> >
> > On Wed, Jan 11, 2023 at 8:50 PM Kenneth Wolcott
> >  wrote:
> > >
> > > Hi;
> > >
> > >   I decided to place my sustain pedal commands in the Dynamics
> > > Context; I hope that solves the problem.
> > >
> > > Thanks,
> > > Ken
> > >
> > > On Wed, Jan 11, 2023 at 7:29 PM Kenneth Wolcott
> > >  wrote:
> > > >
> > > > Hi;
> > > >
> > > > sustain to-barline? LP 2.24.0
> > > >
> > > >   I'd like to have the sustain pedal terminate at the bar line, not at
> > > > the last note in the staff.
> > > >
> > > >   Is there a "to-barline" setting for the sustain pedal?  I searched
> > > > for "to-barline" and found nothing regarding the sustain pedal.
> > > >
> > > >   I looked at the mailing list archive and found something in 2015 
> > > > mentioning:
> > > >
> > > > \override Staff.PianoPedalBracket.to-barline = ##t
> > > >
> > > >   I tried this but it seems to be ignored.
> > > >
> > > > Thanks,
> > > > Ken Wolcott

Re: sustain to-barline? LP 2.24.0

[Kenneth Wolcott]

Hi;

  Now that's weird :-)

  Now the sustain pedal bracket style is working as desired.

Thanks,
Ken

On Wed, Jan 11, 2023 at 9:04 PM Kenneth Wolcott
 wrote:
>
> Hi;
>
>   Placing the sustain pedal actions in the Dynamics Context results in
> the sustain pedal bracket style being ignored, reverting to the
> default style.
>
> Thanks,
> Ken
>
> On Wed, Jan 11, 2023 at 8:50 PM Kenneth Wolcott
>  wrote:
> >
> > Hi;
> >
> >   I decided to place my sustain pedal commands in the Dynamics
> > Context; I hope that solves the problem.
> >
> > Thanks,
> > Ken
> >
> > On Wed, Jan 11, 2023 at 7:29 PM Kenneth Wolcott
> >  wrote:
> > >
> > > Hi;
> > >
> > > sustain to-barline? LP 2.24.0
> > >
> > >   I'd like to have the sustain pedal terminate at the bar line, not at
> > > the last note in the staff.
> > >
> > >   Is there a "to-barline" setting for the sustain pedal?  I searched
> > > for "to-barline" and found nothing regarding the sustain pedal.
> > >
> > >   I looked at the mailing list archive and found something in 2015 
> > > mentioning:
> > >
> > > \override Staff.PianoPedalBracket.to-barline = ##t
> > >
> > >   I tried this but it seems to be ignored.
> > >
> > > Thanks,
> > > Ken Wolcott

Re: sustain to-barline? LP 2.24.0

[Kenneth Wolcott]

Hi;

  Placing the sustain pedal actions in the Dynamics Context results in
the sustain pedal bracket style being ignored, reverting to the
default style.

Thanks,
Ken

On Wed, Jan 11, 2023 at 8:50 PM Kenneth Wolcott
 wrote:
>
> Hi;
>
>   I decided to place my sustain pedal commands in the Dynamics
> Context; I hope that solves the problem.
>
> Thanks,
> Ken
>
> On Wed, Jan 11, 2023 at 7:29 PM Kenneth Wolcott
>  wrote:
> >
> > Hi;
> >
> > sustain to-barline? LP 2.24.0
> >
> >   I'd like to have the sustain pedal terminate at the bar line, not at
> > the last note in the staff.
> >
> >   Is there a "to-barline" setting for the sustain pedal?  I searched
> > for "to-barline" and found nothing regarding the sustain pedal.
> >
> >   I looked at the mailing list archive and found something in 2015 
> > mentioning:
> >
> > \override Staff.PianoPedalBracket.to-barline = ##t
> >
> >   I tried this but it seems to be ignored.
> >
> > Thanks,
> > Ken Wolcott

Re: sustain to-barline? LP 2.24.0

[Kenneth Wolcott]

Hi;

  I decided to place my sustain pedal commands in the Dynamics
Context; I hope that solves the problem.

Thanks,
Ken

On Wed, Jan 11, 2023 at 7:29 PM Kenneth Wolcott
 wrote:
>
> Hi;
>
> sustain to-barline? LP 2.24.0
>
>   I'd like to have the sustain pedal terminate at the bar line, not at
> the last note in the staff.
>
>   Is there a "to-barline" setting for the sustain pedal?  I searched
> for "to-barline" and found nothing regarding the sustain pedal.
>
>   I looked at the mailing list archive and found something in 2015 mentioning:
>
> \override Staff.PianoPedalBracket.to-barline = ##t
>
>   I tried this but it seems to be ignored.
>
> Thanks,
> Ken Wolcott

sustain to-barline? LP 2.24.0

[Kenneth Wolcott]

Hi;

sustain to-barline? LP 2.24.0

  I'd like to have the sustain pedal terminate at the bar line, not at
the last note in the staff.

  Is there a "to-barline" setting for the sustain pedal?  I searched
for "to-barline" and found nothing regarding the sustain pedal.

  I looked at the mailing list archive and found something in 2015 mentioning:

\override Staff.PianoPedalBracket.to-barline = ##t

  I tried this but it seems to be ignored.

Thanks,
Ken Wolcott

Re: Need volta repeat brackets for a Trumpet+Piano "great big staff?"

[Kenneth Wolcott]

Thank you, Abraham, for the feedback.

I feel comfortable now with the volta brackets as they are.

Secondly, I agree that it is overkill to to have the Voice specified
for the left hand when there is only one voice.

I'm fine-tuning as I go...

Thanks,
Ken

On Wed, Dec 21, 2022 at 10:51 PM Abraham Lee  wrote:
>
> Hey, Ken!
>
> On Wed, Dec 21, 2022 at 11:11 PM Kenneth Wolcott  
> wrote:
>>
>> Hi;
>>
>>   I need volta repeat brackets for a Trumpet+Piano "great big staff?".
>>
>>   I see the section in the Notation Reference and a section in the
>> Snippet Reference regarding volte multi-staff, but I'm confused when I
>> already have a PianoStaff and I have a Trumpet above it.  Do I use a
>> GreatStaff surrounding a PianoStaff?
>>
>> I have attached the origin pdf, my Lilypond source and my engraving.
>>
>> Both pdf files have the same name, sorry about that.  The larger one
>> is the origin and the smaller one is my engraving.
>
>
> Admittedly, I'm not 100% certain I understand what question you're asking 
> since it appears you're asking two different ones:
>
> 1. Do you need volta brackets above the trumpet staff and also above the top 
> piano staff? Definitely not. This would be less common in only a three-staff 
> score. If there were more, where the bracket is less visible, then... maybe, 
> but even with four staves in a single system, I'm not sure I'd do more than 
> have the volta bracket above the top-most one.
>
> 2. Do you need to wrap all the staves in another GrandStaff (or similar)? 
> Again, no. Your source file is structured fine the way it is. I think the 
> only thing you didn't *need* to do is explicitly say \new Voice within each 
> of the PianoStaff's Staff. You could just say:
>
> \new PianoStaff \with { ... } <<
>   \new Staff <<
> { \voiceOne \rh_one }
> { \voiceTwo \rh_two }
>   >>
>   \new Staff <<
> { \lh }  % I wouldn't explicitly use \voiceOne here at all since you 
> don't need the forced directionality it will cause
>   >>
> >>
>
> If those weren't what you're asking, then I apologize for not catching the 
> actual question(s).
>
> HTH,
> Abraham

Re: tremolo: 3/4 time, one dotted-half note chord, double-slash tremolo question

[Kenneth Wolcott]

That helps!  Thanks.

On Mon, Dec 19, 2022 at 6:38 PM William Rehwinkel
 wrote:
>
> Hey Ken,
>
> For a tremolo on a single repeating note you can use this other syntax:
>
> \version "2.24.0"
> \relative d' {
>  \time 3/4
>  d2.:16
> }
>
> -will
>
> On 12/19/22 20:41, Kenneth Wolcott wrote:
> > Hi;
> >
> >I'm still do not understand the math (I'd like to generate a
> > formula!) for tremolos.
> >
> >I have a tremolo that I'd like to engrave in 3/4 time, one
> > dotted-half note chord, double-slashed.
> >
> >I'd like to use the repeat tremolo syntax so that I can obtain midi
> > output (without using the articulate feature).
> >
> >Please see attached screenshot.
> >
> > Thanks,
> > Ken Wolcott
> --
> William Rehwinkel

tremolo: 3/4 time, one dotted-half note chord, double-slash tremolo question

[Kenneth Wolcott]

Hi;

  I'm still do not understand the math (I'd like to generate a
formula!) for tremolos.

  I have a tremolo that I'd like to engrave in 3/4 time, one
dotted-half note chord, double-slashed.

  I'd like to use the repeat tremolo syntax so that I can obtain midi
output (without using the articulate feature).

  Please see attached screenshot.

Thanks,
Ken Wolcott

Re: How to implement "f (second time p)" for midi?

[Kenneth Wolcott]

Hi David;

  Thank you!  I copied the right hand notes so that there would be a
midi-specific version.  I then reverted the changes I made to the
right hand notes containing the \volta hint.  I then modified the
right hand notes for midi without the New Dynamic notation but with
the \volta hint.  It works! 

Thanks,
Ken

On Fri, Dec 16, 2022 at 6:42 PM David Kastrup  wrote:
>
> Kenneth Wolcott  writes:
>
> > Hi David;
> >
> >   I have attached the updated Lilypond source.
> >
> >   It looks like my attempt failed to implement your hint :-)
>
> Well, for one thing you might want to remove your
>
> \f_second_time_p
>
> phrases.  For another, the error message occurs in the typeset output.
> Your question was about MIDI...
>
> --
> David Kastrup

Re: How to implement "f (second time p)" for midi?

[Kenneth Wolcott]

Hi David;

  I have attached the updated Lilypond source.

  It looks like my attempt failed to implement your hint :-)

  Here's the results of my attempt to implement your idea...

%%
%%

  Here's my sanitized (long path redacted) log of my engraving attempt:

 1  GNU LilyPond 2.24.0 (running Guile 2.2)
 2  Changing working directory to: long_path/target'
 3  Processing `Procession_of_the_Military_Night_Watch_in_Madrid.ly'
 4  Parsing...
 5  Interpreting music...
 6  
long_path/source/Procession_of_the_Military_Night_Watch_in_Madrid.ly:44:16:
warning: conflict with event: `absolute-dynamic-event'
 7  \volta 1 <>
 8 \f
 9  
long_path/source/Procession_of_the_Military_Night_Watch_in_Madrid.ly:45:16:
warning: discarding event: `absolute-dynamic-event'
10  \volta 2 <>
11 \p
12  [8][16][24][32]
13  
long_path/source/Procession_of_the_Military_Night_Watch_in_Madrid.ly:85:16:
warning: conflict with event: `absolute-dynamic-event'
14  \volta 1 <>
15 \f
16  
long_path/source/Procession_of_the_Military_Night_Watch_in_Madrid.ly:86:16:
warning: discarding event: `absolute-dynamic-event'
17  \volta 2 <>
18 \p
19  [40][48][56][64][72][80]
20  
long_path/source/Procession_of_the_Military_Night_Watch_in_Madrid.ly:162:16:
warning: c
onflict with event: `absolute-dynamic-event'
21  \volta 1 <>
22 \f
23  
long_path/source/Procession_of_the_Military_Night_Watch_in_Madrid.ly:163:16:
warning: d
iscarding event: `absolute-dynamic-event'
24  \volta 2 <>
25 \p
26  [88][96]
27  Preprocessing graphical objects...
28  Interpreting music...
29  MIDI output to
`Procession_of_the_Military_Night_Watch_in_Madrid.midi'...
30  Finding the ideal number of pages...
31  Fitting music on 1 or 2 pages...
32  Drawing systems...
33  Converting to `Procession_of_the_Military_Night_Watch_in_Madrid.pdf'...
34  Success: compilation successfully completed

%%
%%

 The following is a diff of my 2.22.2 version and my 2.24.0 version:

diff ../../lp_2.22.2/source/Procession_of_the_Military_Night_Watch_in_Madrid.ly
./Procession_of_the_Military_Night_Watch_in_Madrid.ly
1c1
< \version "2.22.2"
---
> \version "2.24.0"
4a5,9
> % NOTE: Try the following hint in the repeat voltas that have different 
> dynamics:
> %
> % \volta 1 <>\f
> % \volta 2 <>\p
>
37c42
<   \set Score.markFormatter = #format-mark-box-alphabet
---
>   \set Score.rehearsalMarkFormatter = #format-mark-box-alphabet
38a44,45
> \volta 1 <>\f
> \volta 2 <>\p
77a85,86
> \volta 1 <>\f
> \volta 2 <>\p
152a162,163
> \volta 1 <>\f
> \volta 2 <>\p

%%
%%

Thanks,
Ken Wolcott


Procession_of_the_Military_Night_Watch_in_Madrid.ly
Description: Binary data

Re: How to implement "f (second time p)" for midi?

[Kenneth Wolcott]

Hi David;

  Thank you for the hint.  I successfully ran Lilypond 2.24.0
convert.ly on my source and successfully engraved it using Lilypond
version 2.24.0.  Now I'll look into the /volta idea.

Thanks,
Ken

On Fri, Dec 16, 2022 at 7:16 AM David Kastrup  wrote:
>
> Kenneth Wolcott  writes:
>
> > HI;
> >
> >   Dumb question here.  I'm sure that this is covered in the
> > documentation, but I have yet to find out where.
> >
> >   Lilypond 2.22.2,  MacOs (via homebrew).
> >
> >   How to implement "f (second time p)" for midi?
>
> \volta 1 <>\f
> \volta 2 <>\p
>
> could possibly work.
>
> --
> David Kastrup

Staff.midiExpression is documented but I've been using Voice.midiExpression...

[Kenneth Wolcott]

Hi;

Staff.midiExpression is documented but I've been using
Voice.midiExpression and no warnings or errors were reported.

  I can't seem to find any references to "Voice.midiExpression" in the
documentation (perhaps my searching isn't diligent enough).

Does the "Voice.midiExpression" work the same way as the
"Staff.midiExpression" (or vice-versa)?

  I'm engraving an arrangement of the First Gymnopedie (Satie) where
the melody (sequence of quarter notes) line is overwhelmed by the half
notes and dotted half notes in the other voices.

  Is music like this a bit too difficult for MIDI to handle? :-)

  Too summarize my question:

  What is the correct Lilypond syntax to use and why isn't the "wrong
one" resulting in a warning or error?

  This is a new engraving attempt, not one that needs to be massaged
by convert-ly.

  Lilypond 2.22.2 (Mac, home brew)

Thanks,
Ken Wolcott

another minor quibble: Lilypond really isn't supported on UNIX; Linux and MacOS, not UNIX

[Kenneth Wolcott]

HI;

  This is just a tiny quibble, but the Lilypond Download web page
implies support for UNIX (which implies, at least to me,
SunOS/Solaris, HP-UX, IBM/AIX, etc), where Linux really isn't UNIX.

  See attached screenshot.

Thanks,
Ken Wolcott

Re: Complex vertical positioning (eight items in four bars)

[Kenneth Wolcott]

Hi Vaughan and Knute;

  I guess what I was asking for is a best practice as the clutter
there seems a bit much.

  I think I will make a midi-specific version and hide all the
metronome marks (beyond the initial one) in it.

  That means I need to do "rit.", "accel.", and "a tempo" in place of
the specified metronome marks.

  I'll gladly implement the suggestion of moving the "D.C. al Coda" to bar #131.

  Now no vertical position tweaks are required.

  Then it will be fairly easy to transition the piece from 2.22.2 to
2.23.x/2.24x to gain the new repeat segno feature.

Thanks,
Ken

On Wed, Oct 26, 2022 at 8:55 AM Knute Snortum  wrote:
>
> On Tue, Oct 25, 2022 at 11:06 PM Vaughan McAlley  
> wrote:
> >
> >
> >
> > On Wed, 26 Oct 2022, 10:36 Kenneth Wolcott,  
> > wrote:
> >>
> >> Hi;
> >>
> >> Complex vertical positioning (eight items in four bars)
> >>
> >> I'm engraving a Piano arrangement of the Waltz Nr 2 using a previously
> >> typeset example (from the Suite for Jazz Orchestra composed by Dmitri
> >> Shostakovich), in which I encounter a complex vertical positioning
> >> situation.
> >>
> >> Prior to making any further tweaks, I'd like to ask you all for your
> >> opinion on whether or not the prior typesetter's choices were optimal.
> >>
> >> Original pdf, my engraving and my Lilypond source are attached.
> >>
> >> Thanks,
> >> Ken Wolcott
> >
> >
> > Hi Ken,
> >
> > It looks like the tempo markings are artifacts of producing the MIDI file, 
> > and can be safely left out of the score. I have a rogue tempo marking in 30 
> > printed copies of a 100-page score because I wanted to listen to one 
> > movement quicker than it would eventually sound.
> >
> > Vaughan
> >
>
> What specifically is the problem you're trying to solve?  Measures
> 93-95 look crowded, but that's another problem.  Personally, I would
> put the D.C. al coda on measure 131.  That might help.
>
> --
> Knute Snortum

Re: Complex vertical positioning (eight items in four bars)

[Kenneth Wolcott]

Oops.  Bar #93-#95 in particular.

Thanks,
Ken

On Tue, Oct 25, 2022 at 4:33 PM Kenneth Wolcott
 wrote:
>
> Hi;
>
> Complex vertical positioning (eight items in four bars)
>
> I'm engraving a Piano arrangement of the Waltz Nr 2 using a previously
> typeset example (from the Suite for Jazz Orchestra composed by Dmitri
> Shostakovich), in which I encounter a complex vertical positioning
> situation.
>
> Prior to making any further tweaks, I'd like to ask you all for your
> opinion on whether or not the prior typesetter's choices were optimal.
>
> Original pdf, my engraving and my Lilypond source are attached.
>
> Thanks,
> Ken Wolcott

Re: bar check bug in Lilypond 2.22.2 ??

[Kenneth Wolcott]

HI Jean;

  Thank you for finding the problem due to my not using repeat volta
consistently among all the parts! Problem solved!

Ken

On Fri, Oct 21, 2022 at 2:33 AM Jean Abou Samra  wrote:
>
> Le 21/10/2022 à 00:54, Kenneth Wolcott a écrit :
> > Hi Jean and Adrian;
> >
> >I attached the wrong files! So sorry!  Let me try again.
> >
> > Thanks!
>
>
> Listen to the MIDI, or change the score with \midi to use \layout too,
> and you will find something funnier than just bar check errors: there
> is one staff that continues alone for a long time at the end of the piece.
> The reason is that you used \unfoldRepeats but you only used \repeat volta
> in that staff. When using \repeat volta, you must use it in all staves,
> otherwise \unfoldRepeats will only unfold those where you used \repeat
> volta.
> Because you have a time signature change somewhere, this causes a
> superposition of staves where there are different time signatures.
>
> Best,
> Jean
>
>
>

Re: Duet part, rehearsal marks for both parts?

[Kenneth Wolcott]

Thank you Kieren and Wol.

I'll experiment with what you've offered.

Thank you,
Ken

On Sun, Oct 16, 2022 at 11:10 AM Wol  wrote:
>
> On 16/10/2022 16:47, Kieren MacMillan wrote:
> > Hi Kenneth,
> >
> >> I guess I should just learn how to do tags :-)
> >
> > Well, yes, you should… but I don't think that's the proper solution to the 
> > problem you've stated (as I understand it).
> >
> > 1. Put all your "global" data (time signatures, rehearsal marks, tempi, 
> > etc.) in a single variable.
> >
> > 2. Add that variable in a non-staff context (e.g., TextLine or MarkLine) 
> > above whichever staff context(s) you want to see the rehearsal marks.
> >
> > It's that simple — no tags required.  =)
> >
> And this is probably not the right solution in the right place, but the
> other "obvious" solution is, is your rehearsal mark engraver in the
> right context? Should you move it from staff to score context, or vice
> versa (I don't know which one it is, or which one it should be, just
> that the question makes it sound like it's the wrong one).
>
> As I say, I don't think this is your answer, but this should have been
> one of the first possible answers you should have thought of.
>
> Cheers,
> Wol
>

Re: Duet part, rehearsal marks for both parts?

[Kenneth Wolcott]

Maybe I just should have kept my mouth shut :-)

I have rehearsal marks in both parts.  In the full score only the top
part will show the rehearsal marks.  When I display the parts
separately, they will both have the rehearsal marks.

So, I just need to have more coffee (even though I don't drink coffee)...

Thanks,
Ken

On Sat, Oct 15, 2022 at 3:40 PM Kenneth Wolcott
 wrote:
>
> I guess I should just learn how to do tags :-)
>
> On Sat, Oct 15, 2022 at 3:24 PM Kenneth Wolcott
>  wrote:
> >
> > HI;
> >
> >   I'm engraving a Trombone Duet.  There are rehearsal marks.  I'd like
> > to engrave both parts as a score, both parts having rehearsal marks
> > displayed, not just the first part.
> >
> > How to do this?  Lilypond 2.22.2
> >
> > Thanks,
> > Ken Wolcott

Re: Duet part, rehearsal marks for both parts?

[Kenneth Wolcott]

I guess I should just learn how to do tags :-)

On Sat, Oct 15, 2022 at 3:24 PM Kenneth Wolcott
 wrote:
>
> HI;
>
>   I'm engraving a Trombone Duet.  There are rehearsal marks.  I'd like
> to engrave both parts as a score, both parts having rehearsal marks
> displayed, not just the first part.
>
> How to do this?  Lilypond 2.22.2
>
> Thanks,
> Ken Wolcott

Duet part, rehearsal marks for both parts?

[Kenneth Wolcott]

HI;

  I'm engraving a Trombone Duet.  There are rehearsal marks.  I'd like
to engrave both parts as a score, both parts having rehearsal marks
displayed, not just the first part.

How to do this?  Lilypond 2.22.2

Thanks,
Ken Wolcott

Re: Tried to use "music box" with Lilypond 2.22.2, get lots of Scheme errors

[Kenneth Wolcott]

Oh, doh!

I have to redefine my function to handle the chords!


On Tue, Sep 20, 2022 at 7:50 PM Kenneth Wolcott
 wrote:
>
> Oh, it not only does not like "q"; it silently drops chords.  Oh well,
> it still is cool even though not completely useful for my use case.
>
> Thanks,
> Ken
>
> On Tue, Sep 20, 2022 at 7:43 PM Kenneth Wolcott
>  wrote:
> >
> > No, it does not support the "q' functionality, but it is still a very
> > cool function :-)
> >
> > Thanks,
> > Ken
> >
> > On Tue, Sep 20, 2022 at 7:36 PM Kenneth Wolcott
> >  wrote:
> > >
> > > HI Aaron;
> > >
> > >   Thank you very much!  Works great now.
> > >
> > >   A followup question: I don't think that this function supports the
> > > "q" substitution for chord repetition, does it?
> > >
> > >   I guess I'll find out :-)
> > >
> > > Thanks,
> > > Ken
> > >
> > > On Tue, Sep 20, 2022 at 6:15 PM Aaron Hill  
> > > wrote:
> > > >
> > > > On 2022-09-20 4:27 pm, Kenneth Wolcott wrote:
> > > > > Hi;
> > > > >
> > > > > Tried to use "music box" with Lilypond 2.22.2, get lots of Scheme
> > > > > errors.
> > > > >
> > > > > https://lsr.di.unimi.it/LSR/Search?q=music+box
> > > > >
> > > > > See attachments. I did not include my generated pdf file because it
> > > > > pertains to the input file prior to trying to implement the music box.
> > > > >
> > > > > Thanks,
> > > > > Ken Wolcott
> > > > >
> > > > > ~/bin/engrave.pl --lpv=2.22.2 --s=O_Holy_Night.ly
> > > > > GNU LilyPond 2.22.2 (running Guile 2.2)
> > > > > Processing `O_Holy_Night.ly'
> > > > > Parsing...Backtrace:
> > > > > [...]
> > > > > ice-9/eval.scm:159:9: Value out of range 0 to 18446744073709551615: 
> > > > > -14
> > > >
> > > > Review the documentation for LSR 346.  The transformation pattern must
> > > > use notes starting from middle C.  Your pattern has notes in a much
> > > > lower octave, which results in a negative index.  So, you would want to
> > > > say something like this:
> > > >
> > > > 
> > > > make_bass_pattern = \defineTransform \tuplet 6/4 \fixed c' { c8( d e f g
> > > > a) }
> > > > 
> > > >
> > > > However, you can do this more efficiently, removing the redundant notes:
> > > >
> > > > 
> > > > make_bass_pattern = \defineTransform \tuplet 6/4 \fixed c' { c8( d e f d
> > > > e) } % 1 2 3 4 2 3
> > > > % ...
> > > > | \make_bass_pattern { g, g d b } \make_bass_pattern { b, g d b }
> > > > | \make_bass_pattern { b, g d b } \make_bass_pattern { b, g d b }
> > > > | \make_bass_pattern { b, g d b } \make_bass_pattern { c g e c' }
> > > > % ...
> > > > 
> > > >
> > > >
> > > > -- Aaron Hill

Re: Tried to use "music box" with Lilypond 2.22.2, get lots of Scheme errors

[Kenneth Wolcott]

Oh, it not only does not like "q"; it silently drops chords.  Oh well,
it still is cool even though not completely useful for my use case.

Thanks,
Ken

On Tue, Sep 20, 2022 at 7:43 PM Kenneth Wolcott
 wrote:
>
> No, it does not support the "q' functionality, but it is still a very
> cool function :-)
>
> Thanks,
> Ken
>
> On Tue, Sep 20, 2022 at 7:36 PM Kenneth Wolcott
>  wrote:
> >
> > HI Aaron;
> >
> >   Thank you very much!  Works great now.
> >
> >   A followup question: I don't think that this function supports the
> > "q" substitution for chord repetition, does it?
> >
> >   I guess I'll find out :-)
> >
> > Thanks,
> > Ken
> >
> > On Tue, Sep 20, 2022 at 6:15 PM Aaron Hill  wrote:
> > >
> > > On 2022-09-20 4:27 pm, Kenneth Wolcott wrote:
> > > > Hi;
> > > >
> > > > Tried to use "music box" with Lilypond 2.22.2, get lots of Scheme
> > > > errors.
> > > >
> > > > https://lsr.di.unimi.it/LSR/Search?q=music+box
> > > >
> > > > See attachments. I did not include my generated pdf file because it
> > > > pertains to the input file prior to trying to implement the music box.
> > > >
> > > > Thanks,
> > > > Ken Wolcott
> > > >
> > > > ~/bin/engrave.pl --lpv=2.22.2 --s=O_Holy_Night.ly
> > > > GNU LilyPond 2.22.2 (running Guile 2.2)
> > > > Processing `O_Holy_Night.ly'
> > > > Parsing...Backtrace:
> > > > [...]
> > > > ice-9/eval.scm:159:9: Value out of range 0 to 18446744073709551615: -14
> > >
> > > Review the documentation for LSR 346.  The transformation pattern must
> > > use notes starting from middle C.  Your pattern has notes in a much
> > > lower octave, which results in a negative index.  So, you would want to
> > > say something like this:
> > >
> > > 
> > > make_bass_pattern = \defineTransform \tuplet 6/4 \fixed c' { c8( d e f g
> > > a) }
> > > 
> > >
> > > However, you can do this more efficiently, removing the redundant notes:
> > >
> > > 
> > > make_bass_pattern = \defineTransform \tuplet 6/4 \fixed c' { c8( d e f d
> > > e) } % 1 2 3 4 2 3
> > > % ...
> > > | \make_bass_pattern { g, g d b } \make_bass_pattern { b, g d b }
> > > | \make_bass_pattern { b, g d b } \make_bass_pattern { b, g d b }
> > > | \make_bass_pattern { b, g d b } \make_bass_pattern { c g e c' }
> > > % ...
> > > 
> > >
> > >
> > > -- Aaron Hill

Re: Tried to use "music box" with Lilypond 2.22.2, get lots of Scheme errors

[Kenneth Wolcott]

No, it does not support the "q' functionality, but it is still a very
cool function :-)

Thanks,
Ken

On Tue, Sep 20, 2022 at 7:36 PM Kenneth Wolcott
 wrote:
>
> HI Aaron;
>
>   Thank you very much!  Works great now.
>
>   A followup question: I don't think that this function supports the
> "q" substitution for chord repetition, does it?
>
>   I guess I'll find out :-)
>
> Thanks,
> Ken
>
> On Tue, Sep 20, 2022 at 6:15 PM Aaron Hill  wrote:
> >
> > On 2022-09-20 4:27 pm, Kenneth Wolcott wrote:
> > > Hi;
> > >
> > > Tried to use "music box" with Lilypond 2.22.2, get lots of Scheme
> > > errors.
> > >
> > > https://lsr.di.unimi.it/LSR/Search?q=music+box
> > >
> > > See attachments. I did not include my generated pdf file because it
> > > pertains to the input file prior to trying to implement the music box.
> > >
> > > Thanks,
> > > Ken Wolcott
> > >
> > > ~/bin/engrave.pl --lpv=2.22.2 --s=O_Holy_Night.ly
> > > GNU LilyPond 2.22.2 (running Guile 2.2)
> > > Processing `O_Holy_Night.ly'
> > > Parsing...Backtrace:
> > > [...]
> > > ice-9/eval.scm:159:9: Value out of range 0 to 18446744073709551615: -14
> >
> > Review the documentation for LSR 346.  The transformation pattern must
> > use notes starting from middle C.  Your pattern has notes in a much
> > lower octave, which results in a negative index.  So, you would want to
> > say something like this:
> >
> > 
> > make_bass_pattern = \defineTransform \tuplet 6/4 \fixed c' { c8( d e f g
> > a) }
> > 
> >
> > However, you can do this more efficiently, removing the redundant notes:
> >
> > 
> > make_bass_pattern = \defineTransform \tuplet 6/4 \fixed c' { c8( d e f d
> > e) } % 1 2 3 4 2 3
> > % ...
> > | \make_bass_pattern { g, g d b } \make_bass_pattern { b, g d b }
> > | \make_bass_pattern { b, g d b } \make_bass_pattern { b, g d b }
> > | \make_bass_pattern { b, g d b } \make_bass_pattern { c g e c' }
> > % ...
> > 
> >
> >
> > -- Aaron Hill

Re: Tried to use "music box" with Lilypond 2.22.2, get lots of Scheme errors

[Kenneth Wolcott]

HI Aaron;

  Thank you very much!  Works great now.

  A followup question: I don't think that this function supports the
"q" substitution for chord repetition, does it?

  I guess I'll find out :-)

Thanks,
Ken

On Tue, Sep 20, 2022 at 6:15 PM Aaron Hill  wrote:
>
> On 2022-09-20 4:27 pm, Kenneth Wolcott wrote:
> > Hi;
> >
> > Tried to use "music box" with Lilypond 2.22.2, get lots of Scheme
> > errors.
> >
> > https://lsr.di.unimi.it/LSR/Search?q=music+box
> >
> > See attachments. I did not include my generated pdf file because it
> > pertains to the input file prior to trying to implement the music box.
> >
> > Thanks,
> > Ken Wolcott
> >
> > ~/bin/engrave.pl --lpv=2.22.2 --s=O_Holy_Night.ly
> > GNU LilyPond 2.22.2 (running Guile 2.2)
> > Processing `O_Holy_Night.ly'
> > Parsing...Backtrace:
> > [...]
> > ice-9/eval.scm:159:9: Value out of range 0 to 18446744073709551615: -14
>
> Review the documentation for LSR 346.  The transformation pattern must
> use notes starting from middle C.  Your pattern has notes in a much
> lower octave, which results in a negative index.  So, you would want to
> say something like this:
>
> 
> make_bass_pattern = \defineTransform \tuplet 6/4 \fixed c' { c8( d e f g
> a) }
> 
>
> However, you can do this more efficiently, removing the redundant notes:
>
> 
> make_bass_pattern = \defineTransform \tuplet 6/4 \fixed c' { c8( d e f d
> e) } % 1 2 3 4 2 3
> % ...
> | \make_bass_pattern { g, g d b } \make_bass_pattern { b, g d b }
> | \make_bass_pattern { b, g d b } \make_bass_pattern { b, g d b }
> | \make_bass_pattern { b, g d b } \make_bass_pattern { c g e c' }
> % ...
> 
>
>
> -- Aaron Hill

Tried to use "music box" with Lilypond 2.22.2, get lots of Scheme errors

[Kenneth Wolcott]

Hi;

Tried to use "music box" with Lilypond 2.22.2, get lots of Scheme errors.

https://lsr.di.unimi.it/LSR/Search?q=music+box

See attachments. I did not include my generated pdf file because it
pertains to the input file prior to trying to implement the music box.

Thanks,
Ken Wolcott

~/bin/engrave.pl --lpv=2.22.2 --s=O_Holy_Night.ly
GNU LilyPond 2.22.2 (running Guile 2.2)
Processing `O_Holy_Night.ly'
Parsing...Backtrace:
  15 (apply-smob/1 #)
In ice-9/eval.scm:
   293:34 14 (_ #(#(#) #))
619:8 13 (_ #(#(#(#(#(#(#) …) …) …) …) …))
In srfi/srfi-1.scm:
640:9 12 (for-each # …)
In ice-9/eval.scm:
619:8 11 (_ #(#(#(#(# #f # …) …) …) …))
In ice-9/boot-9.scm:
829:9 10 (catch _ _ # …)
In unknown file:
   9 (ly:parse-file "O_Holy_Night.ly")
In ice-9/eval.scm:
   293:34  8 (_ #(#(#(#(#(#) …) …) …) …))
619:8  7 (_ #(#(#(# #) #) #(# …) #))
619:8  6 (_ #(#(#(# # …) …) …))
619:8  5 (_ #(#(#(# # …) …) …))
In srfi/srfi-1.scm:
640:9  4 (for-each # (# # # # # # #))
In ice-9/eval.scm:
259:9  3 (_ #(#(# # …) …))
619:8  2 (_ #(#(#(# #(# # …)) #) #))
   202:51  1 (_ #(#(#(# #(# # …)) #) #))
159:9  0 (_ #(#(#(# #(# # …)) #) #))

ice-9/eval.scm:159:9: Value out of range 0 to 18446744073709551615: -14


O_Holy_Night_arranged_for_Piano.pdf
Description: Adobe PDF document


define_transform.ily
Description: Binary data


O_Holy_Night.ly
Description: Binary data

Re: Raise the "Fine" and "D.C. Fine" above the repeat volta alternative brackets, how?

[Kenneth Wolcott]

HI Jean;

  Now it finally starts to make sense!

Thanks,
Ken

On Mon, Sep 19, 2022 at 6:30 PM Jean Abou Samra  wrote:
>
> Le 20/09/2022 à 02:45, Kenneth Wolcott a écrit :
> > HI David;
> >
> >Thank you.
> >
> >What is "\rightjust"? Is it a variable (macro) that you have
> > defined? I can't find that command in the NR.
>
>
>
> I suppose David defined it as something like
>
> rightjust = \tweak self-alignment-X #RIGHT \etc
>
>
> The alignment of a mark is defined by self-alignment-X. #RIGHT
> specifies to align on the right side.
>
>
> > How does that differ
> > from right-align, which I tried and it didn't work for me.
>
>
>
> Trying to use alignment markup commands like \left-align, \center-align,
> \right-align, \general-align, \halign, etc. for aligning marks, text
> scripts or other textual objects is a mistake I have seen quite a number
> of people doing. I wonder if the manual should be explicitly warning against
> it, but it's difficult to know in which section to put it, since it can
> occur in many different contexts.
>
> The problem with `\mark \markup \right-align Fine` is that \right-align
> acts on the text that \mark prints as a RehearsalMark grob, but the
> RehearsalMark
> grob also realigns itself. For simplicity, let's assume rehearsal marks are
> always centered by default (it's more complex but this is illustrative).
> When you write "Fine", this makes a markup, and when this markup is
> interpreted,
> it has a certain width, say, '(0 . 4), which means from point 0 horizontally
> to point 4 (in a certain unit defined by LilyPond). To ensure the centering,
> the RehearsalMark grob will move itself by 2 units on the left so that
> this extent becomes '(-2 . 2). By using \right-align, you translate the
> Fine text in the initial step so its extent is '(-4 . 0), but the centering
> step still happens, and recenters at '(-2 . 2).
>
> Here is a little visualization. The red X indicates the X coordinate 0
> in the Fine markup. As you can see, \right-align does move the Fine text
> relative to this X, but the X also gets moved relative to the bar line,
> which cancels the effect.
>
>
> {
>c'1
>\mark \markup \combine
>  Fine % also try \right-align Fine
>  \with-outline \stencil #empty-stencil \fontsize #-5 \with-color
> "red" ×
> }
>
>
> So, instead of \right-align, you need to tweak self-alignment-X, which
> modifies the realignment step to suit your desired alignment. I hope
> that was clear.
>
>

Re: Raise the "Fine" and "D.C. Fine" above the repeat volta alternative brackets, how?

[Kenneth Wolcott]

HI David;

  Thank you.

  What is "\rightjust"? Is it a variable (macro) that you have
defined?  I can't find that command in the NR.  How does that differ
from right-align, which I tried and it didn't work for me.

Thanks,
Ken

On Mon, Sep 19, 2022 at 5:23 PM David Wright  wrote:
>
> On Mon 19 Sep 2022 at 16:28:35 (-0700), Kenneth Wolcott wrote:
>
> >   I have implemented the "Fine" and "D.C. al Fine" as rehearsal mark 
> > markups.
> >
> >   Now I have a problem where the "D.C. al Fine" consumes much more
> > space than the bar containing the dotted-half note, it even falls off
> > the right side of the page.
> >
> >   How does one expand the bar enough to contain the markup instead of
> > modifying the markup to fit the bar?
>
> Right justification is usual:
>
> global = {
>   \key c \major
>   \time 4/4
>   s1 * 4
>   \rightjust \mark \markup{ \smallCaps "Fine"}
>   \bar "|."
>   s1 * 10
>   \bar "||"
>   s1 * 10
>   \bar "||"
>   s1 * 9
>   \bar "||"
>   \rightjust \mark \markup{ "D.C. al Fine"}
> }
>
> Cheers,
> David.

Re: Raise the "Fine" and "D.C. Fine" above the repeat volta alternative brackets, how?

[Kenneth Wolcott]

HI Valentin;

  Thank you for elaboration.

  I have implemented the "Fine" and "D.C. al Fine" as rehearsal mark markups.

  Now I have a problem where the "D.C. al Fine" consumes much more
space than the bar containing the dotted-half note, it even falls off
the right side of the page.

  How does one expand the bar enough to contain the markup instead of
modifying the markup to fit the bar?

Thanks,
Ken

On Mon, Sep 19, 2022 at 9:07 AM Valentin Petzel  wrote:
>
> Hi Ken,
>
> Lilypond has so called engravers at various levels that handle placement of
> stuff. If you do ^"some text" a so called TextScript event is created, which 
> is
> handled by an engraver at Staff level. The voltas on the other hand are 
> created
> by an engraver at Score level. Other events that are handled on score level
> are marks, so prior to Lilypond 23.6 (? I think this is where the new repeat
> segno stuff came) I’d use a RehearsalMark for these kinds of things (this also
> allows us to align the text to the end of the measure instead of a note).
>
> The new repeat segno stuff does create Marks and Stuff on Score level.
>
> Cheers,
> Valentin
>
> Am Sonntag, 18. September 2022, 21:59:04 CEST schrieb Kenneth Wolcott:
> > Hi Valentin;
> >
> >   Thank you.
> >
> >   Regarding point #1, I don't understand what (how to) to change it so
> > that it is Score level.  Would I place the same command inside the
> > \layout {} block inside the \score section?  Do I invoke it in the
> > same way?
> >
> >   Regarding point #2, I'm still trying to understand the new repeat
> > features, so I'm putting that off for now.
> >
> > Thanks,
> > Ken
> >
> > On Sun, Sep 18, 2022 at 11:04 AM Valentin Petzel  wrote:
> > > Hi Ken,
> > >
> > > note that it would be reasonable to create these Marks on a Score level,
> > > not on a Staff level.
> > >
> > > If you are using a sufficiently recent development version you can also
> > > make use of the \repeat segno function, somewhat like this:
> > >
> > > \version "2.23.12"
> > >
> > > \layout {
> > >
> > >   \context {
> > >
> > > \Score
> > > \override JumpScript.direction = #UP
> > >
> > >   }
> > >
> > > }
> > >
> > > \new PianoStaff <<
> > >
> > >   \new Staff s1*6
> > >   \new Staff {
> > >
> > > \repeat segno 2 {
> > >
> > >   \repeat volta 2 {
> > >
> > > c'4 d' e' f'
> > > \alternative {
> > >
> > >   { g'2 f' } { g'1 \fine }
> > >
> > > }
> > >
> > >   }
> > >   \repeat volta 2 {
> > >
> > > c'4 d' e' f'
> > > \alternative {
> > >
> > >   { g'2 f' } { g'1 }
> > >
> > > }
> > >
> > >   }
> > >
> > > }
> > >
> > >   }
> > >
> > > (note how although the marks are defined in the lower Staff they are
> > > displayed above the upper one, since they are created on a Score level).
> > >
> > > Cheers,
> > > Valentin
> > >
> > > Am Sonntag, 18. September 2022, 19:00:23 CEST schrieb Kenneth Wolcott:
> > > > Hi Knute;
> > > >
> > > >   Thank you for reminding me to share :-)
> > > >
> > > >   I did not find a precise search phrase that I should have used but
> > > >
> > > > "Controlling the vertical ordering of scripts" in the Notation
> > > > Reference comes close; reading the entire section helped.
> > > >
> > > >   What I saw there reminded me of what I had been shown before, so I
> > > >
> > > > looked in my previous engravings and I found what I needed.
> > > >
> > > >   Here is my markup command that I had used previously but could not
> > > >
> > > > remember how to search for it:
> > > >
> > > > fine = -\tweak outside-staff-priority #605 ^\markup { \fontsize #3
> > > > "Fine" }
> > > >
> > > >   So I was able to solve my problem, but I still don't have a precise
> > > >
> > > > search phrase that results in information that more closely matches
> > > > that which I had been shown to me on this mailing list previously.
> > > >
> > > >
> > > > Thanks,
> > > > Ken
> > > >
> > > > On Sun, Sep 18, 2022 at 6:29 AM Knute Snortum 
> wrote:
> > > > > On Sat, Sep 17, 2022 at 9:36 PM Kenneth Wolcott
> > > > >
> > > > >  wrote:
> > > > > > HI;
> > > > > >
> > > > > >   I found what I was looking for; sorry to waste your time...
> > > > >
> > > > > Why not share what you found so others can learn from it?
> > > > >
> > > > >
> > > > > --
> > > > > Knute Snortum
>

Re: Raise the "Fine" and "D.C. Fine" above the repeat volta alternative brackets, how?

[Kenneth Wolcott]

Hi Valentin;

  Thank you.

  Regarding point #1, I don't understand what (how to) to change it so
that it is Score level.  Would I place the same command inside the
\layout {} block inside the \score section?  Do I invoke it in the
same way?

  Regarding point #2, I'm still trying to understand the new repeat
features, so I'm putting that off for now.

Thanks,
Ken


On Sun, Sep 18, 2022 at 11:04 AM Valentin Petzel  wrote:
>
> Hi Ken,
>
> note that it would be reasonable to create these Marks on a Score level, not
> on a Staff level.
>
> If you are using a sufficiently recent development version you can also make 
> use
> of the \repeat segno function, somewhat like this:
>
> \version "2.23.12"
>
> \layout {
>   \context {
> \Score
> \override JumpScript.direction = #UP
>   }
> }
>
> \new PianoStaff <<
>   \new Staff s1*6
>   \new Staff {
> \repeat segno 2 {
>   \repeat volta 2 {
> c'4 d' e' f'
> \alternative {
>   { g'2 f' } { g'1 \fine }
> }
>   }
>   \repeat volta 2 {
> c'4 d' e' f'
> \alternative {
>   { g'2 f' } { g'1 }
> }
>   }
> }
>   }
> >>
>
> (note how although the marks are defined in the lower Staff they are displayed
> above the upper one, since they are created on a Score level).
>
> Cheers,
> Valentin
>
> Am Sonntag, 18. September 2022, 19:00:23 CEST schrieb Kenneth Wolcott:
> > Hi Knute;
> >
> >   Thank you for reminding me to share :-)
> >
> >   I did not find a precise search phrase that I should have used but
> > "Controlling the vertical ordering of scripts" in the Notation
> > Reference comes close; reading the entire section helped.
> >
> >   What I saw there reminded me of what I had been shown before, so I
> > looked in my previous engravings and I found what I needed.
> >
> >   Here is my markup command that I had used previously but could not
> > remember how to search for it:
> >
> > fine = -\tweak outside-staff-priority #605 ^\markup { \fontsize #3 "Fine" }
> >
> >   So I was able to solve my problem, but I still don't have a precise
> > search phrase that results in information that more closely matches
> > that which I had been shown to me on this mailing list previously.
> >
> >
> > Thanks,
> > Ken
> >
> > On Sun, Sep 18, 2022 at 6:29 AM Knute Snortum  wrote:
> > > On Sat, Sep 17, 2022 at 9:36 PM Kenneth Wolcott
> > >
> > >  wrote:
> > > > HI;
> > > >
> > > >   I found what I was looking for; sorry to waste your time...
> > >
> > > Why not share what you found so others can learn from it?
> > >
> > >
> > > --
> > > Knute Snortum
>

Re: Extended bar checking?

[Kenneth Wolcott]

Thanks for mentioning this.  I too have encountered this problem.

Ken Wolcott

On Sun, Sep 18, 2022 at 11:33 AM Mats Bengtsson
 wrote:
>
> Hi,
>
> I've been pondering about a missing feature in LilyPond, namely the 
> possibility to get a warning printout if there isn't an explicit bar check 
> ("|") in the input file at the end of each measure. This would catch many of 
> the typos I personally do when entering music, where I happen to forget to 
> change a duration, or enter the wrong duration, so that the current default 
> duration happens to be, say, double the correct duration.
>
> Example: Let's say I want to type
>
> \relative c' {
> c4 d e2 |
> g1 |
> g4 f e d |
> c1
> }
> but forget to add the duration "4" in the third measure:\relative c' {
> c4 d e2 |
> g1 |
> g f e d |
> c1
> }
> Obviously, this will not give any bar check warning, but if there was a 
> possibility to get a warning also for missing bar checks, I would immediately 
> catch those mistakes. This feature should not be on by default, but for those 
> of us who consequently add bar checks in the input files, it would be 
> extremely helpful.
>
> In another email thread today, Valentine provided an implementation of a 
> Bar_check_warning_egraver is somewhat along the same lines, but that 
> unfortunatly fails to catch the typo in the above example since it only 
> detects notes  where the duration crosses a bar line. As far as I can see, 
> the idea of Valentine's implementation cannot easily be extended to do what 
> I'm after and it's not immediately obvious to me how hard it would be to 
> implement it. Perhaps some of you clever LilyPond hackers on the list have an 
> idea, otherwise I will send it as a feature request to the bug list.
>
>/Mats

Re: Raise the "Fine" and "D.C. Fine" above the repeat volta alternative brackets, how?

[Kenneth Wolcott]

Hi Knute;

  Thank you for reminding me to share :-)

  I did not find a precise search phrase that I should have used but
"Controlling the vertical ordering of scripts" in the Notation
Reference comes close; reading the entire section helped.

  What I saw there reminded me of what I had been shown before, so I
looked in my previous engravings and I found what I needed.

  Here is my markup command that I had used previously but could not
remember how to search for it:

fine = -\tweak outside-staff-priority #605 ^\markup { \fontsize #3 "Fine" }

  So I was able to solve my problem, but I still don't have a precise
search phrase that results in information that more closely matches
that which I had been shown to me on this mailing list previously.


Thanks,
Ken



On Sun, Sep 18, 2022 at 6:29 AM Knute Snortum  wrote:
>
> On Sat, Sep 17, 2022 at 9:36 PM Kenneth Wolcott
>  wrote:
> >
> > HI;
> >
> >   I found what I was looking for; sorry to waste your time...
>
> Why not share what you found so others can learn from it?
>
>
> --
> Knute Snortum

Re: Raise the "Fine" and "D.C. Fine" above the repeat volta alternative brackets, how?

[Kenneth Wolcott]

HI;

  I found what I was looking for; sorry to waste your time...

Ken

On Sat, Sep 17, 2022 at 9:06 PM Kenneth Wolcott
 wrote:
>
> Hi;
>
>   Raise the "Fine" and "D.C. Fine" above the repeat volta alternative
> brackets, how?
>
>   Please give me good search words so that I can find how to do this
> in the Lilypond documentation.
>
>   Please see attached files.
>
> Thanks,
> Ken Wolcott

Re: How to engrave this (screenshot attached) 12/8 time (looks like an arpeggio with ties)

[Kenneth Wolcott]

Thank you!

On Fri, Sep 16, 2022 at 10:12 PM Werner LEMBERG  wrote:
>
>
> > How to engrave this (screenshot attached) 12/8 time (looks like an
> > arpeggio with ties)
>
> Exactly.  Look up the Notation Reference Index under 'arpeggio and
> ties'...
>
>
> Werner

Re: is this a slashed grace?

[Kenneth Wolcott]

Hi David;

  It is amazingly sad that I read right past that warning.

Thanks,
Ken

On Thu, Sep 15, 2022 at 10:07 PM David Wright  wrote:
>
> Kenneth Wolcott wrote:
> > >   I asked this question regarding a different piece that I was engraving. 
> > >  It looks like the slashed grace as shown in the Lilypond documentation 
> > > is not the same as what I have engraved (there is no slash).
> > >   Now another piece has come up with the same question.
> > >   Maybe these aren't slashed grace notes?  Maybe (as usual) I'm doing 
> > > something wrong?
> > >   My input, my engraving and the origin I'm reading from are attached.
>
> Mark Stephen Mrotek wrote:
> > > Are you referring to the ornaments is measures 3, 11, and 25?
>
> Kenneth Wolcott wrote:
> > That's correct.
>
> https://lilypond.org/doc/v2.22/Documentation/notation/special-rhythmic-concerns
>
> Scroll down to:
>
>   Known issues and warnings
>
>   A multi-note beamed acciaccatura is printed without a slash,
>   and looks exactly the same as a multi-note beamed appoggiatura.
>
> Cheers,
> David.

Re: is this a slashed grace?

[Kenneth Wolcott]

That's correct.

On Thu, Sep 15, 2022 at 8:56 PM Mark Stephen Mrotek
 wrote:
>
> Kenneth,
>
> Are you referring to the ornaments is measures 3, 11, and 25?
>
>
>
> MArk
>
>
>
> From: lilypond-user 
> [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of 
> Kenneth Wolcott
> Sent: Thursday, September 15, 2022 7:58 PM
> To: Andrew Bernard 
> Cc: lilypond-user@gnu.org
> Subject: Re: is this a slashed grace?
>
>
>
> Hi Andrew;
>
>
>
>   I asked this question regarding a different piece that I was engraving.  It 
> looks like the slashed grace as shown in the Lilypond documentation is not 
> the same as what I have engraved (there is no slash).
>
>
>
>   Now another piece has come up with the same question.
>
>
>
>   Maybe these aren't slashed grace notes?  Maybe (as usual) I'm doing 
> something wrong?
>
>
>
>   My input, my engraving and the origin I'm reading from are attached.
>
>
>
> Thanks,
>
> Ken Wolcott
>
>
>
>
>
> On Wed, Aug 24, 2022 at 8:44 PM Kenneth Wolcott  
> wrote:
>
> That's all I want to know, thanks!
>
>
>
> On Wed, Aug 24, 2022 at 8:36 PM Andrew Bernard  
> wrote:
>
> Yes.
>
> What is the problem?
>
> On 25/08/2022 12:35 pm, Kenneth Wolcott wrote:
> > Is this a slashed grace? See attached screenshot.
> >

Re: How to enlarge the entire Lilypond output (pdf)

[Kenneth Wolcott]

Hi Knute;

  Thank you. It may seem obvious but I wasn't sure if that would also
change the notes and other aspects as well.

  I will experiment with this and see if she likes the new output better.

Thanks,
Ken

On Thu, Sep 15, 2022 at 5:03 PM Knute Snortum  wrote:

> On Thu, Sep 15, 2022 at 4:50 PM Kenneth Wolcott
>  wrote:
> >
> > Hi;
> >
> >   Perhaps I'm not searching the Lilypond documentation wisely, but I do
> not see a way to enlarge the entire Lilypond output in scale (staff, notes,
> text, everything).
> >
> >   Perhaps I have to modify the pdf itself?  If so, does that decrease
> the clarity/precision of the presentation?
> >
> >   I'd like to control this globally, and, preferably, externally.
> >
> >   My wife is trying to use the Lilypond pdf that I generate on her iPad
> and sometimes she tries to resize (enlarge) it and that fails.
> >
> > Thanks,
> > Ken
>
> I think you can do this by manipulating the staff size:
>
>
> https://lilypond.org/doc/v2.23/Documentation/notation/setting-the-staff-size
>

How to enlarge the entire Lilypond output (pdf)

[Kenneth Wolcott]

Hi;

  Perhaps I'm not searching the Lilypond documentation wisely, but I do not
see a way to enlarge the entire Lilypond output in scale (staff, notes,
text, everything).

  Perhaps I have to modify the pdf itself?  If so, does that decrease the
clarity/precision of the presentation?

  I'd like to control this globally, and, preferably, externally.

  My wife is trying to use the Lilypond pdf that I generate on her iPad and
sometimes she tries to resize (enlarge) it and that fails.

Thanks,
Ken

Re: Hairpins can continue around line breaks but not page breaks?

[Kenneth Wolcott]

HI Jean;

  Thank you.  It works now.

Ken

On Mon, Sep 12, 2022 at 8:36 AM Jean Abou Samra  wrote:
>
> Le 12/09/2022 à 04:25, Kenneth Wolcott a écrit :
> > HI;
> >
> >   I have a partial crescendo hairpin followed by a forced page break
> > but the hairpin silently vanishes on the following page.  Is this a
> > known bug or am I doing something stupid?  At this point I can go with
> > the forced line breaks of the original arranger resulting in 6
> > cramped systems on one page followed by the last (and only) system on
> > the following page and still have the hairpin wrap around the line break.
> >
> >   If what I am stating is not obvious, I can provide screenshots.
>
>
> Better than that: please provide LilyPond code. It's very hard to
> diagnose problems otherwise. Cf. https://lilypond.org/tiny-examples.html
>
>
> The only case I know of where LilyPond will remove the hairpin on the
> next system is if it ends on the first note of that system, e.g.
>
> \version "2.22.2"
>
> {
>c'1\< \break c'1\!
> }
>
>
> in which case you can apply the technique from
> https://lsr.di.unimi.it/LSR/Item?id=804 as Andrew said to show it
> nevertheless:
>
> \version "2.22.2"
>
> {
>\override Hairpin.after-line-breaking = ##t
>\override Hairpin.to-barline = ##f
>c'1\< \break c'1\!
> }
>
>
> Jean
>

Re: Hairpins can continue around line breaks but not page breaks?

[Kenneth Wolcott]

Hi Andrew;

  Thanks, it looks like that is yet another thing that I have to put
into the "can't grok now, study it and try it again later" pile of
Lilypond features. **SIGH**

Ken

On Sun, Sep 11, 2022 at 8:20 PM Andrew Bernard
 wrote:
>
> It's LSR 804. I do this all the time.
>
> [I confess I have not checked this moment re page breaking.]
>
>
> Andrew
>
>
>

Re: Hairpins can continue around line breaks but not page breaks?

[Kenneth Wolcott]

Hi Kieren;

  Yeah, I didn't state my question as precisely as I meant to.

  This arranger uses the mixture of styles **in the same action**
(what is a better way to state this?)

  I think it is fine to use text the first time, then use a hairpin
for the next time, etc; but these are distinct actions.

  Anyway, I was able to get the hairpin to work if I disabled the
forced line break and the forced page break.

  I tried fiddling around with "\override Hairpin.to-barline = ##f"
from "Controlling spanner visibility after a line break" in the
Snippets Reference, but apparently I don't know how to use that
properly, as it looks like a NO-OP :-)

Thanks,
Ken


On Sun, Sep 11, 2022 at 7:37 PM Kieren MacMillan
 wrote:
>
> Hi Ken,
>
> > BTW, this arranger uses a mixture of hairpins and "cresc."/"dim." which 
> > seems really silly to me.
> > Why not use only hairpins or only cresc+dim?
>
> There are lots of good reasons to use both in a single score. That being 
> said, a quick glance at the score you attached suggests the good reasons 
> aren't the ones being used here…
>
> Cheers,
> Kieren.

Re: Hairpins can continue around line breaks but not page breaks?

[Kenneth Wolcott]

Well, the hairpin doesn't continue across the forced line break either; it
silently vanishes.

BTW, this arranger uses a mixture of hairpins and "cresc."/"dim." which
seems really silly to me.

Why not use only hairpins or only cresc+dim?

Thanks,
Ken

On Sun, Sep 11, 2022 at 7:25 PM Kenneth Wolcott 
wrote:

> HI;
>
>   I have a partial crescendo hairpin followed by a forced page break but
> the hairpin silently vanishes on the following page.  Is this a known bug
> or am I doing something stupid?  At this point I can go with the forced
> line breaks of the original arranger resulting in 6 cramped systems on one
> page followed by the last (and only) system on the following page and still
> have the hairpin wrap around the line break.
>
>   If what I am stating is not obvious, I can provide screenshots.
>
> Thanks,
> Ken Wolcott
>


Chopin_Prelude_in_E_minor_Op28_Nr4_arranged_for_Piano.pdf
Description: Adobe PDF document

Hairpins can continue around line breaks but not page breaks?

[Kenneth Wolcott]

HI;

  I have a partial crescendo hairpin followed by a forced page break but
the hairpin silently vanishes on the following page.  Is this a known bug
or am I doing something stupid?  At this point I can go with the forced
line breaks of the original arranger resulting in 6 cramped systems on one
page followed by the last (and only) system on the following page and still
have the hairpin wrap around the line break.

  If what I am stating is not obvious, I can provide screenshots.

Thanks,
Ken Wolcott

Re: is this a slashed grace?

[Kenneth Wolcott]

That's all I want to know, thanks!

On Wed, Aug 24, 2022 at 8:36 PM Andrew Bernard 
wrote:

> Yes.
>
> What is the problem?
>
> On 25/08/2022 12:35 pm, Kenneth Wolcott wrote:
> > Is this a slashed grace? See attached screenshot.
> >
>
>

is this a slashed grace?

[Kenneth Wolcott]

Is this a slashed grace? See attached screenshot.

Re: completely filling a page, but not too compact, how?

[Kenneth Wolcott]

Hi Ralph, Lukas and David;

  Thank you all for your responses.

  I had no clue where to start on modifying the layout since there are
so many things to examine in the documentation regarding the layout.

  Now I can guess more effectively for the next one that needs to be
expanded/contracted.

Thanks,
Ken

On Fri, Aug 19, 2022 at 7:31 AM David Wright  wrote:
>
> On Fri 19 Aug 2022 at 09:32:45 (+0200), Lukas-Fabian Moser wrote:
> > What I didn't change: Classical convention would probably give the
> > final bar a length of only 4 (with fermata), not 1. But I wouldn't put
> > too much stock in this, I know that a crotchet final chord would
> > probably look strange, and there are plenty of counterexamples to that
> > convention.
>
> I'm used to seeing this air written in 8/4, which looks like this
> (the last note sung would be 1~4).
>
> Cheers,
> David.

Re: Why not have a Lilypond documentation set arranged as layman's Q: does LP do this?

[Kenneth Wolcott]

HI Pierre-Luc;

  This is very nice, thank you.

Ken

On Thu, Aug 18, 2022 at 12:30 PM Pierre-Luc Gauthier
 wrote:
>
> Thanks Andrew for your input. I did write a few manuals (and still do)
> for some system usage and I know how hard it can be to cover all what
> a system can do and how to do it.
>
> For the record, I learned a *lot* reading all (most) of the change logs :
>
> http://lilypond.org/doc/v2.23/Documentation/changes/
> http://lilypond.org/doc/v2.22/Documentation/changes/
> http://lilypond.org/doc/v2.20/Documentation/changes/
> http://lilypond.org/doc/v2.18/Documentation/changes/
> http://lilypond.org/doc/v2.16/Documentation/changes/new-features-in-2_002e16-since-2_002e14
> http://lilypond.org/doc/v2.14/Documentation/changes/
>
> I also read "git log -p" on a daily basis.
>
> Here are a few of my gotos might it help anyone :
>
> https://lilypond.org/doc/v2.23/Documentation/internals/all-layout-objects.html
> https://lilypond.org/doc/v2.23/Documentation/notation/lilypond-command-index
> https://lilypond.org/doc/v2.23/Documentation/notation/chord-name-chart.en.html
> https://lilypond.org/doc/v2.23/Documentation/notation/common-chord-modifiers.en.html
> http://lilypond.org/doc/v2.23/Documentation/notation/percussion-notes.html
> http://fritz.rmi.de/dokumentation/lilypond/Documentation/user/lilypond/Chords-mode.html#Chords-mode
> https://lists.gnu.org/archive/html/lilypond-user/
>
> FWIW
> --
> Pierre-Luc Gauthier

Re: Why not have a Lilypond documentation set arranged as layman's Q: does LP do this?

[Kenneth Wolcott]

Thank you, Aaron.  Yes, I found that Wikipedia entry at about the same
time that I first struggled with the tremolo.

It really comes back to being able to think and write fluently, doesn't it? :-)

Thanks to you all for your great support on this list.

Ken

On Thu, Aug 18, 2022 at 9:09 AM Aaron Hill  wrote:
>
> On 2022-08-18 8:49 am, Kenneth Wolcott wrote:
> > What even makes it more difficult is when I don't even know what
> > something is called at all (no terminology) and/or when I have no clue
> > how to succinctly describe what it is that I don't know.  For example,
> > the tremolo; I recognized the graphic but I had no way to search for
> > it by appearance, only read every line of the documentation until I
> > find it and the "ah ha".
>
> This is where I imagine the visual index is most helpful.  But I do
> wonder how often the Music Glossary is overlooked as a resource.  It
> includes pictures for entries; in this case, tremolo is represented.
> Going outside of LilyPond's manuals, Wikipedia has a good list [1].
>
> [1]: https://en.wikipedia.org/wiki/List_of_musical_symbols
>
>
> -- Aaron Hill

Re: Why not have a Lilypond documentation set arranged as layman's Q: does LP do this?

[Kenneth Wolcott]

AWESOME!

On Thu, Aug 18, 2022 at 9:14 AM Werner LEMBERG  wrote:
>
>
> > What even makes it more difficult is when I don't even know what
> > something is called at all (no terminology) and/or when I have no
> > clue how to succinctly describe what it is that I don't know.  For
> > example, the tremolo; I recognized the graphic but I had no way to
> > search for it by appearance, only read every line of the
> > documentation until I find it and the "ah ha".
>
> I think you are looking for the 'Visual LilyPond Grob Index':
>
>   https://github.com/joram-berger/visualindex
>
> This gives you the name of the grob, which you can then use for a
> search in the Notation Reference.
>
> Eventually this will become part of the LilyPond documentation.
>
>
>  Werner

Re: Why not have a Lilypond documentation set arranged as layman's Q: does LP do this?

[Kenneth Wolcott]

Thank you all for your commentary on my question.

I think there are some very nice responses here that give me some perspective.

What even makes it more difficult is when I don't even know what
something is called at all (no terminology) and/or when I have no clue
how to succinctly describe what it is that I don't know.  For example,
the tremolo; I recognized the graphic but I had no way to search for
it by appearance, only read every line of the documentation until I
find it and the "ah ha".

  I'm making no complaint about the quality of the documentation; I
think it is excellent.

In addition, the developers and those who assist on this list are
awesome people.

I need to ponder these responses further to figure out what I can do
not only to further my Lilypond education but also try to give back to
the community.

Thank you,
Ken

On Thu, Aug 18, 2022 at 6:11 AM Karlin High  wrote:
>
> On 8/18/2022 5:48 AM, Andrew Bernard wrote:
> > Every layman seems to have a
> > different 'layman's term' for things, some of which are true
> > alternatives and some of which are just plain wrong.
>
> Doing residential tech support, I will never forget the man who referred
> to the desktop background picture as "the screen saver." Or the lady,
> may she rest in peace, whose term for all forms of email was "Outlook
> Express."
>
> > I don't think, as you say, your question is dumb, and in no way intend
> > to diminish it with my comments. I just think this is what I call a
> > 'hard problem.'
>
> I agree, and appreciate the effort you put into writing that.
>
> I second Jean Abou Samra's motion for expanding the index if it seems
> good to so so.
>
> Lilypond.org is hosted on a Google service, I believe? Are there ways to
> see what search terms people use to arrive at given documentation resources?
>
> If there are recognizable patterns, like there's this one word people
> follow over and over again to a manual page mostly using unlike terms,
> maybe that could be seen as a call to add an index entry.
> --
> Karlin High
> Missouri, USA
>

Re: Why not have a Lilypond documentation set arranged as layman's Q: does LP do this?

[Kenneth Wolcott]

I do see the FAQ on the documentation page, but I think that this
needs to be expanded, in more detail, as it frequently takes too long
to find things in the existing documentation.

Maybe I just don't use the right search strings to find what I'm looking for.

On Wed, Aug 17, 2022 at 7:16 PM Kenneth Wolcott
 wrote:
>
> Hi;
>
> Dumb documentation question here:
>
> Kind of like a FAQ but also kind of like an index.
>
> So this would be a "translation" of layman's terms to
> Lilypond/professional terminology and an index; it could even point to
> existing indices (in Notation) and/or the Glossary.
>
> Q: Does Lilypond do X (layman's term/phrase)?
> A: Yes, and this is the Lilypond description/verbiage/etc...
>see Learning (precise section URL);
>see Notation  (precise section URL);
>   etc (Glossary, Snippets)
>
> Now, if I didn't have the correct terminology, I could still obtain
> what I was looking for.
>
> Also, if the grouping or categorization of the concept is not where I
> would expect it, I might not know where to find it.  A text based
> search of the HTML or PDF either does not result in any hits, or
> incorrect hits or too many hits; this is very frustrating.  The
> Lilypond documentation is EXCELLENT, but I think that this might be
> helpful for some people.
>
> Example:
>
> Q. Does Lilypond generate MIDI for articulations/ornaments (such as
> mordant, prall, arpeggios)?
> A. Yes/No; see articulate feature description.
>
> I think that this might help people who aren't high-level musicians
> and/or high-level engravers navigate the excellent Lilypond
> documentation.
>
> Now, I'd be willing to assist  with a very simple beginning of this
> Q/FAQ from a layman's perspective, perhaps on a text basis, using
> some of my own questions on this mailing list with some of the answers
> I've received.
>
> Is this a useful idea?  Is it redundant/superfluous? It looks like a
> lot of work to gather the info and implement within the documentation
> format, but I'd be willing to try to add some value in my limited
> knowledge.
>
> Thanks,
> Ken Wolcott

Why not have a Lilypond documentation set arranged as layman's Q: does LP do this?

[Kenneth Wolcott]

Hi;

Dumb documentation question here:

Kind of like a FAQ but also kind of like an index.

So this would be a "translation" of layman's terms to
Lilypond/professional terminology and an index; it could even point to
existing indices (in Notation) and/or the Glossary.

Q: Does Lilypond do X (layman's term/phrase)?
A: Yes, and this is the Lilypond description/verbiage/etc...
   see Learning (precise section URL);
   see Notation  (precise section URL);
  etc (Glossary, Snippets)

Now, if I didn't have the correct terminology, I could still obtain
what I was looking for.

Also, if the grouping or categorization of the concept is not where I
would expect it, I might not know where to find it.  A text based
search of the HTML or PDF either does not result in any hits, or
incorrect hits or too many hits; this is very frustrating.  The
Lilypond documentation is EXCELLENT, but I think that this might be
helpful for some people.

Example:

Q. Does Lilypond generate MIDI for articulations/ornaments (such as
mordant, prall, arpeggios)?
A. Yes/No; see articulate feature description.

I think that this might help people who aren't high-level musicians
and/or high-level engravers navigate the excellent Lilypond
documentation.

Now, I'd be willing to assist  with a very simple beginning of this
Q/FAQ from a layman's perspective, perhaps on a text basis, using
some of my own questions on this mailing list with some of the answers
I've received.

Is this a useful idea?  Is it redundant/superfluous? It looks like a
lot of work to gather the info and implement within the documentation
format, but I'd be willing to try to add some value in my limited
knowledge.

Thanks,
Ken Wolcott

Re: first repeat at low dynamic; next repeat at higher dynamic; how to do this for midi output?

[Kenneth Wolcott]

Thanks to you all for your forbearance with me.

Well, the answer is really obvious, of course :-)

It was pointed out to me privately that I wasn't taking advantage of
my own midi-specific variables that had the \volta implemented.

So using \rh_midi in place of \rh and  \lh_midi in place of \lh solved
the problem.

Sometimes I am totally blind and deaf to the obvious :-)

Thanks,
Ken

On Thu, Aug 11, 2022 at 3:44 PM Kenneth Wolcott
 wrote:
>
> HI Jean;
>
>   I have implemented a second version using Lilypond 2.23.22 taking
> advantage of the \volta construct.
>
>   I do not hear a difference in the dynamics during midi playback in
> the version using 2.23.11 but I do in the version using 2.22.2 where I
> split out the music into different subsections.
>
> What am I doing wrong?
>
> Please see attachments.
>
> Thanks,
> Ken
>
> On Thu, Aug 11, 2022 at 11:58 AM Jean Abou Samra  wrote:
> >
> >
> >
> > Le 11/08/2022 à 20:56, Kenneth Wolcott a écrit :
> > > HI David;
> > >
> > >I'm sorry that I'm so dense :-(
> > >
> > >I've searched the 2.22.2 documentation and I do not find a "\volta"
> > > command referenced.
> > >
> > >I'll read your reply many times, ponder it and try to figure out why
> > > I just don't get your very simple explanation, and experiment a lot,
> > > maybe I'll get it.
> >
> > You'll need a 2.23 version. \volta was added in 2.23.0.
> >
> > Best,
> > Jean
> >
> >

Re: first repeat at low dynamic; next repeat at higher dynamic; how to do this for midi output?

[Kenneth Wolcott]

HI David;

  I'm sorry that I'm so dense :-(

  I've searched the 2.22.2 documentation and I do not find a "\volta"
command referenced.

  I'll read your reply many times, ponder it and try to figure out why
I just don't get your very simple explanation, and experiment a lot,
maybe I'll get it.

Thanks,
Ken

On Thu, Aug 11, 2022 at 2:19 AM David Kastrup  wrote:
>
> Kenneth Wolcott  writes:
>
> > HI David;
> >
> >   Thank you!
> >
> >   Now what happens when I have multiple repeats with this situation?
> >
> > Ken
> >
> > On Wed, Aug 10, 2022 at 7:51 PM David Kastrup  wrote:
> >>
> >> Kenneth Wolcott  writes:
> >>
> >> > HI;
> >> >
> >> > first repeat at low dynamic; next repeat at higher dynamic; how to do
> >> > this for midi output?
> >>
> >> << \volta 1 \p
> >>\volta 2 \f
> >> >>
> >>
> >> in the \midi section should likely work.
>
> Let me rephrase: "In the score part used for generating the MIDI, namely
> the score containing a \midi output declaration."
>
> Namely, << \volta 1 \p \volta 2 \f >> is placed in the location in the
> score where you want to switch the dynamics.
>
> --
> David Kastrup

Re: first repeat at low dynamic; next repeat at higher dynamic; how to do this for midi output?

[Kenneth Wolcott]

Hi David;

  I must have misunderstood your suggestion :-(


  \midi {
\tempo 4=116
\volta 1 \p
\volta 2 \f
  }


  I'm using Lilypond 2.22.2, \volta inside \midi {} is not accepted by Lilypond:

GNU LilyPond 2.22.2 (running Guile 2.2)
Processing `Screwed_it_up.ly'
Parsing...
Screwed_it_up.ly:97:5: error: unknown escaped string: `\volta'

\volta 1 \p
Screwed_it_up.ly:97:12: error: syntax error, unexpected UNSIGNED,
expecting '.' or '='
\volta
   1 \p
Screwed_it_up.ly:98:5: error: unknown escaped string: `\volta'

\volta 2 \f
Interpreting music...[8][16]
Preprocessing graphical objects...
Interpreting music...
MIDI output to `Screwed_it_up.midi'...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Converting to `Screwed_it_up.pdf'...
fatal error: failed files: "Screwed_it_up.ly"

On Wed, Aug 10, 2022 at 8:10 PM Kenneth Wolcott
 wrote:
>
> HI David;
>
>   Thank you!
>
>   Now what happens when I have multiple repeats with this situation?
>
> Ken
>
> On Wed, Aug 10, 2022 at 7:51 PM David Kastrup  wrote:
> >
> > Kenneth Wolcott  writes:
> >
> > > HI;
> > >
> > > first repeat at low dynamic; next repeat at higher dynamic; how to do
> > > this for midi output?
> >
> > << \volta 1 \p
> >\volta 2 \f
> > >>
> >
> > in the \midi section should likely work.
> >
> > --
> > David Kastrup

Re: first repeat at low dynamic; next repeat at higher dynamic; how to do this for midi output?

[Kenneth Wolcott]

HI David;

  Thank you!

  Now what happens when I have multiple repeats with this situation?

Ken

On Wed, Aug 10, 2022 at 7:51 PM David Kastrup  wrote:
>
> Kenneth Wolcott  writes:
>
> > HI;
> >
> > first repeat at low dynamic; next repeat at higher dynamic; how to do
> > this for midi output?
>
> << \volta 1 \p
>\volta 2 \f
> >>
>
> in the \midi section should likely work.
>
> --
> David Kastrup

first repeat at low dynamic; next repeat at higher dynamic; how to do this for midi output?

[Kenneth Wolcott]

HI;

first repeat at low dynamic; next repeat at higher dynamic; how to do
this for midi output?

I thought I saw an email previously in this mailing list regarding
this subject; but I could not find it.

I think I know how to properly display a "p then f" or "p - f"
instruction at the beginning of a repeat, but how to generate the
distinct dynamic change in the midi output?  Just duplicate the
Lilypond code with the exception of the different dynamics?

  An example downloaded from 8notes.com is attached.

Thanks,
Ken Wolcott


Mozart_Minuet_from_Don_Giovanni_arranged_for_Piano.pdf
Description: Adobe PDF document

Re: How to get cross-staff beaming? Should be automatic; it's not. Why?

[Kenneth Wolcott]

Hi Mark;

  I'm sorry for the long delay in responding to you.

  I appreciate your assistance in adding manual beaming to my code to
get me started on the right path.

Thanks,
Ken

On Sun, Jul 31, 2022 at 8:45 PM Mark Stephen Mrotek
 wrote:
>
> Kenneth,
>
> The auto beaming can be overridden using   [..]. Look up "manual beaming" 
> in the docs.
> Stem direction can be changed with \stemUp and \stemDown.
> Attached is a start.
>
> Mark
>
> -Original Message-
> From: lilypond-user 
> [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of 
> Kenneth Wolcott
> Sent: Sunday, July 31, 2022 7:10 PM
> To: Lily Pond 
> Subject: How to get cross-staff beaming? Should be automatic; it's not. Why?
>
> Hi;
>
>   Making progress on the \change Staff Lilypond feature now.
>
>   However, the current incarnation of my Swan Lake harp part (one bar so 
> far), does not have a complete beam (only each triplet has a beam).
> I thought that this would be automatic.
>
>   Please see attachments.
>
> Thanks,
> Ken Wolcott