2011/7/23 Br. Athanasius Pelletier
> I need to get the letters for the chords above certain notes in the example
> below. I thought of using markup but I don't know if I can get sharp or flat
> symbols.
You can have any symbol from Feta music font inside markup. Search
for "musical notation i
2011/7/23 Christopher R. Maden :
> Adding print-all-headers = ##t to the \paper{} block causes the book
> part and score titles both to print. However, the book and book part
> titles seem mutually exclusive, and if there is a book part title, the
> book title will not print.
I'm not sure, but is
Dmytro (and Neil),
i've just found this in our archives after failing to write a function
like that myself. This is wonderful! Thank you so much!
I don't believe this isn't in the snippets or, better, in the docs.
Shoud i add a tracker issue?
THANKS!
Janek
On Mon, 30 Aug 2010 09:37:59 +0300 Dm
2011/7/23 Janek Warchoł :
> Dmytro (and Neil),
>
> i've just found this in our archives after failing to write a function
> like that myself. This is wonderful! Thank you so much!
> I don't believe this isn't in the snippets or, better, in the docs.
> Shoud i add a tracker issue?
This is on the
2011/7/23 Xavier Scheuer :
> 2011/7/23 Janek Warchoł :
>> Dmytro (and Neil),
>>
>> i've just found this in our archives after failing to write a function
>> like that myself. This is wonderful! Thank you so much!
>> I don't believe this isn't in the snippets or, better, in the docs.
>> Shoud i ad
Janek
I agree this could be a useful addition to the LilyPond distribution
and the docs (both at the same time, preferably). Broken slurs in
particular are often poor by default and messing with the control
points manually is difficult. So, yes, please add a tracker issue
for
a suggested enha
Dear Keith,
thanks for Your explanations.
I think, the thing with the "skyline-horizontal-padding" should be also a
part of the documentation. At least I didn't find it there.
> I would have thought so, too.
>
> > Unfortunately, it doesn't work.How can I avoid the collision in bar 2
> > without
+1
+1
+1 (Hi Janek ;-) )
Urs
Am 23.07.2011 12:00, schrieb Trevor Daniels:
Janek
I agree this could be a useful addition to the LilyPond distribution
and the docs (both at the same time, preferably). Broken slurs in
particular are often poor by default and messing with the control
points manual
On 07/23/2011 04:40 AM, Janek Warchoł wrote:
> I'm not sure, but isn't bookpart intended to be a page-breaking
> device only? I mean, not a structural level like \score and \book.
It’s not clear to me... the manual says:
> * A `\bookpart' block. A book may be divided into several parts,
> us
Hello Ole,
This was exactly what I was looking for. Thanks!!
Cheers,
Javier
2011/7/22 Ole Schmidt
>
> >
> > I would like to make a lead sheet very schematic and simple. My idea is
> > start from the context Chordnames in order to write every name of the
> chord
> > placed over each measure ov
Thank you so much - that is exactly what I needed!
On Fri, Jul 22, 2011 at 11:12 PM, Bill Mooney wrote:
> Hi Sarah,
> There appears to be a mismatched << immediately after the \score { at line
> 136.
> Commenting it out lets your file compile - whether the result is what you
> want, I don't know
Folks:
I want to typeset the following fragment but I can't get lilypond to
produce the effect I'm looking for. Here's what I've provided
lilypond as input:
\new Staff {
\time 2/2 2 ~
}
The effect I want is arcs drawn between each of the three notes in the
two chords; ties between the 'c'
- Original Message -
From: "ehzone"
To:
Sent: Saturday, July 23, 2011 5:43 PM
Subject: where's the slur? (4 year old question)
Folks:
I want to typeset the following fragment but I can't get lilypond to
produce the effect I'm looking for. Here's what I've provided
lilypond as input
- Original Message -
From: "ehzone"
To: "Phil Holmes"
I've read through the link you provided and it doesn't sound like
there will be solution until 2012! Is there no workaround possible
now?
Please reply-all otherwise the discussion is lost.
For a single slur, you can adjust th
Matthew Collett ihug.co.nz> writes:
>
> On 23/07/2011, at 6:26 am, Ruud van Silfhout wrote:
>
> > I saw that in January of this year a new feature called compoundTime
signatures
> > is introduced in Lilypond. A good effort. compoundTime specified the timing
of
> > each measure. However, for
Hello EH
Separating out the voices instead of the chord construct seems to do
what you want:
\version "2.15.6"
voiceA = { \slurUp e'( d') }
voiceB = { \tieUp c'~ c' }
voiceC = { \tieDown a ~ a }
\new Staff <<
\time 2/2
\voiceA
\voiceB
\voiceC
>>
Experimenting with various combinatio
On 22 July 2011 19:26, Ruud van Silfhout wrote:
> \multiMeter { 6/8 3/4 }
I'm afraid you won't have much luck with this syntax since it would
require several parser changes which would most likely be vetoed.
I'd suggest a music function taking a scheme list as an acceptable
alternative, e.g.,
On 20 July 2011 15:26, Neil Puttock wrote:
> Let me think about it for a bit. I have an idea using a scheme
> engraver which might work.
Here's the scheme engraver if you want to try it out. It's obviously
not as sophisticated as Mike's proposed fix, but it does have the
advantage of aligning
2011/7/22 Ruud van Silfhout :
> I saw that in January of this year a new feature called compoundTime
> signatures
> is introduced in Lilypond. A good effort. compoundTime specified the timing of
> each measure. However, for church music (esp. hymns) this does not suffice.
> What
> you see there i
Villum Sejersen wrote:
>
>
> Separating out the voices instead of the chord construct seems to do
> what you want:
>
> \version "2.15.6"
> voiceA = { \slurUp e'( d') }
> voiceB = { \tieUp c'~ c' }
> voiceC = { \tieDown a ~ a }
>
> \new Staff <<
>\time 2/2
>\voiceA
>\voiceB
>
ehzone gmail.com> writes:
> \new Staff {
>\time 2/2 2 ~
> }
>
> How can I get lilypond to produce the arc between the 'e' and the 'd'?
>
If one pitch moves but the others do not, in the language we use
to describe our music to Lilypond, you have two voices
\new Staff <<
\new Voice
21 matches
Mail list logo
