Re: Issue 1161 in lilypond: Lyrics is not centered with CENTER affinity if there is another Lyrics with one of UP or DOWN

2011-02-13 Thread lilypond 

Updates:
Status: Started
Owner: Carl.D.Sorensen

Comment #4 on issue 1161 by carl.d.s...@gmail.com: Lyrics is not centered  
with CENTER affinity if there is another Lyrics with one of UP or DOWN

http://code.google.com/p/lilypond/issues/detail?id=1161

The trick in getting the CENTER lyrics to be centered is to set the  
nonstaff-relatedstaff-spacing basic-distance to half the   
staff-staff-spacing basic-distance and to set the stretchability to zero.


I'll cook a patch for the documentation.


Attachments:
LyricSpacingSolved.ly  1.8 KB
LyricSpacingSolved.png  34.5 KB


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1294 in lilypond: Version 2.13.35 does not properly represent lyric tie

2011-02-13 Thread Phil Holmes 
lilyp...@googlecode.com wrote in message 
news:21-9567054385019064696-4632602130401919519-lilypond=googlecode@googlecode.com...


Comment #21 on issue 1294 by percival.music.ca: Version 2.13.35 does not 
properly represent lyric tie

http://code.google.com/p/lilypond/issues/detail?id=1294

If we compared pngs in the official regtest checks, it would catch this. 
I'm not certain if we *want* to compare pngs, and if we did, it would 
*definitely* wait until after 2.14.


I certainly don't see any benefit to trying to invent a regression test 
right now.


It's my normal course to compare PNGs, and so if there had been a regression 
test (and the example from the NR would have sufficed), and I'd been doing 
the checking back then, I would have spotted the problem.  I realise this 
isn't part of the official release process and does fail when I'm away, but 
I do still try to do it every build.


--
Phil Holmes
Bug Squad




___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1161 in lilypond: Lyrics is not centered with CENTER affinity if there is another Lyrics with one of UP or DOWN

2011-02-13 Thread lilypond 


Comment #5 on issue 1161 by carl.d.s...@gmail.com: Lyrics is not centered  
with CENTER affinity if there is another Lyrics with one of UP or DOWN

http://code.google.com/p/lilypond/issues/detail?id=1161

With the new settings, I think the original problem is now fixed.

Attachments:
1161-test.png  11.7 KB
1161-test.ly  1.1 KB


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1208 in lilypond: Some combination of 'staff-affinity for two Lyrics may cause unwanted vertical space

2011-02-13 Thread lilypond 


Comment #10 on issue 1208 by carl.d.s...@gmail.com: Some combination  
of 'staff-affinity for two Lyrics may cause unwanted vertical space

http://code.google.com/p/lilypond/issues/detail?id=1208

Here's a file that seems to do what you'd like.

If this is acceptable, it will probably become a documentation fix.

%%%  Begin .ly file

\version 2.13.42

lowerMel = \relative c '' {
  c4 c c c |
  a4 a a a |
  a4 a a a |
}

upperMel = \relative c'' {
  c4 c c c |
  c4 c c c |
  a4 a a a |
}

upperLyr = \lyricmode {
  \repeat unfold 4 { \skip 1 }
  u u u u
}

commonLyr = \lyricmode {
  c c c c
  \repeat unfold 4 {\skip 1}
  c c c c
}

lowerLyr = \lyricmode {
  \repeat unfold 4 { \skip 1 }
  l l l l
}


\score {
  \new ChoirStaff 
\new Staff = uppers \with {
  \override VerticalAxisGroup #'staff-staff-spacing =
#'((basic-distance . 9))
} 
  \new Voice = upper { \upperMel }

\new Lyrics = upper \with {
  \override VerticalAxisGroup #'staff-affinity = #UP
} \lyricsto upper \upperLyr
%
\new Lyrics = common \with {
  \override VerticalAxisGroup #'staff-affinity = #CENTER
  \override VerticalAxisGroup #'nonstaff-relatedstaff-spacing
#'basic-distance = #4.5
  \override VerticalAxisGroup #'nonstaff-relatedstaff-spacing
#'stretchability = #0
} \lyricsto upper \commonLyr
%
\new Lyrics = lower \with {
  \override VerticalAxisGroup #'staff-affinity = #DOWN
} \lyricsto upper \lowerLyr
%
\new Staff = lowers 
  \new Voice = lower { \lowerMel }

  
}
 End

Attachments:
lyrics-alignment-combined.png  14.5 KB


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1499 in lilypond: Add modal transformations

2011-02-13 Thread lilypond 

Updates:
Labels: -Patch-review Patch-needs_work

Comment #5 on issue 1499 by percival.music.ca: Add modal transformations
http://code.google.com/p/lilypond/issues/detail?id=1499

(No comment was entered for this change.)


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: slurs and ties confuse note separation

2011-02-13 Thread Phil Holmes 


Keith OHara k-ohara5...@oco.net wrote in message 
news:op.vpjmrsbckr5sjt@ohara...

