Re: Modify a NoteEvent to RestEvent

[David Kastrup]

paolo prete  writes:

> Hello.
> Do you know how to modify a NoteEvent so that it becomes a RestEvent, or
> (vice-versa) in Scheme?

You can't.

> I tried:
>
> (ly:music-set-property! x 'name 'RestEvent)
>
> The note actually becomes a rest, but I don't know if it's the proper way
> to obtain that, because if I display the scheme object with \displayMusic I
> see (note the duplication of 'RestEvent token):
>
> (make-music
> 'RestEvent
> 'name
> 'RestEvent
> 'duration
> (ly:make-duration 2))

You can create a new, different event taking the original as template.
Like

(make-music 'RestEvent x)

However, do you actually want 'pitch copied here?

-- 
David Kastrup

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

Re: lyluatex, call for pre-beta review

[Urs Liska]

Am 11. März 2018 05:34:50 MEZ schrieb Craig Dabelstein 
:
>Hi all,
>
>Even with this path to my Lilypond:
>
>\usepackage[program=/Applications/LilyPond.app/Contents/
>Resources/bin/lilypond]{lyluatex}
>
>I get this error. I'm still not sure what the problem is.
>
>stack traceback:
>
>[C]: in function 'error'
>
>...ocal/texlive/2017/texmf-dist/tex/latex/base/ltluatex.lua:109: in
>function
><...ocal/texlive/2017/texmf-dist/tex/latex/base/ltluatex.lua:108>
>
>(...tail calls...)
>
>./lyluatex.lua:899: in function 'lilypond_version'
>
>./lyluatex.lua:1114: in function 'run_lilypond'
>
>./lyluatex.lua:1095: in function 'process'
>
>[\directlua]:1: in main chunk.
>
>\ly@compilescore ...directlua {ly.score:process()}
>

What is the output immediately *before* that?

>
>On 11 March 2018 at 13:15, Br. Samuel Springuel 
>wrote:
>
>> That's not the executable script inside the package.  Try:
>>
>>
>> \usepackage[program=/Applications/LilyPond.app/Contents/
>> Resources/bin/lilypond]{lyluatex}
>>
>>
>> Or, follow the directions on the following page for making LilyPond
>> available from the command line on a Mac (in which case the program
>option
>> won't be needed):
>>
>> http://lilypond.org/macos-x.html
>>
>>
>> --
>> ✝
>> Br. Samuel, OSB
>> St. Anselm’s Abbey
>> Washington, DC
>> (R. Padraic Springuel)
>>
>> PAX ☧ ΧΡΙΣΤΟΣ
>>
>>
>> ___
>> 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: Lilypond compile error

[Federico Bruni]

Il giorno dom 11 mar 2018 alle 6:32, Craig Dabelstein 
<"craig.dabelstein"@gmail.com> ha scritto:

Hi all,

This compile error is coming up on one of my parts. All other parts 
compile fine. I can only guess that it's something to do with the 
page breaking but I don't know where to start to try to fix it. Any 
help greatly appreciated.


Craig

Preprocessing graphical objects...
Calculating page and line breaks (6 possible page 
breaks).../home/gub/NewGub/gub/target/darwin-x86/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/page-turn-page-breaking.cc:211: 
failed assertion `!isinf (best.demerits_) && start < end - 1'

Exited with exit status 1.






Hi Craig

I'm afraid that you have to comment part of the input until you can 
find which line is triggering the error.

In this case it should be close to where the page break occurs.




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

Lilypond compile error

[Craig Dabelstein]

Hi all,


This compile error is coming up on one of my parts. All other parts compile
fine. I can only guess that it's something to do with the page breaking but
I don't know where to start to try to fix it. Any help greatly appreciated.


Craig


Preprocessing graphical objects...

Calculating page and line breaks (6 possible page breaks)...
/home/gub/NewGub/gub/target/darwin-x86/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/page-turn-page-breaking.cc:211
<0>: failed assertion `!isinf (best.demerits_) && start < end - 1'

Exited with exit status 1.






-- 
*Craig Dabelstein*
Maxime's Music
craig.dabelst...@gmail.com
*http://maximesmusic.com *
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs

[shane]

At this point shouldn't it be called a feature?
Shane


Sent from my T-Mobile 4G LTE Device
 Original message From: Thomas Morley 
 Date: 3/10/18  7:57 PM  (GMT-05:00) To: Lucas 
Werkmeister  Cc: lilypond-user 
 Subject: Re: Bug? Mismatched grace notes at beginning 
of staff cause extra
clefs in other staffs 
2018-03-11 0:58 GMT+01:00 Lucas Werkmeister :
> Hi everyone,
>
> I found what I suspect is a LilyPond bug, but I’m not sure yet :) minimal
> example:
>
> \version "2.18.2"
>
> <<
>   \new Staff { \grace c' c' }
>   \new Staff { \clef "bass" }
>>>
>
> Instead of beginning with a bass clef, the lower staff begins with a violin
> clef and then has a bass clef right after the time signature. If a different
> key signature is set (omitted in the above example for brevity), the
> accidentals are only printed after that extra clef as well, and the whole
> group (bass clef and accidentals) is shifted to the left so that it overlaps
> the time signature.
>
> This seems to happen when the two staves begin with different amounts of
> grace notes. A workaround is to add a silent grace note to the lower staff
> (\grace s) – just make sure that it’s the same duration as the real grace
> note in the upper staff: if it’s longer (e. g. a simple \grace s without
> explicit duration if the current duration is 4 and the duration of the other
> grace note is 8), then the upper staff will have the same problem instead
> (extra clef – same as the original one in this case – and accidentals only
> after that).
>
> Unfortunately, I’m unable to check if this still happens in the current
> development version of LilyPond since I’m getting an error when building
> from Git, but that’s for a different email :) perhaps someone else can check
> that, so I don’t open a bug report for something that’s already fixed? (Or
> perhaps it’s simply expected that grace notes should be aligned between
> staves? But that would surprise me.)
>
> Oh, and for the sake of people googling for this error – it also affects
> \acciaccatura, \appoggiatura and \slashedGrace.
>
> Cheers,
> Lucas


It's issue 34
https://sourceforge.net/p/testlilyissues/issues/34/
Likely our most infamous bug, not fixed.

The workaround you've found is mentioned in the docs ;)
Search for grace synchronization.

Cheers,
  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: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs

[shane]

At this point shouldn't it be called a feature?
Shane


Sent from my T-Mobile 4G LTE Device
 Original message From: Thomas Morley 
 Date: 3/10/18  7:57 PM  (GMT-05:00) To: Lucas 
Werkmeister  Cc: lilypond-user 
 Subject: Re: Bug? Mismatched grace notes at beginning 
of staff cause extra
clefs in other staffs 
2018-03-11 0:58 GMT+01:00 Lucas Werkmeister :
> Hi everyone,
>
> I found what I suspect is a LilyPond bug, but I’m not sure yet :) minimal
> example:
>
> \version "2.18.2"
>
> <<
>   \new Staff { \grace c' c' }
>   \new Staff { \clef "bass" }
>>>
>
> Instead of beginning with a bass clef, the lower staff begins with a violin
> clef and then has a bass clef right after the time signature. If a different
> key signature is set (omitted in the above example for brevity), the
> accidentals are only printed after that extra clef as well, and the whole
> group (bass clef and accidentals) is shifted to the left so that it overlaps
> the time signature.
>
> This seems to happen when the two staves begin with different amounts of
> grace notes. A workaround is to add a silent grace note to the lower staff
> (\grace s) – just make sure that it’s the same duration as the real grace
> note in the upper staff: if it’s longer (e. g. a simple \grace s without
> explicit duration if the current duration is 4 and the duration of the other
> grace note is 8), then the upper staff will have the same problem instead
> (extra clef – same as the original one in this case – and accidentals only
> after that).
>
> Unfortunately, I’m unable to check if this still happens in the current
> development version of LilyPond since I’m getting an error when building
> from Git, but that’s for a different email :) perhaps someone else can check
> that, so I don’t open a bug report for something that’s already fixed? (Or
> perhaps it’s simply expected that grace notes should be aligned between
> staves? But that would surprise me.)
>
> Oh, and for the sake of people googling for this error – it also affects
> \acciaccatura, \appoggiatura and \slashedGrace.
>
> Cheers,
> Lucas


