Search String: Display: Description: Sort:

Results:

References: [ please (Too many documents hit. Ignored) ] [ /mats: 7079 ]

Total 7079 documents matching your query.

101. Re: Stanza font (score: 8)
Author: HIDDEN
Date: Sat, 09 Aug 2008 16:15:00 +0200
I hope you have read the Learning Manual for LilyPond version 2.11 (which applies almost completely also to version 2.10, but has been heavily revised and improved). This should tell you how to find
/archive/html/lilypond-user/2008-08/msg00208.html (5,747 bytes)

102. Re: acciaccatura grace note coming right before an end volta repeat bracket (score: 8)
Author: HIDDEN
Date: Wed, 25 Jun 2008 17:55:48 +0200
Anthony wrote: On Wed, Jun 25, 2008 at 9:09 AM, Mats Bengtsson <address@hidden> wrote: Just insert the slur the same way as if the acciaccatura note was an ordinary note: \relative c'{ \afterGrace c(
/archive/html/lilypond-user/2008-06/msg00516.html (6,201 bytes)

103. Re: String syntax, Was: substitution with \movement (score: 8)
Author: HIDDEN
Date: Thu, 12 Jun 2008 00:10:56 +0200
Rewriting the parser for such a trivial thing would be a waste of resources. Just get used to typing #, just like {} or ,' or any other piece of lilypond input. The docs are supposed to use #"" all
/archive/html/lilypond-user/2008-06/msg00222.html (8,635 bytes)

104. Re: Roman numeral analysis (score: 8)
Author: HIDDEN
Date: Thu, 12 Jun 2008 00:06:35 +0200
If you search the mailing list archive, you will for example find http://lists.gnu.org/archive/html/lilypond-user/2008-04/msg00127.html which contains an attached example that might be useful. /Mats
/archive/html/lilypond-user/2008-06/msg00221.html (8,975 bytes)

105. Re: Context creation (score: 8)
Author: HIDDEN
Date: Mon, 2 Jun 2008 13:51:12 -0400
If \context allegedly allows one to add notes to an existing context, why does the following example not do so? \version "2.10.33" \new Staff = "mycontext" \relative c' { c4 d e f g2. } \context Staf
/archive/html/lilypond-user/2008-06/msg00034.html (9,774 bytes)

106. Re: Context creation (score: 8)
Author: HIDDEN
Date: Mon, 02 Jun 2008 13:14:42 +0200
Am 02.06.2008 um 12:30 schrieb Mats Bengtsson: Am 02.06.2008 um 09:57 schrieb Valentin Villenave: 2008/6/1 James E. Bailey <address@hidden>: How coincidental. I've been wondering myself about the dif
/archive/html/lilypond-user/2008-06/msg00025.html (8,761 bytes)

107. Re: Context creation (score: 8)
Author: HIDDEN
Date: Mon, 02 Jun 2008 12:30:13 +0200
Am 02.06.2008 um 09:57 schrieb Valentin Villenave: 2008/6/1 James E. Bailey <address@hidden>: How coincidental. I've been wondering myself about the difference between \new and \context. I kinda just
/archive/html/lilypond-user/2008-06/msg00024.html (8,058 bytes)

108. Re: Whole bar rests - in the wrong place (score: 8)
Author: HIDDEN
Date: Fri, 23 May 2008 09:58:40 +0200
If you have a monophonic section in the middle of an otherwise polyphonic piece, you can use the \oneVoice command to get the normal settings for stem directions and rest positions and then \voiceOne
/archive/html/lilypond-user/2008-05/msg00452.html (8,238 bytes)

109. Re: markup in header (score: 8)
Author: HIDDEN
Date: Mon, 14 Apr 2008 17:54:21 +0200
The setting of font-name is a low-level setting which means that the other properties will not even be considered. If you want a bold version of the font, then specify the font name of that version.
/archive/html/lilypond-user/2008-04/msg00454.html (7,861 bytes)

