Sven Axelsson writes:
> but specifically it fails to load the struct module from the
> lib-dynload folder.
> Maybe all dynloaded modules fail, I haven't checked that much.
Can you please do some more checking. Do any other DLLs work, such as
math, midi ?
> Perhaps it would be nice if the insta
Lilypond 2.7.17 on Windows XP
Volta brackets that are broken over several lines don't look right anymore.
They are terminated at the end of line and restarted again at the next line.
\version "2.7.17"
\relative c'' {
\repeat volta 2 { a a a a }
\alternative { { a a a a \break a a a a } { a a a a
Lilypond 2.7.17 on Windows XP.
The stems on gracenotes with multiple beams are shorter than before. Too
short, they often squeeze up against the note head.
--
Sven Axelsson
stems.png
Description: PNG image
___
bug-lilypond mailing list
bug-lilypond@gn
Lilypond 2.7.17 on Windows XP.
I seems like the included Python installation has some problems. I'm not
sure of the general problem, but specifically it fails to load the struct
module from the lib-dynload folder. Maybe all dynloaded modules fail, I
haven't checked that much. Perhaps it would be n
Michael Welsh Duggan <[EMAIL PROTECTED]> writes:
> This may help with other ligatures as well. This fixes the bug
> whereby a note head immediately succeeding a ligature became
> invisible. (Example: see 2.7.16 documentation, section 7.7.11. There
> should be a note under the "ctus" of the seco
It seems that the best you can do is something like:
\version "2.6.0"
\score{
% \applymusic #unfold-repeats
\relative c'' {
\time 4/4
\repeat volta 2 {
\partial 4 d4 |
e8 d e d e d e d |
}
\alternative {
{ f2. }
{ \set Timing.measurePosition = #(ly:make-moment 0 4) f8 e f e f e f
g
Hi.
> > (1)
> > First, is this in effect the most straightforward way to obtain
> > the expected result?
>
> No, a problem is that \cadenzaOff doesn't mark the end of the bar (there will
> be four beats before the candenza bar is finished).
>
I don't get what you mean; maybe you could correct t
OK! I hope you add it to the list of feature requests (or the list of
sponsorable
features).
/Mats
Han-Wen Nienhuys wrote:
Mats Bengtsson wrote:
at beat 1 in the above example. Also, I would like to hear an
authoritative
explanation from the main LilyPond hackers on how to input this kin
Now I realize what you mean, sorry. I forward it to bug-lilypond as a bug
report/feature request. As a musician, I completely agree that this should
be done for clarity, still I have seen many printed scores that do not print
out the additional accidentals.
A possible workaround for you is to do
