Beaming problem introduced with 2.13.60
Example below demonstrates (a couple of bars taken from Bach's
chaconne). This problem did not exist in versions prior to 2.13.60:
%=
\version "2.13.60"
\language "english"
\relative c' {
\time 3/4
\key d \minor
\stemUp
d,16 bf''' bf gs gs f f d d b gs e |
\stemDown cs a'' a fs fs ef ef c \stemUp c a fs( d) |
}
%=
The console log contains
Drawing systems...
programming error: No viable beam quanting found. Using unquanted y value.
continuing, cross fingers
/home/nick/lilypond/examples/test.ly:9:18: warning: weird stem size,
check for narrow beams
\stemDown
cs a'' a fs fs ef ef c \stemUp c a fs( d) |
programming error: No viable beam quanting found. Using unquanted y value.
continuing, cross fingers
/home/nick/lilypond/examples/test.ly:9:39: warning: weird stem size,
check for narrow beams
\stemDown cs a'' a fs fs ef ef
c \stemUp c a fs( d) |
And the output looks like
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Git master build for V2.13.60 in fresh directory - make docs fails
On 11-04-16 05:30 AM, Graham Percival wrote: On Fri, Apr 15, 2011 at 10:50:11PM +0100, Ian Hulin wrote: (are you using lilydev or your own system?) Own system. I fetched all the git changes into local repository $HOME/lilypond, then did a $ git rebase origin/master on my local repository. Then nuked the contents of my build subdirectory $ .autogen.sh --noconfigure $ cd build $../configure --disable-optimising hmm. At this step, could you try - edit make/website/make to remove all languages (i.e. you want WEB_LANGS = and then a new line) - from the build dir, run: make website&> log.txt and then send me log.txt. Cheers, - Graham Rather than editing website.make (risking forgetting to undo it, as I have), I believe you can make WEB_LANGS='' website i.e. passing the variable definition on the command line overrides the declaration inside the makefile. hth, Colin -- 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: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice
On Fri, Apr 15, 2011 at 7:59 AM, wrote:
> Comment #3 on issue 1613 by bordage@gmail.com: Beamed stems too long
> when avoiding low note in other voice
> http://code.google.com/p/lilypond/issues/detail?id=1613
>
> Han-Wen's commit has broken Beam_collision_engraver. One example among
> others :
>
> \relative c'' { d32 ees d c b c b a }
I just installed 2.13.60. The code below results in good beams in
2.13.59, but not in 2.13.60. Does this have the same cause as reported
above? Thanks.
-Jay
\version "2.13.60"
\score
{
\new Staff \relative c''
{
<<
{ ees4. c8 }
\\
{ 8 q q q }
>>
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1502 in lilypond: DOcument information in PDF headers requires escapes for accented characters
Updates: Status: Started Comment #3 on issue 1502 by reinhold...@gmail.com: DOcument information in PDF headers requires escapes for accented characters http://code.google.com/p/lilypond/issues/detail?id=1502 Pushed to master with commit dffe04e8e1a7c0b94fdfc30e44fe141dfbe7cbec ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1609 in lilypond: unpredictable change of voicing
Comment #8 on issue 1609 by k-ohara5...@oco.net: unpredictable change of voicing http://code.google.com/p/lilypond/issues/detail?id=1609 The variation in position of the rests appeared somewhere between 2.13.48 and .54 ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1609 in lilypond: unpredictable change of voicing
Comment #7 on issue 1609 by k-ohara5...@oco.net: unpredictable change of voicing http://code.google.com/p/lilypond/issues/detail?id=1609 Regtest change pushed in 6afd86a9b, to appear in 2.15.0 Note that the pushed change only prevents a regression test from generating a .ly file that produces varying typeset output. This problem was, I think, the critical aspect of this issue. As the examples above illustrate, placement of such rests still changes unpredictably. The score in example 2 produces different output with the two command lines lilypond test.ly lilypond test.ly test.ly while version 2.12.3 produces the same output in either case. Both versions produce a warning "too many colliding rests". See also issue 1547 and issue 384. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1609 in lilypond: unpredictable change of voicing
Comment #6 on issue 1609 by k-ohara5...@oco.net: unpredictable change of voicing http://code.google.com/p/lilypond/issues/detail?id=1609 Regtest change pushed in 6afd86a9b, to appear 2.15.0 Note that the pushed change only prevents a regression test from generating a .ly file with multiple simultaneous rests, simultaneous with notes. This problem was, I think, the critical aspect of this issue. As the examples above illustrate, placement of such rests still changes unpredictably, but I think that aspect is covered by issue 1547, and issue 384. I recommend to close this issue, if any bug squadder agrees. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1617 in lilypond: chordGlissando is a hack that should be replaced with a Glissando property such as 'connect-all
Status: Accepted Owner: Labels: Type-Enhancement Priority-Low New issue 1617 by carl.d.s...@gmail.com: chordGlissando is a hack that should be replaced with a Glissando property such as 'connect-all http://code.google.com/p/lilypond/issues/detail?id=1617 chordGlissando is a hack; it uses a bunch of Scheme code with hard-coded settings that can't be adjusted by users. It also creates temporary voices with hidden notes, so the properties set in the current voice aren't used. And it won't handle three notes. It should probably have never been added to music-functions-init.ly, but it's there, so I think we should leave it until we get it fixed right. The ideal way to get slide indications is to add a property to Glissando, e.g. 'connect-all, that will have the Glissando engraver create multiple glissando lines when two chords are linked. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1609 in lilypond: unpredictable change of voicing
Updates: Labels: -Patch-new Patch-review Comment #5 on issue 1609 by colinpkc...@gmail.com: unpredictable change of voicing http://code.google.com/p/lilypond/issues/detail?id=1609 Applies cleranly to 2.13.61 and partcombine-midi shows the rests no longer there. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice
Comment #4 on issue 1613 by mts...@gmail.com: Beamed stems too long when avoiding low note in other voice http://code.google.com/p/lilypond/issues/detail?id=1613 I see a similar issue in my copy of the Webern symphony. Attachments: foo.png 3.0 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1616 in lilypond: old website link gives false doc suggestion info
Updates: Status: Fixed Owner: percival.music.ca Labels: fixed_2_13_61 Comment #1 on issue 1616 by carl.d.s...@gmail.com: old website link gives false doc suggestion info http://code.google.com/p/lilypond/issues/detail?id=1616 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Git master build for V2.13.60 in fresh directory - make docs fails
On Fri, Apr 15, 2011 at 10:50:11PM +0100, Ian Hulin wrote: > (are you using lilydev or your own > > system?) > > > Own system. I fetched all the git changes into local repository > $HOME/lilypond, then did a > $ git rebase origin/master on my local repository. > Then nuked the contents of my build subdirectory > $ .autogen.sh --noconfigure > $ cd build > $../configure --disable-optimising hmm. At this step, could you try - edit make/website/make to remove all languages (i.e. you want WEB_LANGS = and then a new line) - from the build dir, run: make website &> log.txt and then send me log.txt. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1609 in lilypond: unpredictable change of voicing
Updates: Labels: Patch-new Comment #4 on issue 1609 by percival.music.ca: unpredictable change of voicing http://code.google.com/p/lilypond/issues/detail?id=1609 Not tested yet, but I'm very happy to see that a simple patch like that can fix it. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1616 in lilypond: old website link gives false doc suggestion info
Status: Accepted Owner: Labels: Priority-Critical Type-Documentation New issue 1616 by percival.music.ca: old website link gives false doc suggestion info http://code.google.com/p/lilypond/issues/detail?id=1616 Commits ffabc59bec93b934276a0d4aca9ce31ff30ce381 488ad43dacc132fc2b474fd15a068b6872759507 fix some incorrect/unclear information which gives considerable confusion to new contributors wishing to make documentation suggestions. I consider the old to the old website to be a Critical problem, but I think both commits should be applied to stable/2.14. Carl: please mark this fixed_2_13_61 when you have backported it. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: beam/clef crash
On 16 April 2011 11:59, David Bobroff wrote: > > I ran across this in a score I'm preparing. For the example to show the > problem I actually had to raise the chord by a step. Result is good with 2.13.59. Cheers, Xavier -- Xavier Scheuer <>___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
beam/clef crash
I ran across this in a score I'm preparing. For the example to show the
problem I actually had to raise the chord by a step.
-David
The beam passes through the clef:
Bug? Known issue? I'm sure that extending the stem would fix this but
should this be the kind of thing Lily figures our on her own?
% BEGIN LILYPOND %
\version "2.12.3"
\relative c' {
\clef F
g8.
\clef G
16
}
% END LILYPOND %
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 712 in lilypond: alignment of multiple \tempo marks over `church rests'
Comment #4 on issue 712 by x.sche...@gmail.com: alignment of multiple
\tempo marks over `church rests'
http://code.google.com/p/lilypond/issues/detail?id=712
Output is different with 2.13.59 since issue 684 is now fixed.
Now the text string of @code{\tempo} over whole bar rests always starts
at the beginning of a bar.
The output is not very pleasant though (IMHO). It is maybe better than
2.12 but I'd prefer it to be aligned over the first (non-existant) note
(NoteColumn?).
See attachment.
Attachments:
tempo-mark-rest-alignment.ly 695 bytes
tempo-mark-rest-alignment.png 4.7 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1604 in lilypond: MultiMeasureRest staff position 0 is taken as staff position 2
Updates: Labels: -Patch-review Patch-needs_work Comment #4 on issue 1604 by percival.music.ca: MultiMeasureRest staff position 0 is taken as staff position 2 http://code.google.com/p/lilypond/issues/detail?id=1604 Judging from Mike's latest comment, he thinks there is some other work to do before tackling this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1605 in lilypond: PS -> PDF conversion fails
Updates: Status: Fixed Labels: -Patch-review fixed_2_13_60 Comment #6 on issue 1605 by percival.music.ca: PS -> PDF conversion fails http://code.google.com/p/lilypond/issues/detail?id=1605 pushed. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re:Re: midi bug remains in 2.13.58
Ok, Here's my example, just 4 bars. If using 2.13.52, no warnings about channel
wrapping is given. Try using the commented line, and the two results are both
bad.
Haipeng
\version "2.13.59"
piccolo = \relative c''' {
\clef treble \key e \minor \numericTimeSignature \time 6/4
\transposition c''
e2. e | R1. | R1. | e2. e |
}
flutes = \relative c''' {
\clef treble \key e \minor \numericTimeSignature \time 6/4
e2. e | R1. | R1. | e2. e |
}
oboes = \relative c'' {
\clef treble \key e \minor \numericTimeSignature \time 6/4
e2. e | R1. | R1. | e2. e |
}
clarinets = \relative c' {
\clef treble \key fis \minor \numericTimeSignature \time 6/4
\transposition bes
fis2. fis | R1. | R1. | fis2. fis |
}
bassoons = \relative c {
\clef bass \key e \minor \numericTimeSignature \time 6/4
e2. e | R1. | R1. | e2. e |
}
hornI = \relative c'' {
\clef treble \key b \minor \numericTimeSignature \time 6/4
\transposition f
b2. b | R1.*3 |
}
hornII = \relative c' {
\clef treble \key b \minor \numericTimeSignature \time 6/4
\transposition f
b2. b | R1.*3 |
}
trumpets = \relative c'' {
\clef treble \key fis \minor \numericTimeSignature \time 6/4
\transposition bes
fis2. fis |
\set Staff.midiInstrument = "muted trumpet"
fis fis |
\set Staff.midiInstrument = "trumpet"
fis fis | R1. |
}
trombones = \relative c {
\clef tenor \key e \minor \numericTimeSignature \time 6/4
e2. e | R1.*3 |
}
tuba = \relative c, {
\clef bass \key e \minor \numericTimeSignature \time 6/4
e2. e | R1.*3 |
}
timpani = \relative c {
\clef bass \key e \minor \numericTimeSignature \time 6/4
e2. e | R1.*3 |
}
violinI = \relative c''' {
\clef treble \key e \minor \numericTimeSignature \time 6/4
e2. e |
\set Staff.midiInstrument = "pizzicato strings"
e e |
\set Staff.midiInstrument = "violin"
e
\set Staff.midiInstrument = "string ensemble 1"
e | R1. |
}
violinII = \relative c'' {
\clef treble \key e \minor \numericTimeSignature \time 6/4
e2. e |
\set Staff.midiInstrument = "tremolo strings"
e e |
\set Staff.midiInstrument = "pizzicato strings"
e
\set Staff.midiInstrument = "string ensemble 1"
e | R1. |
}
viola = \relative c' {
\clef alto \key e \minor \numericTimeSignature \time 6/4
e2. e |
\set Staff.midiInstrument = "viola"
e e |
\set Staff.midiInstrument = "pizzicato strings"
e e | R1. |
}
cello = \relative c {
\clef bass \key e \minor \numericTimeSignature \time 6/4
e2. e |
\set Staff.midiInstrument = "cello"
e e | R1. | R1. |
}
contrabass = \relative c {
\clef bass \key e \minor \numericTimeSignature \time 6/4
\transposition c
e2. e |
\set Staff.midiInstrument = "contrabass"
e e | R1. | R1. |
}
\score {
\new StaffGroup = "orchestra" <<
%\set Score.midiChannelMapping = #'staff
\new Staff = "piccolo" {
\set Staff.midiInstrument = "piccolo"
\piccolo
}
\new Staff = "flutes" {
\set Staff.midiInstrument = "flute"
\flutes
}
\new Staff = "oboes" {
\set Staff.midiInstrument = "oboe"
\oboes
}
\new Staff = "clarinets" {
\set Staff.midiInstrument = "clarinet"
\clarinets
}
\new Staff = "bassoons" {
\set Staff.midiInstrument = "bassoon"
\bassoons
}
\new Staff = "horns" {
\set Staff.midiInstrument = "french horn"
<< \hornI \\ \hornII >>
}
\new Staff = "trumpets" {
\set Staff.midiInstrument = "trumpet"
\trumpets
}
\new Staff = "trombones" {
\set Staff.midiInstrument = "trombone"
\trombones
}
\new Staff = "tuba" {
\set Staff.midiInstrument = "tuba"
\tuba
}
\new Staff = "timpani" {
\set Staff.midiInstrument = "timpani"
\timpani
}
\new StaffGroup = "strings" <<
\set StaffGroup.midiInstrument = "string ensemble 1"
\new Staff = "violini" { \violinI }
\new Staff = "violinii" { \violinII }
\new Staff = "viola" { \viola }
\new Staff = "violoncello" { \cello }
\new Staff = "bass" { \contrabass }
>>
>>
\midi { }
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
