Op dinsdag 1 april 2008, schreef Mats Bengtsson:
Isn't a better solution to make the first syllable left aligned
with the note? This should automatically result in left aligned
lyrics and aligned notes.
Unfortunately that does not look nice: with long words the spacing of both
notes and words
Am I able to change the number of lines in a [Drum] staff from 5 - 1?
Lily has built-in support for DrumStaves with one, two or five lines --
see the manual.
In your case, it sounds lie you're after something like drumStyleTable =
#percussion-style, like this:
\version 2.10.25
up =
Hi,
Still typesetting my hymn, I use ragged-right = ##t to make the lines not too
long.
But I want the stafflines to be the full line-width. But how do I convert from
staffspaces to milimeters?
Currently I use:
\version 2.11.43
#(set-global-staff-size 18)
\paper {
line-width = 10 \cm
}
Hi all
(Hopefully) a quick question about break autobeams and stem direction.
When I compile the following music, each embellishment that contains more than
one acciaccatura breaks both the autobeaming and the stem direction that I have
written in.
Bars 1-2 contain the music with
thanks for the quick answer. I tried now to figure out how to apply changes to
StaffSymbol properties. It seems they work only as \with \override for a new
staff or inside the layout block. That would mean that they cannot be changed
on the fly but are preset for every score. Is this correct?
---BeginMessage---
CHeers for that...
I need to be able to specify pitches in my score to denote which
hand is play which note. The current single line drum staff doesn't
allow that.
The way that I've done that is to specify a normal staff, but with
only one line. Now I can get pitches for my
Hi Matthew
I'll have to leave an explanation of this to the more knowledgeable, but the
main problem seems to be starting the piece with an \acciaccatura. Doing
this causes problems elsewhere (eg tuplets). Try removing it and the
overrides then seem to work. Seems like the voice-context
Am Dienstag, 1. April 2008 schrieb till Rettig:
How does the line-position property of the StaffSymbol work correctly? I
get it set to different positions only if the staff is empty or the notes
are on ledger lines. Is this behaviour implied? And does the list of the
positions need a specific
If you check the warning printouts from LilyPond when processing the
second example, you will notice that you have misspelled the property name!
Otherwise, both of the examples seem to do what I would expect them to do.
I don't understand exactly what you mean by only if the staff is empty
or
The properties of a layout object are only read when the object is
created, so
for StaffSymbol, for example, this means that you have to do the setting at
the top of the score. However, if you want to change it in the middle of a
score, you can insert
\stopStaff \startStaff
which finishes the
How does the line-position property of the StaffSymbol work correctly? I get it
set to different positions only if the staff is empty or the notes are on
ledger lines. Is this behaviour implied? And does the list of the positions
need a specific order? It obviously takes only as much arguments
Arjan Bos wrote:
On 31 mrt 2008, at 14:59, James E. Bailey wrote:
I'm wondering if there's an easy way to generate a piano reduction
from a choral piece but without all of the dynamics. The choir parts
all have their dynamics, but the piano part shouldn't. And the handy
snippet I found
On 31 mrt 2008, at 14:59, James E. Bailey wrote:
I'm wondering if there's an easy way to generate a piano reduction
from a choral piece but without all of the dynamics. The choir parts
all have their dynamics, but the piano part shouldn't. And the handy
snippet I found generates a piano
Greetings folks,
I have sent this mail on -user a few days ago; perhaps it would belong
to -devel instead (if so, please tell me), or even to the tracker as a
feature request (which I, of course, won't decide on my own).
Anyway, it would be just great if anybody had a clue about how to deal
with
Trevor Daniels t.daniels at treda.co.uk writes:
Seems like the voice-context overrides have
nowhere to go if the first note is an acciaccatura and have no effect. A
work-around is to place all the voice-context overrides in the Staff context
so they apply to all voices.
I did see that
Matthew wrote:
Trevor Daniels t.daniels at treda.co.uk writes:
Seems like the voice-context overrides have
nowhere to go if the first note is an acciaccatura and have no effect. A
work-around is to place all the voice-context overrides in the Staff context
so they apply to all voices.
Oops, yeah, you are right, it works as thought; I just didn't understand
the warning. Thanks!
Till
Mats Bengtsson schrieb:
If you check the warning printouts from LilyPond when processing the
second example, you will notice that you have misspelled the property
name!
Otherwise, both of the
Oh, that's true, I will write this in the staff section of the Docu.
Thanks for all the help!
Greetings
Till
Mats Bengtsson schrieb:
The properties of a layout object are only read when the object is
created, so
for StaffSymbol, for example, this means that you have to do the
setting at
the
\score{
\new Staff \with {
\override StaffSymbol #' line-position = #' ( 6 3 0 -3 -6 )
}{
d' e' f' g' c''
} }
In my idea the second example should print wider spaces and set the notes
somhow off the lines, but it just prints the standard lines 4 2 0 -2 -4.
Why is this so?
Have you
Mats Bengtsson wrote
Matthew wrote:
Trevor Daniels t.daniels at treda.co.uk writes:
Seems like the voice-context overrides have nowhere to go if the first
note is an acciaccatura and have no effect. A work-around is to place
all the voice-context overrides in the Staff context so they apply
Kieren MacMillan wrote:
or
\set Staff.instrumentName = \markup{\column {Violoncello e Basso }}
That's what I'd prefer.
Then I don't understand your question. What's the problem you get when you
use this approach?
Actually, what I'd *really* prefer is
\set Staff.instrumentName =
Kieren MacMillan wrote:
[Lilypond 2.11.42]
Hi all,
I'm trying to define an orchestral stylesheet, based on the
Barenreiter NMA soft-bound edition (Mozart KV 551, to be exact). Their
instrument names are centered in a column, which presents no problem;
however, the InstrumentName text
Hi Mats,
Do you use
\set Staff.instrumentName = \markup{\center-align {Violoncello e
Basso }}
That's what I'm trying to avoid.
or
\set Staff.instrumentName = \markup{\column {Violoncello e Basso }}
That's what I'd prefer. Actually, what I'd *really* prefer is
\set
2008/4/1, Till Rettig [EMAIL PROTECTED]:
About the bug: I thought I would write: this works only with symmetrical
staff lines. As I understand everything is built around symmetrical staves,
but when thinking about it there could be a need for having the staves
positioned on an even number of
2008/4/1, Mats Bengtsson [EMAIL PROTECTED]:
Kieren MacMillan wrote:
Actually, what I'd *really* prefer is
\set Staff.instrumentName = Violoncello e Basso
Have you tried
http://lsr.dsi.unimi.it/LSR/Item?id=383 ?
It was written by Nicolas Sceaux; see a demo here:
Hi,
on DrumStaffs I get two fermatas on multimeasure rests, normal Staffs
work as expected (see below and attached pdf).
Am I doing something wrong?
\version 2.11.42
\score {
\new DrumStaff
{ R1^\fermataMarkup}
\new Staff
{ R1^\fermataMarkup}
}
--
Orm
test.pdf
Description:
Hi Valentin,
Have you tried
http://lsr.dsi.unimi.it/LSR/Item?id=383 ?
Et voila! =)
IIRC he has recently implemented this in LilyPond itself; however I
can't find it in the ChangeLog (or perhaps he just planned to?)
Very cool.
Thanks! And sorry I didn't check the LSR first... =\
Kieren.
That's a bug! I have already commited a fix in GIT. Waiting for the next
release,
you can add the following lines to your file:
\layout{
\context{
\DrumVoice
\remove Multi_measure_rest_engraver
\consists Multi_measure_rest_engraver
}
}
(If you think it looks strange, the problem was
2008/4/1, Orm Finnendahl [EMAIL PROTECTED]:
on DrumStaffs I get two fermatas on multimeasure rests, normal Staffs
work as expected (see below and attached pdf).
Hi Orm,
looks like a bug to me. Unless anyone has some additional information
about it, i'll add it to the tracker.
Cheers,
2008/4/1, Kieren MacMillan [EMAIL PROTECTED]:
Thanks! And sorry I didn't check the LSR first... =\
Actually, I was aware of it only because of the French mailing list... :)
Cheers,
Valentin
___
lilypond-user mailing list
lilypond-user@gnu.org
2008/4/1, Mats Bengtsson [EMAIL PROTECTED]:
(If you think it looks strange, the problem was that the engraver was added
twice and when you do \remove it removes both copies so you have to add
one back afterwards.)
Wow, impressive! thanks for having been so fast!
I didn't know engravers
On 01.04.2008, at 14:22, Mats Bengtsson wrote:
Arjan Bos wrote:
On 31 mrt 2008, at 14:59, James E. Bailey wrote:
I'm wondering if there's an easy way to generate a piano reduction
from a choral piece but without all of the dynamics. The choir
parts all have their dynamics, but the
Hi everybody,
I'm just about to start work on creating snippets for each of the
\markup commands listed in appendix B.6. Before I begin, I'd like to
canvass opinion on how they should be demonstrated.
As I see it, there are two options:
1. Continue in the same vein as the two existing examples
Mats Bengtsson mats.bengtsson at ee.kth.se writes:
Perhaps it helps to explicitly create the Voice context as well, i.e.
replace
\new Staff {...}
by
\new Staff \new Voice {...}
/Mats
Nope, doesn't help.
I've worked around it by using manual beaming; with that in, it all works.
The bar line should go from the uppermost staff line to the downmost
staff line, but now it gets centered on the middle position, so if the
upper or lower half of the staff extends more than the other (from the
middle counted) the bar line is misplaced.
Look at the example:
\new Staff \with
Hi Mats,
thanks a lot, that worked!
Yours,
Orm
Am Tuesday, den 01. April 2008 um 18:19:03 Uhr (+0200) schrieb Mats Bengtsson:
That's a bug! I have already commited a fix in GIT. Waiting for the next
release,
you can add the following lines to your file:
\layout{
\context{
\DrumVoice
On 1 apr 2008, at 16:12, Mats Bengtsson wrote:
Arjan Bos wrote:
Ah, I remember that thread. It is what gave me this idea in the
first place. The problem of centered dynamics crossing bar lines
does not apply to most of my music, which is polyphonic classical
guitar these days. It does
I'm writing a theme and variations on LilyPond, and I've separated the theme and
variations with \break. The trouble I'm having is in creating a title for each
part (Tema, Var I, Var II, etc). Thanks.
___
lilypond-user mailing list
I tried another way of using lilypond-book, which seems to work
better with tex, bibtex, makeindex, ..., -- and makefiles.
If you are interested, read the README at
http://aspodata.se/noter/palestrina/dies_sanctificatus/
and send comments.
Regards,
/Karl
39 matches
Mail list logo
