lilypond --output=directory is not working

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

Re: lilypond --output=directory is not working

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

Re: lilypond --output=directory is not working

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: Absolute temporal positioning of mm-rests

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 cu

Re: lilypond --output=directory is not working

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 > Chang

Re: lilypond --output=directory is not working

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 t

Re: lilypond --output=directory is not working

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 manua

completion heads engraver with sub-measure splitting?

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! T

Re: Frescobaldi’s use of the version statement

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 c

Re: Frescobaldi’s use of the version statement

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

Re: lilypond --output=directory is not working

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

Re: completion heads engraver with sub-measure splitting?

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

Re: lilypond --output=directory is not working

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

Re: completion heads engraver with sub-measure splitting?

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 als

Modify a NoteEvent to RestEvent

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 \disp

fisisis impossible?

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

Re: fisisis impossible?

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 lil

Re: fisisis impossible?

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+0

Re: fisisis impossible?

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+

Re: fisisis impossible?

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 to

Re: fisisis impossible?

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. Bu

RE: that migrating "opus"

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

Re: fisisis impossible?

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 \ra

Re: ScholarLy and Latex

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

Re: lyluatex, call for pre-beta review

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 Marc

Re: ScholarLy and Latex

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 som

Re: lyluatex, call for pre-beta review

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/

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

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 aft

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

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/buil

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

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 i

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

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 sea

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

Re: lilypond --output=directory is not working

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 realiz

Re: lyluatex, call for pre-beta review

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

Re: lyluatex, call for pre-beta review

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

Frescobaldi -> loopMIDI -> Hauptwerk

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) __

Re: Frescobaldi -> loopMIDI -> Hauptwerk

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

Re: that migrating "opus"

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 al

Re: lyluatex, call for pre-beta review

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.lu

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

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 e

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

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 e

Lilypond compile error

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 pag

Re: Lilypond compile error

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

Re: lyluatex, call for pre-beta review

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 func

Re: Modify a NoteEvent to RestEvent

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,