Re: adding stand alone text after a score

[Jean-Charles Malahieude]

Le 08/01/2016 18:50, Ryan Michael a écrit :

Hello I have the following score block:


\score {
   \new StaffGroup <<

[...]  >>

\markup {
   \fill-line {
 Hello hello hello
   }
}

   \layout { }
   \midi { }
}


However I get the error:

syntax error, unexpected \markup



Just move your markup outside of the score block.

Cheers,
Jean-Charles


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

adding stand alone text after a score

[Ryan Michael]

Hello I have the following score block:


\score {
  \new StaffGroup <<



<<
  \new Staff \new Voice = "recorder" << \global \recorder >>

>>





<<
  \new Staff \new Voice = "viola" << \global \viola >>

>>
\new Lyrics \lyricsto "viola" \verseOne
  >>


\markup {
  \fill-line {
Hello hello hello
  }
}


  \layout { }
  \midi { }
}


However I get the error:

syntax error, unexpected \markup

Any help appreciated. Thanks!
Ryan.



-- 
ॐ नमः शिवाय
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

how to add header to markup after score

[Ryan Michael]

I have the following basic lilypond layout
\header{
title = "Title of My Piece"
composer = "Ryan Wieghard"
   }

\score{

%score stuff%
}

\pageBreak

\markup{
 %Text  formatting, columns, etc.%
}



I would like to add a header to the markup that follows the score. When I
write:

\header {
  title = "APPENDIX"
}

within the scope of last \markup{}
I get the following error:

*syntax error, unexpected \header*

Thanks for your help!


-- 
ॐ नमः शिवाय
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Microtonal notation - arrows up and down

[Hans Åberg]

> On 8 Jan 2016, at 18:35, Luca Danieli  wrote:

> It works. Unfortunately I can only re-name the existing standard notation.
> What about adding arrow-"ed" accidentals to the already existing ones?

SMuFl  works together with OpenLilyLib. This way one 
can, by using Graham’s regular.ly, for example have single and double up/down 
arrows in E53.



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: how to add header to markup after score

[Thomas Morley]

2016-01-08 20:27 GMT+01:00 Ryan Michael :
> I have the following basic lilypond layout
> \header{
> title = "Title of My Piece"
> composer = "Ryan Wieghard"
>}
>
> \score{
>
> %score stuff%
> }
>
> \pageBreak
>
> \markup{
>  %Text  formatting, columns, etc.%
> }
>
>
>
> I would like to add a header to the markup that follows the score. When I
> write:
>
> \header {
>   title = "APPENDIX"
> }
>
> within the scope of last \markup{}
> I get the following error:
>
> syntax error, unexpected \header
>
> Thanks for your help!
>
>
> --
> ॐ नमः शिवाय
>


Below three possibilities.
- manually: don't use \header at all, spell it out
- semi-manually: refer to a header-field
- use \bookpart

\version "2.18.2"

 manually
