Re: Guidance on the repeated slur in \volta 2

[Volodymyr Prokopyuk]

Hello Knute,

Interesting approach! I've not seen this before. The solution gives you
precise control on the slur shape.

The problem with this approach is that it is imperative (you have to
manually specify the coordinates of control points in every situation),
quite verbose and explodes in complexity when chords are involved.

I'm looking for more declarative approach in the style of not yet existing
\repeatSlur

Thank you for your suggestion,
Vlad

On Wed, Oct 19, 2022 at 6:22 PM Knute Snortum  wrote:

> On Wed, Oct 19, 2022 at 6:59 AM Volodymyr Prokopyuk
>  wrote:
> >
> > Hello,
> >
> > Could you, please, provide guidance on how to manage the repeated slure
> in \volta 2?
> >
> > Problem
> >
> > There is no simple and convenient way to repeat a slur in \volta 2,
> while the slure from the \repeat volta 2 { body } to the \volta 1 is
> working correctly.
> >
> > Workarounds
> >
> > Use the \repeatTie in \volta 2
> >
> > Benefit: simple and convenient, works for chords in \volta 2. The not
> currently existing \repeatSlur would be an effective solution
> > Drawback: the \repeatTie is too small and looks different from the
> desired repeated slur shape
> >
> > Use a hidden grace note with automatic slure in \volta 2 E. g. \once
> hideNotes \acciaccatura { ... }
> >
> > Benefit: good control on the height of the repeated slur
> > Drawback: the hidden grace note is not part of the score, multiple grace
> notes needed to support repeated slur for chords in \volta 2
> >
> > Questions
> >
> > Does Lilypond have an appropriate solution to the repeated slur in
> \volta 2?
> > Are there a more convenient workaround different from the above
> presented workarounds that 1) draws bigger than \repeatTie slur, 2)
> supports chords without having to introduce multiple hidden grace notes?
> >
> > Thank you very much,
> > Vlad
>
> Maybe this is what you need? (scroll to the bottom)
>
> https://lilypond.org/doc/v2.21/Documentation/notation/modifying-shapes
>
> --
> Knute Snortum
>

Re: Legacy scripted installation, was Re: LilyPond 2.23.14

[David Wright]

On Wed 19 Oct 2022 at 06:46:22 (-0700), Knute Snortum wrote:
> On Tue, Oct 18, 2022 at 11:21 AM David Wright wrote:
> > On Tue 18 Oct 2022 at 05:15:31 (-0400), Craig Bakalian wrote:
> > >
> > > And could we please release the latest greatest lilypond as a shell
> > > script like it used to be released.
> >
> > You seemed to be happy enough when you wrote
> > https://lists.gnu.org/archive/html/lilypond-user/2022-09/msg00071.html
> >
> > Can you tell us what has changed. Is it the shell script itself that
> > you miss, or the attempt to download the documentation, or the
> > uninstall script? Unless you tell us what you miss, there's not much
> > more that can be done except to say "Ain't gonna happen", aka WONTFIX.
> 
> I'll jump in here if it's all right.  Craig, did you notice that
> there's an installation[1] page that you can get to from the download
> page?  I missed that at first.  The command-line installation
> instructions are rather terse, but I guess the assumption is that if
> you're using the command-line, you know how to run tar, mv directories
> around, add things to the PATH, etc.  But is that a good assumption?

