On 26-Apr-06, at 10:36 PM, Michael Brennan wrote:
David Feuer wrote:
On 4/19/06, Erik Sandberg <[EMAIL PROTECTED]> wrote:
In 2.8 there's an essential difference between grob and context
properties,
which is visible for end-users: the \tweak command only makes sense
on layout
object propertie
Hello,
When I first read the manual I didn't see any clear explanation of the
difference,
the docs could be more clear on that point. But when I realized that one
was for grobs
and the other for context, it became much clearer, for me it helps
separating and understanding
grobs and contexts.
> [...] when I realized that one was for grobs and the other for
> context, it became much clearer, for me it helps separating and
> understanding grobs and contexts.
A big help would be a simple means to distinguish grobs and context
properties. For example, context property names could always
David Feuer wrote:
On 4/19/06, Erik Sandberg <[EMAIL PROTECTED]> wrote:
In 2.8 there's an essential difference between grob and context properties,
which is visible for end-users: the \tweak command only makes sense on layout
object properties, not on context properties. This difference migh
I want to put in the symbol voor the disscant for the accordion. In the installed .ly example file's I found the text for it.If I do " \mark \markup { \musicglyph #"accDiscantEEE" } it runs without errors but the sign isn't there. Also --^\markup {musicglypyh ,, ,,, ,, ,}.
What must I do to ge
> > In 2.8 there's an essential difference between grob and context properties,
> > which is visible for end-users: the \tweak command only makes sense on
> > layout
> > object properties, not on context properties. This difference might make it
> > easier for new users to understand grob properti
> > In 2.8 there's an essential difference between grob and context
> > properties, which is visible for end-users: the \tweak command
> > only makes sense on layout object properties, not on context
> > properties. This difference might make it easier for new users to
> > understand grob properti
On 4/19/06, Erik Sandberg <[EMAIL PROTECTED]> wrote:
> In 2.8 there's an essential difference between grob and context properties,
> which is visible for end-users: the \tweak command only makes sense on layout
> object properties, not on context properties. This difference might make it
> easier
Mats Bengtsson wrote:
In contrast to the previous people who answered the questions, I would
say that you cannot directly apply the same idea to move
a whole line of chords. See
http://lists.gnu.org/archive/html/lilypond-user/2006-03/msg00411.html
for a hint on how to solve the problem.
Thank
See http://lists.gnu.org/archive/html/lilypond-user/2006-04/msg00363.html
/Mats
Quoting Michal Vopalensky <[EMAIL PROTECTED]>:
Hi,
I am using the LilyPond 2.8.1 on WinXP Home Edition. I have installed
it running
the lilypond-2.8.1-4.mingw.exe file, downloaded from the LilyPond website. I
In contrast to the previous people who answered the questions, I would
say that you cannot directly apply the same idea to move
a whole line of chords. See
http://lists.gnu.org/archive/html/lilypond-user/2006-03/msg00411.html
for a hint on how to solve the problem.
/Mats
Quoting Jennifer Cla
> \define-music-function {\foo \x \y} { c8 \x d8 \y }
> ...
> { \foo e16 {f g} }
> =>
> { c8 e16 d8 {f16 g16} }
>
> The usefulness of this kind of function is disputed among developers, so it
> might not become part of the official lilypond distribution.
I am not a developer (though I do read the
On Friday 07 April 2006 00:50, Geoff Horton wrote:
> > Just read sections 11.1.3 and 11.1.6 in the manual.
>
> That's far more complicated than I want, and even further more
> complicated than a musician who's not a computer programmer is going
> to want to deal with--please note that those section
On Tuesday 11 April 2006 23:56, Werner LEMBERG wrote:
> > \set: set the value of a context property
> > \override: set the value of a layout object property
>
> I've always wondered why it isn't possible to unify them...
In 2.8 there's an essential difference between grob and context properties,
On 26-Apr-06, at 7:30 AM, Jennifer Clark wrote:
Sorry for answering my own post, but I have found something that may
be relevant; in the manual, it says you can move about items through
use of the extra-offset, e.g. for markup text, which seems quite
effective;
\once \override TextScript
- Original Message -
From: "Jennifer Clark" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, April 26, 2006 11:30 AM
Subject: Re: Markup text to the left of first chord on ChordNames staff
>
> Sorry for answering my own post, but I have found something that may be
> relevant; in the manual,
I, a beginner too, and maybe others don't really understand your need, but
here are my guesses (I hope someone else will help too).
My first advice is to upgrade your version of Lilypond. :)
About item 2:
You might find answers in 8.4.1 Polymetric notation. Also if you use \set
Score.defaultBarType
Jennifer Clark wrote:
Rick Hansen (aka RickH) wrote:
This should be simple but I cant find an answer after exhaustive tries.
How can I attach a bit of markup text immediately to the left of the
first
chord in a ChordNames context staff?
Did anyone reply to this? I have a similar requir
Hello all,
I sent a message to the list a couple of days ago and never heard
anything back, I'm just wondering if the message actually went
through, because it seems like people here are good at responding :)
So here it is again, my apologies if I'm double-posting...
---
If anyo
Hi,
I am using the LilyPond 2.8.1 on WinXP Home Edition. I have installed it running
the lilypond-2.8.1-4.mingw.exe file, downloaded from the LilyPond website. I
have not intalled anything more, like Cygwin, for instance. TeX was already
installed on my system. The program works well, but when I
Rick Hansen (aka RickH) wrote:
This should be simple but I cant find an answer after exhaustive tries.
How can I attach a bit of markup text immediately to the left of the first
chord in a ChordNames context staff?
Did anyone reply to this? I have a similar requirement as well, i.e. if
I
On 25-Apr-06, at 4:36 AM, Sean Reed wrote:
Is there documentation somewhere on how the .midiMinimumVolume and
.midiMaximum values specifically effect the velocity scaling? I
expected it to scale #0.0=0 to #1.0=127, but I discovered that you can
go above 1.0 and below 0.0 into negative values.
Quoting Panteck <[EMAIL PROTECTED]>:
Is there a way to do this in Lilypond (2.8)? I've looked at the
\pitchedTrill command, but that specifies a note to trill to, and I'd
rather just specify sharp, flat, or natural in the trill line.
--Steven
You can redefine what is printed at the beginn
Graham Percival wrote:
On 25-Apr-06, at 6:36 PM, Paul Scott wrote:
Paul Scott wrote:
Just the addition of
#(set-octavation 1)
causes the rest of the staff lines to be dashed. (commenting that
line restores the solid staff lines.)
Example later if necessary. I'm trying to get some parts o
On 25-Apr-06, at 6:36 PM, Paul Scott wrote:
Paul Scott wrote:
Just the addition of
#(set-octavation 1)
causes the rest of the staff lines to be dashed. (commenting that
line restores the solid staff lines.)
Example later if necessary. I'm trying to get some parts out right
away.
This pro
25 matches
Mail list logo
