Re: [OT] Linking to threads in this list Re: Infinite page length
David Wright wrote: [snip] > As you probably know, each email posting has a "unique" Message-ID in > the header, and typically this will be available in replies as the > In-Reply-To header. Earlier Message-IDs may also be included in the > References header. > > Unfortunately, the system that copies the postings onto > http://lists.gnu.org/archive/html/lilypond-user/ strips > these fields from the header, and considers the User-agent > a more important line. Is anyone here seriously interested > that I post with Mutt/1.5.21 (2010-09-15) wheras Urs uses > Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 > Thunderbird/38.5.0? The Message-IDs are certainly more useful. They can still be obtained by using the mboxes from ftp://lists.gnu.org/lilypond-user/ or from the "Subject:" link at http://article.gmane.org/gmane.comp.gnu.lilypond.general/109513 -Felix ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond compile with no midi output
Hi, something like lilypond -e "(set! write-performances-midis (lambda (performances basename . rest) 0))" piece.ly seems to suppress the midi output. (at least in version 2.16.2) Felix ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: can Tuplet #'avoid-slur #'outside?
On 06/12/06 at 04:24pm, Han-Wen Nienhuys wrote: > Mats Bengtsson schreef: > > You could use something like > > \override TupletBracket #'padding = #2 > > but it would of course be nicer if you could convince LilyPond > > to do it automatically by setting some avoid-slur property (I didn't manage > > either). > > slur-engraver.cc hardcodes what interfaces it listens to, and > tuplet-bracket isn't among them. Has anything changed about this in the last years? >From skimming slur-engraver.cc it seems to listen to tuplet_number but not to tuplet_bracket. Why is that? (From experimenting (with 2.16.2) I've also observed that TupletNumber can #'avoid-slur but TupletBracket not.) Felix ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mutopia
On 02/23/13 at 05:58pm, Noeck wrote: > Hi, > > I have some pieces (vocal scores of 3 chorals of Bach's Christmas > Oratorio and in future some more) that I would like to share. > > I got no response from the mutopiaproject. Is there anything new since: > http://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00300.html > > What should I do? Upload it to imslp and forget about mutopia? > Did someone start an official mutopia-collection-git-repository? You can find the official git repository at github at http://github.com/chrissawer/The-Mutopia-Project It should be useful to have a look at the issues and the wiki. Some new pieces have been added via github's pull-requests but not many, yet. So fork the repository and file a pull-request. It won't be forgotten, but it might take some time for it to make it into the official repository. Thanks that you also want to help with updating some pieces. Pieces in very old lilypond syntax make it hard for people to tweak scores from Mutopia to their hearts content. Glen Larsen has described a workflow for updating pieces in the wiki. For updates you won't have to wait that long to find them in the main repository. Felix ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Dealing with almost-repetitive stuff
Something like the following?
\version "2.16.0"
melody = \relative c'' {a4 b c d e1}
\new Staff {
\melody
<<\melody s4\p>>
<<\melody s4-\markup {\italic pizz.}>>
<<\melody {s4\< s2. s1\!}>>
}
Felix
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Scheme music function to expand lyrics
Hi,
how about putting the lyrics into a list and looping over this list?
Like:
\version "2.16.0"
one = \lyricmode {Some text }
two = \lyricmode {more text }
#(define rawlyrics (list #{ \one #} #{ \two #}))
#(define packedlyrics (map (lambda (arg) #{
\new Lyrics \lyricsto "voice" $arg
#}) rawlyrics))
#(define alllyrics (make-simultaneous-music packedlyrics))
\score {
\new Staff <<
\new Voice = "voice" {
\relative c'' {c c }
}
\alllyrics
>>
\layout {}
}
As an alternative to putting the score templates into a music function
one could also use "\include":
score.ily --
\version "2.16.0"
% Score template
\score {
\new Staff <<
\music
}
\layout {}
}
song1.ly ---
\version "2.16.0"
music = \relative c'' c
\include "score.ily"
Felix
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Scheme music function to expand lyrics
On 04/06/13 at 02:14pm, Yannick CHARLES wrote: > Hello ! > > Thank you for your answer and your suggestions. > I plan anyways to use inclusion and to split my code between multiple > files. > My main problem is that the number of verses can vary between songs. But a > solution to this could be to build the list in the lyric file, which is > specific to each song. That sounds good. There is no specific need to know the number of verses, is there? > Then I can use the other functions you suggested me in the template file. > > Thanks a lot I'll look to the code to figure out it's different parts. They were just some (too) minimal examples. I hope you find a nice solution. Felix ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond 2.16+ on WINE 1.0
Hello, > My options are: > > 1. Install Sarge's lilypond package and related software >- this will leave the user stuck in 2005 with LilyPond 2.2.6. > > 2. Try to compile all the prerequisites for a newer LilyPond >- this is a headache because so much is outdated on Sarge >(even the version of Python is too old), and you can't even >get a recent enough version of gcc without bootstrapping it. > > 3. Try to run a newer distro in a chroot environment > - but how long would it be before I hit something that > doesn't get on well with that old 2.4 kernel? > > 4. Use WINE. Is there no way to upgrade the kernel? From what I've read Debian Sarge also ran 2.6.8. Have you tried some (current) lightweight distributions? Felix ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Removing fingerings from the general score
Hi,
using something like
\version "2.16.0"
\notes = \relative c'' {a-. b-3 c-4 d\f}
\score {
\new Voice \with {
\remove "Fingering_engraver"
\remove "New_fingering_engraver"
} \notes
\layout {}
}
you can remove the fingerings from one Voice. To do so for all the
entire score you can use instead the following score block:
\score {
\notes
\layout {
\context {
\Voice
\remove "Fingering_engraver"
\remove "New_fingering_engraver"
}
}
}
Felix
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
lilypond -H
Hello, I've seen that lilypond has an option to print out header fields into separate files. For example "lilypond -H composer piece.ly" will in addition to compiling the piece put the composer header field (if it exists) into piece.composer. It however does only seem to work with the ps/eps/pdf backends. Is that behavior desired? What I would like to have is a way to retrieve for example the composer header field in a short amount of time without having to parse the ly file. Regards, Felix ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Make \upbow an empty command + Segmentation fault
Hi,
say I have a violin part with bowing instructions in a variable. Now I want
to use the same variable in the full orchestral score but the bowing marks
should be suppressed.
\upbow is treated by lilypond as an articulation, but the other
articulations should be unaffected by the suppressing of \upbow.
upbow={}
doesn't work because it breaks things like
a\upbow ~ a
Playing a bit with the definition of \upbow gave me a segfault.
Minimal example:
\version "2.18.0"
upbow = #(make-music 'ArticulationEvent
'articulation-type "upbow" 'types #f)
downbow = \upbow
Anyway, how do I make a command which has no effect at all?
Cheers,
Felix
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Make \upbow an empty command + Segmentation fault
Ok, something like upbow = #(make-music 'PostEvents) works with 2.18.2. But I guess there is a less hacky solution. Felix ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