(Disclaimer: I'm speaking only to the linux version.)

The stable version seems to get this right:
  http://lilypond.org/
  http://lilypond.org/download.html
  http://lilypond.org/unix.html
and here we get instructions for using the old script
method to install a downloaded version of LilyPond.

The unstable version seems in need of some tweaking:
  http://lilypond.org/
  http://lilypond.org/development.html
and here we see:

  Instructions for git and compiling are in the Contributor’s Guide.
lilypond git repository
  Documentation writers and testers will generally want to download the latest 
binary:
GNU/Linux x86_64: LilyPond 2.23.14
[ … ]
  If you are unsure about how to install these binaries,
  please read the start of the Learning manual.

Conventional wisdom is that development versions are for more than
just documentation writers and testers. But even sophisticated LP
users might be unsure about how to deal with a .tar.gz file. So
I would at least move the last paragraph to before the download
links, though an alternative would be to copy stable's approach
and make the "GNU/Linux x86_64: LilyPond 2.23.14" link open its
own unix-only page.

I would collect the git, compiling and Source information together,
and place it at the end of the Download panel, out of the way for
the great majority of users. (Accidentally unpacking the source
could be very confusing, as its top-level directory has the same
name as the binary's.)

Moving on to:
  http://lilypond.org/doc/v2.23/Documentation/learning/index.html
itself. For a graphical setup:
  
http://lilypond.org/doc/v2.23/Documentation/learning/graphical-setup-under-gnu_002flinux
the instructions are interesting as they rely on a distribution's
versions of LP and Fresco in the first place, before tackling
the addition of a development version. But not running a DE, I'm
not really qualified to comment further.

For running LP from the command-line:
  http://lilypond.org/doc/v2.23/Documentation/learning/command-line-setup
you get the following:

  1.4 Command line setup

  On many GNU/Linux distributions, LilyPond can be installed from
  the package manager. This is also the case on macOS using either
  MacPorts or Homebrew.

  In any case, you can install LilyPond by downloading the archive
  from Download and unpacking it. The binaries are usable
  immediately after unpacking. You can run

/.../lilypond-x.y.z/bin/lilypond file.ly

  (on Windows, replace the slashes ‘/’ with backslashes ‘\’).

The first sentence seems odd: I presume that package managers can only
install distributions' versions (eg Debian can install .debs, or rpms
etc converted by alien), and they're unlikely to comprise the latest
development version. And "In any case" seems an odd way to introduce
the reason that most people will visit the page in the first place;
kind of "well, you're here now, so you might as well know that …).

Wouldn't it be better to write first about what to do with a .tar.gz
binary. For a typical single user, suggest they unpack it in their
home directory, with   tar xf …/lilypond-N.N.N-linux-x86_64.tar.gz
(or tar xvf to see the filenames as they're unpacked).¹ The top-level
directory can then be moved/renamed as desired, without the
side-effects that might have happened in the past with the old
script method.

Perhaps also suggest that someone installing LP for all the users on
a system should unpack it as root in a directory like /usr/local/bin/
or /opt/, or as recommended by their distribution or tradition.

It might also be fair to refer to the https://frescobaldi.org/download
page for those who want to run LP from Fresco but still by way of a
terminal's command line.

I don't know how much any of this applies to command line Windows
and Macs, but I guess the OP might like to comment on whether
such changes might have he

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: Guidance on the repeated slur in \volta 2

[Knute Snortum]

On Wed, Oct 19, 2022 at 6:59 AM Volodymyr Prokopyuk
 wrote:
>
> Hello,
>
> Could you, please, provide guidance on how to manage the repeated slure in 
> \volta 2?
>
> Problem
>
> There is no simple and convenient way to repeat a slur in \volta 2, while the 
> slure from the \repeat volta 2 { body } to the \volta 1 is working correctly.
>
> Workarounds
>
> Use the \repeatTie in \volta 2
>
> Benefit: simple and convenient, works for chords in \volta 2. The not 
> currently existing \repeatSlur would be an effective solution
> Drawback: the \repeatTie is too small and looks different from the desired 
> repeated slur shape
>
> Use a hidden grace note with automatic slure in \volta 2 E. g. \once 
> hideNotes \acciaccatura { ... }
>
> Benefit: good control on the height of the repeated slur
> Drawback: the hidden grace note is not part of the score, multiple grace 
> notes needed to support repeated slur for chords in \volta 2
>
> Questions
>
> Does Lilypond have an appropriate solution to the repeated slur in \volta 2?
> Are there a more convenient workaround different from the above presented 
> workarounds that 1) draws bigger than \repeatTie slur, 2) supports chords 
> without having to introduce multiple hidden grace notes?
>
> Thank you very much,
> Vlad

Maybe this is what you need? (scroll to the bottom)

https://lilypond.org/doc/v2.21/Documentation/notation/modifying-shapes

--
Knute Snortum

Guidance on the repeated slur in \volta 2

[Volodymyr Prokopyuk]

Hello,

Could you, please, provide guidance on how to manage the repeated
slure in \volta
2?

*Problem*

There is no simple and convenient way to repeat a slur in \volta 2, while
the slure from the \repeat volta 2 { body } to the \volta 1 is working
correctly.

*Workarounds*

   - Use the \repeatTie in \volta 2
  - Benefit: simple and convenient, works for chords in \volta 2. The
  not currently existing \repeatSlur would be an effective solution
  - Drawback: the \repeatTie is too small and looks different from the
  desired repeated slur shape
  - Use a hidden grace note with automatic slure in \volta 2 E. g. \once
   hideNotes \acciaccatura { ... }
  - Benefit: good control on the height of the repeated slur
  - Drawback: the hidden grace note is not part of the score, multiple
  grace notes needed to support repeated slur for chords in \volta 2

*Questions*

   - Does Lilypond have an appropriate solution to the repeated slur in \volta
   2?
   - Are there a more convenient workaround different from the above
   presented workarounds that 1) draws bigger than \repeatTie slur, 2)
   supports chords without having to introduce multiple hidden grace notes?