% Note spacing should allow for accidentals and articulations
% Usually it does, but slurs and ties can cause errors

\version 2.12.3 % same in 2.13.46
{ g''8( c''\espressivo geses'' b''') }

To make the image showing the debug-output, I added to what is above,

\layout { \context { \Score
  \override PaperColumn #'stencil = #ly:separation-item::print
}} #(ly:set-option 'debug-skylines

http://code.google.com/p/lilypond/issues/detail?id=1511



--
Phil Holmes
Bug Squad



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Issue 1511 in lilypond: Slurs and ties confuse note separation

2011-02-13 Thread lilypond 

Status: Accepted
Owner: 
Labels: Type-Collision Priority-Medium

New issue 1511 by philehol...@googlemail.com: Slurs and ties confuse note  
separation

http://code.google.com/p/lilypond/issues/detail?id=1511

Reported by Keith O'Hara:

% Note spacing should allow for accidentals and articulations
% Usually it does, but slurs and ties can cause errors

\version 2.12.3 % same in 2.13.46
{ g''8( c''\espressivo geses'' b''') }

To make the image showing the debug-output, I added to what is above,

\layout { \context { \Score
   \override PaperColumn #'stencil = #ly:separation-item::print
}} #(ly:set-option 'debug-skylines


Attachments:
needless.collision.png  12.1 KB


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1511 in lilypond: Slurs and ties confuse note separation

2011-02-13 Thread lilypond 


Comment #1 on issue 1511 by philehol...@googlemail.com: Slurs and ties  
confuse note separation

http://code.google.com/p/lilypond/issues/detail?id=1511

Keith also commented:

The problem should be rare, but seems hard to fix completely.  Workarounds  
are


1)\once\override Script #'avoid-slur = #'outside
before each occurrence, replacing 'outside by 'inside if you want the  
Script inside, and replacing Script by Fingering or StringNumber if those  
are the things being collided with.


or 2)\override Script #'extra-spacing-height = #'(-3 . 3)
if you want to avoid trying to tuck notes in these situations, through the  
rest of the score.





___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Issue 1512 in lilypond: Page-label.ly regtest failure

2011-02-13 Thread lilypond 

Status: Accepted
Owner: 
Labels: Type-Defect Priority-Critical Regression

New issue 1512 by philehol...@googlemail.com: Page-label.ly regtest failure
http://code.google.com/p/lilypond/issues/detail?id=1512

Page 3 of page-label.ly changed significantly between 13.46 and 13.47.   
With .46, the music occupies a single system - with .47 and subsequent it  
splits into 2 systems and some of the \mark text disappears off the side of  
the page.  It looks like the difference comes from minor adjustments to the  
spacing algorithms causing Lily to decide to break the music into 2 systems  
- it can easily be rectified by updating the regtest itself to place a  
\noBreak on the relevant line.  Doing this causes the image to return to  
being identical.


I'm classifying this as regression-critical, since that's the strict  
situation, but propose a patch to the regtest as above should be used to  
fix it.


Attachments:
page-label-page3.13.46.png  7.8 KB
page-label-page3.13.47.png  8.6 KB


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1131 in lilypond: Spacing bug with above lyrics

2011-02-13 Thread lilypond 

Updates:
Status: Fixed

Comment #3 on issue 1131 by philehol...@googlemail.com: Spacing bug with  
above lyrics

http://code.google.com/p/lilypond/issues/detail?id=1131

This has been fixed with documentation changes introduced with 1483.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Regression: Interrupted extender line, figured bass

2011-02-13 Thread Mats Bengtsson 

Hi,

The following example shows a regression compared to version 2.12. It 
produces two extender lines that were vertically aligned in 2.12 but are 
not aligned in version 2.13.49. I'm not sure if it worked by incident or 
if it was intended behavior in 2.12, and I can hardly recall why I used 
this specific construct when typesetting the piece two years back.


\version 2.13.49

ext = {
  \once \set useBassFigureExtenders = ##t
}

\score{

\new Staff \relative c' {
\clef bass
c2 c, ~ | % \break
c4 c c2 |
  }
\new FiguredBass \figuremode{
_!1 \ext |
_!2 \ext _!2 |
  }

}


   /Mats


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1512 in lilypond: Page-label.ly regtest failure

2011-02-13 Thread lilypond 


Comment #1 on issue 1512 by k-ohara5...@oco.net: Page-label.ly regtest  
failure

http://code.google.com/p/lilypond/issues/detail?id=1512

LilyPond version 2.12.3 also used 2 lines on page '3', like 2.13.47+ do.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1512 in lilypond: Page-label.ly regtest failure

2011-02-13 Thread lilypond 


Comment #2 on issue 1512 by philehol...@googlemail.com: Page-label.ly  
regtest failure

http://code.google.com/p/lilypond/issues/detail?id=1512

Good spot.  However, the result from 2.12.3 shows all of the \mark label,  
whereas 2.13.47+ do not.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Issue 1513 in lilypond: Figured bass extenders do not line up

