Am 12.07.2013 03:10, schrieb Thomas Morley:
Hi Urs,
I was annoyed by the loads of warnings for beamed half notes.
I was annoyed too, but unfortunately I'm still way from being able to
fix that myself.
Therefore I wrote some code to avoid that:
\version "2.16.2"
#(define delete-beams-for-cer
Am 12.07.2013 00:35, schrieb Thomas Morley:
2013/7/11 Urs Liska :
Am 11.07.2013 23:19, schrieb Thomas Morley:
[...]
Please use 2.16-syntax, if you declare \version "2.16.2" in
building-blocks-start.ly
or change the version.
Hm, actually I thought about that.
I never used 2.16 so it would mean
Am 11.07.2013 23:19, schrieb Thomas Morley:
Don't use \set in \layout { \context { ... } }
Oh, wow. That also solved the line-count issue!
Urs
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
2013/7/12 Urs Liska :
> Am 12.07.2013 03:10, schrieb Thomas Morley:
>
>
> Hi Urs,
>
> I was annoyed by the loads of warnings for beamed half notes.
>
> I was annoyed too, but unfortunately I'm still way from being able to fix
> that myself.
>
> Therefore I wrote some code to avoid that:
>
> \versio
On Thu, Jul 11, 2013 at 2:06 PM, Paul Scott wrote:
> Does anyone know of a score for Donizzeti's Il Duca d'Alba or in
> particular for "Angelo casto e bel?" A rental source would be fine.
> I realize that that opera wasn't completed by Donizetti and has an
> interesting history.
>
> The Southern
As some of you will have noticed, Janek yesterday published an article
on lilypondblog.org announcing that he intends to make a considerable
effort substantially improving LilyPond's tie formatting - one of the
fields Lily really can use some updates.
After having collected countless examples of
Urs Liska writes:
> As some of you will have noticed, Janek yesterday published an article
> on lilypondblog.org announcing that he intends to make a considerable
> effort substantially improving LilyPond's tie formatting - one of the
> fields Lily really can use some updates.
> After having coll
Sebastian,
So the issue is that in mm. 3-4, the alto lyrics are on a second line? I
think this is intentional...each Lyrics context is given a dedicated line
on a system. To do what you would want, you would need to combine the
Lyrics and set the associated voice (which, given the non-overlapping
Check
http://lilypond.org/doc/v2.16/Documentation/notation/techniques-specific-to-lyrics#placing-lyrics-vertically
--
Phil Holmes
- Original Message -
From: Sebastian Canagaratna
To: lilypond-user@gnu.org
Cc: carlopeter...@gmail.com ; m...@philholmes.net
Sent: Friday, July
Hi, I'm very new to lilypond and trying to hack my way to a
score for a small brazilian percussion ensemble. Actually the visive
output is fine for now, there's just one piece of code I don't
understand.
To achieve a staff with two lines for an agogo bell, I used the example
for woodblocks in the
This sample causes 2.17.20-1 on Mac OS X 10.8.4 to loop forever after producing:
Traitement de « /Users/menu/Documents/LaTeX/PartitionsLilypond/AwfulTies.ly »
Analyse...
Interprétation en cours de la musique...
Interprétation en cours de la musique...[8][16][16]
Pré-traitement des éléments graphi
Is there a way of shifting dynamics away from the staff when you're using a
dynamics context?
\new Score {
<<
\new Staff \relative c'' {
c4 c c c |
c c c c |
}
\new Dynamics {
\override DynamicLineSpanner.staff-padding = #20
s4 s \f s s
\override DynamicLineSpanner.staff-paddin
2013/7/12 jboogie :
> Hi, I'm very new to lilypond and trying to hack my way to a
> score for a small brazilian percussion ensemble. Actually the visive
> output is fine for now, there's just one piece of code I don't
> understand.
>
> To achieve a staff with two lines for an agogo bell, I used the
Hi Harm, Hi David,
Here's what can be done as a first step, just to go a little further even
if, for sure, that does not solve our calculation problem.
The idea is to make as many conditions as staff sizes from 1 to 30 (or more
if needed).
Each staff size has an acurate parameter tested and contro
Hi,
2013/7/10 Karl Hammar :
> David:
>> Janek Warchoł writes:
>>
>> > Hi all,
>> >
>> > i managed to get internet connection for a moment.
>> >
>> > 2013/7/7 Karl Hammar :
>> >> Urs:
>> >>> Would you mind writing the same as a comment to the original post
>> >>> on the blog? That would be nice.
>
Hi,
2013/7/12 David Kastrup :
> Urs Liska writes:
>> So anybody who is interested in getting better default ties from
>> LilyPond _please_ read his post at
>> http://lilypondblog.org/2013/07/lilypond-tie-crusade and consider
>> joining him. While the most urgent need would be people who analyze
>
Forwarding to bug-lilypond:
2013/7/12 Jacques Menu :
> This sample [example of bad ties by David Kastrup, from issue 2607]
> causes 2.17.20-1 on Mac OS X 10.8.4 to loop forever after
> producing:
>
> Traitement de « /Users/menu/Documents/LaTeX/PartitionsLilypond/AwfulTies.ly
> »
> Analyse...
> In
Thank you for that. It is greatly appreciated.I'm still on the learning curve
for this one.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Huge-gap-between-piano-staves-tp146457p147953.html
Sent from the User mailing list archive at Nabble.com.
_
I use lilypond to prepare modern-notation editions from mensural
notation. Many performers prefer to have the original note values (lots
of breves, longs, etc.) but it is quicker in lilypond to enter the notes
as half-value. In other words, it is quicker, and more readable, to
enter
c1 c2 c1
Graham King writes:
> I use lilypond to prepare modern-notation editions from mensural
> notation. Many performers prefer to have the original note values (lots
> of breves, longs, etc.) but it is quicker in lilypond to enter the notes
> as half-value. In other words, it is quicker, and more re
20 matches
Mail list logo
