Re: Not happy with results
On 3/18/07, Matthias Berndt [EMAIL PROTECTED] wrote:
Hi,
I tried writing a few lines with lilypond, but I don't like the way that
the
result looks. Perhaps I'm doing something wrong, but I don't think so. In
the
attachments, you'll find some source code and the resulting pdf.
The big bracket at the beginning of the second line crosses the bar
number,
which looks odd to me.
Yes, this padding property is well tuned for simple staff, with the bracket
you should put a
\override Score.BarNumber #'padding = #2
somewhere in your score { }
Lilypond give a pretty good result out of the box... but manual tuning is
also a part of the game... hopefully, you can re-use your preferred tweaks
in a snap.
The crescendo at the beginning of the second line is
much longer for Alto and 2nd Bass than for Soprano, Tenor and 1st Bass,
and
of course it's not supposed to.
You ended your crescendo one note later in the 2nd and last part.
a4 \ b c d
e4 d \! c b
here the crescendo start on a a and end on a d (not after the d but on
it... and if the d is the first note in a bar, the typographic rule says
to stop the hairpin at the bar... even if you can disable this behaviour,
have a look at the doc)
line 27 was : g2^\mf^\ g4 (fis) g (fis)^\! e e e a a g a f fis^\ (e)
line 27 : g2^\mf^\ g4 (fis) g ( ^\! fis) e e e a a g a f fis^\ (e)
or (to show that the order doesn't matter, every supplementary symbol
always refers to the previous note : \! -. ( \mf etc.)
line 27 : g2^\mf^\ g4 (fis) g ^\! (fis) e e e a a g a f fis^\ (e)
Are there any workarounds for those issues? I'm using the latest development
release of lilypond.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
well this is a matter of personnal taste but... the dynamics over the
staff are really hard to read O_o
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Not happy with results
The crescendo at the beginning of the second line is
much longer for Alto and 2nd Bass than for Soprano, Tenor and 1st
Bass, and
of course it's not supposed to.
Do you want the longer crescendos to be shortened or vice versa? I
suppose the latter because otherwise you would probably have written the
*.ly file in a different way.
As Yota pointed out, ...
here the crescendo start on a a and end on a d (not after the d
but on it... and if the d is the first note in a bar, the typographic
rule says to stop the hairpin at the bar... even if you can disable this
behaviour, have a look at the doc)
... hairpins corresponding to (de-)crescendos which end on the first
note in a bar stop at the barline by default. The relevant property
controlling this is 'hairpinToBarline'. Just insert
\set hairpinToBarline = ##f
at the beginning of your score to change this behaviour. See also the
file hairpin-to-barline.ly in the regression tests which you can find at
http://lilypond.org/doc/v2.11/input/regression/collated-files
.
Note, however, that even with this setting the crescendi will still have
different length because lily also somehow takes the duration of the
notes (halves and quarters in our case) into account. The tweak I
sometimes use to correct this uses an invisible temporary second voice
containing two quarters instead of a half note. The end of the crescendo
is then attached to the second of these invisible quarters. For example,
changing the beginning of line 18 in your file as follows
line 18 old: d'2^\mf^\ e4 (h)g2^\! [...]
line 18 new: d'2^\mf^\ e4 (h) g2 {s4 s4^\!} [...]
yields a crescendo which has precisely the same length as the one in the
alto voice.
I am almost certain, however, that this is not the standard way to
achieve this. I would be glad to know if someone had a better solution.
Cheers,
Max
P.S.: BTW, I suppose you write (for example) d^\ instead of d\ in
order to place the dynamics above the staves instead of below (where
they are placed by default). Section 6.6.3 Dynamics in the manual
mentions the command \dynamicUp which, when inserted at the beginning of
your music, achieves this behaviour without all the manual overrides
using '^'. This can save you a lot of typing and IMHO also makes the
file more readable.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Not happy with results
Many thanks to both of you, this rocks! ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