2011-02-13 Thread lilypond 

Status: Accepted
Owner: 
Labels: Type-Defect Priority-Critical Regression

New issue 1513 by philehol...@googlemail.com: Figured bass extenders do not  
line up

http://code.google.com/p/lilypond/issues/detail?id=1513

Reported by Mats Bengtsson:

The following example shows a regression compared to version 2.12. It
produces two extender lines that were vertically aligned in 2.12 but are
not aligned in version 2.13.49. I'm not sure if it worked by incident or
if it was intended behavior in 2.12, and I can hardly recall why I used
this specific construct when typesetting the piece two years back.

\version 2.13.49

ext = {
   \once \set useBassFigureExtenders = ##t
}

\score{

\new Staff \relative c' {
 \clef bass
 c2 c, ~ | % \break
 c4 c c2 |
   }
\new FiguredBass \figuremode{
_!1 \ext |
_!2 \ext _!2 |
   }
 
}



Attachments:
2.12.3.png  2.5 KB
2.13.49.png  1.9 KB


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1512 in lilypond: Page-label.ly regtest failure

2011-02-13 Thread lilypond 


Comment #3 on issue 1512 by n.putt...@gmail.com: Page-label.ly regtest  
failure

http://code.google.com/p/lilypond/issues/detail?id=1512

However, the result from 2.12.3 shows all of the \mark label, whereas  
2.13.47+ do not.


http://code.google.com/p/lilypond/issues/detail?id=997#c5

(+ http://lists.gnu.org/archive/html/bug-lilypond/2009-12/msg00394.html)


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1426 in lilypond: [PATCH]Better support for beat slashes (multi-slash mixed duration). (issue212048)

2011-02-13 Thread lilypond 

Updates:
Status: Fixed
Labels: -Patch-review fixed_2_13_51

Comment #3 on issue 1426 by n.putt...@gmail.com: [PATCH]Better support for  
beat slashes (multi-slash  mixed duration). (issue212048)

http://code.google.com/p/lilypond/issues/detail?id=1426

(No comment was entered for this change.)


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1208 in lilypond: Some combination of 'staff-affinity for two Lyrics may cause unwanted vertical space

2011-02-13 Thread lilypond 


Comment #11 on issue 1208 by carl.d.s...@gmail.com: Some combination  
of 'staff-affinity for two Lyrics may cause unwanted vertical space

http://code.google.com/p/lilypond/issues/detail?id=1208

Here's another version that is even tighter.


% -8--
\version 2.13.42

lowerMel = \relative c '' {
  c4 c c c |
  a4 a a a |
  a4 a a a |
}

upperMel = \relative c'' {
  c4 c c c |
  c4 c c c |
  a4 a a a |
}

upperLyr = \lyricmode {
  \repeat unfold 4 { \skip 1 }
  u u u u
}

commonLyr = \lyricmode {
  c c c c
  \repeat unfold 4 {\skip 1}
  c c c c
}

lowerLyr = \lyricmode {
  \repeat unfold 4 { \skip 1 }
  l l l l
}

\score {
  \new ChoirStaff 
\new Staff = uppers \with {
  \override VerticalAxisGroup #'staff-staff-spacing =
#'((basic-distance . 12))
} 
  \new Voice = upper { \upperMel }

\new Lyrics = upper \with {
  \override VerticalAxisGroup #'staff-affinity = #UP
  \override VerticalAxisGroup #'nonstaff-nonstaff-spacing
#'minimum-distance = #0
  \override VerticalAxisGroup #'nonstaff-nonstaff-spacing
#'stretchability = #1000
} \lyricsto upper \upperLyr
%
\new Lyrics = common \with {
  \override VerticalAxisGroup #'staff-affinity = #CENTER
  \override VerticalAxisGroup #'nonstaff-relatedstaff-spacing
#'basic-distance = #6
  \override VerticalAxisGroup #'nonstaff-relatedstaff-spacing
#'stretchability = #0
  \override VerticalAxisGroup #'nonstaff-nonstaff-spacing
#'minimum-distance = #0
  \override VerticalAxisGroup #'nonstaff-unrelatedstaff-spacing
#'stretchability = #1000
  \override VerticalAxisGroup #'nonstaff-nonstaff-spacing
#'stretchability = #1000
} \lyricsto upper \commonLyr
%
\new Lyrics = lower \with {
  \override VerticalAxisGroup #'staff-affinity = #DOWN
  \override VerticalAxisGroup #'nonstaff-relatedstaff-spacing
#'basic-distance = #2
  \override VerticalAxisGroup #'nonstaff-relatedstaff-spacing
#'stretchability = #0
} \lyricsto upper \lowerLyr
%
\new Staff = lowers 
  \new Voice = lower { \lowerMel }

  
  %
  \layout {
\context {
  \Lyrics
%\override VerticalAxisGroup
%  #'nonstaff-nonstaff-spacing #'stretchability = #10
}
  }
}
% -8--


Attachments:
lyric-align-new-closer.png  13.9 KB


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond