Re: In other news ...

2019-11-15 Thread Urs Liska
Since our post announcement function doesn't seem to work anymore, I'll 
just use this thread to point you to the second issue in this post 
series: 
http://lilypondblog.org/2019/11/leopold-mozart-violin-school-2-lilypond-structure-and-organization/


Thank you David Olson for copy-editing!

The remaining two posts will take more time because the underlying stuff 
will have to be tidied-up.


Have fun
Urs

Am 12.11.19 um 17:26 schrieb Urs Liska:
... may I for once engage in some self-advertisment and point you to 
this post: 
http://lilypondblog.org/2019/11/leopold-mozart-violin-school-1-the-project/ 
?


Is there any way we can make this (the project, not the post) more 
prominently advertise for LilyPond than putting it on 
http://lilypond.org/productions.html?


With best regards and many thanks to all who helped me get this over 
the goal line. As usual, I wouldn't have managed without the expertise 
on this list.


Urs






Re: drawing a range reguardless of transposition

2019-11-15 Thread Malte Meyn




Am 14.11.19 um 18:09 schrieb Aaron Hill:

On 2019-11-14 8:53 am, Sandro Santilli wrote:

In order to determine if I'm writing something that can
be played by an instrument, is there a way to display
on the score the supported range by that instrument ?

I'd like to have something that doesn't change when I
transpose, so to know if transpositions are possible
at all...


You could do something like this:


\version "2.19.83"

highlightOutOfRange = #(define-scheme-function
   (color lower upper)
   ((color? red) ly:pitch? ly:pitch?)
   (grob-transformer 'color (lambda (grob orig)
     (let* ((cause (ly:grob-property grob 'cause))
     (pitch (ly:event-property cause 'pitch)))
   (if (or (ly:pitch

Nice! This should be added at least to the snippet repository if not to 
vanilla LilyPond. I don’t know whether many people would use it but it’s 
a small addition and AFAIK this feature is present in every other 
engraving software I know …




Re: drawing a range reguardless of transposition

2019-11-15 Thread Sandro Santilli
On Thu, Nov 14, 2019 at 09:09:16AM -0800, Aaron Hill wrote:

> \layout {
>   \context { \Voice
> \override NoteHead.color = \highlightOutOfRange c' c''
>   }
> }

I like the highlighting idea! Is it compatible at all with 2.18.2 ?

It seems not to be: http://lilybin.com/166vv7/1

  Parsing.../usr/share/lilypond/2.18.2/scm/ly-syntax-constructors.scm:56:23: In 
expression (apply (ly:music-function-extract fun) parser ...):
  /usr/share/lilypond/2.18.2/scm/ly-syntax-constructors.scm:56:23: Wrong number 
of arguments to #

--strk;



Re: drawing a range reguardless of transposition

2019-11-15 Thread Michael Käppler

While I would strongly suggest that you update to the latest development
version, which can regarded
as very stable, this would work with 2.18.2:

% LilyBin
\version "2.18.2"

highlightOutOfRange = #(define-scheme-function
  (parser location color lower upper)
  ((color? red) ly:pitch? ly:pitch?)
  (lambda (grob)
    (let* ((cause (ly:grob-property grob 'cause))
    (pitch (ly:event-property cause 'pitch)))
  (if (or (ly:pitch
On Thu, Nov 14, 2019 at 09:09:16AM -0800, Aaron Hill wrote:


\layout {
   \context { \Voice
 \override NoteHead.color = \highlightOutOfRange c' c''
   }
}

I like the highlighting idea! Is it compatible at all with 2.18.2 ?

It seems not to be: http://lilybin.com/166vv7/1

   Parsing.../usr/share/lilypond/2.18.2/scm/ly-syntax-constructors.scm:56:23: 
In expression (apply (ly:music-function-extract fun) parser ...):
   /usr/share/lilypond/2.18.2/scm/ly-syntax-constructors.scm:56:23: Wrong number of 
arguments to #

--strk;







\epsfile

2019-11-15 Thread Martin Tarenskeen



Hi LilyPonders,

I am experimenting with the \epsfile command to include various pictures 
in my score. 
http://lilypond.org/doc/v2.19/Documentation/notation/graphic.en.html 
describes:


 \epsfile axis (number) size (number) file-name (string)
Inline an EPS image. The image is scaled along axis to size.

I don't quite understand what "axis (number)" means and how it works. I 
can reproduce the examples, using my own images, but would like to 
understand the values better.


Related issue: When using frescobaldi the syntax help and 
autocompletion balloon gives "\eps-file" instead of "\epsfile". A little bug?


--

MT



Re: drawing a range reguardless of transposition

2019-11-15 Thread Sandro Santilli
On Thu, Nov 14, 2019 at 06:02:40PM +0100, k...@aspodata.se wrote:
> Sandro:
> > In order to determine if I'm writing something that can
> > be played by an instrument, is there a way to display
> > on the score the supported range by that instrument ?
> > 
> > I'd like to have something that doesn't change when I
> > transpose, so to know if transpositions are possible
> > at all...
> 
> The other way around, search for "ambitus" in the manual to see how to 
> make lilypond print out the range used.

Thanks, "ambitus" works great for a start.
Next step would be automatic checking if the ambitus is within
an instrument capability, which the coloring hint by Aaron should
help with, if I handle to make it work :)

--strk;



Re: \epsfile

2019-11-15 Thread Malte Meyn




Am 15.11.19 um 10:47 schrieb Martin Tarenskeen:
I am experimenting with the \epsfile command to include various pictures 
in my score. 
http://lilypond.org/doc/v2.19/Documentation/notation/graphic.en.html 
describes:


  \epsfile axis (number) size (number) file-name (string)
     Inline an EPS image. The image is scaled along axis to size.

I don't quite understand what "axis (number)" means and how it works. I 
can reproduce the examples, using my own images, but would like to 
understand the values better.


size gives the height *or* width of the image, depending on axis which 
should be set to #X (for height) or #Y.




Related issue: When using frescobaldi the syntax help and autocompletion 
balloon gives "\eps-file" instead of "\epsfile". A little bug?




Seems so, yes. IIUC it has been \epsfile for at least a very long time 
(f. e. version 2.7.30) if not ever so Frescobaldi is wrong here.




Re: How to color objects that cause collision

2019-11-15 Thread Malte Meyn




Am 15.11.19 um 01:50 schrieb Paolo Prete:


I think that a very useful function would be a way to highlight or 
change the color for all the objects that are causing a collision.

Is there already some code for that?
Look for example at the two slurs in the following snippet:

[…]

When there are many and many graphic objects on a score, it's easy to 
ignore some of these errors relying on observation only...


If LilyPond knew that there was a collision it wouldn’t engrave it that 
way so IMO that’s a bug. Without knowing about a collision LilyPond 
cannot tell you about it ;)




Re: \epsfile

2019-11-15 Thread Urs Liska


Am 15.11.19 um 10:56 schrieb Malte Meyn:



Am 15.11.19 um 10:47 schrieb Martin Tarenskeen:
I am experimenting with the \epsfile command to include various 
pictures in my score. 
http://lilypond.org/doc/v2.19/Documentation/notation/graphic.en.html 
describes:


  \epsfile axis (number) size (number) file-name (string)
 Inline an EPS image. The image is scaled along axis to size.

I don't quite understand what "axis (number)" means and how it works. 
I can reproduce the examples, using my own images, but would like to 
understand the values better.


size gives the height *or* width of the image, depending on axis which 
should be set to #X (for height) or #Y.



X and Y are speaking variable names for the numbers 0 and 1 (which you 
can verify through


#(display Y)

), hence the docstring.






Related issue: When using frescobaldi the syntax help and 
autocompletion balloon gives "\eps-file" instead of "\epsfile". A 
little bug?




Seems so, yes. IIUC it has been \epsfile for at least a very long time 
(f. e. version 2.7.30) if not ever so Frescobaldi is wrong here.



... which is of course possible but somehow surprising. AFAIK 
Frescobaldi's "knowledge" about LilyPond's syntax is retrieved 
automatically, although I don't recall whether that involves parsing the 
documentation or running LilyPond itself.


What *is* known is that Frescobaldi's autocompletion works on the 2.18 
syntax because it's official policy to support the "latest stable 
release". We have agreed upon the idea that it would be better to 
support both the current stable and development releases but so far 
noone has found the time to implement that.


It should not be *that* complicated, so any volunteers are encouraged to 
step forward ;-)


Best
Urs



Re: \epsfile

2019-11-15 Thread Andrew Bernard
I think the doc is a bit misleading. Axis is technically a number, but 
it's really #X or #Y, and the following number is that the image is 
scaled along the specified axis to size, a number.


\markup {
  \general-align #Y #DOWN {
\epsfile #X #20 #"context-example.eps"
\epsfile #Y #20 #"context-example.eps"
  }
}

The example is clearer than the text.

Andrew



On 15/11/19 8:47 pm, Martin Tarenskeen wrote:


I don't quite understand what "axis (number)" means and how it works. 
I can reproduce the examples, using my own images, but would like to 
understand the values better.




Re: Display the control points of a slur

2019-11-15 Thread Urs Liska



Am 15.11.19 um 00:06 schrieb Aaron Hill:

On 2019-11-14 2:20 pm, Paolo Prete wrote:

I propose to include your snippet in a new release of Lilypond because
it's very useful.


It would be nice to include more debug annotations within LilyPond.  
If I am not mistaken, we currently have the following options:


  \paper { annotate-spacing = ##t }
  #(ly:set-option 'debug-skylines)
  \override [Non]PaperColumn.stencil = #ly:paper-column::print

For the future, we could add support for these cases:

- Plotting curve control points.
- Visualizing the extents and origins of grob stencils.
- Indicating the relationships between grobs (i.e. parents, children, 
siblings).


Are there other annotations that folks would find helpful? Providing 
there is enough interest in such support, we should open a ticket for 
tracking the work.



Frescobaldi also offers the following options (in the Layout Control Tool):

- coloring voices with explicit \voiceXXX
  (unfortunately implicit ones in polyphonic settings are not possible)
- coloring explicit directions with ^ or _
- print the grob names

What I'd find interesting in addition would be:

- visualizing extra-offset (by plotting a line between the final and the 
original refpoints)
- visualizing *other* properties of bezier curves, for example angles 
and ratios
  (those that can be set with \shapeII). These are of course not 
available as properties

  but would have to be calculated.
  The results should be printed in a semi-transparent (?) rectangle 
overlaying the score
- in a similar vein there could be a more generic function to "debug" a 
grob by printing
  selected property values on top of the score (something like a ballon 
text, but overlaid)


These visualizations should also be possible to switch on and off in the 
course of the document to just apply them to a selected range or even a 
single item.


Urs





-- Aaron Hill





Re: Display the control points of a slur

2019-11-15 Thread Urs Liska



Am 15.11.19 um 11:18 schrieb Urs Liska:

What I'd find interesting in addition would be:

- visualizing extra-offset (by plotting a line between the final and 
the original refpoints)



What I would also love to see (but can't really imagine being possible) 
is any offset that has been automatically applied due to collision 
avoidance.





Re: drawing a range reguardless of transposition

2019-11-15 Thread Sandro Santilli
On Fri, Nov 15, 2019 at 10:45:45AM +0100, Michael Käppler wrote:
> While I would strongly suggest that you update to the latest development
> version, which can regarded
> as very stable, this would work with 2.18.2:

Thanks, this works!
Can I specify a different override for different
voices by name ? Ie: I have these voices:

  \new Staff \with {
instrumentName = #"Voice"
  } {
\new Voice = "vocal" { \melody }
  }

  \new Staff \with {
instrumentName = #"Alto"
  } {
\transpose c a
\new Voice = "sax" { \melody_alto }
  }

  \new Staff \with {
instrumentName = #"Trumpet"
  } {
\transpose c d
\new Voice = "trp" { \melody_trp }
  }

--strk;



Re: drawing a range reguardless of transposition

2019-11-15 Thread Michael Käppler

notes = \relative c' { c d e f g a b c }

\score {
  <<
    \new Staff \with {
  instrumentName = #"Voice"

    } {
  \new Voice = "vocal" \with {
    \override NoteHead.color = \highlightOutOfRange e' b'
  } { \notes }

    }

    \new Staff \with {
  instrumentName = #"Alto"
    } {
  \new Voice = "sax" \with {
    \override NoteHead.color = \highlightOutOfRange a e'
  } { \transpose c g, \notes }
    }

    \new Staff \with {
  instrumentName = #"Trumpet"
    } {
  \new Voice = "trp" \with {
    \override NoteHead.color = \highlightOutOfRange g' f''
  } { \transpose c b \notes }
    }
  >>
  \layout { }
}

Am 15.11.2019 um 11:25 schrieb Sandro Santilli:

On Fri, Nov 15, 2019 at 10:45:45AM +0100, Michael Käppler wrote:

While I would strongly suggest that you update to the latest development
version, which can regarded
as very stable, this would work with 2.18.2:

Thanks, this works!
Can I specify a different override for different
voices by name ? Ie: I have these voices:

   \new Staff \with {
 instrumentName = #"Voice"
   } {
 \new Voice = "vocal" { \melody }
   }

   \new Staff \with {
 instrumentName = #"Alto"
   } {
 \transpose c a
 \new Voice = "sax" { \melody_alto }
   }

   \new Staff \with {
 instrumentName = #"Trumpet"
   } {
 \transpose c d
 \new Voice = "trp" { \melody_trp }
   }

--strk;






Re: drawing a range reguardless of transposition

2019-11-15 Thread Sandro Santilli
On Fri, Nov 15, 2019 at 12:00:09PM +0100, Michael Käppler wrote:

> \score {
>   <<
>     \new Staff \with {
>   instrumentName = #"Voice"
> 
>     } {
>   \new Voice = "vocal" \with {
>     \override NoteHead.color = \highlightOutOfRange e' b'
>   } { \notes }
> 
>     }
> 
>     \new Staff \with {
>   instrumentName = #"Alto"
>     } {
>   \new Voice = "sax" \with {
>     \override NoteHead.color = \highlightOutOfRange a e'
>   } { \transpose c g, \notes }
>     }
> 
>     \new Staff \with {
>   instrumentName = #"Trumpet"
>     } {
>   \new Voice = "trp" \with {
>     \override NoteHead.color = \highlightOutOfRange g' f''
>   } { \transpose c b \notes }
>     }
>   >>

The thing is I'm writing multiple scores with the same parts
replicated (some with all 3 voices, some with just 2 voices)
so I'd like to avoid the duplication of ranges. A range is
specific to an instrument so I'd like to specify that in the
header for each instrument, reguardless of score...

--strk;



Re: drawing a range reguardless of transposition

2019-11-15 Thread Sandro Santilli
On Fri, Nov 15, 2019 at 12:09:27PM +0100, Sandro Santilli wrote:
> 
> The thing is I'm writing multiple scores with the same parts
> replicated (some with all 3 voices, some with just 2 voices)
> so I'd like to avoid the duplication of ranges. A range is
> specific to an instrument so I'd like to specify that in the
> header for each instrument, reguardless of score...

Actually, I'm thinking I'd build a database of available ranges
for instruments and players / singers, so that when a score
is intended for playing by known people I'd just reference
their names in the score...

--strk;



Error with layout control (again)

2019-11-15 Thread Peter Toye
I'm reposting this as I didn't get an answer from my original posting. Surely 
someone here must know the answer!

I'm trying to find out exactly what grobs are produced as one point ins a 
score, so tried engraving with layout control and "display grob names" ticked 
on the layout control. And got this on the log:

warning: no such internal option: debug-grob-names
Processing `D:/Peter/Music/Lilypond/Herz/Variations/Intro/Intro.ly'
Parsing...C:/Program Files 
(x86)/Frescobaldi/frescobaldi_app/layoutcontrol/debug-layout-options.ly:65:8: 
In procedure ly:parser-include-string in expression (ly:parser-include-string 
parser "\\include \"display-grob-names.ily\""):
C:/Program Files 
(x86)/Frescobaldi/frescobaldi_app/layoutcontrol/debug-layout-options.ly:65:8: 
Wrong number of arguments to #
Exited with return code 1.

I'm using LP 2.19.52 and Frescobaldi 2.20

Where do I go from here please?
 
Regards,

Peter
mailto:lilyp...@ptoye.com
www.ptoye.com

Re: drawing a range reguardless of transposition

2019-11-15 Thread Michael Käppler

Why not put it in the underlying "input" then?

melody = {
    \override NoteHead.color = \highlightOutOfRange e' b'
   \relative c' {  c4 d e f }
}

You could even define a shortcut for this:

melodyRange = \override NoteHead.color = \highlightOutOfRange e' b'

melody = {
   \melodyRange
   \relative c' {  c4 d e f }
}



Am 15.11.2019 um 12:09 schrieb Sandro Santilli:

On Fri, Nov 15, 2019 at 12:00:09PM +0100, Michael Käppler wrote:


\score {
   <<
     \new Staff \with {
   instrumentName = #"Voice"

     } {
   \new Voice = "vocal" \with {
     \override NoteHead.color = \highlightOutOfRange e' b'
   } { \notes }

     }

     \new Staff \with {
   instrumentName = #"Alto"
     } {
   \new Voice = "sax" \with {
     \override NoteHead.color = \highlightOutOfRange a e'
   } { \transpose c g, \notes }
     }

     \new Staff \with {
   instrumentName = #"Trumpet"
     } {
   \new Voice = "trp" \with {
     \override NoteHead.color = \highlightOutOfRange g' f''
   } { \transpose c b \notes }
     }
   >>

The thing is I'm writing multiple scores with the same parts
replicated (some with all 3 voices, some with just 2 voices)
so I'd like to avoid the duplication of ranges. A range is
specific to an instrument so I'd like to specify that in the
header for each instrument, reguardless of score...

--strk;






Re: Error with layout control (again)

2019-11-15 Thread Urs Liska
Didn't I reply to your inital question, asking for more version details? 
Sorry.


I can't look into the details right now, but the version of the code 
included in Frescobaldi 2.20 obviously isn't compatible with LP 2.19.52. 
We fixed that at some point, but I think that will only be easily 
available with the 3.1 release we are currently planning.


However, you can look into 
https://github.com/openlilylib/oll-misc/tree/master/layout/display and 
try integrating the code in the control-points.ily file. Maybe that 
works for you.


And I suggest updating LilyPond to 2.19.83 if there is no specific 
reason not to do so (although that will probably not help you with the 
issue at hand).


Urs

Am 15.11.19 um 12:21 schrieb Peter Toye:
Error with layout control (again) I'm reposting this as I didn't get 
an answer from my original posting. Surely someone here must know the 
answer!


I'm trying to find out exactly what grobs are produced as one point 
ins a score, so tried engraving with layout control and "display grob 
names" ticked on the layout control. And got this on the log:


warning: no such internal option: debug-grob-names
Processing `D:/Peter/Music/Lilypond/Herz/Variations/Intro/Intro.ly'
Parsing...C:/Program Files 
(x86)/Frescobaldi/frescobaldi_app/layoutcontrol/debug-layout-options.ly:65:8: 
In procedure ly:parser-include-string in expression 
(ly:parser-include-string parser "\\include \"display-grob-names.ily\""):
C:/Program Files 
(x86)/Frescobaldi/frescobaldi_app/layoutcontrol/debug-layout-options.ly:65:8: 
Wrong number of arguments to #ly:parser-include-string>

Exited with return code 1.

I'm using LP 2.19.52 and Frescobaldi 2.20

Where do I go from here please?

Regards,

Peter
mailto:lilyp...@ptoye.com
www.ptoye.com  


Re: drawing a range reguardless of transposition

2019-11-15 Thread Sandro Santilli
On Fri, Nov 15, 2019 at 12:20:51PM +0100, Michael Käppler wrote:
> Why not put it in the underlying "input" then?
> 
> melody = {
>     \override NoteHead.color = \highlightOutOfRange e' b'
>    \relative c' {  c4 d e f }
> }

Yep, that works

> You could even define a shortcut for this:
> 
> melodyRange = \override NoteHead.color = \highlightOutOfRange e' b'

And this is great to build that library, thanks !

--strk;



Re: How to color objects that cause collision

2019-11-15 Thread Paolo Prete
 I don't think it's a bug. It's a snippet from the official documentation.Look 
at the first snippet in the following page, there's a collision as well:
LilyPond Learning Manual: 4.6.3 Real music example

| 
| 
|  | 
LilyPond Learning Manual: 4.6.3 Real music example

LilyPond Learning Manual: 4.6.3 Real music example
 |

 |

 |



A function that helps in discovering these things would be really useful...
Il venerdì 15 novembre 2019, 11:01:14 CET, Malte Meyn 
 ha scritto:  
 
 

Am 15.11.19 um 01:50 schrieb Paolo Prete:
> 
> I think that a very useful function would be a way to highlight or 
> change the color for all the objects that are causing a collision.
> Is there already some code for that?
> Look for example at the two slurs in the following snippet:
> 
> […]
> 
> When there are many and many graphic objects on a score, it's easy to 
> ignore some of these errors relying on observation only...

If LilyPond knew that there was a collision it wouldn’t engrave it that 
way so IMO that’s a bug. Without knowing about a collision LilyPond 
cannot tell you about it ;)

  

Re: Error with layout control (again)

2019-11-15 Thread Peter Toye
Friday, November 15, 2019, 1:52:46 PM, lilypond-user-requ...@gnu.org wrote:

> Didn't I reply to your inital question, asking
> for more version details?
> Sorry.

I replied on 3 november - you must have missed it.

> I can't look into the details right now, but
> the version of the code
> included in Frescobaldi 2.20 obviously isn't
> compatible with LP 2.19.52.
> We fixed that at some point, but I think that will only be easily
> available with the 3.1 release we are currently planning.

I'm not sure what you mean about 3.1. Is that a new LP or Fresco version?

> However, you can look into
> https://github.com/openlilylib/oll-misc/tree/master/layout/display and
> try integrating the code in the
> control-points.ily file. Maybe that
> works for you.

I sort of solved the problem without looking at the grob details, so the need 
has gone away. If I get any spare time I may look at it.

> And I suggest updating LilyPond to 2.19.83 if there is no specific
> reason not to do so (although that will
> probably not help you with the
> issue at hand).

Will do next time I have a score to engrave. By which time it will probably be 
a different version anyway.

> Urs

Re: Error with layout control (again)

2019-11-15 Thread Urs Liska

Hi Peter,

Am 15.11.19 um 16:24 schrieb Peter Toye:
Re: Error with layout control (again) Friday, November 15, 2019, 
1:52:46 PM, lilypond-user-requ...@gnu.org 
 wrote:


*> Didn't I reply to your inital question, asking
> for more version details?
> Sorry.

I replied on 3 november - you must have missed it.
*



Ok, sorry,



*
> I can't look into the details right now, but
> the version of the code
> included in Frescobaldi 2.20 obviously isn't
> compatible with LP 2.19.52.
> We fixed that at some point, but I think that will only be easily
> available with the 3.1 release we are currently planning.

I'm not sure what you mean about 3.1. Is that a new LP or Fresco version?
*



We are looking forward to finally making a release of Frescobaldi 3.1 in 
the foreseable future.




*
> However, you can look into
*> https://github.com/openlilylib/oll-misc/tree/master/layout/display 
* and

> try integrating the code in the
> control-points.ily file. Maybe that
> works for you.

I sort of solved the problem without looking at the grob details, so 
the need has gone away. If I get any spare time I may look at it.


> And I suggest updating LilyPond to 2.19.83 if there is no specific
> reason not to do so (although that will
> probably not help you with the
> issue at hand).

Will do next time I have a score to engrave. By which time it will 
probably be a different version anyway.

*



OK.

May I ask you a favour to send unformatted emails to the list? It's 
extremely awkward to read when I first have to *select* each paragraph 
of text to be able to discern it from the background (and I'm probably 
not the only one).


Best
Urs



*
> Urs * 


Re: Error with layout control (again)

2019-11-15 Thread Peter Toye
Friday, November 15, 2019, 3:28:20 PM, Urs Liska wrote:

May I ask you a favour to send unformatted emails to the list? It's extremely 
awkward to read when I first have to *select* each paragraph of text to be able 
to discern it from the background (and I'm probably not the only one).
Best
Urs

Sorry - my email client (The Bat!) seems to have a mind of its own in 
auto-formatting replies. I notice that the > indents have vanished from this 
one, for example.

Peter

repeat in alternative

2019-11-15 Thread Sandro Santilli
Is there a way to obtain what I'm finding in this paper sheet ?
http://strk.kbt.io/tmp/repeat-in-alternative.png

It's basically a repating section starting within an alternative
section...

--strk; 



Re: repeat in alternative

2019-11-15 Thread Aaron Hill

On 2019-11-15 8:02 am, Sandro Santilli wrote:

Is there a way to obtain what I'm finding in this paper sheet ?
http://strk.kbt.io/tmp/repeat-in-alternative.png

It's basically a repating section starting within an alternative
section...


Two options here:


\version "2.19.83"

{
  \time 3/4
  \repeat volta 2 { a'4 b'2 }
  \alternative {
{ g'2 r4 \bar ":|.|:" }
{ c''2. }
  }
  { b'8 a' g'2 \bar ":|." f'2. \bar "|." }
}

{
  \time 3/4
  \set Score.repeatCommands = #'(start-repeat)
  a'4 b'2
  \set Score.repeatCommands = #'((volta "1."))
  g'2 r4
  \set Score.repeatCommands = #'((volta #f) end-repeat start-repeat 
(volta "2."))

  c''2.
  \set Score.repeatCommands = #'((volta #f))
  b'8 a' g'2
  \set Score.repeatCommands = #'(end-repeat)
  f'2. \bar "|."
}


Note that using repeatCommands handles the bar line types for you, 
although it opts for ":..:" as the double-sided repeat.


-- Aaron Hill



Re: repeat in alternative

2019-11-15 Thread Jacques Menu
Hello Sandro,

> On 2019-11-15 8:02 am, Sandro Santilli wrote:
>> Is there a way to obtain what I'm finding in this paper sheet ?
>> http://strk.kbt.io/tmp/repeat-in-alternative.png
>> It's basically a repating section starting within an alternative
>> section…

It’s in fact a second alternative (second volta) in a single repeat.

JM




Re: repeat in alternative

2019-11-15 Thread Aaron Hill

On 2019-11-15 8:24 am, Aaron Hill wrote:

On 2019-11-15 8:02 am, Sandro Santilli wrote:

Is there a way to obtain what I'm finding in this paper sheet ?
http://strk.kbt.io/tmp/repeat-in-alternative.png

It's basically a repating section starting within an alternative
section...


Two options here:


Nope, I tell a lie.  Here's a third:


{
  \time 3/4
  \repeat volta 2 { a'4 b'2 }
  \alternative {
{ g'2 r4 }
{ \repeat volta 2 { c''2. b'8 a' g'2 } }
  }
  g'2. \bar "|."
}


This one has the volta bracket extending further.

-- Aaron Hill



Has LSR moved?

2019-11-15 Thread David Sumbler
Has the Lilypond Snippets Repository moved?

The address I have bookmarked, http://lsr.di.unimi.it/LSR/Search ,
gives me a "Not Found" error.

David




Re: How to color objects that cause collision

2019-11-15 Thread Thomas Morley
Am Fr., 15. Nov. 2019 um 01:51 Uhr schrieb Paolo Prete :

> Hello,
>
> I think that a very useful function would be a way to highlight or change
> the color for all the objects that are causing a collision.
> Is there already some code for that?
>

Well, you would need to define what exactly _is_a collision?
Printing one grob above the other?
No, can't be a sufficient condition.

Look at this code:
{
  \override Stem.color = #red
  \override Stem.layer = -1000
  b8[
  \override Stem.layer = 1000
  b8]
}

Obviously the Clef collides with StaffSymbol, as well as the TimeSignature.
The NoteHeadcollides with the LedgerLine and Stem.
The Stem collides with the Beam, which collides with the StaffSymbol.

Ofcourse all this is wished.

How to limit to unwished things?
And if unwished things happens, then because Grobs are not aware of each
other. Making it difficult to get something like a "collision yes/no"-info
out of LilyPond

I don't see how to solve.


Cheers,
  Harm


Re: Has LSR moved?

2019-11-15 Thread Aaron Hill

On 2019-11-15 11:39 am, David Sumbler wrote:

Has the Lilypond Snippets Repository moved?

The address I have bookmarked, http://lsr.di.unimi.it/LSR/Search ,
gives me a "Not Found" error.


How peculiar.  I just used the site earlier this morning.  And I am now 
also getting the same error.



-- Aaron Hill



Re: Has LSR moved?

2019-11-15 Thread Thomas Morley
Am Fr., 15. Nov. 2019 um 20:40 Uhr schrieb David Sumbler :
>
> Has the Lilypond Snippets Repository moved?
>
> The address I have bookmarked, http://lsr.di.unimi.it/LSR/Search ,
> gives me a "Not Found" error.
>
> David

Yesterday it worked, now I get the same error.
Hopefully temporary ...


Cheers,
  Harm



RE: Has LSR moved?

2019-11-15 Thread Mark Stephen Mrotek
Same with me 1:01 pm PST

Mark

-Original Message-
From: lilypond-user
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of
Aaron Hill
Sent: Friday, November 15, 2019 12:18 PM
To: lilypond-user@gnu.org
Subject: Re: Has LSR moved?

On 2019-11-15 11:39 am, David Sumbler wrote:
> Has the Lilypond Snippets Repository moved?
> 
> The address I have bookmarked, http://lsr.di.unimi.it/LSR/Search , 
> gives me a "Not Found" error.

How peculiar.  I just used the site earlier this morning.  And I am now also
getting the same error.


-- Aaron Hill




Re: Mac OS 10.15 Catalina

2019-11-15 Thread Allan Kinnaird
So here I am (as I see it) :
My current version of Lilypond is not going to work on my Mac if I upgrade to 
Catalina (v10.15) because of an incomprehensible licence impasse between GNU 
and Apple.
Hans Åberg has provided an installable package ( 
https://www.et.byu.edu/~sorensen/lilypond-devel-2.19.83_2.mpkg 
 ) which runs 
as 64-bit on Catalina. It appears that it has problems with convert-ly but is 
otherwise OK. (And Frescobaldi users need to point Frescobaldi preferences 
towards the right version of Lilypond.)
I have downloaded Hans’s file and tried to install it. Unfortunately the 
installer blocked the process, requiring that the OS be 10.15 Catalina - I have 
to go for Catalina before I can test for problems with it.
So, to continue using Lilypond, either I have to stay forever on v2.18.2 and 
have my computer stay forever on OS 10.14, or just go for Catalina, run Hans’s 
installer, and accept what disasters then ensue. (Hans seems a pretty good guy, 
so with luck there won’t be many!)
Geronimo!


> On 14 Nov 2019, at 17:00, lilypond-user-requ...@gnu.org wrote:
> 
> Send lilypond-user mailing list submissions to
>   lilypond-user@gnu.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>   https://lists.gnu.org/mailman/listinfo/lilypond-user
> or, via email, send a message with subject or body 'help' to
>   lilypond-user-requ...@gnu.org
> 
> You can reach the person managing the list at
>   lilypond-user-ow...@gnu.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lilypond-user digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: Mac OS 10.15 Catalina (Tim McNamara)
>   2. Re: Macro with (David Kastrup)
>   3. Re: Mac OS 10.15 Catalina (Hans Åberg)
>   4. Re: Re: Macro with pitches as parameters (Mats Bengtsson)
>   5. drawing a range reguardless of transposition (Sandro Santilli)
> 
> 
> --
> 
> Message: 1
> Date: Thu, 14 Nov 2019 07:59:26 -0600
> From: Tim McNamara 
> To: lilypond-user 
> Subject: Re: Mac OS 10.15 Catalina
> Message-ID: <7adb0dd2-f14d-4af2-8f84-8c81c0e58...@bitstream.net>
> Content-Type: text/plain; charset="utf-8"
> 
> Frescobaldi itself does not generate sheet music. You need to install 
> Lilypond also. In my experience with Catalina, Hans Aberg's .mkpg installs 
> with a double click and works fine(except for convert-ly, apparently). 
> 
> Frescobaldi 3 does not work out of the box on the Mac; there are a half a 
> dozen dependencies that have to be installed first. The 64-bit version of 
> 2.20 does work well. I haven't gotten around to getting F3 running as 
> obtaining and installing the dependencies on the Mac is kind of a nuisance 
> due to how locked down MacOS is, unless one is using a package manager such 
> as Homebrew, MacPorts, etc. I am not using one of those.
> 
> 
>> On Nov 14, 2019, at 3:20 AM, Jeremiah Reilly  
>> wrote:
>> 
>> 
>> Carl, thanks for both tips.
>> 
>> The Frescobaldi Downloads page states "Install a copy of Lilypond as well." 
>> Not sure how that jives with Catalina.
>> 
>> Sorry to be inept re packages and making from source. I am a musician, not a 
>> developer.
>> 
>> Your help much appreciated.
>> 
>>> On Wed, Nov 13, 2019 at 4:34 PM Carl Sorensen  wrote:
>>> 
>>> 
>>> From: Jeremiah Reilly 
>>> Date: Wednesday, November 13, 2019 at 3:14 AM
>>> To: 
>>> Subject: Mac OS 10.15 Catalina
>>> 
>>> What is the status of running Lilypond under Mac os 10.15 Catalina?
>>> 
>>> Thanks.
>>> 
>>> 
>>> (Apologies if the answer is clearly posted on the website or Lilypond blog. 
>>> I searched 20+ minutes without success. I cannot upgrade to Catalina until 
>>> I know whether Lilypond will run. I found posting for folks running 
>>> Lilypond in a virtual machine or Decker, but that's not my bag.)
>>> 
>>> Search for 64-bit, and you’d find it.  But putting a response on a thread 
>>> with Catalina in a title is probably a good idea.
>>> 
>>> You can get an installable LilyPond package created by Hans Aberg here:
>>> 
>>>  https://www.et.byu.edu/~sorensen/lilypond-devel-2.19.83_2.mpkg
>>> 
>>> There is a 64-bit Frescobaldi installer for Version 2.20: 
>>> 
>>> 
>>> https://github.com/frescobaldi/frescobaldi/releases/download/v2.20.0/Frescobaldi-2.20.0-x86_64.dmg
>>> 
>>> HTH,
>>> 
>>> Carl
>>> 
>>> 
>>> 
> -- next part --
> An HTML attachment was scrubbed...
> URL: 
> 
> 
> --
> 
> Message: 2
> Date: Thu, 14 Nov 2019 15:15:00 +0100
> From: David Kastrup 
> To: David Menéndez Hurtado 
> Cc: Aaron Hill ,  lilypond-user@gnu.org
> Subject: Re: Macro with
> Message-ID: <8736eqee8r@fencepost.gnu.org>
> Content-Type: text/plain; charset=utf-8
> 
> David Menéndez Hurtado  writes:
> 
>> On Thu, 14 Nov 2019 at 1

Re: Mac OS 10.15 Catalina

2019-11-15 Thread Carl Sorensen


From: Allan Kinnaird 
Date: Friday, November 15, 2019 at 2:35 PM
To: 
Subject: Re: Mac OS 10.15 Catalina

So here I am (as I see it) :
My current version of Lilypond is not going to work on my Mac if I upgrade to 
Catalina (v10.15) because of an incomprehensible licence impasse between GNU 
and Apple.
Hans Åberg has provided an installable package ( 
https://www.et.byu.edu/~sorensen/lilypond-devel-2.19.83_2.mpkg ) which runs as 
64-bit on Catalina. It appears that it has problems with convert-ly but is 
otherwise OK. (And Frescobaldi users need to point Frescobaldi preferences 
towards the right version of Lilypond.)
I have downloaded Hans’s file and tried to install it. Unfortunately the 
installer blocked the process, requiring that the OS be 10.15 Catalina - I have 
to go for Catalina before I can test for problems with it.
So, to continue using Lilypond, either I have to stay forever on v2.18.2 and 
have my computer stay forever on OS 10.14, or just go for Catalina, run Hans’s 
installer, and accept what disasters then ensue. (Hans seems a pretty good guy, 
so with luck there won’t be many!)
Geronimo!


Not quite.

You can stay on Mojave, and continue to run LilyPond as a 32-bit binary in all 
of the current versions.  Because we have a darwin SDK that is at least tacitly 
approved by Apple, we can build 32-bit.  We just can’t build 64-bit.

If you want to use Hans’s installable port, you’ll need to jump to Catalina.

One possibility that could avoid the potentially risky jump to Catalina would 
be to get somebody to follow Hans’s MacPorts build instructions on Mojave, and 
verify that it works on Mojave.

But we have enough people saying Hans’s port runs on Catalina that I don’t 
think it’s much of a risk, if all you’re worried about is LilyPond.

Carl




Re: Mac OS 10.15 Catalina

2019-11-15 Thread eBooks



> On Nov 15, 2019, at 2:35 PM, Allan Kinnaird  wrote:
> 
> So here I am (as I see it) :
> My current version of Lilypond is not going to work on my Mac if I upgrade to 
> Catalina (v10.15) because of an incomprehensible licence impasse between GNU 
> and Apple.
> Hans Åberg has provided an installable package ( 
> https://www.et.byu.edu/~sorensen/lilypond-devel-2.19.83_2.mpkg ) which runs 
> as 64-bit on Catalina. It appears that it has problems with convert-ly but is 
> otherwise OK. (And Frescobaldi users need to point Frescobaldi preferences 
> towards the right version of Lilypond.)
> I have downloaded Hans’s file and tried to install it. Unfortunately the 
> installer blocked the process, requiring that the OS be 10.15 Catalina - I 
> have to go for Catalina before I can test for problems with it.
> So, to continue using Lilypond, either I have to stay forever on v2.18.2 and 
> have my computer stay forever on OS 10.14, or just go for Catalina, run 
> Hans’s installer, and accept what disasters then ensue. (Hans seems a pretty 
> good guy, so with luck there won’t be many!)
> Geronimo!

You could also run LilyPond under Linux in a virtual machine on your mac.






Extract measures with function

2019-11-15 Thread Michael Käppler

Hi all,
is there a way to extract some particular measure from a voice through a
music function?
Like

bla = { c4 d e f | d e f g | e f g a }

\someMagicFunction #2 \bla -> d e f g
I would be very happy if someone could point me in the right direction.

Thanks,
Michael



Re: Mac OS 10.15 Catalina

2019-11-15 Thread Mario Bolognani
After having installed Catalina I tried to install Frescobaldi plus LilyPond 
(the 64bit version provided by Hans  Åberg) but, while Frescobaldi 2.20 64bit 
apparently runs normally, I had no success with LilyPond… I am a musician not a 
developer so I’m not able to understand the reasons of this failure. So I am 
back to Mojave and the 32bit versions of Frescobaldi and LilyPond. Waiting for 
good news on the subject.

Best,

Mario Bolognani
www.baroquemusic.it



> Il giorno 15 nov 2019, alle ore 22:35, Allan Kinnaird  
> ha scritto:
> 
> So here I am (as I see it) :
> My current version of Lilypond is not going to work on my Mac if I upgrade to 
> Catalina (v10.15) because of an incomprehensible licence impasse between GNU 
> and Apple.
> Hans Åberg has provided an installable package ( 
> https://www.et.byu.edu/~sorensen/lilypond-devel-2.19.83_2.mpkg 
>  ) which runs 
> as 64-bit on Catalina. It appears that it has problems with convert-ly but is 
> otherwise OK. (And Frescobaldi users need to point Frescobaldi preferences 
> towards the right version of Lilypond.)
> I have downloaded Hans’s file and tried to install it. Unfortunately the 
> installer blocked the process, requiring that the OS be 10.15 Catalina - I 
> have to go for Catalina before I can test for problems with it.
> So, to continue using Lilypond, either I have to stay forever on v2.18.2 and 
> have my computer stay forever on OS 10.14, or just go for Catalina, run 
> Hans’s installer, and accept what disasters then ensue. (Hans seems a pretty 
> good guy, so with luck there won’t be many!)
> Geronimo!
> 
> 
>> On 14 Nov 2019, at 17:00, lilypond-user-requ...@gnu.org 
>>  wrote:
>> 
>> Send lilypond-user mailing list submissions to
>>  lilypond-user@gnu.org 
>> 
>> To subscribe or unsubscribe via the World Wide Web, visit
>>  https://lists.gnu.org/mailman/listinfo/lilypond-user
>> or, via email, send a message with subject or body 'help' to
>>  lilypond-user-requ...@gnu.org
>> 
>> You can reach the person managing the list at
>>  lilypond-user-ow...@gnu.org
>> 
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of lilypond-user digest..."
>> 
>> 
>> Today's Topics:
>> 
>>   1. Re: Mac OS 10.15 Catalina (Tim McNamara)
>>   2. Re: Macro with (David Kastrup)
>>   3. Re: Mac OS 10.15 Catalina (Hans Åberg)
>>   4. Re: Re: Macro with pitches as parameters (Mats Bengtsson)
>>   5. drawing a range reguardless of transposition (Sandro Santilli)
>> 
>> 
>> --
>> 
>> Message: 1
>> Date: Thu, 14 Nov 2019 07:59:26 -0600
>> From: Tim McNamara 
>> To: lilypond-user 
>> Subject: Re: Mac OS 10.15 Catalina
>> Message-ID: <7adb0dd2-f14d-4af2-8f84-8c81c0e58...@bitstream.net>
>> Content-Type: text/plain; charset="utf-8"
>> 
>> Frescobaldi itself does not generate sheet music. You need to install 
>> Lilypond also. In my experience with Catalina, Hans Aberg's .mkpg installs 
>> with a double click and works fine(except for convert-ly, apparently). 
>> 
>> Frescobaldi 3 does not work out of the box on the Mac; there are a half a 
>> dozen dependencies that have to be installed first. The 64-bit version of 
>> 2.20 does work well. I haven't gotten around to getting F3 running as 
>> obtaining and installing the dependencies on the Mac is kind of a nuisance 
>> due to how locked down MacOS is, unless one is using a package manager such 
>> as Homebrew, MacPorts, etc. I am not using one of those.
>> 
>> 
>>> On Nov 14, 2019, at 3:20 AM, Jeremiah Reilly  
>>> wrote:
>>> 
>>> 
>>> Carl, thanks for both tips.
>>> 
>>> The Frescobaldi Downloads page states "Install a copy of Lilypond as well." 
>>> Not sure how that jives with Catalina.
>>> 
>>> Sorry to be inept re packages and making from source. I am a musician, not 
>>> a developer.
>>> 
>>> Your help much appreciated.
>>> 
 On Wed, Nov 13, 2019 at 4:34 PM Carl Sorensen  wrote:
 
 
 From: Jeremiah Reilly 
 Date: Wednesday, November 13, 2019 at 3:14 AM
 To: 
 Subject: Mac OS 10.15 Catalina
 
 What is the status of running Lilypond under Mac os 10.15 Catalina?
 
 Thanks.
 
 
 (Apologies if the answer is clearly posted on the website or Lilypond 
 blog. I searched 20+ minutes without success. I cannot upgrade to Catalina 
 until I know whether Lilypond will run. I found posting for folks running 
 Lilypond in a virtual machine or Decker, but that's not my bag.)
 
 Search for 64-bit, and you’d find it.  But putting a response on a thread 
 with Catalina in a title is probably a good idea.
 
 You can get an installable LilyPond package created by Hans Aberg here:
 
  https://www.et.byu.edu/~sorensen/lilypond-devel-2.19.83_2.mpkg
 
 There is a 64-bit Frescobaldi 

Re: \epsfile

2019-11-15 Thread Martin Tarenskeen




On Fri, 15 Nov 2019, Martin Tarenskeen wrote:

Related issue: When using frescobaldi the syntax help and autocompletion 
balloon gives "\eps-file" instead of "\epsfile". A little bug?


Reported it on github.

https://github.com/frescobaldi/frescobaldi/issues/1213