It's issue 34
https://sourceforge.net/p/testlilyissues/issues/34/
Likely our most infamous bug, not fixed.

The workaround you've found is mentioned in the docs ;)
Search for grace synchronization.

Cheers,
  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: lyluatex, call for pre-beta review

[Craig Dabelstein]

Hi all,

Even with this path to my Lilypond:

\usepackage[program=/Applications/LilyPond.app/Contents/
Resources/bin/lilypond]{lyluatex}

I get this error. I'm still not sure what the problem is.

stack traceback:

[C]: in function 'error'

...ocal/texlive/2017/texmf-dist/tex/latex/base/ltluatex.lua:109: in
function <...ocal/texlive/2017/texmf-dist/tex/latex/base/ltluatex.lua:108>

(...tail calls...)

./lyluatex.lua:899: in function 'lilypond_version'

./lyluatex.lua:1114: in function 'run_lilypond'

./lyluatex.lua:1095: in function 'process'

[\directlua]:1: in main chunk.

\ly@compilescore ...directlua {ly.score:process()}


On 11 March 2018 at 13:15, Br. Samuel Springuel 
wrote:

> That's not the executable script inside the package.  Try:
>
>
> \usepackage[program=/Applications/LilyPond.app/Contents/
> Resources/bin/lilypond]{lyluatex}
>
>
> Or, follow the directions on the following page for making LilyPond
> available from the command line on a Mac (in which case the program option
> won't be needed):
>
> http://lilypond.org/macos-x.html
>
>
> --
> ✝
> Br. Samuel, OSB
> St. Anselm’s Abbey
> Washington, DC
> (R. Padraic Springuel)
>
> PAX ☧ ΧΡΙΣΤΟΣ
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>



-- 
*Craig Dabelstein*
Maxime's Music
craig.dabelst...@gmail.com
*http://maximesmusic.com *
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: that migrating "opus"

[David Wright]

On Sat 10 Mar 2018 at 13:28:20 (-0800), Mark Stephen Mrotek wrote:
> David,
> 
> Thank you for your pointed reply.
> Yes, I did take away something from your explanation.
> I have used it on the previously referenced score.
> My basic question, more operational than technical (I really don't get all of 
> the \scoreTitlemarkup stuff!).
> 
> Why is it that "piece" and "opus" are the only ones beatified to migrate?

Because a musical work "typically" has one title at the top
(cf a novel) and one composer (cf author), whereas each movement
(particularly where they're often performed separately) will be
numbered (cf chapters) and sometimed titled (like children's
stories).

> The process you provide seems a little kludgy to get "opus" behave as it 
> would on a normal score with multiple movements.

I think the example (which BTW I didn't write) was designed to give
you a lot of flexibility without using the \fromproperty method.
If your music is very conventional as just described, then the
default scheme may work for you, as attached (modified from that
example cited).

Cheers,
David.
\version "2.18.2"

\paper {
  #(set-paper-size "a6")
  bookTitleMarkup = \markup \with-color #red \bookTitleMarkup
  scoreTitleMarkup = \markup \with-color #green \scoreTitleMarkup
}

\header {
  title = "Morning Canticles"
  composer = "Edward Elgar (1857–1934)"
}
\score {
  \new ChoirStaff <<
\new Staff { s1 }
\new Staff { \clef "bass" s1 }
  >>
  \header {
opus = "Op.34 no.1 (1897)"
piece = "Te Deum laudamus"
  }
}
\score {
  \new ChoirStaff <<
\new Staff { s1 }
\new Staff { \clef "bass" s1 }
  >>
  \header {
opus = "Op.34 no.2 (1897)"
piece = "Benedictus"
  }
}


titles.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Frescobaldi -> loopMIDI -> Hauptwerk

[Andrew Bernard]

Hi Giampaolo,

Perhaps Frescobaldi is heeding Wittgenstein. [:-)]

Andrew


On 11 March 2018 at 14:17, Giampaolo Orrigo  wrote:

> Anybody tried to do the same?
> I connected everything together but no sound comes out from Frescobaldi.
>
> Thanks!
>
> Giampaolo Orrigo, MBA
>
> "*Whereof one cannot speak, thereof one must be silent"*
>
> (L. Wittgenstein, *Tractatus Logico-Philosophicus, *Proposition 7)
>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Frescobaldi -> loopMIDI -> Hauptwerk

[Giampaolo Orrigo]

Anybody tried to do the same?
I connected everything together but no sound comes out from Frescobaldi.

Thanks!

Giampaolo Orrigo, MBA

"*Whereof one cannot speak, thereof one must be silent"*

(L. Wittgenstein, *Tractatus Logico-Philosophicus, *Proposition 7)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lyluatex, call for pre-beta review

[Br. Samuel Springuel]

That's not the executable script inside the package.  Try:


\usepackage[program=/Applications/LilyPond.app/Contents/Resources/bin/lilypond]{lyluatex}


Or, follow the directions on the following page for making LilyPond 
available from the command line on a Mac (in which case the program 
option won't be needed):


http://lilypond.org/macos-x.html


--
✝
Br. Samuel, OSB
St. Anselm’s Abbey
Washington, DC
(R. Padraic Springuel)

PAX ☧ ΧΡΙΣΤΟΣ

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

Re: lyluatex, call for pre-beta review

[Craig Dabelstein]

Hi Fr. Jacques,

I have this in my code but still can't get lyluatex to find Lilypond.

\usepackage[program=/Applications/LilyPond.app/Contents/MacOS/LilyPond]{lyluatex}

Any other ideas?

Craig


On 11 March 2018 at 09:49, Abbé Jacques Peron 
wrote:

> Hello,
>
> Le 11 mars 2018 00:24:48 GMT+01:00, Craig Dabelstein <
> craig.dabelst...@gmail.com> a écrit :
> >Hi Urs,
> >
> >I can't get it to find my
> >installation of Lilypond. Could you give me an example of the code I
> >need
> >to point lyluatex to a Lilypond installation?
>
> You should use the option "program":
>
> \usepackage[program= PATH/TO/LILYPOND]{lyluatex}
>
> Hoping this helps,
>
> Fr. Jacques Peron +
>



-- 
*Craig Dabelstein*
Maxime's Music
craig.dabelst...@gmail.com
*http://maximesmusic.com *
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond --output=directory is not working

[Andrew Bernard]

 Hi Federico,

Sure enough, on Ubuntu doing this in /tmp fails.

Clearly lilypond is treating /tmp differently to other directories. Sounds
like a defect to me.

Andrew

On 11 March 2018 at 02:47, Federico Bruni  wrote:

>
>
> There's something wrong in my system (Fedora 27)?
> No, I've just realized that this problem occurs only when the output
> directory is within /tmp. Does it happen in Ubuntu as well?
> Can anybody explain why
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs

[Thomas Morley]

2018-03-11 0:58 GMT+01:00 Lucas Werkmeister :
> Hi everyone,
>
> I found what I suspect is a LilyPond bug, but I’m not sure yet :) minimal
> example:
>
> \version "2.18.2"
>
> <<
>   \new Staff { \grace c' c' }
>   \new Staff { \clef "bass" }
>>>
>
> Instead of beginning with a bass clef, the lower staff begins with a violin
> clef and then has a bass clef right after the time signature. If a different
> key signature is set (omitted in the above example for brevity), the
> accidentals are only printed after that extra clef as well, and the whole
> group (bass clef and accidentals) is shifted to the left so that it overlaps
> the time signature.
>
> This seems to happen when the two staves begin with different amounts of
> grace notes. A workaround is to add a silent grace note to the lower staff
> (\grace s) – just make sure that it’s the same duration as the real grace
> note in the upper staff: if it’s longer (e. g. a simple \grace s without
> explicit duration if the current duration is 4 and the duration of the other
> grace note is 8), then the upper staff will have the same problem instead
> (extra clef – same as the original one in this case – and accidentals only
> after that).
>
> Unfortunately, I’m unable to check if this still happens in the current
> development version of LilyPond since I’m getting an error when building
> from Git, but that’s for a different email :) perhaps someone else can check
> that, so I don’t open a bug report for something that’s already fixed? (Or
> perhaps it’s simply expected that grace notes should be aligned between
> staves? But that would surprise me.)
>
> Oh, and for the sake of people googling for this error – it also affects
> \acciaccatura, \appoggiatura and \slashedGrace.
>
> Cheers,
> Lucas


It's issue 34
https://sourceforge.net/p/testlilyissues/issues/34/
Likely our most infamous bug, not fixed.

The workaround you've found is mentioned in the docs ;)
Search for grace synchronization.

Cheers,
  Harm

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

Re: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs

[Lucas Werkmeister]

On 11.03.2018 01:29, Lucas Werkmeister wrote:
> I’m not sure if the clef behavior would still qualify as a bug (in the
> docs, the grace note isn’t at the very beginning of the score, so the
> clef behavior doesn’t happen)
And it turns out this has also been described [1]. I must just have been
searching for the completely wrong terms earlier, because now I found
these two links on the problem within minutes of each other while
searching for a solution to a *different* grace note problem… sorry
again for the noise, I think this thread is really done now.

Cheers,
Lucas

[1]:
https://stackoverflow.com/questions/37037679/lilypond-grace-note-affects-formatting
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs

[Lucas Werkmeister]

On 11.03.2018 00:58, Lucas Werkmeister wrote:
> (Or perhaps it’s simply expected that grace notes should be aligned
> between staves? But that would surprise me.)
Color me surprised, then – I just found this issue mentioned in the docs
[1], with the same workaround I also discovered. I’m not sure if the
clef behavior would still qualify as a bug (in the docs, the grace note
isn’t at the very beginning of the score, so the clef behavior doesn’t
happen) – if not, sorry for the noise :D

Cheers,
Lucas

[1]:
http://lilypond.org/doc/v2.18/Documentation/notation/special-rhythmic-concerns#Known-issues-and-warnings-71
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Build error. MergeFonts: Can't find font: feta11.pfb

[Lucas Werkmeister]

Hi everyone,

I’m getting the following error message when trying to build LilyPond
from git (specifically, building the AUR lilypond-git package).

if test -f out/parmesan-noteheads23.enc; then touch
out/parmesan-noteheads23.enc ; fi
/home/lucas/.cache/pacaur/lilypond-git/src/lilypond/scripts/build/out/gen-emmentaler-scripts
--dir=./out --design-size=11
cat out/feta11.lisp out/parmesan11.lisp out/parmesan-noteheads11.lisp
out/feta-noteheads11.lisp out/feta-flags11.lisp out/feta-alphabet11.lisp
> out/feta11.otf-table
cd ./out && /usr/bin/fontforge -script emmentaler-11.genpe
Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors.
 License GPLv3+: GNU GPL version 3 or later

 with many parts BSD . Please read
LICENSE.
 Based on sources from 23:10 UTC  5-Aug-2017-ML-D.
 Based on source from git with hash:
Cannot open
/home/lucas/.cache/pacaur/lilypond-git/src/lilypond/mf/out/feta11.pfb
The requested file, feta11.pfb, does not exist
MergeFonts: Can't find font: feta11.pfb
Called from...
 emmentaler-11.genpe: line 17
make[1]: *** [GNUmakefile:138: out/emmentaler-11.otf] Error 1
make[1]: Leaving directory
'/home/lucas/.cache/pacaur/lilypond-git/src/lilypond/mf'
make: ***
[/home/lucas/.cache/pacaur/lilypond-git/src/lilypond/stepmake/stepmake/generic-targets.make:6:
all] Error 2

This error was already reported on this list in 2012 [1], also by a user
of the AUR package, but the conclusion back then was that it was a
parallel build problem fixed by reducing make parallelism, which doesn’t
match my situation: my build isn’t parallelized (no -j flags to make),
and yet I got the same error four times in a row. Does anyone have an
idea what might be going on here?

Cheers,
Lucas

[1]: https://lists.gnu.org/archive/html/lilypond-user/2012-03/msg00155.html

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

Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs

[Lucas Werkmeister]

Hi everyone,

I found what I suspect is a LilyPond bug, but I’m not sure yet :)
minimal example:

\version "2.18.2"

<<
  \new Staff { \grace c' c' }
  \new Staff { \clef "bass" }
>>

Instead of beginning with a bass clef, the lower staff begins with a
violin clef and then has a bass clef right after the time signature. If
a different key signature is set (omitted in the above example for
brevity), the accidentals are only printed after that extra clef as
well, and the whole group (bass clef and accidentals) is shifted to the
left so that it overlaps the time signature.

This seems to happen when the two staves begin with different amounts of
grace notes. A workaround is to add a silent grace note to the lower
staff (\grace s) – just make sure that it’s the same duration as the
real grace note in the upper staff: if it’s longer (e. g. a simple
\grace s without explicit duration if the current duration is 4 and the
duration of the other grace note is 8), then the upper staff will have
the same problem instead (extra clef – same as the original one in this
case – and accidentals only after that).

Unfortunately, I’m unable to check if this still happens in the current
development version of LilyPond since I’m getting an error when building
from Git, but that’s for a different email :) perhaps someone else can
check that, so I don’t open a bug report for something that’s already
fixed? (Or perhaps it’s simply expected that grace notes should be
aligned between staves? But that would surprise me.)

Oh, and for the sake of people googling for this error – it also affects
\acciaccatura, \appoggiatura and \slashedGrace.

Cheers,
Lucas

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

Re: lyluatex, call for pre-beta review

[Abbé Jacques Peron]

Hello,

Le 11 mars 2018 00:24:48 GMT+01:00, Craig Dabelstein 
 a écrit :
>Hi Urs,
>
>I can't get it to find my
>installation of Lilypond. Could you give me an example of the code I
>need
>to point lyluatex to a Lilypond installation?

You should use the option "program":

\usepackage[program= PATH/TO/LILYPOND]{lyluatex}

Hoping this helps,

Fr. Jacques Peron +

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

Re: ScholarLy and Latex

[Craig Dabelstein]

Urs,

The "temp-print-message" branch worked perfectly first time. You are
amazing! One small problem for me though -- the output is rendering the
measure and beat with the lilyglyphs ({1}{4.\,\crotchet}). How can I get it
back to just {1}{4} without the lilyglyph? I know I've seen how to do it
somewhere but I just can't find it.

All the best,

Craig


On 11 March 2018 at 09:22, Craig Dabelstein 
wrote:

