Re: Issue with download link

[Jonas Hahnfeld via LilyPond user discussion]

(sorry for the slow reply)

On Mon, 2022-07-25 at 09:07 -0700, Knute Snortum wrote:
> On Mon, Jul 25, 2022 at 6:56 AM Simon Albrecht  wrote:
> > 
> > Hello everyone,
> > 
> > On 24/07/2022 19:44, Jonas Hahnfeld via LilyPond user discussion wrote:
> > > Please refer to the Installing section in the
> > > Learning Manual for instructions how to set up the provided binaries:
> > > https://lilypond.org/doc/v2.23/Documentation/learning/installing
> > 
> > This link leads to a 2.23 documentation page which contains links for
> > 2.22.1 binaries.
> > 
> > Would it make more sense linking to
> >  and
> >  instead?
> 
> Ah, this ties in to what I posted early.  The webpage...
> 
> https://lilypond.org/doc/v2.23/Documentation/learning/command-line-setup
> 
> ...has a link labeled Download that leads to this page:
> 
> https://lilypond.org/doc/v2.23/Documentation/web/download
> 
> It has "v2.23" in the URL, but the page still says "Downloads for
> LilyPond 2.22.2"  Following this link you get to:
> 
> https://lilypond.org/doc/v2.23/Documentation/web/unix
> 
> Which is the best page I found earlier.  It has 2.22 downloads.

Yes, I think this should be changed: For development versions, the
Installing section of the LM should refer people to
https://lilypond.org/doc/v2.23/Documentation/web/development instead of
the "Downloads" page, which is for stable versions.

Jonas


signature.asc
Description: This is a digitally signed message part

Re: question about arranger.ly, export notes as text.

[Gilles Thibault]

In the manual is says"

" Once the arrangement is finished, it can be exported to usual 
LilyPond source:


   flute = {...}
   clar = {...}



From arrangerDoc.pdf :

export-instruments syntax

  (export-instruments instruments filename #:optional overwrite?)

So something like

  (export-instruments '(flute clar...) "exported-file.ly" #f)

should produce in the current directory, a file called 
"exported-file.ly", with the definition of flute and clar.



Is this the case ? It's a problem if not !


--
Gilles

Re: question about arranger.ly, export notes as text.

[Eef Weenink]

It gives error;
"72:2<0>: fout: GUILE signaleerde een fout voor de hier beginnende expressie"

 makes a file: in file is only:

%% instruments export : za 30 jul 22:36:19 2022 %%

I tried it with this file: ( a bit long ... but should be)


\version "2.22.2"

\include "arranger.ly"

\header {
  title = "Romance Oubliée"
  composer = "Liszt, Ferenc (1880)"
  tagline = "Arrangement Eef Weenink"
}

\paper {
  #(set-paper-size "a4")
}

\layout {
  \context {
\Voice
\consists "Melody_engraver"
\override Stem #'neutral-direction = #'()
  }
}

global = {
\key e \minor
%  \twoCompoundMeters #'(9 8) #'(3 4)
\time 9/8
  \partial 8*3 s8*3

 s4. *3 *18
%\twoCompoundMeters #'(6 8) #'(2 4)
\time 6/8
  s4.*2*71
  \bar "|."
}

viola = \relative c' {
  \partial 8*3
c8\downbow_( \mf ^\markup {\italic "Andante malinconico"} b a e'4. \< 
f2. \! )  | % 1
r2.c8_( b a  | % 2
f'4. \< fis2. \! )  | % 3
r2. fis,8\downbow ( e dis | % 4
a' g fis ) c' (b a g fis a )| % 5
c (b a) dis\upbow (c b a b c) | % 6
dis ( e eis fis4 ) r8 g\upbow_"espr." ( fis e) | % 7
b'4.~ b8 b(  c b  \acciaccatura { d16 } c8 b)  | % 8
b4.\> ( fis4) \!  r8 fis( g \acciaccatura { b16 } a8)  | % 9
c,4.~ c8  b( \acciaccatura { d16} c8 b4 g'8)   | % 10
fis4.( e4) r8 g\upbow( fis e)   | % 11
 b'4.~ b8 b(  c b  \acciaccatura { d16 } c8 b)  | % 12
   b4.( e,4->) r8 es( b' a ) | % 13
   a4. d,4 ( e!8 fis4 \tuplet 3/2 { e16 fis g) }  | % 14
   fis4( e8 fis4) r8 es( b' a ) | % 15
a4. d,4 ( e!8 fis4 \tuplet 3/2 { e16_"dim." fis g) }  | % 16
fis4 \>( e8 fis2.) \! | % 17
R4.*3  | % 18

R2.  | % 19
r4 r8 \p \ ^~ ^(  % 21
a8 [ g fis]) fis^--  \! r8 r
f4.\downbow(  \acciaccatura { a16} g4 fis8)  % 22
%verder met pagina 3
}

#(begin
(export-instruments 'viola "exported-file.ly" #t)
)

\score {
  \new Staff \with {
instrumentName = "Altviool"
shortInstrumentName = "Avl."
\consists "Merge_rests_engraver"
printPartCombineTexts = ##f
  } {
\clef alto
\partCombine \global  \viola
  }
  \layout { }
}

RE: Learning how to use "\change Staff"; don't get it yet, obviously

[Mark Stephen Mrotek]

Kenneth,

Not dense at all.
Change staff works within a single voice. You split it between rh and lh. Might 
suggest you use "upper" and "lower" for staff designation if you use rh and lh 
as variable names.

Assuming you start in "lower" with lh.
Then 
\tuplet 3/2 { b,8(d b }
  \change Staff = "upper"   %% now continue with what you want in "upper"
{ d'8 fs' b' } \tuplet 3/2 { d''8 b' fs' }
  \change Staff = "lower"   %% and so on.

Note: that rh must contain spacers all the while so that the voice can move 
back and forth without collisions.

Mark

-Original Message-
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] 
On Behalf Of Kenneth Wolcott
Sent: Saturday, July 30, 2022 2:49 PM
To: Lily Pond 
Subject: Learning how to use "\change Staff"; don't get it yet, obviously

Hi;

  I'm learning how to engrave music that changes from one staff to another.

  I, obviously, do not understand yet how to do this, even after reading the 
pertinent section in the Notation Reference.

  My attempt to engrave the first three bars of the harp score of Swan Lake 
fails with the following:

Swan_Lake.ly:40:3: warning: cannot find context to change to: Staff = RH

  \change Staff = "RH"
Swan_Lake.ly:22:3: warning: cannot find context to change to: Staff = LH

  \change Staff = "LH" <> s4| % m01

  I have attached a screenshot of the first three bars of the harp score of 
Swan Lake, my LIlypond source code and the result of my engraving attempt.

  I don't think that there's anything wrong with Lilypond, and there's nothing 
wrong with the documentation, but this Lilypond user is a bit dense.

  If I can just get the first bar engraving correctly, I think I can make it 
the rest of the way :-)

Thanks,
Ken Wolcott

Re: Learning how to use "\change Staff"; don't get it yet, obviously

[Kenneth Wolcott]

Hi Mark;

  Thank you for the help.

  I'm still having trouble wrapping my head around this.

  I think that the problem (in general) with my being able to apply
examples from the documentation to my engraving attempts is that the
example is not large enough (not enough notes, too minimal) to require
its own variable to contain the notes, so that gets in the way of the
Lilypond feature that I want to use.

  I will try removing the variables and just place the notes for the
first measure only to see if I can finally make this work, and
generalize it later.

Thanks,
Ken

On Sat, Jul 30, 2022 at 3:04 PM Mark Stephen Mrotek
 wrote:
>
> Kenneth,
>
> Not dense at all.
> Change staff works within a single voice. You split it between rh and lh. 
> Might suggest you use "upper" and "lower" for staff designation if you use rh 
> and lh as variable names.
>
> Assuming you start in "lower" with lh.
> Then
> \tuplet 3/2 { b,8(d b }
>   \change Staff = "upper"   %% now continue with what you want in "upper"
> { d'8 fs' b' } \tuplet 3/2 { d''8 b' fs' }
>   \change Staff = "lower"   %% and so on.
>
> Note: that rh must contain spacers all the while so that the voice can move 
> back and forth without collisions.
>
> Mark
>
> -Original Message-
> From: lilypond-user 
> [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of 
> Kenneth Wolcott
> Sent: Saturday, July 30, 2022 2:49 PM
> To: Lily Pond 
> Subject: Learning how to use "\change Staff"; don't get it yet, obviously
>
> Hi;
>
>   I'm learning how to engrave music that changes from one staff to another.
>
>   I, obviously, do not understand yet how to do this, even after reading the 
> pertinent section in the Notation Reference.
>
>   My attempt to engrave the first three bars of the harp score of Swan Lake 
> fails with the following:
>
> Swan_Lake.ly:40:3: warning: cannot find context to change to: Staff = RH
>
>   \change Staff = "RH"
> Swan_Lake.ly:22:3: warning: cannot find context to change to: Staff = LH
>
>   \change Staff = "LH" <> s4| % m01
>
>   I have attached a screenshot of the first three bars of the harp score of 
> Swan Lake, my LIlypond source code and the result of my engraving attempt.
>
>   I don't think that there's anything wrong with Lilypond, and there's 
> nothing wrong with the documentation, but this Lilypond user is a bit dense.
>
>   If I can just get the first bar engraving correctly, I think I can make it 
> the rest of the way :-)
>
> Thanks,
> Ken Wolcott
>

RE: Learning how to use "\change Staff"; don't get it yet, obviously

[Mark Stephen Mrotek]

Kenneth,

If you want, send your code to me and I shall try to achieve what you want with 
an explanation.

Mark

-Original Message-
From: Kenneth Wolcott [mailto:kennethwolc...@gmail.com] 
Sent: Saturday, July 30, 2022 6:45 PM
To: Mark Stephen Mrotek 
Cc: Lily Pond 
Subject: Re: Learning how to use "\change Staff"; don't get it yet, obviously

Hi Mark;

  Thank you for the help.

  I'm still having trouble wrapping my head around this.

  I think that the problem (in general) with my being able to apply examples 
from the documentation to my engraving attempts is that the example is not 
large enough (not enough notes, too minimal) to require its own variable to 
contain the notes, so that gets in the way of the Lilypond feature that I want 
to use.

  I will try removing the variables and just place the notes for the first 
measure only to see if I can finally make this work, and generalize it later.

Thanks,
Ken

On Sat, Jul 30, 2022 at 3:04 PM Mark Stephen Mrotek  
wrote:
>
> Kenneth,
>
> Not dense at all.
> Change staff works within a single voice. You split it between rh and lh. 
> Might suggest you use "upper" and "lower" for staff designation if you use rh 
> and lh as variable names.
>
> Assuming you start in "lower" with lh.
> Then
> \tuplet 3/2 { b,8(d b }
>   \change Staff = "upper"   %% now continue with what you want in "upper"
> { d'8 fs' b' } \tuplet 3/2 { d''8 b' fs' }
>   \change Staff = "lower"   %% and so on.
>
> Note: that rh must contain spacers all the while so that the voice can move 
> back and forth without collisions.
>
> Mark
>
> -Original Message-
> From: lilypond-user 
> [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf 
> Of Kenneth Wolcott
> Sent: Saturday, July 30, 2022 2:49 PM
> To: Lily Pond 
> Subject: Learning how to use "\change Staff"; don't get it yet, 
> obviously
>
> Hi;
>
>   I'm learning how to engrave music that changes from one staff to another.
>
>   I, obviously, do not understand yet how to do this, even after reading the 
> pertinent section in the Notation Reference.
>
>   My attempt to engrave the first three bars of the harp score of Swan Lake 
> fails with the following:
>
> Swan_Lake.ly:40:3: warning: cannot find context to change to: Staff = 
> RH
>
>   \change Staff = "RH"
> Swan_Lake.ly:22:3: warning: cannot find context to change to: Staff = 
> LH
>
>   \change Staff = "LH" <> s4| % m01
>
>   I have attached a screenshot of the first three bars of the harp score of 
> Swan Lake, my LIlypond source code and the result of my engraving attempt.
>
>   I don't think that there's anything wrong with Lilypond, and there's 
> nothing wrong with the documentation, but this Lilypond user is a bit dense.
>
>   If I can just get the first bar engraving correctly, I think I can 
> make it the rest of the way :-)
>
> Thanks,
> Ken Wolcott
>

hspace in markup cancels other directives

[Jim Cline]

I am trying to use \hspace to adjust the horizontal position of a text 
markup.   In addition I want the text to be colored and smaller.  But the 
\hspace directive somehow disables the others, as in this example.


\version "2.20.0"
lower =
  \relative c {
   \time 3/4
  \clef bass
  bes^\markup{\smaller  \with-color #blue \hspace #-3 text} r4 
bes^\markup{\smaller  \with-color #blue  text}

}

\score {
\new Staff = "lower" \lower
}

The second text has the right font and color, but the first one only has 
the right horizontal position. --Jim

Re: hspace in markup cancels other directives

[Aaron Hill]

On 2022-07-30 8:12 pm, Jim Cline wrote:

I am trying to use \hspace to adjust the horizontal position of a text
markup.


\hspace is probably not the best tool.  Consider \tweaking the text 
script:


  bes-\tweak self-alignment-X #RIGHT
 ^\markup \smaller \with-color #blue text

  bes-\tweak X-offset #-3
 ^\markup \smaller \with-color #blue text



  In addition I want the text to be colored and smaller.  But
the \hspace directive somehow disables the others, as in this example.

\version "2.20.0"
lower =
  \relative c {
   \time 3/4
  \clef bass
  bes^\markup{\smaller  \with-color #blue \hspace #-3 text} r4
bes^\markup{\smaller  \with-color #blue  text}
}


The effects of markup commands only apply to their specific markup 
arguments.


What you have effectively done is this:

  \markup {
\smaller { \with-color #blue { \hspace #-3 } }
text
  }

You could explicitly group the space and text:

  \markup \smaller \with-color #blue { \hspace #-3 text }

Alternately, move the space outside the other commands:

  \markup { \hspace #-3 \smaller \with-color #blue text }


-- Aaron Hill