Lyrics extender problem
Hi all,
I have the following problem with Lyrics extenders. In the altos voice it
is drawn properly.
But in the sopranos the externder is missed out.
Thanks for any suggestion.
Georg
\version 2.8.0
global = {
\key c \major
\time 4/4
}
sopMusic = \relative c'' {
c4 c c8( b) c4
}
sopWords = \lyricmode {
hi hi hi __ hi
}
altoMusic = \relative c' {
e4 f d8( d) e4
}
altoWords =\lyricmode {
ha ha ha __ ha
}
\score {
\new ChoirStaff
\new Lyrics = sopranos { s1 }
\new Staff = women
\new Voice =
sopranos { \voiceOne \global \sopMusic }
\new Voice =
altos { \voiceTwo \global \altoMusic }
\new Lyrics = altos { s1 }
\context Lyrics = sopranos \lyricsto sopranos \sopWords
\context Lyrics = altos \lyricsto altos \altoWords
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Disappearing volta brackets? Need help.
Hi. I'm trying to typeset some dance music (contradance and waltz) and I'm running into a problem with volta repeat brackets. Actually, I'm running into a lot of problems (I'm new at lilypond), and I've got them all solved and this volta repeat bracket problem came up.
What I'm trying to do is get chord names above the staff, key of G major, and an alternate ending on part b of the piece. Here is an abridged snippet of the .ly file I'm working with:---
\include english.ly\version 2.7.24partA = { \repeat volta 2 { \chords { d2. | g | a2:m d4 | g2. \break | }
} \repeat volta 2 { \key g \major \relative c'' { a4 fs8 g a4 | b d,8 g b4 | c8 b a g fs a | g2. |} } }partB = { \chords {
\repeat volta 2 { c2. | g | } \alternative { { a2.:m | d } { a2:m d4 | g2. } } } \repeat volta 2 { \key g \major \relative c'' {
e4 d8 c b a | d4 c8 b a g | } } \alternative { { \relative { c'8 b a g fs g | a4 fs d'} } { \relative { c'8 b a g fs a | g4 r r } } }
}{ \time 3/4% \partA \partB}If I run this through lilypond, part B displays correctly (chords above the staff, alternative volta brackets in place, proper key signature, proper time signature, etc.). If I delete the % commenting out part A, I lose the alternative volta brackets, which is unacceptable.
Why? And how do I get it to keep the volta brackets, the chords above the staff, and the proper key and time signatures?
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Still unable to Start Lilypond
Robin wrote: That will mean a new computer, and that won't happen for a while. You should not say it will work on 98 and then say it won't. The download sight says expressly that it will work on W98. Change that, or modify that if it isn't true. Don't lie and mislead. Last time we looked it did work, but things like this are very unpredictable with w98. Will an older version work on 98, and if so, which one. you'll have to try; see http://lilypond.org/download/binaries/mingw/ -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
combining stems
I'm (a relative newbie) trying to typeset a choir-type piece, where I'd have SAT on one staff, *with* combined stems,Now, I realize that I can do it by adding everything as chords, but this does not feel natural to me, and I'd like to keep the different voices separate in the input file if at all possible,
I tried to set them as different voices, and overriden stem direction to be \stemUp, which is not ideal but better than S-up A-down T-up. This works, sort of, as long as the duration is quarternotes or longer (and ignoring the fact that I get a sh*tload of warnings), the beams do not combine, rendering things seen in attached screenshot,
(fromsopranThree = \relative c' { d8 e16 f ~ f8 g16 e ~ e8 d16 c r8 c16 d ~ | d8 e16 f ~ f8 g16 a ~ a4 ~ a8 d16 d16 ~ | \key g \major d1 |}altThree = \relative c' { b8 c16 d ~ d8 d16 c\( ~ c8 a16 g\) r8 g16 b ~ |
b8 c16 d ~ d8 d16 g ~ g4 g8 h16 h ~ | \key g \major a1 |}tenorThree = \relative c' { s1 | s4 s8 s16 d16 ~ d4 ~ d8 g16 g( | \key g \major fiss1 |})So, how am I supposed to merge stems and beams (into chords, but without writing them as chords)?
regards,SimonI'm using 2.8.0 on windows FWIW.A somewhat related note, the documented behaviour about stem directions when using \partcombine seem to be off, or there's a bug in section
8.3.1 Automatic part combining http://lilypond.org/doc/v2.8/Documentation/user/lily-781809215.png
non-combining-stems.png
Description: PNG image
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Moving dynamic markings changing font weight
On 28-Mar-06, at 6:14 PM, Geoff Horton wrote:
I found a post on the list which suggests using the staff-padding
parameter to put all dynamic markings on the same baseline. But it
didn't say, and I can't figure out, how to actually make that happen.
Based on the manual, this parameter belongs to TextSpanner, which
lives in Voice, so
It certainly _does_ belond to TextSpanner. But dynamics aren't
TextSpanners -- see the very bottom of 6.5.3. Vertical positioning of
these symbols is handled by **SPOILER DELETED**
See the documentation to find out the deleted information. :)
looks like it ought to do the trick (and more--the enormous padding is
there so I could make sure any effect would be obvious). It doesn't.
Whenever I think I've found a bug, I test it out on a small example:
{
c'4^foo c' c' c'
\override TextScript #'staff-padding = #10
c'4^foo c' c' c'
}
(I changed TextScript to TextSpanner because I couldn't remember
offhand what the syntax is for spanners). This works as expected.
Likewise, I'm trying to change the font weight for dynamics from bold
to medium. This belongs to DynamicText, which also lives in Voice, and
\Voice
\override DynamicText #'font-size = #-2
does work to shrink it, so I'm in the right ballpark. But
\override DynamicText #'font-series = #'medium
does nothing.
What am I missing?
You're missing an update to the docs that got submitted just after
2.8.0 was released. :)
Some situations (such as dynamic marks) have preset font-related
properties. If you are creating text in such situations, it
is advisable to cancel those properties with
@code{normal-text}. See @ref{Overview of text markup commands}
for more details.
This was added to the manual to 8.1.3, and I've just added it to 8.1.8
as well.
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
problem wish TextSpanner dash-fraction
Hi, I am trying to use dash-fraction as 1.0 on my sheet, but when I
pass 1.0 the lilypond return error when I pass 0.9 it return
success
I am attaching my .ly is :
\version 2.8.0
\score
{
\context Voice
{
\textSpannerUp
\override TextSpanner #'edge-text = #'(C1 . )
\override TextSpanner #'dash-fraction = #1
\relative c'
{
f
\startTextSpan
a c
\stopTextSpan
}
}
}
anyone knows what is wrong ?
--
An application asked:
Requeires Windows 9x, NT4 or better,
so I´ve installed Linux
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem wish TextSpanner dash-fraction SOLVED
I used dash-period = 1 and dash-fraction = 0.9 and is visually right
On 3/28/06, Allan Spagnol Comar [EMAIL PROTECTED] wrote:
Hi, I am trying to use dash-fraction as 1.0 on my sheet, but when I
pass 1.0 the lilypond return error when I pass 0.9 it return
success
I am attaching my .ly is :
\version 2.8.0
\score
{
\context Voice
{
\textSpannerUp
\override TextSpanner #'edge-text = #'(C1 . )
\override TextSpanner #'dash-fraction = #1
\relative c'
{
f
\startTextSpan
a c
\stopTextSpan
}
}
}
anyone knows what is wrong ?
--
An application asked:
Requeires Windows 9x, NT4 or better,
so I´ve installed Linux
--
An application asked:
Requeires Windows 9x, NT4 or better,
so I´ve installed Linux
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
emacs mode with the new installer
just installed 2.8 on fedora core 4 with the universal installer. no emacs mode. is there something I am missing? and if not, is the e-lisp code in CVS workable with version 2.8? thanks in advance. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
2.8 postscript and other subjects
Yesterday, I wrote on lilypond-users:
I get a postscript file that I can see with gv, and looks correct, but is
not printable.
OK. I understand that my postscript printer simply doesn't accept the
postscript level produced by lilypond 2.8. Too bad.
On previous ly files, with 2.8 I get a lot ot warning messages such as
---
AVERTISSEMENT : Ignoring grob for slur. avoid-slur not set?
---
for example on the following bar :
{ e''4 dis'' e''8 _( d''? ) cis''\prall _( b' ) } \\ { fis' b'2 e'
gis' }
The cause seems to be the second slur specification, but I don't
understand what happens. Could anybody explain me the above message ?
Thanks in advance for your help.
Regards.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Guy DURRIEU ONERA/TIS/DTIMtel(33) 05.62.25.26.59
CERT, 2, avenue Edouard Belin B.P. 4025 fax(33) 05.62.25.25.93
31055 TOULOUSE CEDEX 4 FRANCE e-mail [EMAIL PROTECTED]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Moving dynamic markings changing font weight
On 28-Mar-06, at 11:01 PM, Geoff Horton wrote:
You're missing an update to the docs that got submitted just after
2.8.0 was released. :)
Some situations (such as dynamic marks) have preset font-related
properties. If you are creating text in such situations, it
is advisable to cancel those properties with
@code{normal-text}. See @ref{Overview of text markup commands}
for more details.
This was added to the manual to 8.1.3, and I've just added it to 8.1.8
as well.
Maybe I'm suffering from a severe case of the stupids, but I can't
find anything in the docs (in 8.1.3 or 8.1.8) which tells me how to go
about cancelling the properties with normal-text (or anything else).
Ah, sorry, I was a bit unclear -- or rather, I assumed you had
knowledge that you didn't have. When I update the documentation, I
make a change to the CVS source tree. When a new version of lilypond
is released, the source (for lilypond itself as well as the
documentation) is compiled, and a new version of the documentation is
put on the web. So when I said that this material was submitted right
after 2.8.0 came out, it means that it won't appear on the web until
2.8.1 is released.
That's why I sometimes tell people ok, I've made a few changes; take a
look when $VERSION+1 comes out -- they can't see the changes until the
next version is released, which might be days or a week away.
Regardless of this, you should find info about normal-text in Overview
of text markup commands. (section 8.1.something)
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
