On Tue, Jan 1, 2013 at 2:39 PM, Eluze wrote:
> Alberto Simões-2 wrote
>> Second, I am having two different problems with rests.
>>
>> 1) rests1.gif shows some examples of:
>>
>> f4 ~ f8[ r16 f]
>>
>> but the rest is over the beam. If you notice at the left, the other is
>> uglier. What is the
Alberto Simões-2 wrote
> Second, I am having two different problems with rests.
>
> 1) rests1.gif shows some examples of:
>
> f4 ~ f8[ r16 f]
>
> but the rest is over the beam. If you notice at the left, the other is
> uglier. What is the best approach to fix this?
>
>
> 2) rests2.gif sh
judi wrote
> Hi
>
> I would like to increase the size of the easy note heads however the
> commands that increase the size of normal note heads only increase the
> size of the letter of the easy heads, rather than the head itself. Eg
> \override Voice.NoteHead #'font-size = #2
>
> Is there a way
Hey, Friends
First of all, Good New Year!!
Second, I am having two different problems with rests.
1) rests1.gif shows some examples of:
f4 ~ f8[ r16 f]
but the rest is over the beam. If you notice at the left, the other is
uglier. What is the best approach to fix this?
2) rests2.gif s
Nick Payne writes:
> #(define dirn 1)
>
> #(define (updown grob)
> (let ((ud (ly:event-property (event-cause grob) 'direction)))
> (if (eq? -1 ud)
> (begin
> (set! dirn DOWN)
> DOWN)
> UP)))
>
> beginStringNum = #(define-event-function (parser location strng)
>
On 01/01/13 20:21, David Kastrup wrote:
Nick Payne writes:
In the following lilypond code, why is the value of the scheme
variable dirn not being changed by the set! command in the updown
function? The updown function is called on the first line of
beginStringNum,
No, it isn't.
beginStringN
Kevin Patrick Barry wrote
> My files compile with no errors. Perhaps we are using different versions
> of LilyPond? I am on 2.16.1. I made no alterations to line-width in any
> of
> the files linking to the style file.
I can't reproduce it with 2.16.1 (on windows)
can you send a tiny example -
Thank you for responding.
My files compile with no errors. Perhaps we are using different versions
of LilyPond? I am on 2.16.1. I made no alterations to line-width in any of
the files linking to the style file.
I found that if I set a margin of 0.5\mm on the left that it corrects the
width of t
Kevin Patrick Barry wrote
> P.S. here is the style code I am using:
when I use your settings I get a warning
/warning: margins do not fit with line-width, setting default values/
is your run ok?
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/png-export-width-t
David Kastrup:
> "Phil Holmes" writes:
> > From: "Karl Hammar"
> >
> >> Yes, you can place the dynamics above the staff, but I don't really
> >> see the point of that. Now your forte collides with the tempo
> >> mark. And in choir notes it would only solve any potential collisions
> >> between dy
David Kastrup:
> k...@aspodata.se (Karl Hammar) writes:
...
> > This looks like a bug.
> >
> > \version "2.17.10"
> >
> > Ms = \relative a' { c4 c c c | }
> > Ds = \relative a' { s\p s s\f s | }
> > Ma = \relative a' { c4\p c c\f c }
> >
> > \score {
> > <<
> > \new Staff \relative a' { c4\p
Phil Holmes:
> > Yes, you can place the dynamics above the staff, but I don't really see
> > the
> > point of that. Now your forte collides with the tempo mark. And in choir
> > notes
> > it would only solve any potential collisions between dynamics and lyrics
> > for
> > one staff only.
>
> Th
Dear LilyPond users/experts,
I am trying to produce images that are exactly 4 inches in width (at a
resolution of 1200 dpi). To accomplish this I set paper width to 4\in and
left and right margins both to 0 (except for systems with brackets, when I
have to add 2mm to the left so it will appear).
"Phil Holmes" writes:
> From: "Karl Hammar"
>
>> Yes, you can place the dynamics above the staff, but I don't really
>> see the point of that. Now your forte collides with the tempo
>> mark. And in choir notes it would only solve any potential collisions
>> between dynamics and lyrics for one st
- Original Message -
From: "Karl Hammar"
To:
Sent: Tuesday, January 01, 2013 11:35 AM
Subject: Re: dynamics seperatate from the notes entry
Yes, you can place the dynamics above the staff, but I don't really see
the
point of that. Now your forte collides with the tempo mark. And in c
k...@aspodata.se (Karl Hammar) writes:
> Karl Hammar:
>> Xavier Scheuer:
>> > On 31 December 2012 15:22, Karl Hammar wrote:
>> > > How do I merge Ds and Ms below so it will behave as if I wrote the
>> > > dynamics together with the notes?
> ...
>> > << \Ms \Ds >> % without the "\\"
>> > will be
James Bailey:
> On Dec 31, 2012, at 3:22 PM, Karl Hammar wrote:
> > How do I merge Ds and Ms below so it will behave as if I wrote the
> > dynamics together with the notes?
... [ ly code for Ms and Ds ] ...
> > If I use << \Ms \\ \Ds >> the dynamics will come out to the left
> > (compared to the i
Karl Hammar:
> Xavier Scheuer:
> > On 31 December 2012 15:22, Karl Hammar wrote:
> > > How do I merge Ds and Ms below so it will behave as if I wrote the
> > > dynamics together with the notes?
...
> > << \Ms \Ds >> % without the "\\"
> > will behave as if you wrote the dynamics together with th
Nick Payne writes:
> In the following lilypond code, why is the value of the scheme
> variable dirn not being changed by the set! command in the updown
> function? The updown function is called on the first line of
> beginStringNum,
No, it isn't.
> beginStringNum = #(define-event-function (pars
Il 01/01/2013 09:19, Federico Bruni ha scritto:
Il 31/12/2012 21:47, Helge Kruse ha scritto:
Am 31.12.2012 18:53, schrieb Federico Bruni:
A new bar is never started within a cadenza, even if one or more \bar
commands are inserted within it. Therefore, reminder accidentals will
need to be added
Il 31/12/2012 21:47, Helge Kruse ha scritto:
Am 31.12.2012 18:53, schrieb Federico Bruni:
A new bar is never started within a cadenza, even if one or more \bar
commands are inserted within it. Therefore, reminder accidentals will
need to be added manually. See Accidentals.
So what's the point
21 matches
Mail list logo
