bug-lilypond
[Top][All Lists]
Advanced

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

Re: Unwanted explicit flats


From: Erik Sandberg
Subject: Re: Unwanted explicit flats
Date: Mon, 11 Apr 2005 16:34:07 +0200
User-agent: KMail/1.7.2

Thanks, added to database as auto-accidental-barnumber.ly.

Erik

%
%Karl Hammar <address@hidden>

\version "2.4.2"

\header {
reportedin = "2.4.2"
texidoc = "Automatic accidentals don't work as expected when changing 
Score.currentBarNumber"
}

\relative c'' {
  \key c \minor
  a4 b4 c2 |
  d1 |
  \set Score.currentBarNumber = #1
  c2 as4 bes |
%  ^   ^  theese two are rendered with flats
}


On Sunday 10 April 2005 14.29, Karl Hammar wrote:
> For both:
> $ dpkg -l lilypond-snapshot | tail -1
> ii  lilypond-snaps 2.4.2-1        A program for typesetting sheet music
> $ grep ChangeLog CVS/Entries
> /ChangeLog/1.3417/Sat Apr  9 19:46:03 2005//
>
> score below gives me an unwanted explicit flat in
> the next to last measure.
>
> \version "2.4.2"
>
> \relative c'' {
>   \override Score.BarNumber  #'break-visibility = #end-of-line-invisible
>   \mark #03
>   \clef treble
>   \key c \minor
>   a2 b |
>   d1 |
>   \mark #04
>   \set Score.currentBarNumber = #1
>   d2 es8. as,16 bes8 c |
> %         ^     ^  theese two are rendered with flats
>   d1
> }
>
> This is a condenced example of http://aspodata.se/motett/noter/act1.ly.
> See act1.pdf at same site, page 5, Be staff, measure 5.
> Similar errors are all over the place.
>
> When comment the \set Score.currentBarNumber = #1, the flats disappear.





reply via email to

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