Re: lilypond v2.13.54
Hi, 2011/3/17 Phil Holmes > > It looks like the LilyPond installation is no longer adding the path > to the executable to the Windows PATH. I have installed .54 and > don't have it on my path. For me that's actually good - my PATH > variable overflowed and I lost all the ones I wanted. However, > for people who rely on the command line, it'll mean LP won't run. > Can someone check whether this has been changed in the Windows install? I recently uninstalled 2.13.53 and installed 2.13.54 on my WinXP machine and it worked both from command line and by double-clicking. Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1570 in lilypond: Fixes accidental suggestions in the beam collision engraver
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical regression Patch-review
New issue 1570 by colinpkc...@gmail.com: Fixes accidental suggestions in
the beam collision engraver
http://code.google.com/p/lilypond/issues/detail?id=1570
Per Mike Solo:
A bug just hit the French list. It seems like a critical regression.
\score { %avec "surcharge" des ligatures double croches
allongées
\new Staff {
\time 2/2
\set suggestAccidentals = ##t
g'4 fis'8 [ g'8 ] a'8 [ g'8 a'16 g'16 fis'!16 e'16 ] |
d'1
}
}
\score { %sans "surcharge" des ligatures : bon
\new Staff {
\time 2/2
\set suggestAccidentals = ##t
g'4 fis'8 g'8 a'8 g'8 a'16 g'16 fis'!16 e'16|
d'1
}
}
Mike has proposed a patch on reitveld:
http://codereview.appspot.com/4271054/
The patch compiles and passes reg tests.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Placement of outside-staff objects: bug and behaviour change between 2.12.3 and 2.13.54
On 11-03-20 12:53 AM, Frédéric Bron wrote:
Although outside-staff-priorities seem to not have changed between
2.12 and 2.13 (I compared roughtly define-grobs.scm), there is
something strange:
In the example below, the vertical placement of OttavaBracket,
TextScript and MetronomeMark is not in the same order with 2.12.3 and
2.13.54 although using the same code.
\layout {
\context { \Score \override MetronomeMark
#'outside-staff-priority = #200 }
}
\relative c' {
\tempo "tempo" 4 = 66
\ottava #1
c''1^"markup"
\ottava #0
}
Following the documentation
http://lilypond.org/doc/v2.13/Documentation/learning/outside_002dstaff-objects,
MetronomeMark should be in the Score context, not in the Staff context
as are OttavaBracket and TextScript so that changing it
outside-staff-priority should not affect the output as with 2.12.3 so
that I think this is a regression.
There should be a test including absolutly all possible objects that
are to be placed outside a staff so that this behaviour can be
controlled.
I have built such a test:
\relative c' {
\override Score.BarNumber #'break-visibility = #all-visible
\set Score.skipBars = ##t
\dynamicUp
\override TextSpanner #'(bound-details left text) = \markup
"TextSpanner (Staff 350)"
\tempo "MetronomeMark (Score 1000)" 4 = 60
\repeat volta 2 {
\ottava #1
c''1\p\<^"TextScript (Staff 450)"\startTextSpan\startTrillSpan
}
\alternative {
{
R1*2\mark "RehearsalMark (Score 1500)"
c\!\stopTextSpan\stopTrillSpan\trill
\ottava #0
}
{
c
}
}
}
With this test, using only default outside-staff-priorities, there are
differencies between 2.12.3 and 2.13.54:
Order should be from top to bottom:
1 RehearsalMark
2 MetronomeMark
3 BarNumber
4 MultiMeasureRestText
5 TextScript
6 OttavaBracket
7 TextSpanner
8 DynamicLineSpanner
9 VoltaBracketSpanner
10 TrillSpanner
We get wrong result with 2.12.3:
1 RehearsalMark
2 MetronomeMark
3 VoltaBracketSpanner
4 BarNumber
5 TextScript
6 OttavaBracket
7 TextSpanner
8 DynamicLineSpanner
9 TrillSpanner
10 MultiMeasureRestText
We get a different wrong result with 2.13.54:
1 RehearsalMark
2 MetronomeMark
3 VoltaBracketSpanner
4 TextScript
5 OttavaBracket
6 TextSpanner
7 DynamicLineSpanner
8 BarNumber
9 TrillSpanner
10 MultiMeasureRestText
Frédéric
___
I believe the documentation specifies that the Rehearsal, Metronome and
Bar Number marks normally live in the Score context; to put them into
your order, you need to take them out of Score and put them into Staff,
per the note in NR 4.4.3.
Colin Campbell
Bug Squad
--
The test of our progress is not whether we add more to the abundance
of those who have much, it is whether we provide enough for those who
have too little.
-Franklin D. Roosevelt, 32nd US President (1882-1945)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.13.54 breaks NoteNames vertical spacing
On 11-03-19 08:25 PM, Michael Ellis wrote:
On Sat, Mar 19, 2011 at 8:22 PM, Xavier Scheuer wrote:
On 20 March 2011 01:05, Michael Ellis wrote:
Just installed 2.13.54 on OS X. Attached images show what happens to
the NoteNames engraver (which I use every day) under this release. In
2.12, the NoteNames output lays close beneath the lyric line. In
2.13.54 the gap is quite large and the output collides with markup
above the next staff. Is there a workaround?
Looks like a problem of staff-affinity not defined for NoteNames
context or something like that.
This definitely deserves to be reported.
Could you send a message to bug-lilypond@gnu.org with a proper minimal
example of code?
Done by CC of this message. Image from example below suggest that
NoteNames vertical is incompletely synchronized with Staff vertical
spacing. Amount of interference varies from line to line. Worst at
bottom of image.
Thanks!
Mike
%
\version "2.13.54"
notes = \relative c {
\repeat unfold 40 { c'4 c c c }
}
mylyrics = \repeat unfold 40 \lyricmode { \tempo "Allegro" ly -- ric ly -- ric }
\score {
<<
\new Voice = "voice" { \notes }
\new Lyrics \lyricsto "voice" { \mylyrics }
\context NoteNames \notes
>>
}
%-
Thanks, Mike. Added as
http://code.google.com/p/lilypond/issues/detail?id=1569
Colin Campbell
Bug Squad
--
The test of our progress is not whether we add more to the abundance
of those who have much, it is whether we provide enough for those who
have too little.
-Franklin D. Roosevelt, 32nd US President (1882-1945)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1569 in lilypond: 2.13.54 breaks NoteNames vertical spacing
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical
New issue 1569 by colinpkc...@gmail.com: 2.13.54 breaks NoteNames vertical
spacing
http://code.google.com/p/lilypond/issues/detail?id=1569
Reported by Michael Ellis in
http://article.gmane.org/gmane.comp.gnu.lilypond.general/63005/match=notenames
In 2.12, the NoteNames output lays close beneath the lyric line. In
2.13.54 the gap is quite large and the output collides with markup
above the next staff.
\version "2.13.54"
notes = \relative c {
\repeat unfold 40 { c'4 c c c }
}
mylyrics = \repeat unfold 40 \lyricmode { \tempo "Allegro" ly -- ric ly --
ric }
\score {
<<
\new Voice = "voice" { \notes }
\new Lyrics \lyricsto "voice" { \mylyrics }
\context NoteNames \notes
>>
}
There are workarounds discussed in the thread, but this seems like a
regression, and so the Critical rating.
Attachments:
notenamesexample.png 57.3 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \repeat percent does not use the beat-slash stencil
On 11-03-19 12:12 PM, Ed Gordijn wrote:
\version "2.13.54"
\relative c''{
\time 4/4
\key c \major
% Ok
\repeat percent 4 {c8 c }
% Not Ok
\repeat percent 4 {c8 c16 c}
}
\layout{ ragged-right = ##t }
I believe this is a known issue, arising from using percent repeats on
16th note, Ed. Please have a look at the Notation Reference 1.4.2
Percent Repeats.
Colin Campbell
Bug Squad
--
The test of our progress is not whether we add more to the abundance
of those who have much, it is whether we provide enough for those who
have too little.
-Franklin D. Roosevelt, 32nd US President (1882-1945)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Release candidate 3 of 2.14 - LilyPond 2.13.54 released
>> I noticed that convert-ly does not converts auto beaming settings.
> Didn't convert-ly give you a message that said you needed to change it
> manually?
I have run conver-ly for many files so that I did not see the message!
It would have been nice to have a rule that added a comment in the
file it-self, just before the command.
Something like:
%{ convert-ly: you must change this manually %}
#(override-auto-beam-setting '(end 1 8 3 4) 3 8 'Score)
which you can get with:
str = re.sub ('(?=#\\( *(override|revert)-auto-beam-setting)', '%{
convert-ly: you must change this manually %} ', str)
Frédéric
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: tempo causes insertion of empty staff line
Am Sonntag, 20. März 2011, um 22:21:58 schrieb Phil Holmes: > "Philip Stolz" wrote in message > news:loom.20110320t212309-...@post.gmane.org... > > % If tempo is specified for the whole score > > % lilypond adds an empty staff line. > > % This issue did not exist in version 2.13.49. > > % The first version where it occurred was 2.13.50. > > % It also exists in 2.13.54. [...] > This is a very interesting regression. However, the example you provide is > more complicated than necessary. I think the issue is that previously, the \tempo command simply set some context properties, while it now is a separate music event and thus causes an implicit voice to be generated if no voice is yet created. Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: tempo causes insertion of empty staff line
"Philip Stolz" wrote in message
news:loom.20110320t212309-...@post.gmane.org...
I'm not top posting.
% If tempo is specified for the whole score
% lilypond adds an empty staff line.
% This issue did not exist in version 2.13.49.
% The first version where it occurred was 2.13.50.
% It also exists in 2.13.54.
\version "2.13.50"
\score {
<<
\time 4/4
\tempo 4 = 114
\new Staff = "Voice" <<
\set Staff.instrumentName = \markup {"Voice"}
\set Staff.shortInstrumentName = #""
{
\key bes \major
\relative c' {bes'4 c4 d,2} \bar "|."
}
>>
\new PianoStaff = "Piano" <<
\set PianoStaff.instrumentName = #"Piano"
\set PianoStaff.shortInstrumentName = #""
<<
\new Staff { \key bes \major \clef treble \relative c' {bes4 c4 d2}
\bar
"|."}
\new Staff { \key bes \major \clef bass \relative c {bes4 c4 d2}
\bar "|."}
>>
>>
>>
}
This is a very interesting regression. However, the example you provide is
more complicated than necessary. Please could you provide a "tiny" example
to help debugging?
http://lilypond.org/website/tiny-examples.html
--
Phil Holmes
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Possible bug on \addlyrics in Lilypond 2.13.54
On 3/19/11 4:18 PM, "Wim van Dommelen" wrote:
>> I'm not top posting.
>
> I found some weird behaviour in music disappearing when adding a lyric.
>
> This is the smallest I could get the problem reduced to:
>
> \version "2.13.54"
>
> \score {
> \new Staff {
> \relative g' { g1 }
> % as soon as the next line is commented in the piece truncates,
> % when commented out we see more notes appearing
> \addlyrics { milk milk }
> \relative g' { c2 g }
> \addlyrics { su- gar su- gar }
> }
> }
>
> Not too sure ifnthis counts as a real bug, nor how serious it might be. When I
> did something wrong please accept my apologies.
>
> On the whole I'm very content with Lilypond, keep up the good work !
>
> Regards,
> Wim.
>
>
You've got the lyrics in a sequential block with the music, rather than in a
parallel block.
\new Staff {
<<
\relative g' {g1}
\addlyrics { milk }
>>
<<
\relative g' { c2 g }
\addlyrics { su- gar }
>>
}
HTH,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
tempo causes insertion of empty staff line
> I'm not top posting.
% If tempo is specified for the whole score
% lilypond adds an empty staff line.
% This issue did not exist in version 2.13.49.
% The first version where it occurred was 2.13.50.
% It also exists in 2.13.54.
\version "2.13.50"
\score {
<<
\time 4/4
\tempo 4 = 114
\new Staff = "Voice" <<
\set Staff.instrumentName = \markup {"Voice"}
\set Staff.shortInstrumentName = #""
{
\key bes \major
\relative c' {bes'4 c4 d,2} \bar "|."
}
>>
\new PianoStaff = "Piano" <<
\set PianoStaff.instrumentName = #"Piano"
\set PianoStaff.shortInstrumentName = #""
<<
\new Staff { \key bes \major \clef treble \relative c' {bes4 c4 d2} \bar
"|."}
\new Staff { \key bes \major \clef bass \relative c {bes4 c4 d2} \bar
"|."}
>>
>>
>>
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
big format for Notation Manual: unsupported compression type
2.13.54 There is an issue with Notation Manual in big format: http://lilypond.org/doc/v2.13/Documentation/notation-big-page.html when clicking on an item of the table of contents (with firefox 3.6.15 on Windows), I get an error message: "Erreur d'encodage de contenu. La page que vous essayez de voir ne peut être affichée car elle utilise un type de compression invalide ou non pris en charge." If I try to translate, it could give: "Content encoding error. The page you try to see cannot be displayed because it uses an invalid or unsupported compression type" Frédéric ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1269 in lilypond: Doc: using #'non-break-align-symbols = #'() to align MetronomeMark should be documented
Comment #8 on issue 1269 by pkx1...@hotmail.com: Doc: using #'non-break-align-symbols = #'() to align MetronomeMark should be documented http://code.google.com/p/lilypond/issues/detail?id=1269 I think this is invalid. We state we don't document issues that are not postponed nor bugs which this seems to be. James ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1568 in lilypond: ENHANCEMENT: Adds the Articulate script with documentation
Status: Accepted Owner: Labels: Type-Enhancement Priority-High New issue 1568 by colinpkc...@gmail.com: ENHANCEMENT: Adds the Articulate script with documentation http://code.google.com/p/lilypond/issues/detail?id=1568 This issue is intended to track the proposed patch on http://codereview.appspot.com/4277067 which adds Dr Peter Chubb's Articulate script and adds some documentation explaining its use. The discussion on http://article.gmane.org/gmane.comp.gnu.lilypond.general/62923/match=articulate brings up the question of licensing. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
critical issues
Hey guys, I've been busy/distracted/sick for the past week, and I'll continue to be busy/distracted/sick for the next ten days. I'm also fed up with announcing a release candidate and then discovering that there's a known critical issue that wasn't on the tracker a day later. 1) if you're working on a Critical issue, could you add it to the tracker? directly? i.e. don't rely on the bug squad to add it for you? 2) if you suspect that there's a Critical issue, and you're either on the bug squad or have git push access, could you add it to the tracker? directly? and by "suspect", I mean as in "shoot first, ask questions later"? like, don't wait until somebody has confirmed it, just dump it in there so that I don't make yet another false release candidate announcement? Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1567 in lilypond: Add documentation for footnotes
Status: Accepted Owner: Labels: Type-Documentation Priority-High New issue 1567 by philehol...@googlemail.com: Add documentation for footnotes http://code.google.com/p/lilypond/issues/detail?id=1567 The recent addition of footnotes to LilyPond will require documentation on how to use them and how they work across page breaks. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1560 in lilypond: Lyrics can not be aligned below ossia staff
Comment #1 on issue 1560 by carl.d.s...@gmail.com: Lyrics can not be aligned below ossia staff http://code.google.com/p/lilypond/issues/detail?id=1560 I think this issue is invalid. The first code example asks to align a Lyrics context below a non-existent Staff context (ossiaStaff is not created until measure position 1/4; the Lyrics begin at 0/4). The second code example is a duplicate of Issue 1551. \lyricsto does not work on the last syllable of an ossia staff. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Possible bug on \addlyrics in Lilypond 2.13.54
2011/3/19 Wim van Dommelen :
>> I'm not top posting.
>
> I found some weird behaviour in music disappearing when adding a lyric.
>
> This is the smallest I could get the problem reduced to:
>
> \version "2.13.54"
>
> \score {
> \new Staff {
> \relative g' { g1 }
> % as soon as the next line is commented in the piece truncates,
> % when commented out we see more notes appearing
> \addlyrics { milk milk }
> \relative g' { c2 g }
> \addlyrics { su- gar su- gar }
> }
> }
What follows is my opinion only.
It looks as if the voice context for the second \addlyrics is lost
after the first \addlyrics. This does not surprise me.
The behaviour is not more weird than the code itself. \addlirycs is
not intented do be used this way, that's why you obtain an unexpected
result.
{ music } \addlyrics { lyrics }
is a short for
<< \newStaff { \new Voice=name {music} } \new Lyrics \lyricsto name
\lyricmode { lyrics } >>
It is a simultaneous construct, but you don't use <<>> and therefore
is not clear what you try to achieve by just putting more music after
an addlyrics.
This is what you can do depending on what you want:
Do you want your music and lyrics to be simultaneous? use <<\new
Staff {music} \addlyrics {lyrics}\new Staff {music} \addlyrics
{lyrics}>> .
Do you want your music to be sequential and your lyrics to be
simultaneous? first concatenate music in a single voice, then use
addlyrics twice.
Do you want it all to be sequential? first concatenate music and
lyrics, then use addlyrics once.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
