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 g
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.
Th
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
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
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
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 produ
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
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
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.
__
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
__
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.)
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 buil
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.
__
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
488ad43dacc132fc2b474fd15a06
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-
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
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
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
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-lil
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
\transpos
20 matches
Mail list logo
