bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "Stress test" for the regression tests


From: Neil Puttock
Subject: Re: "Stress test" for the regression tests
Date: Thu, 6 Aug 2009 23:48:31 +0100

2009/7/30 Reinhold Kainhofer <address@hidden>:

> How would you fix this? By default, the TimeSignature Grob does not have the
> text-interface, however, if you use the #ly:text-interface::print function as
> stencil, you need to set the text...

grob-interpret-markup

>> MusicXML programming errors:
>>
>> 42a-MultiVoice-TwoVoicesOnStaff-Lyrics.ly:    cyclic dependency: 
>> calculation-in-
>> progress encountered for #'X-extent (PaperColumn)
>
> I have no idea what this warning is about...

It's something to do with the two scripts attached to a skip in
PartPOneVoiceTwo:

s2 ^\fermata _>

>
>> 46a-Barlines.ly:                              Improbable offset for stencil: 
>> inf staff space (x2; bad
>> barline string, type not implemented yet)
>
> Ah, that's a typo, the bar type for short barlines should be "'" like for tick
> (although I suppose that is not entirely correct, but it's the best
> approximation that is available without including gregorian.ly and using
> \divisioMaior)

\divisioMaior's not really ideal either though; according to MusicXML
2.0, it should be a partial barline between the second and fourth
lines.  If I ever get round to moving ly:bar-line::print to scheme (as
Han-Wen suggested), it should be easy to implement this by changing
'bar-size.

>> 12a-Clefs.ly:                                   unknown clef type `None'
>
> It seems that lilypond does not provide any possibility to not show any clef
> at all... That's what would be needed here. The "None" comes simply from the
> MusicXML clef name in that case, which is taken verbatim for clefs where I
> didn't find a proper lilypond implementation.

There used to be a "none" type, but it was removed ages ago; I wonder
whether it would be worth reimplementing it somehow.

>
>
>> 13a-KeySignatures.ly:                           No ordering for key
>> signature alterations (x2) (outlandish keys)
>
> That's a general problem for all keys with more than 7 sharps/flats... E.g. 
> try
> \relative { \key bis \major bis1}

Indeed.

It's not worth adding the extra orderings, so it's justified to ignore
the warning.

>> 61h-Lyrics-BeamsMelismata.ly:                   unterminated hyphen;
> removing
>
> That's a general problem / inconsistency with lilypond and MusicXML: The
> MusicXML file has several slurred notes with lyrics attached, while lilypond
> does not allow assigning lyrics syllables to slurred notes... Thus the
> syllabled after the hyphen are ignored by musicxml.

Could you remove Slurs from melismaBusyProperties for this?

Regards,
Neil




reply via email to

[Prev in Thread] Current Thread [Next in Thread]