Re: possible bad output in mensural-ligatures.ly

2011-09-22 Thread Bertrand Bordage
I'm ok with this subject.

A better minimal example would be :

\new MensuralStaff {
  \cadenzaOn
  \[ a'\breve g' as' \]
}

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


Re: possible bad output in mensural-ligatures.ly

2011-09-18 Thread Bertrand Bordage
This collision has always been (2.12.3, 2.14.2...).

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


Misleading clef placement at the end of a volta.

2011-09-02 Thread Bertrand Bordage
Hi all,

Here's the problem:

% Bug report snippet
\markup "This gives the impression that the repeat should be done with a F
clef."
{
\clef F r2 r4 \clef G r8 a
\repeat volta 2 { \repeat unfold 8 d'4 }
\alternative {
{ d' r4 r r8 a }
{ \clef F d4 d d d }
}
}

\markup "This is what should be engraved."
{
\clef F r2 r4 \clef G r8 a
\repeat volta 2 { \repeat unfold 8 d'4 }
\alternative {
{ d' r4 r r8 a }
{
\override Score.Clef #'break-align-symbol = #'time-signature
\clef F d4 d d d
}
}
}
% End of bug report snippet

There's a similar problem with time signatures. See Kurt Stone's “Music
Notation in the Twentieth Century”, page 34.

Regards,
Bertrand
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: NR3.2.2: erroneous example?

2011-08-19 Thread Bertrand Bordage
You should ask to James Lowe

It's one of his commits :9bc65fa2efa4711ce96c648db6d703ae190f944c

Maybe it's to show something; there was a line
title = "title"  % not printed
before this commit.

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


Re: Inconsistent baseline-skip in markups with multi-rows commands

2011-08-14 Thread Bertrand Bordage
I'll add an issue on the tracker.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Misleading autobeaming in 3/4

2011-08-14 Thread Bertrand Bordage
Hi again,

There's a small defect in autobeaming:

%%%
\markup "This:"
\relative c'' { \time 3/4 a4. b8 c d e d c b4. a8 b c d c b a2. }
\markup "looks like 6/8:"
\relative c'' { \time 6/8 a4. b8 c d e d c b4. a8 b c d c b a2. }
\markup "but should be like this:"
\relative c'' { \time 3/4 a4. b8\noBeam c d e d c\noBeam b4. a8 b c d c b
a2. }
%%%

Unfortunately, I don't think this can be easily fixed with the current
system.

Regards,
Bertrand
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Inconsistent baseline-skip in markups with multi-rows commands

2011-08-14 Thread Bertrand Bordage
Hi,

In such examples, baseline-skip doesn't behave as expected:

%%
#(set-default-paper-size "a9")
\markuplines {
  \justified-lines { a a a a a a a a a a a a }
  "a" }
%%

I think this would be avoided if multi-rows commands were really creating a
new markup for each line instead of making a single markup.
A fix for this may probably require a lot of downstream changes.

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


Markuplines doesn't respect well top-markup-spacing.

2011-08-04 Thread Bertrand Bordage
Hello,

In the following example, the markups on the second page should be on its
bottom:

#(set-default-paper-size "a10" 'landscape)
\paper {
  top-markup-spacing = #'((padding . 5))
}
\markuplines { a a a a a a a a a a a  }

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


Re: Collision between figures and tie

2011-07-28 Thread Bertrand Bordage
>
> Is this possibly related to
> http://code.google.com/p/lilypond/issues/detail?id=1277 ?


Probably. 'Tis difficult to say without some code browsing.

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


Collision between figures and tie

2011-07-26 Thread Bertrand Bordage
Hi all,

Figures avoid slur but not ties :

\new Staff << { c'2( c') c'~ c' }
\figuremode {
  \bassFigureStaffAlignmentDown
  \repeat unfold 8 <5 3>4
} >>

Regards,
Bertrand
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Ties colliding in single-staff polyphony

2011-07-18 Thread Bertrand Bordage
Thanks Dmytro !

I looked at what Mike said.
Could not there be more code in common between ties and slurs?
A tie isn't so different from a slur, is it ?
By doing so, we could get rid of TieColumn and many bugs.
Do you think that keeping just the slur scoring and an hypothetic
slur_collision_engraver would do the job?

Thanks,
Bertrand
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Ties colliding in single-staff polyphony

2011-07-18 Thread Bertrand Bordage
Hi all,

A bug I noticed years ago :

<<
  { a'4~ a' a'~ a' ~  } \\
  { c' c' c' c' } \\
  { f'~ f' \shiftOff f'~ f' } \\
>>

Ties should take noteheads from other contexts into account.

Regards,
Bertrand
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Balloon fails with cross-staff arpeggios

2011-05-16 Thread Bertrand Bordage
Example :

\version "2.15"
\new PianoStaff \with { \consists "Balloon_engraver" } <<
  \set PianoStaff.connectArpeggios = ##t
 { \balloonGrobText #'Arpeggio #'(-0.1 . 0) \markup "G.O." \repeat unfold 5
a''\arpeggio }
 { \repeat unfold 5 a\arpeggio } >>

Regards,
Bertrand
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Beam_collision_engraver sometimes fails on demisemiquavers or shorter notes

2011-05-04 Thread Bertrand Bordage
This isn't a regression. I suggest a medium or high prority.
Here is an example :

\version "2.15"
<<
  { a'32[ a' a' a'] }
  \\
  { c''[ d'' d'' d''] }
>>

Regards,
Bertrand
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


[Regression] Beam_collision_engraver and StaffSymbol overrides

2011-04-08 Thread Bertrand Bordage
Hello,

When we use a smaller staff, Beam_collision_engraver creates collisions that
where not in 2.12.

\version "2.13"
music = << \relative c'' { e16 f e c } \\ \relative c''' { g a g e } >>

\new Staff \music
\new Staff \with {
  fontSize = #-3
  \override StaffSymbol #'staff-space = #(magstep -3)
  \override StaffSymbol #'thickness = #(magstep -3) }
  \music

In this simple case, removing Beam_collision_engraver on the small staff
solves the problem. But on more complicated cases, Beam_collision_engraver
should handle this.
Or, at least for the moment, we should add "\remove Beam_collision_engraver"
to the ossia staves doc (NR 1.6.2).

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


[small regression?] Demisemiquaver beamException when in 12/8

2011-04-07 Thread Bertrand Bordage
Hi !

Why is there an exception for demisemiquavers when time is 12/8 ?
Shouldn't this be for hemidemisemiquavers ? Or no exception ?
I have many scores with such cases :

\version "2.13"
{ \time 12/8 \repeat unfold 6 a16 a8 a a16 a32 a \repeat unfold 6 a8 }

I don't think any editor will represent it the way 2.13 does.

Another question :
In time-signature-settings.scm, lines 164 and 170, why are baseMoment
defined ?

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


Re: Bass figures are not horizontally aligned to whole notes

2011-03-01 Thread Bertrand Bordage
I'm not quite sure of my workaround. It's a poor modification of this
snippet : http://lsr.dsi.unimi.it/LSR/Item?id=637
I think it affects all figures because they are not centered on notes. As
you can see on slashed digits or on a column of figures...
That's also why I call this a workaround and not a solution :)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Bass figures are not horizontally aligned to whole notes

2011-03-01 Thread Bertrand Bordage
Yes, I forgot a \new FiguredBass.
figuredBassCenterOnNote = \override BassFigure #'X-offset =
#(lambda (grob)
 (let* ((paper-col (ly:grob-parent grob X))
(elts (ly:grob-object paper-col 'elements))
(figure grob))

   (for-each
(lambda (idx)
  (let ((elt (ly:grob-array-ref elts idx)))
(set! figure elt)))
(iota (ly:grob-array-length elts)))

   (-
 (interval-center (ly:grob-robust-relative-extent figure figure X))
 (interval-center (ly:stencil-extent(ly:text-interface::print grob) X)


\new Staff << { \clef F c4 c c c c2 c c1 c c c \bar "|."}
  \new FiguredBass \figuremode {
\figuredBassCenterOnNote
<5>4 <6 4> <6 5> <_+> <6 4>2 <5> <_+>1 <5> <6 4 2> <6>
  } >>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Bass figures are not horizontally aligned to whole notes

2011-03-01 Thread Bertrand Bordage
\new Staff << { \clef F f4 g g2 c1 d }
  \figuremode {
<5/>4 <6 4> <4> <_+> <_!>1 <6/>
  } >>

Figures should be aligned to whole notes.

Workaround attached.
figuredBassCenterOnNote = \override BassFigure #'X-offset =
#(lambda (grob)
 (let* ((paper-col (ly:grob-parent grob X))
(elts (ly:grob-object paper-col 'elements))
(figure grob))

   (for-each
(lambda (idx)
  (let ((elt (ly:grob-array-ref elts idx)))
(set! figure elt)))
(iota (ly:grob-array-length elts)))

   (-
 (interval-center (ly:grob-robust-relative-extent figure figure X))
 (interval-center (ly:stencil-extent(ly:text-interface::print grob) X)


\new Staff << { \clef F c4 c c c c2 c c1 c c c \bar "|."}
  \figuremode {
\figuredBassCenterOnNote
<5>4 <6 4> <6 5> <_+> <6 4>2 <5> <_+>1 <5> <6 4 2> <6>
  } >>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond