Jayaratna wrote:
Dear members,
I am reading this forum since sometimes, as I am doing my first steps in
Lilypond.
I am making a score in which I have two systems of eight staves each per
page (I managed to do that by setting page size to a3 and shrinking it to a4
on printing it: I guess it's n
Dear Lilypond-users,
I want to make a substitution with the \movement-command ( look at:
http://lsr.dsi.unimi.it/LSR/Item?id=444).
But unfortunately this doesn't work:
langsamer = { \movement "subito meno mosso" "4" #69 }
How can I change it?
I had another strange experience with the movement-comm
Hi Luis
The value given to 'right-padding controls the
distance between the pair of accidentals and the
following note. To adjust the placement of the
individual accidentals you can use various alignment
markup commands (see Appendix B6.2 in the 2.11
Notation Reference). Here I've used \halign
2008/6/11 Stefan Thomas <[EMAIL PROTECTED]>:
> But unfortunately this doesn't work:
> langsamer = { \movement "subito meno mosso" "4" #69 }
You have to add a # before each quoted string:
langsamer = { \movement #"subito meno mosso" #"4" #69 }
It's in order to tell the Scheme interpreter: "hey
May I chime in a bit here? This prodding of the scheme interpreter is
one of the few things I do not like in the lilypond syntax. I do love
LilyPond and as a programmer at heart, I adore its syntax. However, as
a programmer, it is my duty to let the computer do the work instead of
the user.
I hoped there might be a seperate context for roman numerals similar
to the ChordNames context, in which you would specify the roman
numeral and its inversion (and any alterations using figured bass),
along with a duration. Depending on the duration of the chord in
question, the context would autom
I think this would be a wonderful implamentation for a future version of
Lilypond. I know that lots of people would benefit from a context like this.
Hugo
2008/6/11 Jesse Engle <[EMAIL PROTECTED]>:
> I hoped there might be a seperate context for roman numerals similar
> to the ChordNames context,
Hi Jesse, Hugo, et al.:
I think this would be a wonderful implamentation for a future
version of Lilypond.
I know that lots of people would benefit from a context like this.
Well, in as much as this could possibly be done -- without *immense*
amounts of programming (and some AI) -- it's al
El Wed, 11 Jun 2008 13:29:02 -0400
Kieren MacMillan <[EMAIL PROTECTED]> escribió:
> heck, it's often extremely difficult to get two *humans* to agree on
> the analysis of a given musical passage!
you're right. that's why it would be a good idea to let the computers
do the job... :-)
__
luis jure wrote:
> El Wed, 11 Jun 2008 13:29:02 -0400
> Kieren MacMillan <[EMAIL PROTECTED]> escribió:
>
>> heck, it's often extremely difficult to get two *humans* to agree on
>> the analysis of a given musical passage!
>
> you're right. that's why it would be a good idea to let the computers
> do
It's not a matter of whether the actual analysis of a musical passage
is right or wrong, the issue is whether or not the software can help
us make the analytical symbols look better, clearer and more concise
-- precisely what Lilypond is all about, if I am not mistaken --
without breaking too much
Jesse Engle gmail.com> writes:
>
> I hoped there might be a seperate context for roman numerals similar
> to the ChordNames context, in which you would specify the roman
> numeral and its inversion (and any alterations using figured bass),
> along with a duration. Depending on the duration of th
Le 11 juin 08 à 13:21, Arjan Bos a écrit :
May I chime in a bit here? This prodding of the scheme interpreter
is one of the few things I do not like in the lilypond syntax. I do
love LilyPond and as a programmer at heart, I adore its syntax.
However, as a programmer, it is my duty to let th
Dear all,
I have a problem concerning automatic note splitting (using the
Completion_heads_engraver) of long notes created by explicit ties.
Below is an example. This example breaks the dotted halve notes all
right. The problem is, that the ties between these dotted notes are
gone: instea
http://code.google.com/p/lilypond/issues/detail?id=498&can=1&q=completion
Cheers,
- Graham
On Wed, 11 Jun 2008 21:42:42 +0100
Torsten Anders <[EMAIL PROTECTED]> wrote:
> Dear all,
>
> I have a problem concerning automatic note splitting (using the
> Completion_heads_engraver) of long notes cr
Hi.
> > I hoped there might be a seperate context for roman numerals [...]
I use a \Lyrics context.
Best,
Gilles
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
2008/6/11 Nicolas Sceaux <[EMAIL PROTECTED]>:
> Bullshit.
There may be one point on which I tend to agree with Arjan: it's not
always handy to constantly put a hash character before text strings.
If I remember correctly (but I may have been hallucinating), you have
some functions in your framewor
On Wed, 11 Jun 2008 23:28:00 +0200
"Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> 2008/6/11 Nicolas Sceaux <[EMAIL PROTECTED]>:
> > Tis its extensibility that make LilyPond more likely to be able to
> > fit the more users needs, and its extensibility is made possible
> > because LilyPond is pro
Graham Percival wrote:
Oh, come on! What is so hard about typing #? On an English
keyboard, you already need to be pressing the shift key to get the
" that you'll type for your string anyway.
Rewriting the parser for such a trivial thing would be a waste of
resources. Just get used to typing
2008/6/11 Graham Percival <[EMAIL PROTECTED]>:
> Oh, come on! What is so hard about typing #? On an English
> keyboard, you already need to be pressing the shift key to get the
> " that you'll type for your string anyway.
Yes, French keyboard layout is much more annoying (it requires
twisting yo
On Wed, 11 Jun 2008 23:57:00 +0200
Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> Graham Percival wrote:
>
> >Rewriting the parser for such a trivial thing would be a waste of
> >resources. Just get used to typing #, just like {} or ,' or any
> >other piece of lilypond input. The docs are supposed
If you search the mailing list archive, you will for example find
http://lists.gnu.org/archive/html/lilypond-user/2008-04/msg00127.html
which contains an attached example that might be useful.
/Mats
Jesse Engle wrote:
I hoped there might be a seperate context for roman numerals similar
to t
Graham Percival wrote:
On Wed, 11 Jun 2008 23:57:00 +0200
Mats Bengtsson <[EMAIL PROTECTED]> wrote:
Graham Percival wrote:
Rewriting the parser for such a trivial thing would be a waste of
resources. Just get used to typing #, just like {} or ,' or any
other piece of lilypond input.
Meaning, not lyrics, but the notes. Suppose I want to shrink a whole
score by a few percent so that it takes one page less?
Or in piano + solo instrument, it's customary to print the solo
slightly smaller in the score. How do I do that?
Victor.
___
On Thu, 12 Jun 2008 00:10:56 +0200
Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> Graham Percival wrote:
>
> >All the time that it's getting passed as a scheme value, for
> >example
> > \set instrumentName = #"cello"
> >
> >Not for things like
> > \markup { this "is some quoted text" }
> >
> Whi
Victor Eijkhout wrote:
Meaning, not lyrics, but the notes. Suppose I want to shrink a whole
score by a few percent so that it takes one page less?
See section "Setting the staff size" in the reference manual.
Or in piano + solo instrument, it's customary to print the solo
slightly smalle
Hi Victor,
Suppose I want to shrink a whole score by a few percent so that it
takes one page less?
That info is in the documentation -- specifically, in Section 4.2.1
("Setting the staff size").
Or in piano + solo instrument, it's customary to print the solo
slightly smaller in the scor
Op donderdag 12 juni 2008, schreef Victor Eijkhout:
> Meaning, not lyrics, but the notes. Suppose I want to shrink a whole
> score by a few percent so that it takes one page less?
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Global-sizes#Global-sizes
http://lilypond.org/doc/v2.11/Docu
Am 12.06.2008 um 00:16 schrieb Victor Eijkhout:
Meaning, not lyrics, but the notes. Suppose I want to shrink a whole
score by a few percent so that it takes one page less?
Or in piano + solo instrument, it's customary to print the solo
slightly smaller in the score. How do I do that?
Vic
Is there a good way to have a partial measure at the end of a piece and not
get barcheck warnings? The manual says that using \partial is only
supported at the beginning of a piece, and you should expect warnings if you
use it elsewhere, but the only other alternative I've come up with is much
les
2008/6/11 Mats Bengtsson <[EMAIL PROTECTED]>:
> If you search the mailing list archive, you will for example find
> http://lists.gnu.org/archive/html/lilypond-user/2008-04/msg00127.html
> which contains an attached example that might be useful.
>
>
That is what I was talking about. But, anyway, it
Hi Steven,
Is there a good way to have a partial measure at the
end of a piece and not get barcheck warnings?
Since it's the end of the piece, why not just leave off the final |
in your code?
Its absence will not stop the actual (visible/engraved) barline from
appearing...
If you really
Bonjour,
Valentin Villenave a écrit :
Yes, French keyboard layout is much more annoying (it requires
twisting your right hand to have the thumb on AltGr and the middle
finger on the alpha-num "3" key).
Va falloir ajouter les doigtés dans les traductions de la doc, alors, et
prévoir des sous-p
I Wrote:
(...)
Va falloir ajouter les doigtés dans les traductions de la doc, alors, et
(...)
Shame on me!
Wrong addresses...(and Snippet?id=435)
--
Sorry,
FM
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/lis
Thank you, Mats,
The #(set-global-staff-size 18) works properly: it didn't work for me
because I put it in the wrong place.
I tried the two pass vertical spacing, but still the staves float, even if
the pages now have a better look.
I think I really have to go through this:
http://lilypond.org
On 11 jun 2008, at 23:48, Graham Percival wrote:
Rewriting the parser for such a trivial thing would be a waste of
resources. Just get used to typing #, just like {} or ,' or any
other piece of lilypond input. The docs are supposed to use #""
all the time, to reinforce this point.
If it we
36 matches
Mail list logo
