This looks like a bug to me.
However, why do you use the verticalExtent property instead of
the minimumVerticalExtent, as described in
http://lilypond.org/doc/v2.3/Documentation/user/out-www/lilypond/Vertical-spacing.html
If you change that, it seems that the rests position is correct.
/Mats
On Monday 23 August 2004 01.25, Kieren Richard MacMillan wrote:
Erik:
(ugly, but it should work)
Yup (to both!)... ;-)
Thanks!
BTW: is this a known bug/feature, or should I report it?
It's a consequence of the way grace note timing currently works.
After thinking twice, I found that
Hello,
I am working on a Haendel Aria and already entered the string's notes.
There is a piano reduction in the score as well and I wonder wether
there is a way to merge the Violins and the Viola to a right hand piano
staff.
I tried to copy all events of Lilypond's midi output into one track but
Unfortunately, LilyPond is not clever enough to handle the translation
for the moment. I hope you know how to force the natural sign of the
next note manually: just add an exclamation mark after the note name!
/Mats
Frédéric Bron wrote:
Dear all,
I would like to print a turn sign with a sharp
On Mon, 2004-08-23 at 04:46, Mats Bengtsson wrote:
I hope you know how to force the natural sign of the
next note manually: just add an exclamation mark after
the note name!
What perfect timing that you mentioned that trick! I have a quartet
piece, and on the bass clef the baritone has f# on
There's actually an even better solution to that problem, see
http://lilypond.org/doc/v2.2/Documentation/user/out-www/lilypond/Accidentals.html
/Mats
Peter B. Steiger wrote:
On Mon, 2004-08-23 at 04:46, Mats Bengtsson wrote:
I hope you know how to force the natural sign of the
next note
I've never used \partcombine, but I suppose it could be good:
http://www.lilypond.org/doc/v2.2/Documentation/user/out-www/lilypond/Automatic-part-combining.html
Bert
___
lilypond-user mailing list
[EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
^ and _ are provided as a shorthand for:
\override Script #'direction = UP/DOWN
My only comment here is that (when using \markup) it does not appear to
be a shorthand for *override*. It seems to be a shorthand for *specify*.
In other words, an override is
In message [EMAIL PROTECTED], Han-Wen Nienhuys
[EMAIL PROTECTED] writes
[EMAIL PROTECTED] writes:
^ and _ are provided as a shorthand for:
\override Script #'direction = UP/DOWN
My only comment here is that (when using \markup) it does not appear to
be a shorthand for *override*. It seems to
[EMAIL PROTECTED] writes:
In message [EMAIL PROTECTED], Han-Wen Nienhuys
[EMAIL PROTECTED] writes
[EMAIL PROTECTED] writes:
^ and _ are provided as a shorthand for:
\override Script #'direction = UP/DOWN
My only comment here is that (when using \markup) it does not appear to
In message [EMAIL PROTECTED], Han-Wen Nienhuys
[EMAIL PROTECTED] writes
If I get the time, I'll code it myself (I want to learn) but what it
would need is some way of specifying the fundamental note (eg for a
trumpet I would choose concert B flat below middle C), and once you've
Try writing a
11 matches
Mail list logo