[EMAIL PROTECTED] writes:
> 1) Page 3, bar 20. The hairpins and \p in Alto and Tenor goes below the
> staves even though I have specified Voice.dynamicDirection = \up. Those
> two staves have a second voice in them, while Soprano and Bass do not.
> I wonder if the second voice is causing the problem.
try this
--- ../lilypond-1.3.45/scm/generic-property.scm Thu Apr 13 20:23:54 2000
+++ ./scm/generic-property.scm Thu Apr 13 22:09:45 2000
@@ -80,16 +80,16 @@
(define generic-crescendo-properties
(cons "Crescendo" (list
- (list 'verticalDirection dir? 'direction)
(list 'dynamicDirection dir? 'direction)
+ (list 'verticalDirection dir? 'direction)
(list 'dynamicPadding number? 'padding)
(list 'dynamicMinimumSpace number? 'minimum-space)
)))
(define generic-dynamic-line-spanner-properties
(cons "Dynamic_line_spanner" (list
- (list 'verticalDirection dir? 'direction)
(list 'dynamicDirection dir? 'direction)
+ (list 'verticalDirection dir? 'direction)
(list 'dynamicPadding number? 'padding)
(list 'dynamicMinimumSpace number? 'minimum-space)
)))
> 3) Page 6, bar 20. The hairpin in the Bass clashes with the tuplet
> number. By the way, are tuplet brackets supported? I have never seen
> them.
yes, have a look at tupletBracketVisibility in the manual.
>
> 4) Page 9, bar 46. The \f in the Bass cannot be specified a height so
> that it won't clash with the upper G. You can see in the source that I
> have specified a very large value for Voice.textScriptPadding in
> attempting to push the \f upward.
>
have you considered putting the f on the upper voice?
> 5) Processing HaveMercoOnMe_OGod_2.ly produces the following warning:
>
> HaveMercyOnMe_OGod_2.ly:657:53: warning: no one to print a tuplet start
> bracket:
> _4 _8. A16 -- wake,2. __ harp8 and lyre! _ \times
> 2/3 {I8 will8 a8}
Harmless. Tuplet brackets are n't pritned in Lyrics.
> I want to enter the lyrics matching the triplet rhythm in the voice.
> Also, the duration "8" in the tuplet is not carried over, that is why I
> have input an explicit "8" for each syllable. Am I doing it right?
I'm sorry, I don't understand. Can you send a shorter example?
> 8) Version 43. lily does not understand the translator
> "Staff_margin_engraver". Is it removed?
The name changed to Instrument_name_engraver.
> 1) Change time/key signatures in the middle of a piece. I don't know
> how to do this, so I have splitted the score into two files. Even
> though page number remains in a series, bar numbers do not.
how about
{ .. piece1 stuff .. \time 2/4; \key cis; .. piece2 stuff ..}
?
> 2) Change the starting number of bar numbering.
set \property Score.currentBarNumber.
> 3) Is it possible to change the behaviour of certain properties to bind
> to a system as opposed to the staff for the whole score? For
No.
> 4) How to adjust the space between the two staves in a PianoStaff
> context?
see ly/engraver.ly for the definition of PianoStaff
> 9) Graphical clashes. Sometimes I see that slurs and hairpins tend to
> clash with texts, especially \textscript. Can such clashes be detected
> and avoided?
It is very hard to detect these automatically. See
input/test/generic-ouput-property.ly for a possible solution.
> I would appreciate if someone (perhaps HWN) can update me on these
> issues. Somehow, one of my postings about lyrics a week ago went
> unnoticed. Moreover, this piece is for my composition assignment which
> is due Friday. It would be nice if those graphical glitches could be
> fixed by the time I hand in the assignment. The most critical one is
> the hairpins and the \pp get moved below the staff in page 3, bar 20. I
> apologize if this request is too much.
Sorry, I've been real busy this week. And I am enjoying the rest, now
that my gnu-music-discuss mail is filtered into a separate folder.
The rest of your mail still awaits consideration in that folder :-)
--
Han-Wen Nienhuys, [EMAIL PROTECTED] ** GNU LilyPond - The Music Typesetter
http://www.cs.uu.nl/people/hanwen/lilypond/index.html
