2009/3/5 Robin Bannister :
> Maybe these are trivial difficulties compared to those you constantly
> cope with, but, as a general priciple, I would have thought you would be
> better off going with the flow:
> not fighting Lilypond but rather
> letting Lilypond do its graphic thing as much as po
2009/3/5 胡海鹏 - Hu Haipeng :
> I don't
> want to assign two separate voices with plenty of confusing spacer notes.
> \relative c' {
> \stemUp c8(^"I" d e f g a b c | )(_"II" \stemDown c b a g f e d | c1)
> }
Unfortunately, I'm afraid the only proper way to do it is to use
spacer notes. At least,
accompanying (automatic) beaming looks rather silly.
If you apply \stemDown to the chord too, the beamimg looks better,
but the "I" scale gets (a notehead but) no stem on reaching this chord.
\stemBoth provokes the silly beamimg here too. You need something like
stemBothTwoOne = #(define
Hello,
I encounter a new problem with this function:
stemBoth = #(define-music-function (parser location m) (ly:music?)
#{ << \voiceOne $m \new Voice { \voiceTwo $m } >> \oneVoice #})
When I attach the slur, it is copied too. Now I want a function to write
things like this: the f
Hu,
2009/2/3 胡海鹏 - Hu Haipeng :
> Hello,
> Vallentin ever helped me to get a stemBoth function when I wrote the full
> score of my song for attending the CCTV piano competition:
> stemBoth = #(define-music-function (parser location m) (ly:music?)
> #{ << \voiceOne $m \new
Hello,
Vallentin ever helped me to get a stemBoth function when I wrote the full
score of my song for attending the CCTV piano competition:
stemBoth = #(define-music-function (parser location m) (ly:music?)
#{ << \voiceOne $m \new Voice { \voiceTwo $m } >> \oneVoice #})
Now I
voice \stemUp , the lower voice \StemDown, and the
middle part Stem
trnasparent.
What I havedone is to write \stemBoth twice. And it does work.
Why isn't it the same as in Lily2.0 ?
--
=
Mats Bengtsson
Signal Processing
Signals, S
The \stemUp is used because I have a viola da gamba part and some chords to write at
the beginning
of the score, with the upper voice \stemUp , the lower voice \StemDown, and the
middle part Stem
trnasparent.
What I havedone is to write \stemBoth twice. And it does work.
Why isn't i
operty value in some memory and then add the new property value to
use. If you later say
\revert blabla #'someproperty
(as is done in stemBoth), you tell LilyPond to throw away the current
value and find the previous one from the memory where you saved it.
However, if you keep \override:ing se
Hi list !
Some weird behaviour under Lily 2.2 and XP.
I've just moved from Lily2.0 to 2.2, and \stemBoth doesn't seem to work the same way.
Here's my script :
tr = \markup {\musicglyph #"scripts-rcomma"}
basseI =\notes
\context Staff <<
10 matches
Mail list logo
