Hello,
For what I know, it's mainly due to the way lilypond-book works : it
separate systems in multiple files, compile them, then include them as
graphics.
The right side could be corrected by adding a horizontal size (in the
options of the lilypond environnemnt, I think). Something like
\lilyp
On 7 August 2011 01:45, Paul Scott wrote:
>
> Hi,
>
> Is there a reason for this default beaming? I get (3 3 2) with 2.15.8.
>
> \version "2.15.8"
>
> { \time 8/8 \repeat unfold 16 a'8 }
>
This is indeed the default setting as expressed in
'scm/time-signature-settings.scm'. What did you expect
Hi again,
I'm preparing a transcription of a Baroque piece (by Zelenka) and my goal is
to have a PDF with a title page, a page of commentary, and then the score.
I'm a daily LaTeX user. The score is ready. I created a "dummy" lytex
document with a small commentary and I used the \lilypondfile comm
Hi,
Is there a reason for this default beaming? I get (3 3 2) with 2.15.8.
\version "2.15.8"
{ \time 8/8 \repeat unfold 16 a'8 }
TIA,
Paul
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-use
I am trying to put together a book composed of multiple scores. From reading
through the archives it seems that variables are not allowed within \bookpart.
I was wondering what people do to get around this. I'd like to be able to use
the same code for putting together multiple files where so
Dear Janek and Harm,
thank you both for very nice solutions! Both are working nicely, of course.
Harm's method seems indeed very flexible and potentially very useful.
Janek's solution has the advantage of allowing a newbie such as myself
freedom of choice regarding the shape of the parentheses, or
Tim McNamara wrote:
>
>
> Also, IMHO the syntax for placing a coda, a segno, etc. ought to be as
> elegant and simple as possible (e.g., \coda or \segno instead of \mark
> \markup { \musicglyph #"scripts.coda" } or \mark \markup { \musicglyph
> #"scripts.segno" } Less typing means fewer errors
Ed,
From: lilypond-user-bounces+james.lowe=datacore@gnu.org
[lilypond-user-bounces+james.lowe=datacore@gnu.org] on behalf of Ed
Ardzinski [ed_ardzin...@hotmail.com]
Sent: 06 August 2011 22:47
To: lilypond-user@gnu.org
Subject: Different Font for di
Trying to make some lead sheets and I'd like to have a separate stave be
smaller/different font. For example, and separate stave for a solo instead of
a vocal verse. I'm still in the stone age, but if this is something that 2.12
does that 2.6.5 won't I'm prepared to change ;-) Thanks for an
harm6 wrote:
>
>
> Elwro wrote:
>>
>> Dear Group,
>>
>> I'd like the input
>>
>> \parenthesize R1
>>
>> to produce a whole measure rest in parentheses. (...)
>>
>> Best regards,
>>
>> Leszek.
>>
>
> Hi,
>
> here's another, more elaborated workaround:
>
> (...)
>
> HTH,
> Harm
>
>
On Aug 6, 2011, at 11:30 AM, James Lowe wrote:
> Hello,
>
> From: lilypond-user-bounces+james.lowe=datacore@gnu.org
> [lilypond-user-bounces+james.lowe=datacore@gnu.org] on behalf of Tim
> McNamara [tim...@bitstream.net]
> Sent: 06 August 2011 17
Hello,
From: lilypond-user-bounces+james.lowe=datacore@gnu.org
[lilypond-user-bounces+james.lowe=datacore@gnu.org] on behalf of Tim
McNamara [tim...@bitstream.net]
Sent: 06 August 2011 17:17
To: LilyPond User
Subject: Overriding shifting of coda wh
By default Lilypond moves a coda placed at the end of a line to the beginning
of the next line of \break is used. I consider this bad behavior- the
rehearsal marks should stay put where I place them rather than having that
placement changed by the application (I have no idea why Lilypond is cod
On 24 July 2011 21:10, Xavier Scheuer wrote:
> I'm running into issue #1150 (RehearsalMark placement at start of line)
> again and again.
> http://code.google.com/p/lilypond/issues/detail?id=1150
>
> Neil's workaround (see comment 2 & 5) is nice but:
>
> 1. It does not shift enough. I'd like thes
Elwro wrote:
>
> Dear Group,
>
> I'd like the input
>
> \parenthesize R1
>
> to produce a whole measure rest in parentheses. (...)
>
> Best regards,
>
> Leszek.
>
Hi,
here's another, more elaborated workaround:
\version "2.14.2"
parenthesizeMMR =
#(define-music-function (parser locatio
Hi Leszek,
2011/8/4 Leszek Wroński :
> I'd like the input
> \parenthesize R1
> to produce a whole measure rest in parentheses.
The fact that it doesn't work is indeed interesting.
I don't know how to fix it right now, but there is a workaround:
{
\once \override MultiMeasureRestText #'outside-
Janek,
From: Janek Warchoł [lemniskata.bernoull...@gmail.com]
Sent: 06 August 2011 08:48
To: James Lowe
Cc: Phil Holmes; robert.schm...@web.de; lilypond-user@gnu.org
Subject: Re: Mix of Chordnames and Notes
Hi,
2011/8/5 James Lowe :
> )-Original Messag
Hi,
2011/8/5 James Lowe :
> )-Original Message-
> )From: Phil Holmes [mailto:m...@philholmes.net]
> )- Original Message -
> )From: "James Lowe"
> )
> )> @Phil, you're on XP right?
> )>
> )> If anyone reading this has windows 7 SP1 can they try the above
> )> snippet and see if it
18 matches
Mail list logo
