If I have a section like:
\relative c'
{
\time 4/4
\transposition f
c e g c |
\transposition ees
c, e g c |
\transposition d
c, e g c |
}
Is there an easy way to change it all to the same key for printing?
Something like '\normalizeTransposition f \music' would be equivalent to:
\
I'm writing some harp glissandos, where the first several notes of the gliss
are written out for accidentals, then the rest of the measure is just the
wavy gliss line to the next note. I've got it looking right, except there's
way too much empty space at the end of the measure.
\version "2.11.
> i guess i have to apply your patch (and werner's)
Only my patch.
> to the sources and recompile lilypond, right? is it OK to patch
> against 2.11.49 sources?
Yes.
> how can i modify the file to get what i want?
>
> +straight_flag_angle = -37;
> +straight_upflag_length# = .65 black_notehead_
on 2008-06-19 at 16:21 Reinhold Kainhofer wrote:
>Actually, adding different flags in lilypond is quite simple:
great, actually i've been wanting to ask this for a long time, but not
related to old notation styles but rather to more "contemporary"
practices. it has been quite common for the las
> Attached is a first attempt to do this, plus a sample file showing
> the new "straight", the "mensural" and the default flag styles.
Attached is a patch which fixes the metrics and glyph shapes so that
the straight flags convert nicely to PS outlines. IMHO, the shapes
are ready for inclusion n
Reinhold,
I noticed that on the second staff (downward stems), the eighth notes have
their flags all in the C space, rather than at the end of their stems. Do
you know why that happened?
Tim Reeves
original message:
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
06/19/2008 09:05 AM
Ple
Am Donnerstag, 19. Juni 2008 schrieb Arno Rog:
> Problem is that using the Staff context the figures/symbols are way to low
> beneath the notes (it looks like they belong to the notes on the staff
> below)
Yes, that's also a problem I'm encountering
(http://lists.gnu.org/archive/html/lilypond-dev
Reinhold Kainhofer wrote:
>
> Actually, adding different flags in lilypond is quite simple: Simply use
> \override Stem #'flag-style = #'flagstylename
> and lilypond will use the characters "flags.flagstylename[ud][3456]" as
> flags.
>
> Now, to implement straight flags, all one has to do
Am Dienstag, 17. Juni 2008 schrieb madhg:
> Valentin Villenave wrote:
> > I'd be ready to add this as an Enhancement request; can you find a
> > better picture please?
> >
> > Cheers,
> > Valentin
>
> Good, thank you. These are all keyboard music, scanned from published
> facsimiles (which are cle
L.S.
I am trying to engrave a Bach cantata using lilypond (latest devel. version
on WinXP) So far no problems I can't handle (except for the sheer magnitude
of this 'job')
Until now, the figured bass.
Problem is that using the Staff context the figures/symbols are way to low
beneath the notes (
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Text-marks#Text-marks
Printing marks on every staff
Although text marks are normally only printed above the topmost staff,
they may also be printed on every staff.
{
\new Score \with {
\remove "Mark_en
A \score{...} block is a syntactical construct, which internally creates
a Score context (among others).
It is also possible to explicitly instantiate a Score context, but I
don't really see the added value of
doing it (even though I seem to recall that there was some specific
reason to introduc
I don't quite understand what the difference between score and Score
are. I'm sure this is discussed in some documentation somewhere, but I
just don't know where to look. Can someone point me in the right
direction?
___
lilypond-user mailing list
Mats said
I don't really see the point of using
a separate MarkLine context for the individual parts
By curiosity, i simply test this MarkLine in an example (using Haipeng
music) :
%%
\version "2.11"
allegroassai = \markup { \bold \italic "Allegro assai" }
agi
14 matches
Mail list logo