%%{
\header{
  title = "Title of My Piece"
  composer = "Ryan Wieghard"
}

\score { \new Staff { c''1 } }

\pageBreak

\markup \column {
  \huge \larger \larger \bold
  \fill-line { "Appendix-I" }
 "Text  formatting, columns, etc."
}
%}

 semi-manually with use of `markupWithHeader'
 from: http://lsr.di.unimi.it/LSR/Item?id=467
%{
#(define-markup-command (markupWithHeader layout props markup) (markup?)
   "Interpret the given markup with the header fields added to the props.
This way, one can re-use the same functions (using fromproperty
#'header:field) in the header block and as top-level markup."
   (let* (
  ;; TODO: If we are inside a score, add the score's local header
block, too!
  ;; Currently, I only use the global header block, stored in $defaultheader
  (scopes (list $defaultheader))
  (alists (map ly:module->alist scopes))
  (prefixed-alist
   (map (lambda (alist)
  (map (lambda (entry)
 (cons
  (string->symbol (string-append "header:"
 (symbol->string
  (car entry
  (cdr entry)))
   alist))
alists))
  (props (append prefixed-alist
 props
 (layout-extract-page-properties layout
 (interpret-markup layout props markup)))


\header{
  title = "Title of My Piece"
  composer = "Ryan Wieghard"
  appendix = "Appendix-II"
}

\score { \new Staff { c''1 } }

\pageBreak

\markup \markupWithHeader \column {
  \huge \larger \larger \bold
  \fill-line { \fromproperty #'header:appendix }
 "Text  formatting, columns, etc."
}
%}

 using bookparts
 this may need to clear some header-fields, otherwise the book-header
 (if any), will step in
%{
\bookpart {
  \header{
title = "Title of My Piece"
composer = "Ryan Wieghard"
  }

  \score { \new Staff { c''1 } }
}

\bookpart {
  \header { title = "Appendix-III" }
  \markup "Text  formatting, columns, etc."
}
%}


HTH,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Microtonal notation - arrows up and down

[Hans Åberg]

> On 8 Jan 2016, at 18:35, Luca Danieli  wrote:

> It works. Unfortunately I can only re-name the existing standard notation.
> What about adding arrow-"ed" accidentals to the already existing ones?

SMuFl  works together with OpenLilyLib. This way one 
can, by using Graham’s regular.ly, for example have single and double up/down 
arrows in E53.



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Snippet: Vertical brace spanning several lyrics lines [addition]

[Thomas Morley]

2016-01-06 12:14 GMT+01:00 Thomas Morley :
> 2016-01-06 10:01 GMT+01:00 Robert Blackstone :
>> Dear list,
>>
>> I found the snippet: "Vertical brace spanning several lyrics lines"
>> (http://lsr.di.unimi.it/LSR/Item?id=265 and
>> http://lsr.di.unimi.it/LSR/Snippet?id=265).
> [...]
>> If yes, is this post sufficient? I'm fairly new in the LilyPond universe and
>> I have no clear idea who manages the snippet repository and  how.
>>
>> Best regards,
>> Robert Blackstone
>
>
> Hi Robert,
>
> this list is fine to announce new snippets and/or get help in usage of them.
> If you observe a bug in a LSR-snippet or want to propose some
> addition, etc, you may post here as well or on the bug-list.
> I think all people with permission to edit snippets are reading both lists.
>
> I'll have a look at your proposal later the day.
>
> Cheers,
>   Harm

Hi Robert,

I added your proposal as a comment to
http://lsr.di.unimi.it/LSR/Item?id=265

Thanks,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Repeat 8va

[H. S. Teoh]

On Fri, Jan 08, 2016 at 04:16:15PM -0600, Christopher R. Maden wrote:
> On 01/08/2016 04:08 PM, John Gourlay wrote:
> >As an exercise in learning to use LilyPond I’m engraving “The
> >Entertainer” by Scott Joplin. In the old published version I’m
> >working from (1902), the score looks like this at measure 22:
> >
> >I’m concerned about the “Repeat 8va”, which I assume means that on
> >the second repetition of this section it should be played an octave
> >higher than the first time. Do you know how to make this happen in
> >LilyPond? I can easily make the LilyPond output simply say “Repeat
> >8va”, but I’d really like LilyPond to know about the octave change,
> >so the midi output of the second repetition is played in the correct
> >octave.
> 
> Generally, once you get into any kind of moderately complicated score,
> you have to concoct your score and MIDI separately, e.g.:
> 
> theTune = c c c c
> 
> theScore = \repeat volta 2 { \theTune }
> 
> theMidi = \theTune \transpose c c' \theTune
> 
> \score{ \theScore \layout{} }
> 
> \score{ \theMidi \midi{} }
> 
> I like to use \articulate in the MIDI block, too, for instance.
[...]

Agreed. Once you get past a certain level of complexity, trying to use
the same score for both layout & midi is an exercise in pain. Almost all
of my scores start out with just a single score block, and end up
needing a separate midi score just so I can do things with the midi that
I don't want represented in the printed score.


T

-- 
Valentine's Day: an occasion for florists to reach into the wallets of nominal 
lovers in dire need of being reminded to profess their hypothetical love for 
their long-forgotten.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Repeat 8va

[Simon Albrecht]

On 08.01.2016 23:08, John Gourlay wrote:
As an exercise in learning to use LilyPond I’m engraving “The 
Entertainer” by Scott Joplin.


Without wanting to spoil your efforts and interest: I’ve only just 
updated the engraving on Mutopia. Since the pull request is still 
pending, you must retrieve the updated version from 
 
(click ‘Raw’ to download the code).
This one doesn’t have a semantically appropriate solution for the 
‘Repeat 8va’. Perhaps you want to add it there?


Best, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Where to look up explanation of syntax

[Joseph N. Srednicki]

I downloaded a Lilypond file from the Mutopia site containing Bach's chorale
prelude O Mensch Bewein.

 

The first measure contains the following:

 

ef8.*5/6 \mordent [f32 ef f] f8. \trill ef32 f g16 af g f32 ef ef8 g16 f |

 

I searched, but I cannot locate the appropriate location the in the Lilypond
documentation that explains the "*5/6" syntax.

 

Can someone point me to this documentation?

 

Thanks.

 

Joe Srednicki

 

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Repeat 8va

[John Gourlay]

As an exercise in learning to use LilyPond I’m engraving “The Entertainer” by 
Scott Joplin. In the old published version I’m working from (1902), the score 
looks like this at measure 22:


I’m concerned about the “Repeat 8va”, which I assume means that on the second 
repetition of this section it should be played an octave higher than the first 
time. Do you know how to make this happen in LilyPond? I can easily make the 
LilyPond output simply say “Repeat 8va”, but I’d really like LilyPond to know 
about the octave change, so the midi output of the second repetition is played 
in the correct octave.

John Gourlay




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Repeat 8va

[Christopher R. Maden]

On 01/08/2016 04:08 PM, John Gourlay wrote:

As an exercise in learning to use LilyPond I’m engraving “The
Entertainer” by Scott Joplin. In the old published version I’m
working from (1902), the score looks like this at measure 22:

I’m concerned about the “Repeat 8va”, which I assume means that on
the second repetition of this section it should be played an octave
higher than the first time. Do you know how to make this happen in
LilyPond? I can easily make the LilyPond output simply say “Repeat
8va”, but I’d really like LilyPond to know about the octave change,
so the midi output of the second repetition is played in the correct
octave.


Generally, once you get into any kind of moderately complicated score, 
you have to concoct your score and MIDI separately, e.g.:


theTune = c c c c

theScore = \repeat volta 2 { \theTune }

theMidi = \theTune \transpose c c' \theTune

\score{ \theScore \layout{} }

\score{ \theMidi \midi{} }

I like to use \articulate in the MIDI block, too, for instance.

~Chris
--
Chris Maden, text nerd  http://crism.maden.org/ >
“If you’ve been a man o’ action, though you’re lying there in traction,
 You will gain some satisfaction thinkin’, ‘Jesus, at least I tried.’”
  — Andy M. Stewart (1952–2015), “Ramblin’ Rover”

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Bravura svg font

[Paul Booker]

David Kastrup  gnu.org> writes:

> 
> Andrew Bernard  gmail.com> writes:
> 
> > Hi Paul,
> >
> > I don’t know if it is by design or not in lilypond, but I incorporate
> > a lot of postscript in my scores and they simply will not render as
> > SVG. So far, I have never had any clear answers about this
> > behaviour. Is it that lilypond can’t do conversion from postscript
> > code in markups and so on to SVG? That would not be surprising.
> 
> Correct.  But one can do a lot using the \path markup which should
> transfer to SVG just fine.


Thanks David, for the clue. 

Between you and the log file, and LSR snippet 623, it seems I chose the
worst possible example to try with the parallelogram.

parallelogram =
  #(ly:make-stencil (list 'embedded-ps
"gsave
  currentpoint translate
  newpath
  -0.3 0 moveto
  -0.3 1.4 1.8 1.3 1.8 0 curveto
  1.7 -1.9 -0.5 -2.5 -0.5 -2.5 curveto . . . etc

Note all the segment names after the coordinates. I missed this before.

But svg backend requires different markup, such as 

customClefStencilTwo = 
  #(ly:make-stencil
`(path 0.1
  `(moveto 0 0
curveto 0 1 0.7 2.5 1.5 1.5
lineto 1.5 -3
closepath)
  'round
  'round
  #t)
 (cons 0 1.5)
 (cons -3 2))

to help conversion to svg.
I'm back in business!

Paul


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Repeat 8va

[mskala]

On Fri, 8 Jan 2016, Christopher R. Maden wrote:
> Generally, once you get into any kind of moderately complicated score, you
> have to concoct your score and MIDI separately, e.g.:
>
> theTune = c c c c
> theScore = \repeat volta 2 { \theTune }
> theMidi = \theTune \transpose c c' \theTune
> \score{ \theScore \layout{} }
> \score{ \theMidi \midi{} }

This is pretty much exactly what I do for a similar instruction in an
original ragtime piece.

It's a shame that LilyPond's requirement to completely evaluate music
expressions immediately, and therefore once and for all, forces this kind
of thing on us.  The natural thing to want to do would be to have an "if
(MIDI) { }" kind of construction at the point in the music where there's a
difference; but that's simply impossible the way LilyPond currently
works.  And so anyone who wants both a printed score and MIDI is forced to
write the whole thing twice over, attempting to keep the two versons
updated relative to each other by hand, with the ability to share code
only at the lowest levels of the hierarchy.

I'm sure that someone will now respond with a claim that the way LilyPond
currently works is actually better for users too, instead of being only a
consequence of behind-the-scenes design issues.

-- 
Matthew Skala
msk...@ansuz.sooke.bc.ca People before principles.
http://ansuz.sooke.bc.ca/

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Repeat 8va

[H. S. Teoh]

On Sat, Jan 09, 2016 at 12:11:48AM -0600, msk...@ansuz.sooke.bc.ca wrote:
> On Fri, 8 Jan 2016, Christopher R. Maden wrote:
> > Generally, once you get into any kind of moderately complicated
> > score, you have to concoct your score and MIDI separately, e.g.:
> >
> > theTune = c c c c
> > theScore = \repeat volta 2 { \theTune }
> > theMidi = \theTune \transpose c c' \theTune
> > \score{ \theScore \layout{} }
> > \score{ \theMidi \midi{} }
> 
> This is pretty much exactly what I do for a similar instruction in an
> original ragtime piece.
> 
> It's a shame that LilyPond's requirement to completely evaluate music
> expressions immediately, and therefore once and for all, forces this
> kind of thing on us.  The natural thing to want to do would be to have
> an "if (MIDI) { }" kind of construction at the point in the music
> where there's a difference; but that's simply impossible the way
> LilyPond currently works.  And so anyone who wants both a printed
> score and MIDI is forced to write the whole thing twice over,
> attempting to keep the two versons updated relative to each other by
> hand, with the ability to share code only at the lowest levels of the
> hierarchy.
[...]

This is not really true. What I usually do is something like this:

music = <<
\new Staff {
a1 b c
\tag #'midi { a8 r b r c r }
\tag #'layout { a4-. b-. c-. }
}
>>

\score {
\removeWithTag #'midi \music
\layout {}
}
\score {
\removeWithTag #'layout \music
\midi {}
}

The \tag #'layout and \tag #'midi lines basically behave like an if
(MIDI) block. This lets you intersperse layout-specific and
midi-specific stuff in the same place, so that you don't forget to
update one after editing the other.


T

-- 
The richest man is not he who has the most, but he who needs the least.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Repeat 8va

[mskala]

On Fri, 8 Jan 2016, H. S. Teoh wrote:
> > It's a shame that LilyPond's requirement to completely evaluate music
> > expressions immediately, and therefore once and for all, forces this
> > kind of thing on us.  The natural thing to want to do would be to have

> This is not really true. What I usually do is something like this:

>   \tag #'midi { a8 r b r c r }
>   \tag #'layout { a4-. b-. c-. }

> The \tag #'layout and \tag #'midi lines basically behave like an if
> (MIDI) block. This lets you intersperse layout-specific and
> midi-specific stuff in the same place, so that you don't forget to
> update one after editing the other.

I've had trouble getting that to work in more complicated situations, such
as when there's nesting involved.  If I want a few notes different inside
\foo (for instance, because of needing to split them into separate voices
for typographical reasons while keeping them in a single voice for MIDI)
but then I want to either repeat \foo in a volta for print, or write out
the repeat to transpose one of them, then using the same tag for both
conditionals is a problem.  That can be worked around in turn by using
more tags, but the complexity steadily increases, and all of it is work I
think the computer should be doing, not the human.

-- 
Matthew Skala
msk...@ansuz.sooke.bc.ca People before principles.
http://ansuz.sooke.bc.ca/

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: how to add header to markup after score

[Jacques Menu]

Hello Harm,

It’s always a pleasure to see Scheme virtuosi at work, thanks!

As is happens, 2.19.33 doesn’t succeed on the semi-manual example:

 Starting lilypond 2.19.33 [MarkupAfterScoresExample.ly]...
Processing 
`/Users/menu/Documents/LaTeX/PartitionsLilypond/MarkupAfterScoresExample.ly'
Parsing...
Interpreting music...
Preprocessing graphical 
objects.../Users/menu/Documents/LaTeX/PartitionsLilypond/MarkupAfterScoresExample.ly:40:4:
 In procedure memoization in expression (let* (block, too! # ...) 
(interpret-markup layout props ...)):
/Users/menu/Documents/LaTeX/PartitionsLilypond/MarkupAfterScoresExample.ly:40:4:
 In file 
"/Users/menu/Documents/LaTeX/PartitionsLilypond/MarkupAfterScoresExample.ly", 
line 39: Bad binding block, in expression (let* (block, too! (scopes (list 
$defaultheader)) (alists (map ly:module->alist scopes)) (prefixed-alist (map 
(lambda (alist) (map (lambda # #) alist)) alists)) (props (append 
prefixed-alist props (layout-extract-page-properties layout 
(interpret-markup layout props markup)).
Exited with return code 1.

JM

> Le 8 janv. 2016 à 22:34, Thomas Morley  a écrit :
> 
> 2016-01-08 20:27 GMT+01:00 Ryan Michael :
>> I have the following basic lilypond layout
>> \header{
>>title = "Title of My Piece"
>>composer = "Ryan Wieghard"
>>   }
>> 
>> \score{
>> 
>> %score stuff%
>> }
>> 
>> \pageBreak
>> 
>> \markup{
>> %Text  formatting, columns, etc.%
>> }
>> 
>> 
>> 
>> I would like to add a header to the markup that follows the score. When I
>> write:
>> 
>> \header {
>>  title = "APPENDIX"
>> }
>> 
>> within the scope of last \markup{}
>> I get the following error:
>> 
>> syntax error, unexpected \header
>> 
>> Thanks for your help!
>> 
>> 
>> --
>> ॐ नमः शिवाय
>> 
> 
> 
> Below three possibilities.
> - manually: don't use \header at all, spell it out
> - semi-manually: refer to a header-field
> - use \bookpart
> 
> \version "2.18.2"
> 
>  manually
> %%{
> \header{
>  title = "Title of My Piece"
>  composer = "Ryan Wieghard"
> }
> 
> \score { \new Staff { c''1 } }
> 
> \pageBreak
> 
> \markup \column {
>  \huge \larger \larger \bold
>  \fill-line { "Appendix-I" }
> "Text  formatting, columns, etc."
> }
> %}
> 
>  semi-manually with use of `markupWithHeader'
>  from: http://lsr.di.unimi.it/LSR/Item?id=467
> %{
> #(define-markup-command (markupWithHeader layout props markup) (markup?)
>   "Interpret the given markup with the header fields added to the props.
> This way, one can re-use the same functions (using fromproperty
> #'header:field) in the header block and as top-level markup."
>   (let* (
>  ;; TODO: If we are inside a score, add the score's local header
> block, too!
>  ;; Currently, I only use the global header block, stored in 
> $defaultheader
>  (scopes (list $defaultheader))
>  (alists (map ly:module->alist scopes))
>  (prefixed-alist
>   (map (lambda (alist)
>  (map (lambda (entry)
> (cons
>  (string->symbol (string-append "header:"
> (symbol->string
>  (car entry
>  (cdr entry)))
>   alist))
>alists))
>  (props (append prefixed-alist
> props
> (layout-extract-page-properties layout
> (interpret-markup layout props markup)))
> 
> 
> \header{
>  title = "Title of My Piece"
>  composer = "Ryan Wieghard"
>  appendix = "Appendix-II"
> }
> 
> \score { \new Staff { c''1 } }
> 
> \pageBreak
> 
> \markup \markupWithHeader \column {
>  \huge \larger \larger \bold
>  \fill-line { \fromproperty #'header:appendix }
> "Text  formatting, columns, etc."
> }
> %}
> 
>  using bookparts
>  this may need to clear some header-fields, otherwise the book-header
>  (if any), will step in
> %{
> \bookpart {
>  \header{
>title = "Title of My Piece"
>composer = "Ryan Wieghard"
>  }
> 
>  \score { \new Staff { c''1 } }
> }
> 
> \bookpart {
>  \header { title = "Appendix-III" }
>  \markup "Text  formatting, columns, etc."
> }
> %}
> 
> 
> HTH,
>  Harm
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Repeat 8va

[David Kastrup]

John Gourlay  writes:

> As an exercise in learning to use LilyPond I’m engraving “The Entertainer” by
> Scott Joplin. In the old published version I’m working from (1902), the score
> looks like this at measure 22:
> *
>
> I’m concerned about the “Repeat 8va”, which I assume means that on the
> second repetition of this section it should be played an octave higher than 
> the
> first time. Do you know how to make this happen in LilyPond? I can easily make
> the LilyPond output simply say “Repeat 8va”, but I’d really like LilyPond to 
> know
> about the octave change, so the midi output of the second repetition is played
> in the correct octave.

Place a

\transposition c''

right at the end of the repeat volta and a \transposition c' outside of
it.

I could imagine that to work.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Where to look up explanation of syntax

[H. S. Teoh]

On Fri, Jan 08, 2016 at 06:30:21PM -0500, Joseph N. Srednicki wrote:
[...]
> I searched, but I cannot locate the appropriate location the in the
> Lilypond documentation that explains the "*5/6" syntax.
> 
> Can someone point me to this documentation?

http://www.lilypond.org/doc/v2.19/Documentation/notation/writing-rhythms#scaling-durations


T

-- 
Everybody talks about it, but nobody does anything about it!  -- Mark Twain

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Manual page breaking causing assertion failure

[Chris Yate]

Hi,
I'm trying to paginate my score nicely and the automatic paging isn't good
enough. So I'm doing all the page breaks manually -- and a certain
situation is causing an assertion failure on compilation:

<< Snippet of output:



MIDI output to `BeiMannernScore.mid'...

Finding the ideal number of pages...

Fitting music on 9 or 10 pages...

This application has requested the Runtime to terminate it in an unusual
way.

Please contact the application's support team for more information.

Assertion failed!

Program: C:\Program Files (x86)\LilyPond\usr\bin\lilypond.exe

File:
/home/gub/NewGub/gub/target/mingw/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/page-breaking.cc,
Line 1180

Expression: ret <= cached_line_details_.size ()

Exited with return code 3.

>>


The problem occurs with the page break on a specific bar. For now I've done
the obvious thing and gone with a working state -- it's not critical.


Happy to push the code up to a Gist for anyone that wishes to debug the
issue. Let me know.


(This is apparently not happening if I build on Linux, only in Windows).

Chris
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Bravura svg font

[paul booker]

Nathan Ho  snappizz.com> writes:

> 
> On 2016-01-07 15:49, Simon Albrecht wrote:
> > 
> > In case others be interested:
> > 
> > Nice and funny  Thanks, Abraham (and Mark)!
> > 
> > Yours, Simon
> 
> There aren't enough novelty music fonts out there. Once I was a kid and 
> I entered "Take Me Out to the Ballgame" in Finale PrintMusic, then 
> edited it in Paint to make the noteheads baseballs and to make the clefs 
> wear little baseball caps.
> 
> Nathan
> 
I'm now trying postscript, drawing the clef of my dreams, but getting the
same problem, works as a png, not as svg. I'm using this cmd command.

"c:\Program Files (x86)\LilyPond\usr\bin\lilypond-windows.exe" -dgui
-dbackend=svg -dpreview file.ly

And my postscript is as per the parallelogram example in Snippets, p.185 in
the pdf version.
The log file offers this.

Layout output to `file.svg'...
warning: missing stencil expression `embedded-ps'
Layout output to `file.preview.svg'...
warning: missing stencil expression `embedded-ps' 

Same bug? Or something else? Any workaround tips would be welcomed.

Regards
Paul




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Rewriting an expression that uses ly:make-simple-closure

[David Kastrup]

Paul Morris  writes:

> Hi all,  Here’s a tricky one…  I’m working on updating a piece from the 
> Mutopia Project[1] (from LilyPond 2.16.1 to 2.19.35) and it uses the 
> following:
>
> centermarkup = {
>   \once \override TextScript.self-alignment-X = #CENTER
>   \once \override TextScript.X-offset =#(ly:make-simple-closure
> `(,+
>   ,(ly:make-simple-closure (list
> ly:self-alignment-interface::centered-on-x-parent))
>   ,(ly:make-simple-closure (list
> ly:self-alignment-interface::x-aligned-on-self
> }
>
> But ly:make-simple-closure is no longer around[2].  So how to rewrite this 
> without it?
>
> It seems to be documented (barely) in the 2.18 extending manual:
> http://www.lilypond.org/doc/v2.18/Documentation/extending/callback-functions.html
>
> Looking in the source code I find the example given there from 
> define-grobs.scm:
>
> (X-offset . ,(ly:make-simple-closure
>   `(,+
> ,(ly:make-simple-closure
>   (list 
> ly:self-alignment-interface::centered-on-x-parent))
> ,(ly:make-simple-closure
>   (list 
> ly:self-alignment-interface::x-aligned-on-self)
>
> and see it has now become the following in 2.19.35:
>
> (X-offset . ,ly:self-alignment-interface::aligned-on-x-parent)

It's probably the same if parent-alignment-X is set to ,CENTER as well.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Bravura svg font

[Andrew Bernard]

Hi Paul,

I don’t know if it is by design or not in lilypond, but I incorporate a lot of 
postscript in my scores and they simply will not render as SVG. So far, I have 
never had any clear answers about this behaviour. Is it that lilypond can’t do 
conversion from postscript code in markups and so on to SVG? That would not be 
surprising.

Andrew


On 8/01/2016, 20:52, "paul booker" 
 wrote:

Same bug? Or something else? 

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: warning for duplicate definitions

[David Kastrup]

Mike Solomon  writes:

> Hey all,
>
> I’m combining several documents into a large book tonight and I am
> positive that I have:
>
> legato = \markup \italic “legato”
>
> in at least 10 documents.  I’d like to consolidate these into a style
> sheet but I’m worried that I’ll miss some, so it’d be useful to issue
> a warning for duplicate definitions in case I miss some.  Is this
> possible?

Not really.  In lily/parser.yy I see

assignment:
assignment_id '=' identifier_init  {
parser->lexer_->set_identifier ($1, $3);
$$ = SCM_UNSPECIFIED;
}
| assignment_id property_path '=' identifier_init {
SCM path = scm_cons (scm_string_to_symbol ($1), $2);
parser->lexer_->set_identifier (path, $4);
$$ = SCM_UNSPECIFIED;
}
| assignment_id '.' property_path '=' identifier_init {
SCM path = scm_cons (scm_string_to_symbol ($1), $3);
parser->lexer_->set_identifier (path, $5);
$$ = SCM_UNSPECIFIED;
}
;

Either hook into the first of those syntax rules, checking for the
existence of the identifier before setting it, or hook into
Lily_lexer::set_identifier itself.

Expect lots of false positives from LilyPond itself...

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Variable names

[David Kastrup]

"H. S. Teoh"  writes:

> On Thu, Jan 07, 2016 at 08:59:22PM +0100, Johan Vromans wrote:
>> I assume there have been discussions on extending the syntax for LP
>> identifiers to include dashes and underscores. My personal opinion is
>> that a non-alpha separator is good to have, but two different
>> separators may quickly become confusing. Is it 'set_variable' or
>> 'set-variable'?
>> 
>> Given the relation between LP and Guile, I'd suggest to only allow the
>> dash and disallow the underscore (by syntax rule, not just by
>> convention).
> [...]
>
> I think extending identifiers to include '-' and '_' is a bad idea. They
> introduce ambiguities in cases like:
>
>   c1\myCustomMarkup_"text"-\pp-\moreCustomMarkup-.

Sigh.  This is an extremely dead horse to beat.  Markups have included -
signs 10 years ago already, engravers have included _ signs 10 years ago
already.  The above is perfectly well interpreted by current LilyPond
which allows - and _ in identifier names even inside of music since
version 2.15.43 in August 2012, as of

commit 70a153b14ba32767e1ecbe680f435bdd533ae819
Author: David Kastrup 
AuthorDate: Sun Jul 29 16:05:10 2012 +0200
Commit: David Kastrup 
CommitDate: Mon Aug 6 01:28:01 2012 +0200

Unify the lexer's idea of words and commands across all modes.

A "word" (a string recognized even when not quoted) and a "command"
(something starting with \ and followed by letters and other folderol,
indicating a Scheme control sequence or similar) get the same syntax
in all modes:

A "word" is a sequence of alphabetic characters possibly containing
single dashes or underlines inside (not at the beginning or end).

A "command" is a "word" preceded by a backslash.


-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: not justify page last score to score

[tisimst]

Martin,

On Fri, Jan 8, 2016 at 4:22 AM, Martin Oboe [via Lilypond] <
ml-node+s1069038n185681...@n5.nabble.com> wrote:

> Buenos dias!
> Soy nuevo por aquí, pero no utilizando frescobaldi.
> Mi intención es aprender más poco a poco sobre la finalización de
> partituras.
> My problema:
> Sé justificar la última pàgina del libro, pero no de cada partitra.
> Aquí dejo más o menos el ejemplo a tratar.
> Gràcias. Si alguien puede escribirme en español se lo agradeceria.
>

Echa un vistazo a esta sección:

http://lilypond.org/doc/v2.18/Documentation/notation/horizontal-spacing-paper-variables.es.html

- Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/not-justify-page-last-score-to-score-tp185681p185690.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

warning for duplicate definitions

[Mike Solomon]

Hey all,

I’m combining several documents into a large book tonight and I am positive 
that I have:

legato = \markup \italic “legato”

in at least 10 documents.  I’d like to consolidate these into a style sheet but 
I’m worried that I’ll miss some, so it’d be useful to issue a warning for 
duplicate definitions in case I miss some.  Is this possible?

Cheers,
MS
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Bravura svg font

[David Kastrup]

Andrew Bernard  writes:

> Hi Paul,
>
> I don’t know if it is by design or not in lilypond, but I incorporate
> a lot of postscript in my scores and they simply will not render as
> SVG. So far, I have never had any clear answers about this
> behaviour. Is it that lilypond can’t do conversion from postscript
> code in markups and so on to SVG? That would not be surprising.

Correct.  But one can do a lot using the \path markup which should
transfer to SVG just fine.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

RE: Microtonal notation - arrows up and down

[Luca Danieli]

Thank you Graham.
I don't understand very much what is written within the page you sent me. But 
from the "quick start" I have understood the basic and was able to implement 
this code:
http://lsr.di.unimi.it/LSR/Snippet?id=786
It works. Unfortunately I can only re-name the existing standard notation.What 
about adding arrow-"ed" accidentals to the already existing ones?
I can read on the "accidental" paragraph of the web-page you have provided:
"Whether or not you want new accidentals, you need a new associative array for 
microtonal tunings."

But really I don't understand where to look about to learn how to create new 
accidentals (instead of just replacing existing ones).
Luca

> Subject: Re: Microtonal notation - arrows up and down
> To: lilypond-user@gnu.org
> From: gbr...@gmail.com
> Date: Wed, 9 Dec 2015 21:18:16 +
> 
> > Date: Wed, 9 Dec 2015 01:05:11 +0100
> > From: Luca Danieli
> 
> > Hello everybody,
> > I found out very few about arrows down and up for microtonal 
> > notation.Neither a quick research on the mailing-list has shown many 
> > results.
> > I found the best example of it in the following page but I hoped to find 
> > some more information on how to set up arrows down and up.
> > http://lsr.di.unimi.it/LSR/Search?q=microtonal
> > Can someone lead me to the right tutorial, if there is any?
> 
> http://x31eq.com/lilypond
> 
> You have to decide what they mean.  Then, set new note names, define the 
> accidentals, and set a base scale, if you need it.  Probably the default 
> or a regular retuning of it will do.
> 
> 
>Graham
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
  ___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: warning for duplicate definitions

[David Wright]

On Fri 08 Jan 2016 at 15:44:32 (+0200), Mike Solomon wrote:
> I’m combining several documents into a large book tonight and I am positive 
> that I have:
> 
> legato = \markup \italic “legato”
> 
> in at least 10 documents.  I’d like to consolidate these into a style sheet 
> but I’m worried that I’ll miss some, so it’d be useful to issue a warning for 
> duplicate definitions in case I miss some.  Is this possible?

Depending on how consistent you are with your syntax, find/grep might help.
I keep the following line in my recall buffer:

find ~/LilyScores ~/LilyLib -name \*ly -exec grep -H -i 'x' {} \; | less

so I can replace the x and do a quick (caseless, -i) search for anything
(-H for the filename when only a single file matches).

You could try something like:

find top-of-sources-tree -name \*ly -exec grep -H '\