Thank you very much,
Vlad

Re: Legacy scripted installation, was Re: LilyPond 2.23.14

[Knute Snortum]

On Tue, Oct 18, 2022 at 11:21 AM David Wright  wrote:
>
> On Tue 18 Oct 2022 at 05:15:31 (-0400), Craig Bakalian wrote:
> >
> > And could we please release the latest greatest lilypond as a shell
> > script like it used to be released.
>
> You seemed to be happy enough when you wrote
> https://lists.gnu.org/archive/html/lilypond-user/2022-09/msg00071.html
>
> Can you tell us what has changed. Is it the shell script itself that
> you miss, or the attempt to download the documentation, or the
> uninstall script? Unless you tell us what you miss, there's not much
> more that can be done except to say "Ain't gonna happen", aka WONTFIX.
>
> Cheers,
> David.
>

I'll jump in here if it's all right.  Craig, did you notice that
there's an installation[1] page that you can get to from the download
page?  I missed that at first.  The command-line installation
instructions are rather terse, but I guess the assumption is that if
you're using the command-line, you know how to run tar, mv directories
around, add things to the PATH, etc.  But is that a good assumption?

I do think the tarball could benefit from having a README file with
even just this text:

"Installation instructions can be found at
https://lilypond.org/doc/v2.23/Documentation/learning/installing.";

...or even the text from the command-line instructions.

[1] https://lilypond.org/doc/v2.23/Documentation/learning/installing

--
Knute Snortum

Re: Add extra space before key cancellation and a new key signature

[Volodymyr Prokopyuk]

Hi Jean,

Thank you very much for your help! I really appreciate the quick response
and useful content!

Thank you,
Vlad

On Wed, Oct 19, 2022 at 12:58 PM Jean Abou Samra  wrote:

>
>
> Le 19/10/2022 à 12:42, Volodymyr Prokopyuk a écrit :
> > Hi,
> >
> > Could you please help me with the below situation?
> >
> > *Context*
> >
> > I've changed the order of key cancellation and a new key signature to
> > be placed before the bar line with the following code
> >
> > keyChangeBeforeBar = \once \override
> > Score.BreakAlignment.break-align-orders =
> >   #(make-vector 3 '(
> >  left-edge
> >  staff-ellipsis
> >  cue-end-clef
> >  ambitus
> >  breathing-sign
> >  signum-repetitionis
> >  clef
> >  cue-clef
> >  key-cancellation
> >  key-signature
> >  staff-bar
> >  time-signature
> >  custos))
> >
> > Now I use \keyChangeBeforeBar \key g \major to change the key at the
> > end of the score with the below result
> >
> >
> > *Problem*
> > The key cancellation and a new key signature are *too close to the
> > last note* g'.
> >
> > *Question*
> > How can I *add extra space before the key cancellation* and a new key
> > signature?
> >
> > I tried a few options following the documentation but with no luck.
>
>
>
> \version "2.23.14"
>
> keyChangeBeforeBar =
>\once \override Score.BreakAlignment.break-align-orders =
>#(make-vector 3 '(
>   left-edge
>   staff-ellipsis
>   cue-end-clef
>   ambitus
>   breathing-sign
>   signum-repetitionis
>   clef
>   cue-clef
>   key-cancellation
>   key-signature
>   staff-bar
>   time-signature
>   custos))
>
> \fixed c' {
>\key g \minor
>s2 b16 a g fis g4
>\keyChangeBeforeBar
>\once \override Staff.KeyCancellation.extra-spacing-width = #'(-2 . 0)
>\key g \major
> }
>
>
>
> Have a look at this page:
>
> https://lilypond.org/doc/v2.23/Documentation/notation/spacing-between-adjacent-columns.html
>
> Best,
> Jean
>
>

Re: Add extra space before key cancellation and a new key signature

[Jean Abou Samra]

Le 19/10/2022 à 12:42, Volodymyr Prokopyuk a écrit :

Hi,

Could you please help me with the below situation?

*Context*

I've changed the order of key cancellation and a new key signature to 
be placed before the bar line with the following code


keyChangeBeforeBar = \once \override 
Score.BreakAlignment.break-align-orders =

  #(make-vector 3 '(
     left-edge
     staff-ellipsis
     cue-end-clef
     ambitus
     breathing-sign
     signum-repetitionis
     clef
     cue-clef
     key-cancellation
     key-signature
     staff-bar
     time-signature
     custos))

Now I use \keyChangeBeforeBar \key g \major to change the key at the 
end of the score with the below result



*Problem*
The key cancellation and a new key signature are *too close to the 
last note* g'.


*Question*
How can I *add extra space before the key cancellation* and a new key 
signature?


I tried a few options following the documentation but with no luck.




\version "2.23.14"

keyChangeBeforeBar =
  \once \override Score.BreakAlignment.break-align-orders =
  #(make-vector 3 '(
 left-edge
 staff-ellipsis
 cue-end-clef
 ambitus
 breathing-sign
 signum-repetitionis
 clef
 cue-clef
 key-cancellation
 key-signature
 staff-bar
 time-signature
 custos))

\fixed c' {
  \key g \minor
  s2 b16 a g fis g4
  \keyChangeBeforeBar
  \once \override Staff.KeyCancellation.extra-spacing-width = #'(-2 . 0)
  \key g \major
}



Have a look at this page:
https://lilypond.org/doc/v2.23/Documentation/notation/spacing-between-adjacent-columns.html

Best,
Jean

Add extra space before key cancellation and a new key signature

[Volodymyr Prokopyuk]

Hi,

Could you please help me with the below situation?

*Context*

I've changed the order of key cancellation and a new key signature to be
placed before the bar line with the following code

keyChangeBeforeBar = \once \override
Score.BreakAlignment.break-align-orders =
  #(make-vector 3 '(
 left-edge
 staff-ellipsis
 cue-end-clef
 ambitus
 breathing-sign
 signum-repetitionis
 clef
 cue-clef
 key-cancellation
 key-signature
 staff-bar
 time-signature
 custos))

Now I use \keyChangeBeforeBar \key g \major to change the key at the end of
the score with the below result

[image: image.png]
*Problem*
The key cancellation and a new key signature are *too close to the last
note* g'.

*Question*
How can I *add extra space before the key cancellation* and a new key
signature?

I tried a few options following the documentation but with no luck.

Thank you very much,
Vlad

Re: No shell script needed

[Andrew Bernard]

Calculating an arbitrary number of digits of pi is a very sophisticated 
algorithmic process. Sounds to me like you _were_ the smartest kids.


Andrew


On 19/10/2022 9:06 pm, Craig Bakalian wrote:
Call me old fashioned.  Shesh, I remember the first computer I saw in 
my math class back in 1978, the kind with the punch cards with holes, 
and how we as foolish kids would calculate pi to the longest number we 
could and thought we were the coolest smartest kids ever.

No shell script needed

[Craig Bakalian]

Hi,

Okay, I get it now.  I just downloaded the latest and greatest version 
of lilypond, extracted, and put the folder in my home folder, fired up 
frescobaldi, added 2.23.14 to the list of lilypond(s) and ran it just 
fine.  I just thought everything had to be in its correct linux folder 
for it to run.


Call me old fashioned.  Shesh, I remember the first computer I saw in my 
math class back in 1978, the kind with the punch cards with holes, and 
how we as foolish kids would calculate pi to the longest number we could 
and thought we were the coolest smartest kids ever.


Thanks Lilypond Team!

I love my lilypond, lol.

Re: Text under recitative note

[Leo Correia de Verdier]

I think you are looking for the markup commands wordwrap or wordwrap-string, 
something like:

\version "2.23.11"
\fixed c' { \cadenzaOn d4 e a g f g f d d e2 g1 f4 e  }
\addlyrics { When the stone had been seal -- ed by the Jews.
 \markup { 
   \override #'(line-width . 25)
   \wordwrap { 
 While the soldiers were guarding Thy most pure }
 }
 Bo -- dy 
}

You need the override to set the desired width to be taken up, and probably a 
bit of formatting with other markup commands to make it look decent. 

HTH
/Leo

> 19 okt. 2022 kl. 10:51 skrev mjchadwic...@gmail.com:
> 
> I am starting to set Orthodox chant (in English). How do I get a whole phrase 
> of text to split into two (or even three) lines. EG I would like to fit 
> “while the soldiers were guarding Thy most pure” under one semibreve. So that 
> it comes out something like:
>  
> While the soldiers
> were guarding Thy
> most pure
>  
> Rather than taking up half a staff of music.
>  
> Thank you for any help you can give a beginner.
>  
> Martin
>  
> Martin Chadwick
>  
> mjchadwic...@gmail.com

Text under recitative note

[mjchadwick55]

I am starting to set Orthodox chant (in English). How do I get a whole
phrase of text to split into two (or even three) lines. EG I would like to
fit "while the soldiers were guarding Thy most pure" under one semibreve. So
that it comes out something like:

 

While the soldiers

were guarding Thy

most pure

 

Rather than taking up half a staff of music.

 

Thank you for any help you can give a beginner.

 

Martin

 

Martin Chadwick

 

mjchadwic...@gmail.com