110. Re: combining parts (score: 8)
Author: HIDDEN
Date: Wed, 9 Apr 2008 20:54:37 +0200
Yeah, I got as far as: ErsteStimme = { r2 c''4 d'' g'8 g' g'4 fis' g'4} ZweiteStimme = { g'4 a' r2 e'8 e' d'2 c'4 } DritteStimme = { r2 fis''4 g'' g'8 g' g'4 fis' g'4 } VierteStimme = {c'4 c' r2 e'8
/archive/html/lilypond-user/2008-04/msg00310.html (10,469 bytes)

111. Re: combining parts (score: 8)
Author: HIDDEN
Date: Wed, 09 Apr 2008 20:50:35 +0200
\partcombine will indeed produce Voice contexts. The reason that you get problems is that the names of these Voice contexts is hard-coded, which means that the results of your two \partcombine comman
/archive/html/lilypond-user/2008-04/msg00309.html (9,709 bytes)

112. Re: Parenthesizing rests (score: 8)
Author: HIDDEN
Date: Wed, 26 Mar 2008 15:19:06 +0100
Playing around with \displayMusic, I got a hint on how to obtain a parenthesized rest: \version "2.10.0" \relative c' { c d e 'EventChord 'elements (list (make-music 'RestEvent 'parenthesize 'duratio
/archive/html/lilypond-user/2008-03/msg00459.html (8,051 bytes)

113. Re: Flamenco notation, something for LSR? (score: 8)
Author: HIDDEN
Date: Wed, 19 Mar 2008 09:47:37 +0100
@Mats, is it correct that objects, once 'switched off' with #'stencil = When I try, I get: warning: type check for `stencil' failed; value `#t' must be of type `unknown' Of course it can be switched
/archive/html/lilypond-user/2008-03/msg00380.html (9,409 bytes)

114. Re: Autobeaming with subdivision in 4/4 (score: 8)
Author: HIDDEN
Date: Wed, 05 Mar 2008 23:52:01 +0100
The problem is that you want to beam differently than implied by the time signature you want to write. So you want to beam in what might be described as 8 = (1+1)+(1+1)+(1+1)+(1+1), whereas the comm
/archive/html/lilypond-user/2008-03/msg00148.html (8,904 bytes)

115. Re: Staff spacing and collisions (score: 8)
Author: HIDDEN
Date: Wed, 05 Mar 2008 07:11:11 +0100
Thanks again Mats. I've chosen for a different fix based on something I saw in the LSR. In your buglist code it would be: \version "2.11.41" << \new Staff = up { s1*2 } \new Staff = down \relative c,
/archive/html/lilypond-user/2008-03/msg00128.html (8,905 bytes)

116. Re: Staff spacing and collisions (score: 8)
Author: HIDDEN
Date: Tue, 04 Mar 2008 22:55:46 +0100
Mats, Thanks for your reply, but it's fixed already :) The output was based on an old template I grabbed from the 2.6 documentation. I updated it with the latest piano from the snippets doc; the URL
/archive/html/lilypond-user/2008-03/msg00122.html (8,298 bytes)

117. Re: pedal bracket too short (score: 8)
Author: HIDDEN
Date: Fri, 29 Feb 2008 10:37:47 +0100
I have just tried your example with the latest version of the source code and it seems that the problem remains. It seems related to http://lists.gnu.org/archive/html/lilypond-devel/2008-02/msg00172.
/archive/html/lilypond-user/2008-02/msg00838.html (9,318 bytes)

118. Re: GDP: \articulation and -\articulation (score: 8)
Author: HIDDEN
Date: Fri, 29 Feb 2008 08:52:13 +0100
Graham Percival wrote: That's not specific to articulations, though. For example, dynamics are (normally) always below notes, while slurs depend on the stem direction. I've added a note to mention th
/archive/html/lilypond-user/2008-02/msg00829.html (9,233 bytes)

119. Re: GDP: NR 1.1 comment (score: 8)
Author: HIDDEN
Date: Thu, 28 Feb 2008 10:35:36 +0100
Right! GrandStaff contexts are often used in orchestral scores, for example, to group a number of staves together, such as the string parts. In LilyPond, the GrandStaff and PianoStaff contexts appear
/archive/html/lilypond-user/2008-02/msg00786.html (8,283 bytes)

120. Re: Full bar rests in multi-voiced piano scores -- question and a suggestion (score: 8)
Author: HIDDEN
Date: Mon, 25 Feb 2008 11:54:21 +0100
So far, there's no automatic support in LilyPond to avoid collisions between multi-measure rests and other objects. Their vertical position is determined by the staff-position property, which by defa
/archive/html/lilypond-user/2008-02/msg00673.html (18,236 bytes)


This search system is powered by Namazu