> Hi Urs,
>
> Thanks very much for all that information. I'll check out the
> "temp-print-message" branch and let you know how I go.
>
> All the best,
>
> Craig
>
>
> On 8 March 2018 at 02:12, Urs Liska  wrote:
>
>> Hi Craig,
>>
>> sorry for the delay, but I had quite reduced capacities during the past
>> week.
>>
>> I'm even more sorry to inform you that what you experience is "expected
>> behaviour" and the result of incomplete implementation :-(
>>
>> The exported annotations put a number of information items (including the
>> message!) in one optional argument, followed by four mandatory arguments
>> with the curly braces.
>>
>>
>> However, in the .sty file the commands are defined to expect six
>> arguments, the first one being optional:
>>
>> \newcommand{\criticalRemark}[6][]{
>> \annotation[#1]{#2}{#3}{#4}{#5}{#6}
>>  {Critical Remark}}
>>
>> This makes \criticalRemark call \annotation, pass its six arguments to it
>> and one hard-coded "Critical Remark" argument as seventh.
>>
>> The code exported from scholarly does not export that sixth argument, and
>> consequently it is empty when it reaches \annotation.
>> As you have noticed, if you copy the entry to the end of the list of
>> arguments it will be printed correctly.
>>
>> I'm not sure what to advise you right now. Your are actually suffering
>> from the fact that I didn't manage to keep hold of the project. In addition
>> to what is "publicly" available there is an "initial LaTeX package" in the
>> repository, on the unmerged branch 'initial-latex-package' with substantial
>> code additions and unfortunately the lack of review on my part. Maybe this
>> branch is actually ready to be merged, but I simply don't really know.
>> And unfortunately I can't promise to change that immediately. Although I
>> should take your report as the incentive to finally get back to that, now
>> that lyluatex is also "out".
>>
>> I have pushed a temporary fix to the temp-print-message branch. If you
>> checkout that branch and recompile the LilyPond score the annotation
>> message will be added to the list of arguments, and your report.sty will
>> properly read in the message.
>> But I don't really like that hack, and you have to be aware that this
>> interface may not be stable.
>>
>> Sorry for not having much better info for you
>> Best
>> Urs
>>
>>
>> Am 02.03.2018 um 10:25 schrieb Craig Dabelstein:
>>
>> Hi Urs,
>>
>> I hope you can understand these files. I think the report.sty file was
>> borrowed from your Scores of Beauty post a long time ago (maybe). My
>> problem is trying to get the content of the "message" field to be
>> displayed.
>>
>> All the best,
>>
>> Craig
>>
>>
>> On 1 March 2018 at 19:05, Urs Liska  wrote:
>>
>>> Hi Craig,
>>>
>>> Am 23.02.2018 um 10:07 schrieb Craig Dabelstein:
>>>
>>> Hi Lilyponders,
>>>
>>> I'm having a minor problem with getting my ScholarLy inp file to work
>>> with Latex. The Latex output for each annotation looks like this:
>>>
>>> \criticalRemark
>>>[grob={DynamicText},
>>> grob-location={Can't display grob location yet},
>>> grob-type={DynamicText},
>>> input-file-name={fluteI.ily},
>>> context-id={Flauto 1},
>>> location={/Users//Maximes_Music/Projects/MM0110/Hallager/critical
>>> edition/Parts/../Notes/fluteI.ily 55:2:2},
>>> type={critical-remark},
>>> message={Added missing \lilyDynamics{p}}]
>>> {18}{6}
>>> {Flauto 1}
>>> {DynamicText}
>>>
>>> And within my Latex file each entry is displayed with this code:
>>>
>>> \noindent
>>> \theAnnotationNo\,)\\
>>> \textit{(#7)}\\
>>> \ifthenelse{\equal{#2}{\value{CurrentMeasure}}}
>>> {}{\textbf{M. #2},
>>> \setcounter{CurrentMeasure}{#2}}%
>>> beat #3\\
>>> #4\\
>>> Affects: #5\\
>>> ``#6''}
>>>
>>> My problem is that Latex won't display the #6 (the contents of the
>>> message field). It is displaying the quotation marks but just empty space
>>> in between. If I cut and paste the message field and add it to the bottom
>>> of the code it displays perfectly correctly:
>>>
>>> \criticalRemark
>>>[grob={DynamicText},
>>> grob-location={Can't display grob location yet},
>>> grob-type={DynamicText},
>>> input-file-name={fluteI.ily},
>>> context-id={Flauto 1},
>>> location={/Users//Maximes_Music/Projects/MM0110/Hallager/critical
>>> edition/Parts/../Notes/fluteI.ily 55:2:2},
>>> type={critical-remark},
>>> message={Added missing \lilyDynamics{p}}]
>>> {18}{6}
>>> {Flauto 1}
>>> {DynamicText}
>>> {Added missing \lilyDynamics{p}}
>>>
>>>
>>> Any ideas where I could be going wrong?
>>>

Re: lyluatex, call for pre-beta review

[Craig Dabelstein]

Hi Urs,

I've had a look at lyluatex. It looks amazing but I can't get it to find my
installation of Lilypond. Could you give me an example of the code I need
to point lyluatex to a Lilypond installation? I assume you are compiling
via command line, not through TexShop or TexPad?

Craig


On 8 March 2018 at 01:26, Urs Liska  wrote:

> lyluatex (https://github.com/jperon/lyluatex) is a package for LuaLaTeX
> that allows the inclusion of LilyPond code in .tex documents and
> automatically manages their compilation with LilyPond.
>
> By now the package is a fully-compatible superset to the lilypond-book
> script that ships with LilyPond, and we are preparing a significant v1
> release. Before uploading a Beta version to CTAN we invite the members of
> this mailing list to thoroughly test and review the package and its
> documentation. Please find the description and a rendered manual at
> https://github.com/jperon/lyluatex/issues/177
>
> Best regards
> Urs (Liska)
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>



-- 
*Craig Dabelstein*
Maxime's Music
craig.dabelst...@gmail.com
*http://maximesmusic.com *
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ScholarLy and Latex

[Craig Dabelstein]

Hi Urs,

Thanks very much for all that information. I'll check out the
"temp-print-message" branch and let you know how I go.

All the best,

Craig


On 8 March 2018 at 02:12, Urs Liska  wrote:

> Hi Craig,
>
> sorry for the delay, but I had quite reduced capacities during the past
> week.
>
> I'm even more sorry to inform you that what you experience is "expected
> behaviour" and the result of incomplete implementation :-(
>
> The exported annotations put a number of information items (including the
> message!) in one optional argument, followed by four mandatory arguments
> with the curly braces.
>
>
> However, in the .sty file the commands are defined to expect six
> arguments, the first one being optional:
>
> \newcommand{\criticalRemark}[6][]{
> \annotation[#1]{#2}{#3}{#4}{#5}{#6}
>   {Critical Remark}}
>
> This makes \criticalRemark call \annotation, pass its six arguments to it
> and one hard-coded "Critical Remark" argument as seventh.
>
> The code exported from scholarly does not export that sixth argument, and
> consequently it is empty when it reaches \annotation.
> As you have noticed, if you copy the entry to the end of the list of
> arguments it will be printed correctly.
>
> I'm not sure what to advise you right now. Your are actually suffering
> from the fact that I didn't manage to keep hold of the project. In addition
> to what is "publicly" available there is an "initial LaTeX package" in the
> repository, on the unmerged branch 'initial-latex-package' with substantial
> code additions and unfortunately the lack of review on my part. Maybe this
> branch is actually ready to be merged, but I simply don't really know.
> And unfortunately I can't promise to change that immediately. Although I
> should take your report as the incentive to finally get back to that, now
> that lyluatex is also "out".
>
> I have pushed a temporary fix to the temp-print-message branch. If you
> checkout that branch and recompile the LilyPond score the annotation
> message will be added to the list of arguments, and your report.sty will
> properly read in the message.
> But I don't really like that hack, and you have to be aware that this
> interface may not be stable.
>
> Sorry for not having much better info for you
> Best
> Urs
>
>
> Am 02.03.2018 um 10:25 schrieb Craig Dabelstein:
>
> Hi Urs,
>
> I hope you can understand these files. I think the report.sty file was
> borrowed from your Scores of Beauty post a long time ago (maybe). My
> problem is trying to get the content of the "message" field to be
> displayed.
>
> All the best,
>
> Craig
>
>
> On 1 March 2018 at 19:05, Urs Liska  wrote:
>
>> Hi Craig,
>>
>> Am 23.02.2018 um 10:07 schrieb Craig Dabelstein:
>>
>> Hi Lilyponders,
>>
>> I'm having a minor problem with getting my ScholarLy inp file to work
>> with Latex. The Latex output for each annotation looks like this:
>>
>> \criticalRemark
>>[grob={DynamicText},
>> grob-location={Can't display grob location yet},
>> grob-type={DynamicText},
>> input-file-name={fluteI.ily},
>> context-id={Flauto 1},
>> location={/Users//Maximes_Music/Projects/MM0110/Hallager/critical
>> edition/Parts/../Notes/fluteI.ily 55:2:2},
>> type={critical-remark},
>> message={Added missing \lilyDynamics{p}}]
>> {18}{6}
>> {Flauto 1}
>> {DynamicText}
>>
>> And within my Latex file each entry is displayed with this code:
>>
>> \noindent
>> \theAnnotationNo\,)\\
>> \textit{(#7)}\\
>> \ifthenelse{\equal{#2}{\value{CurrentMeasure}}}
>> {}{\textbf{M. #2},
>> \setcounter{CurrentMeasure}{#2}}%
>> beat #3\\
>> #4\\
>> Affects: #5\\
>> ``#6''}
>>
>> My problem is that Latex won't display the #6 (the contents of the
>> message field). It is displaying the quotation marks but just empty space
>> in between. If I cut and paste the message field and add it to the bottom
>> of the code it displays perfectly correctly:
>>
>> \criticalRemark
>>[grob={DynamicText},
>> grob-location={Can't display grob location yet},
>> grob-type={DynamicText},
>> input-file-name={fluteI.ily},
>> context-id={Flauto 1},
>> location={/Users//Maximes_Music/Projects/MM0110/Hallager/critical
>> edition/Parts/../Notes/fluteI.ily 55:2:2},
>> type={critical-remark},
>> message={Added missing \lilyDynamics{p}}]
>> {18}{6}
>> {Flauto 1}
>> {DynamicText}
>> {Added missing \lilyDynamics{p}}
>>
>>
>> Any ideas where I could be going wrong?
>>
>>
>> Not yet, but could you please send a MWE, i.e. a complete file, with
>> maybe that critical remark just added in the file (instead of inputted)?
>> What exactly is context of the code that displays the annotation, i.e.
>> where's the complete definition of the "\criticalRemark" macro?
>>
>> Urs
>>
>> Thanks in advance,
>>
>> Craig
>>
>>
>> --
>> *Craig Dabelstein*
>> Maxime's Music
>> craig.dabelst...@gmail.com
>> *http://maximesmusic.com *
>>
>>
>> ___
>> lilypond-user m

Re: fisisis impossible?

[Noeck]

Hi,

you mean like this?

<<
  \new FretBoards \chordmode { bis/gis }
  \new ChordNames \chordmode {
\once\override ChordName.text = \markup \line {
  \concat { "B" \raise #0.8 \small \sharp } "/"
  \concat { "F" \raise #0.8 \small \sharp
\hspace #0.1
\raise #0.8 \fontsize #-0.5 \doublesharp }
}
bis/gis }
>>

Best,
Joram

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

RE: that migrating "opus"

[Mark Stephen Mrotek]

David,

Thank you for your pointed reply.
Yes, I did take away something from your explanation.
I have used it on the previously referenced score.
My basic question, more operational than technical (I really don't get all of 
the \scoreTitlemarkup stuff!).

Why is it that "piece" and "opus" are the only ones beatified to migrate?
The process you provide seems a little kludgy to get "opus" behave as it would 
on a normal score with multiple movements.

Mark


-Original Message-
From: David Wright [mailto:lily...@lionunicorn.co.uk] 
Sent: Friday, March 09, 2018 8:31 PM
To: Mark Stephen Mrotek 
Cc: lilypond-user@gnu.org
Subject: Re: that migrating "opus"

On Thu 08 Mar 2018 at 21:35:34 (-0800), Mark Stephen Mrotek wrote:
> David,
> 
> Very interesting, been there, done that!

Except that the example you just posted doesn't seem to indicate that you took 
anything away from the one already posted in 
http://lists.gnu.org/archive/html/lilypond-user/2017-04/msg00784.html
which you could use as a pattern for your own scores.

> Now I am focusing on Haydn Sonatas - very inventive!
> 
> Mark
> 
> -Original Message-
> From: David Wright [mailto:lily...@lionunicorn.co.uk]
> Sent: Thursday, March 08, 2018 9:20 PM
> To: Mark Stephen Mrotek 
> Cc: 'Lilypond-User Mailing List' 
> Subject: Re: that migrating "opus"
> 
> On Thu 08 Mar 2018 at 16:17:16 (-0800), Mark Stephen Mrotek wrote:
> > I am setting a Haydn piano sonata
> > \version "2.19.80"
> > \header {
> >   title = "Sonata"
> >   composer = "F. J. Haydn"
> >   opus = "XVI:6"
> > }
> > \include "XVI-6-1.ly"
> > \pageBreak
> > \include "XVI-6-2a.ly"
> > \pageBreak
> > \include "XVI-6-2b.ly"
> > \pageBreak
> > 
> > As expected the "opus" migrates to each and every score. The 
> > documentation
> > states:  "only piece and opus fields are printed by default in Score 
> > Titles."
> > 
> > Since I have not, in my limited experience, seen an opus number on 
> > each movement that I have read, I am asking for the rational/purpose 
> > for having the opus migrate.
> 
> If I've got hold of the right end of the stick, imagine you're setting the 
> Brahms opus 118 Klavierstüke, then you would label the six scores thus:
> 
> 1: piece=Intermezzo, opus=opus 118 no 1
> 2: piece=Intermezzo, opus=opus 118 no 2
> 3: piece=Ballade,opus=opus 118 no 3
> 4: piece=Intermezzo, opus=opus 118 no 4
> 5: piece=Romanze,opus=opus 118 no 5
> 6: piece=Intermezzo, opus=opus 118 no 6
> 
> Cheers,
> David.
> 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

Cheers,
David.


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

Re: fisisis impossible?

[bart deruyter]

Hey,

thanks for the info :-) .

I thought about something like that, but now how to get that in
"\chordmode". I make a \chordmode entry for both the chord names and the
diagrams, looks like this would only work on notes.

I know it is a rare situation in which triple sharps and flats are used.

But out of curiousity I looked at the the big shots: finale handles it
without any problem for quite a while (just read a post from 2013:
https://forum.makemusic.com/default.aspx?f=6&m=404097),
and sibelius made it easier (but it was possible earlier) only since 2017
in an update of a plugin (
http://www.sibelius.com/download/plugins/index.html?plugin=411).

So I guess the demand for handling them is there, or they wouldn't develop
it for sure.

grtz
Bart

http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 

2018-03-10 22:08 GMT+01:00 Noeck :

> Hi Bart,
>
> fisisis is not part of the input language (of any defined input
> language). So from this technical point, it can't work.
>
> I wanted to write that there is no symbol for it. But then I found this:
> http://dictionary.onmusic.org/terms/3687-triple_sharp
>
> > Etude no. 10 from Douze etudes dans tous les tons mineur, Op. 39 (1857),
> by Charles-Valentin Alkan.
>
> You can make a fisis look like a fisisis by this override (which can
> surely be made more elegant or turned into a tweak):
>
> \version "2.19.80"
>
> isisis = {
>   \once \override Accidental.stencil = #ly:text-interface::print
>   \once \override Accidental.text = \markup {
> \concat {
>   \musicglyph #"accidentals.sharp"
>   \musicglyph #"accidentals.doublesharp"
> }
>   }
> }
> \relative {
>   \isisis fisis'
> }
>
> It's not impossible that these triple-accidentals could be added to both
> the input language and the music font. However, I am not convinced that
> it should be used :)
>
> Best,
> Joram
>
> ___
> 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: fisisis impossible?

[Noeck]

Hi Bart,

fisisis is not part of the input language (of any defined input
language). So from this technical point, it can't work.

I wanted to write that there is no symbol for it. But then I found this:
http://dictionary.onmusic.org/terms/3687-triple_sharp

> Etude no. 10 from Douze etudes dans tous les tons mineur, Op. 39 (1857), by 
> Charles-Valentin Alkan.

You can make a fisis look like a fisisis by this override (which can
surely be made more elegant or turned into a tweak):

\version "2.19.80"

isisis = {
  \once \override Accidental.stencil = #ly:text-interface::print
  \once \override Accidental.text = \markup {
\concat {
  \musicglyph #"accidentals.sharp"
  \musicglyph #"accidentals.doublesharp"
}
  }
}
\relative {
  \isisis fisis'
}

It's not impossible that these triple-accidentals could be added to both
the input language and the music font. However, I am not convinced that
it should be used :)

Best,
Joram

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

Re: fisisis impossible?

[Ben]

On 3/10/2018 3:44 PM, bart deruyter wrote:
The "why" is described in my mail: showing the logic behind the 
structure of chords.


grtz,
Bart

http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 



Hi Bart,

Ok. I think LilyPond has some issues with triple-sharps. I remember 
reading that it didn't deal with them well, so you may be in a tough 
spot. But this was back a few years...
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fisisis impossible?

[bart deruyter]

The "why" is described in my mail: showing the logic behind the structure
of chords.

grtz,
Bart

http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 

2018-03-10 21:33 GMT+01:00 Ben :

> On 3/10/2018 3:20 PM, bart deruyter wrote:
>
> Hi all,
>
> got in a situation, trying to describe the bis augmented chord in second
> inversion, which would contain fisisis in a slashed chord name.
>
> Lilypond returns an error, unexpected symbol, expecting tonicname pitch,
> which makes me believe that lilypond does not know triple sharps (isisis).
>
> Am I right? Are there solutions for this?
>
> using version 2.19.65 here.
>
> I'm making a list of guitar chord diagrams of triads, and their inversions
> for my students. Using an enharmonic equivalent would fail in showing the
> logic behind the structure of chords, so that wouldn't work for me.
>
> grtz,
> Bart
>
>
> Triple sharps? For a classroom chord chart? Just curious, but why?
>
> http://lilypond.1069038.n5.nabble.com/Triple-b-or-do-
> they-exist-td55106.html
>
>
>
> ___
> 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: fisisis impossible?

[Ben]

On 3/10/2018 3:20 PM, bart deruyter wrote:

Hi all,

got in a situation, trying to describe the bis augmented chord in 
second inversion, which would contain fisisis in a slashed chord name.


Lilypond returns an error, unexpected symbol, expecting tonicname 
pitch, which makes me believe that lilypond does not know triple 
sharps (isisis).


Am I right? Are there solutions for this?

using version 2.19.65 here.

I'm making a list of guitar chord diagrams of triads, and their 
inversions for my students. Using an enharmonic equivalent would fail 
in showing the logic behind the structure of chords, so that wouldn't 
work for me.


grtz,
Bart



Triple sharps? For a classroom chord chart? Just curious, but why?

http://lilypond.1069038.n5.nabble.com/Triple-b-or-do-they-exist-td55106.html


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

fisisis impossible?

[bart deruyter]

Hi all,

got in a situation, trying to describe the bis augmented chord in second
inversion, which would contain fisisis in a slashed chord name.

Lilypond returns an error, unexpected symbol, expecting tonicname pitch,
which makes me believe that lilypond does not know triple sharps (isisis).

Am I right? Are there solutions for this?

using version 2.19.65 here.

I'm making a list of guitar chord diagrams of triads, and their inversions
for my students. Using an enharmonic equivalent would fail in showing the
logic behind the structure of chords, so that wouldn't work for me.

grtz,
Bart


http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Modify a NoteEvent to RestEvent

[paolo prete]

Hello.
Do you know how to modify a NoteEvent so that it becomes a RestEvent, or
(vice-versa) in Scheme?

I tried:

(ly:music-set-property! x 'name 'RestEvent)

The note actually becomes a rest, but I don't know if it's the proper way
to obtain that, because if I display the scheme object with \displayMusic I
see (note the duplication of 'RestEvent token):

(make-music
'RestEvent
'name
'RestEvent
'duration
(ly:make-duration 2))
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: completion heads engraver with sub-measure splitting?

[Kieren MacMillan]

Hi David,

> \score {
>  \new Voice \with { \remove "Note_heads_engraver"
> \consists "Completion_heads_engraver"
> completionUnit = #(ly:make-moment 1/4)
> }
>  { c'8. 8. 8. 8. 4 }
> }

Amazing! Thanks.

Best,
Kieren.

p.s. The answer also happened to come in while we were still working together 
here, so Adam is further impressed with the responsiveness and helpfulness of 
the community. I think we might have a convert here!!  =)


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re: lilypond --output=directory is not working

[Federico Bruni]

Il giorno sab 10 mar 2018 alle 18:18, David Wright 
 ha scritto:

On Sat 10 Mar 2018 at 16:58:37 (+0100), Federico Bruni wrote:



 Il giorno sab 10 mar 2018 alle 16:26, David Wright
  ha scritto:
 >On Sat 10 Mar 2018 at 09:18:59 (+0100), Federico Bruni wrote:
 >> [...]
 >
 >> The documentation in Usage 1,2 is pretty clear:
 >>
 >> -o, --output=FILE or FOLDER
 >
 >I don't recognise this. What is Usage 1,2?

 It's chapter 1.2 of Usage manual.
 Sorry, a typo.. and I should have put a link instead.


Interesting, so the manual and the man page disagree with each other.



Good catch, I've added an issue in the tracker:
https://sourceforge.net/p/testlilyissues/issues/5288/




 No, it's not this.
 See my last email. The problem occurs only in the /tmp directory. It
 happens on Debian as well (not only in Fedora).


That helps. Now we can make comparisons. It isn't just the source file
whose path is forgotten. When LP changes directory to the output
directory, it loses the / at the beginning of the previous working
directory.

[...]


Waiting for comments from developers here.
I've added bug-lilypond in Cc.

Thanks
Federico




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

Re: completion heads engraver with sub-measure splitting?

[David Kastrup]

Kieren MacMillan  writes:

> Hi all,
>
> I have a new-to-the-Pond noviciate who asked me an interesting
> question: Can the completion-heads engraver be tweaked to affect note
> values that don’t cross the barline? For example
>
>   c'8. 8. 8. 8. 4
>
> should come out like
>
>   c'8. 16 ~ 8 8 ~ 16 8. 4
>
> Any thoughts would be appreciated!

\score {
  \new Voice \with { \remove "Note_heads_engraver"
 \consists "Completion_heads_engraver"
 completionUnit = #(ly:make-moment 1/4)
 }
  { c'8. 8. 8. 8. 4 }
}

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

Re: lilypond --output=directory is not working

[David Wright]

On Sat 10 Mar 2018 at 16:58:37 (+0100), Federico Bruni wrote:
> 
> 
> Il giorno sab 10 mar 2018 alle 16:26, David Wright
>  ha scritto:
> >On Sat 10 Mar 2018 at 09:18:59 (+0100), Federico Bruni wrote:
> >> [...]
> >
> >> The documentation in Usage 1,2 is pretty clear:
> >>
> >> -o, --output=FILE or FOLDER
> >
> >I don't recognise this. What is Usage 1,2?
> 
> It's chapter 1.2 of Usage manual.
> Sorry, a typo.. and I should have put a link instead.

Interesting, so the manual and the man page disagree with each other.

> >>Set the default output file to FILE or, if a folder with that
> >> name exists, direct the output to FOLDER, taking the file name from
> >> the input file. The appropriate suffix will be added (e.g. .pdf for
> >> pdf) in both cases.
> >
> >/home/david/lilypond-docs/2.19.80/man1/lilypond.1   3287/3451
> >95%
> >
> >   -o, --output=FILE  write output to FILE (suffix
> >will be added)
> >
> >Perhaps the documentation is running ahead of the program's
> >capabilities?
> >
> >A workaround is to give the full path of test.ly to LP, ie
> >/tmp/test.ly.
> >
> >
> 
> No, it's not this.
> See my last email. The problem occurs only in the /tmp directory. It
> happens on Debian as well (not only in Fedora).

That helps. Now we can make comparisons. It isn't just the source file
whose path is forgotten. When LP changes directory to the output
directory, it loses the / at the beginning of the previous working
directory.

Here's the difference between two runs at the first point of failure:

 stat("/usr/share/lilypond/2.18.2/ly/test.ly", ) = -1 ENOENT (No such file or 
directory)
 stat("test.ly", {st_mode=S_IFREG|0640, st_size=27, ...}) = 0
 stat("pdf", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0
-stat(".", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0
-stat("/tmp/intmp", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0
-stat(".", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0
-stat("/tmp/intmp", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0
+stat(".", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=12288, ...}) = 0
+stat("/tmp", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=12288, ...}) = 0
+stat(".", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=12288, ...}) = 0
+stat("/tmp", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=12288, ...}) = 0
 write(2, "Changing working directory to: `"..., 36Changing working directory 
to: `pdf') = 36
 chdir("pdf")= 0
-stat("/tmp/intmp/init.ly", ) = -1 ENOENT (No such file or directory)
+stat("tmp/init.ly", ) = -1 ENOENT (No such file or directory)
 stat("/usr/share/lilypond/2.18.2/fonts/svg/init.ly", ) = -1 ENOENT (No such 
file or directory)

As you can see, the very first system call after changing directory
has the wrong path, with a missing /.

And the following shows that the error will occur for any top-level
directory, though the only one accessible to most people is /tmp.

 stat("/usr/share/lilypond/2.18.2/ly/test.ly", ) = -1 ENOENT (No such file or 
directory)
 stat("test.ly", {st_mode=S_IFREG|0640, st_size=27, ...}) = 0
 stat("pdf", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0
-stat(".", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0
-stat("/tmp/intmp", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0
-stat(".", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0
-stat("/tmp/intmp", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0
+stat(".", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
+stat("/nonce", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
+stat(".", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
+stat("/nonce", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
 write(2, "Changing working directory to: `"..., 36Changing working directory 
to: `pdf') = 36
 chdir("pdf")= 0
-stat("/tmp/intmp/init.ly", ) = -1 ENOENT (No such file or directory)
+stat("nonce/init.ly", )   = -1 ENOENT (No such file or directory)
 stat("/usr/share/lilypond/2.18.2/fonts/svg/init.ly", ) = -1 ENOENT (No such 
file or directory)

BTW I'll just point out, for strace aficionados, that I have passed its
output through a filter that strips any string resembling 0xdefaced (ie hex).

Cheers,
David.

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

Re: Frescobaldi’s use of the version statement

[Urs Liska]

Am 10.03.2018 um 17:12 schrieb David Wright:

On Fri 09 Mar 2018 at 23:02:53 (+0100), Simon Albrecht wrote:

On 09.03.2018 17:13, David Wright wrote:

You can even use Frescobaldi's option "Automatically choose LilyPond version

>from document".
Ouch. I hadn't come across that one. Sounds really bad to me.
a) you're not really in control of what's running,

Huh? You can choose which of the LilyPond versions (that you have
installed) you make available to Frescobaldi. Then you start on a
project, and by typing the \version statement you also tell
Frescobaldi which LilyPond version to compile it with (assuming that
version is installed – fallback options are handled gracefully). In
the ‘terrible’ case that the version specified by the version
statement or the one chosen by Frescobaldi isn’t the one you wanted
to compile it with, you’d be able to see in the log panel.
I don’t see any problem with that.

When the problem under discussion appears to be one of versioning,
it doesn't seem a wise course of action to add one more method of
having version changes made under ones feet.


b) what happening when all the includes have different version numbers,

Frescobaldi will always go after the first one.

In the case cited, the problem started when the OP was running old
source files. If there were includes of, say, a user's collection
of .ily files, then one is inviting more wasted runs due to
"program too old" errors.


c) it sends a misleading message to a naive user that \version
statements are meant to*do*  something, when that is not their function.

Just for interest, here are the version statements from the files
installed by lilypond-2.19.80-1.linux-64.sh

\version "2.14.0"
\version "2.16.0"
\version "2.17.25"
\version "2.17.6"
\version "2.18.2"
\version "2.19.16"
\version "2.19.22"
\version "2.19.25"
\version "2.19.29"
\version "2.19.46"
\version "2.19.80"

Development policy states that the \version statements will only be
updated when the file is actually changed. So all this means is that
some .ly file in the source code has been around without change
since 2.14.0, some were updated quite recently, etc.

Yes, I was aware of that. The point I was making was that any
collection of *ly files is likely to contain a variety of version
statements, and the one selected from a particular source file might
not be appropriate for all the files that get compiled in that run.


Frescobaldi will (if that option is enabled) check the version statement 
in the file that is passed to LilyPond, i.e. the one that is "compiled". 
It will then choose that version or the next higher that is registered 
(which can be considered the closest match).


Whether all directly or implicitly included files match that version or 
are even compatible isn't the problem of Frescobaldi but that of the 
document author. (Actually I don't use the function and generally use 
the latest LilyPond version I have).


But I agree that in a situation like the current it wouldn't be a good 
idea to use that heuristics (but I don't think that's what Simon was 
actually suggesting anyway ...).


Urs


Cheers,
David.

___
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: Frescobaldi’s use of the version statement

[David Wright]

On Fri 09 Mar 2018 at 23:02:53 (+0100), Simon Albrecht wrote:
> On 09.03.2018 17:13, David Wright wrote:
> >>You can even use Frescobaldi's option "Automatically choose LilyPond version
> >>from document".
> >Ouch. I hadn't come across that one. Sounds really bad to me.
> >a) you're not really in control of what's running,
> 
> Huh? You can choose which of the LilyPond versions (that you have
> installed) you make available to Frescobaldi. Then you start on a
> project, and by typing the \version statement you also tell
> Frescobaldi which LilyPond version to compile it with (assuming that
> version is installed – fallback options are handled gracefully). In
> the ‘terrible’ case that the version specified by the version
> statement or the one chosen by Frescobaldi isn’t the one you wanted
> to compile it with, you’d be able to see in the log panel.
> I don’t see any problem with that.

When the problem under discussion appears to be one of versioning,
it doesn't seem a wise course of action to add one more method of
having version changes made under ones feet.

> >b) what happening when all the includes have different version numbers,
> 
> Frescobaldi will always go after the first one.

In the case cited, the problem started when the OP was running old
source files. If there were includes of, say, a user's collection
of .ily files, then one is inviting more wasted runs due to
"program too old" errors.

> >c) it sends a misleading message to a naive user that \version
> >statements are meant to*do*  something, when that is not their function.
> >
> >Just for interest, here are the version statements from the files
> >installed by lilypond-2.19.80-1.linux-64.sh
> >
> >\version "2.14.0"
> >\version "2.16.0"
> >\version "2.17.25"
> >\version "2.17.6"
> >\version "2.18.2"
> >\version "2.19.16"
> >\version "2.19.22"
> >\version "2.19.25"
> >\version "2.19.29"
> >\version "2.19.46"
> >\version "2.19.80"
> 
> Development policy states that the \version statements will only be
> updated when the file is actually changed. So all this means is that
> some .ly file in the source code has been around without change
> since 2.14.0, some were updated quite recently, etc.

Yes, I was aware of that. The point I was making was that any
collection of *ly files is likely to contain a variety of version
statements, and the one selected from a particular source file might
not be appropriate for all the files that get compiled in that run.

Cheers,
David.

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

completion heads engraver with sub-measure splitting?

[Kieren MacMillan]

Hi all,

I have a new-to-the-Pond noviciate who asked me an interesting question: Can 
the completion-heads engraver be tweaked to affect note values that don’t cross 
the barline? For example

  c'8. 8. 8. 8. 4

should come out like

  c'8. 16 ~ 8 8 ~ 16 8. 4

Any thoughts would be appreciated!

Thanks,
Kieren (and Adam).


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re: lilypond --output=directory is not working

[Federico Bruni]

Il giorno sab 10 mar 2018 alle 16:26, David Wright 
 ha scritto:

On Sat 10 Mar 2018 at 09:18:59 (+0100), Federico Bruni wrote:

 [...]



 The documentation in Usage 1,2 is pretty clear:

 -o, --output=FILE or FOLDER


I don't recognise this. What is Usage 1,2?


It's chapter 1.2 of Usage manual.
Sorry, a typo.. and I should have put a link instead.





Set the default output file to FILE or, if a folder with that
 name exists, direct the output to FOLDER, taking the file name from
 the input file. The appropriate suffix will be added (e.g. .pdf for
 pdf) in both cases.


/home/david/lilypond-docs/2.19.80/man1/lilypond.1   3287/3451 
   95%


   -o, --output=FILE  write output to FILE (suffix 
will be added)


Perhaps the documentation is running ahead of the program's 
capabilities?


A workaround is to give the full path of test.ly to LP, ie 
/tmp/test.ly.





No, it's not this.
See my last email. The problem occurs only in the /tmp directory. It 
happens on Debian as well (not only in Fedora).





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

Re: lilypond --output=directory is not working

[Federico Bruni]

Il giorno sab 10 mar 2018 alle 9:27, Andrew Bernard 
<"andrew.bernard"@gmail.com> ha scritto:

Hi Federico,

Works as described on 2.19.81. [Ubuntu linux.]



In fact I remember I used it in the past without any problem.

There's something wrong in my system (Fedora 27)?
No, I've just realized that this problem occurs only when the output 
directory is within /tmp. Does it happen in Ubuntu as well?

Can anybody explain why?




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

Re: lilypond --output=directory is not working

[David Wright]

On Sat 10 Mar 2018 at 09:18:59 (+0100), Federico Bruni wrote:
> Hi folks
> 
> I'm puzzled by this error. What I'm doing wrong?
> 
> [tmp]$ mkdir pdf
> [tmp]$ cat test.ly
> \version "2.18.2"
> 
> { c1 }
> 
> [tmp]$ ls pdf
> [tmp]$
> [tmp]$ lilypond --output=pdf test.ly
> GNU LilyPond 2.19.81
> Changing working directory to: `pdf'
> Processing `test.ly'
> Parsing...
> /usr/share/lilypond/2.19.81/ly/init.ly:43:1: error: cannot find
> file: `test.ly'
> (search path: 
> `/tmp:/usr/share/lilypond/2.19.81/fonts/svg/:/usr/share/lilypond/2.19.81/fonts/type1/:/usr/share/lilypond/2.19.81/fonts/otf/:/usr/share/lilypond/2.19.81/scm:/usr/share/lilypond/2.19.81/ps:/usr/share/lilypond/2.19.81/ly:')
> 
> \maininput
> test.ly:1: warning: no \version statement found, please add
> 
> \version "2.19.81"
> 
> for future compatibility
> fatal error: failed files: "test.ly"
> [tmp]$
> [tmp]$
> [tmp]$ ls -l pdf
> total 0
> 
> 
> Why it's changing working directory to pdf before running test.ly?

So that LP's output ends up there. I do that in my own lily function,
only I remember to keep hold of the source file's path BEFORE I go
there. Here it appears not to.

> The documentation in Usage 1,2 is pretty clear:
> 
> -o, --output=FILE or FOLDER

I don't recognise this. What is Usage 1,2?

>Set the default output file to FILE or, if a folder with that
> name exists, direct the output to FOLDER, taking the file name from
> the input file. The appropriate suffix will be added (e.g. .pdf for
> pdf) in both cases.

/home/david/lilypond-docs/2.19.80/man1/lilypond.1   3287/345195%

   -o, --output=FILE  write output to FILE (suffix will be 
added)

Perhaps the documentation is running ahead of the program's capabilities?

A workaround is to give the full path of test.ly to LP, ie /tmp/test.ly.

Cheers,
David.

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

Re: Absolute temporal positioning of mm-rests

[Malte Meyn]

Am 09.03.2018 um 11:45 schrieb Arttu Punkkinen:


I was wondering, if there is a way to specify a multimeasure rest which 
length is only relatively defined so that it ends at predetermined bar 
number?


I often find myself needing to adjust or add material between 
multimeasure rests, which currently need manual adjustment to keep 
alignment.


Not for bar numbers but for “anchors” that can be placed in a separate 
music expression, you could use the code below. You find the file 
alignTo.ily attached. This is a modified version of the file posted 
here: http://lists.gnu.org/archive/html/lilypond-user/2015-07/msg00235.html


The following commands are defined:
• \anchor, to be used as
\anchor "anchorname"
• \until, to be used as
s \until "anchorname"
or
R \until "anchorname"
or even
f \until "anchorname"
The latter for long notes is probably useful only if you use the 
Completion_heads_engraver.

• \quoteUntil, to be used as
\quoteUntil "instrument" "anchorname"
Here you have to use \alignTo in the \addQuote command for correct results.
• \alignTo and \useAndAlignTo, to be used as
\alignTo \anchormusic \music
The former only makes use of the anchors, the latter also uses the music 
of \anchormusic (f. e. key signature changes).


Thanks to the original authors!

%%%

\version "2.19.81"

\include "alignTo.ily"

global = {
  \key es \major
  s1*3
  \anchor "1st theme"
  \time 3/4
  s2.*8
  \anchor "mid"
  s2.*4
  \anchor "coda"
  \tempo "Coda"
  s2. \bar "|."
}

flute = \relative {
  R \until "1st theme"
  es'4 f g as bes c d2.
  s \until "mid"
  es4 d c bes as g f es f es2.
}
\addQuote "flute" \alignTo \global \flute

clarinet = \relative {
  \transposition bes
  c'1
  R \until "mid"
  es4 f g as bes c
  \quoteUntil "flute" "coda"
  es2.
}
\addQuote "clarinet" \alignTo \global \clarinet

\new StaffGroup <<
  \new Staff \useAndAlignTo \global \flute
  \new Staff \transpose bes c' \useAndAlignTo \global \clarinet
>>
\version "2.19.25"

#(define anchor-color blue)

% slightly modified/improved version of
% alignTo from 
http://lists.gnu.org/archive/html/lilypond-user/2015-07/msg00235.html
alignTo =
#(define-music-function (conductor music) (ly:music? ly:music?)
   "Lengthen any note or rest in the sequence MUSIC just before each tag
that matches a tag in the sequence CONDUCTOR, so that the tags occur
at the same times from to the beginnings of MUSIC and CONDUCTOR."
   (define (find-sequence music)
 (or (fold-some-music
  (lambda (x) (music-is-of-type? x 'sequential-music))
  (lambda (x e1) (or e1 ; use the first nonempty sequence
 (let ((es (ly:music-property x 'elements)))
   (if (null? es) #f es
  #f
  music)
 (begin
  (ly:input-warning (ly:music-property music 'origin)
"alignTo: cannot find sequential music")
  '(
   (let loop ((aligner (find-sequence conductor))
  (alignee (find-sequence music))
  (time-left (ly:music-length conductor)))
 (case (length alignee)
   ((0) music)
   ((1) music)
   (else
(let* ((a (first alignee)) ; music that might be lengthened,
(b (second alignee)) ; if this music is tagged
; if a has an until property, add this to tag (which is b’s 
tags)
(tag (if (not (null? (ly:music-property a 'until)))
 (cons (ly:music-property a 'until)
   (ly:music-property b 'tags))
 (ly:music-property b 'tags)))
(tail (and (not (null? tag))
   (find-tail
(lambda (x)
  (not (null? (lset-intersection
   eq? tag
   (ly:music-property x 'tags)
aligner
  (if tail
  (let ((tail-length (ly:music-length
  (make-sequential-music tail
(if (ly:moment>
   #})

anchor =
#(define-music-function (text) (string?)
   (if (ly:get-option 'point-and-click)
   #{
 \tag #(string->symbol text)
 \single \override RehearsalMark.self-alignment-X = #LEFT
 \mark \markup \with-color #anchor-color #text
   #}
   #{
 \tag #(string->symbol text) s1*0
   #}))

until =
#(define-music-function (anchor) (string?)
   #{
 \tag #(string->symbol anchor) s1*0
   #})

% don’t redefine quoteUntil if advancedQuote.ily was included before
% because of different transposition behaviour
#(if (not (defined? 'quoteUntil))
 (define quoteUntil
   (define-music-function (what anchor) (string? string?)
 (make-music 'QuoteMusic
   'until (string->symbol anchor)
   'quoted-music-name wha

Re: lilypond --output=directory is not working

[Andrew Bernard]

Hi Federico,

Works as described on 2.19.81. [Ubuntu linux.]

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

Re: lilypond --output=directory is not working

[Andrew Bernard]

Hi Federico,

Is  some reserved word in the option parsing perhaps?

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

lilypond --output=directory is not working

[Federico Bruni]

Hi folks

I'm puzzled by this error. What I'm doing wrong?

[tmp]$ mkdir pdf
[tmp]$ cat test.ly
\version "2.18.2"

{ c1 }

[tmp]$ ls pdf
[tmp]$
[tmp]$ lilypond --output=pdf test.ly
GNU LilyPond 2.19.81
Changing working directory to: `pdf'
Processing `test.ly'
Parsing...
/usr/share/lilypond/2.19.81/ly/init.ly:43:1: error: cannot find file: 
`test.ly'
(search path: 
`/tmp:/usr/share/lilypond/2.19.81/fonts/svg/:/usr/share/lilypond/2.19.81/fonts/type1/:/usr/share/lilypond/2.19.81/fonts/otf/:/usr/share/lilypond/2.19.81/scm:/usr/share/lilypond/2.19.81/ps:/usr/share/lilypond/2.19.81/ly:')


\maininput
test.ly:1: warning: no \version statement found, please add

\version "2.19.81"

for future compatibility
fatal error: failed files: "test.ly"
[tmp]$
[tmp]$
[tmp]$ ls -l pdf
total 0


Why it's changing working directory to pdf before running test.ly?


The documentation in Usage 1,2 is pretty clear:

-o, --output=FILE or FOLDER

   Set the default output file to FILE or, if a folder with that name 
exists, direct the output to FOLDER, taking the file name from the 
input file. The appropriate suffix will be added (e.g. .pdf for pdf) in 
both cases.





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