Hi,
As of now the proper way of entering unmetered music is with cadenzas
(or am i wrong?). This has quite serious (or at least quite seriously
inconvenient) drawback: LilyPond won't make line breaks itself, you
have to add them manually.
Probably because of that some people don't use cadenzas and
Updates:
Status: Started
Comment #9 on issue 37 by carl.d.s...@gmail.com: collision notehead and
beams
http://code.google.com/p/lilypond/issues/detail?id=37
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilypo
Updates:
Status: Fixed
Labels: fixed2_13_47
Comment #9 on issue 1061 by carl.d.s...@gmail.com: Pure-height inaccuracy
very large when skyline significantly non-rectangular
http://code.google.com/p/lilypond/issues/detail?id=1061
This is now fixed in 2.13.47. I'm not sure exact
Updates:
Status: Fixed
Labels: fixed_2_13_47
Comment #1 on issue 317 by carl.d.s...@gmail.com: Aligned-above lyrics
should stay close to their staff
http://code.google.com/p/lilypond/issues/detail?id=317
This has been fixed. I'm not sure exactly when.
But it certainly works
Updates:
Status: Started
Owner: Carl.D.Sorensen
Labels: Patch
Comment #15 on issue 1483 by carl.d.s...@gmail.com: Lyric alignment is
wrong in 2.13.46
http://code.google.com/p/lilypond/issues/detail?id=1483
Patch posted to Rietveld.
http://codereview.appspot.com/406104
Updates:
Owner: Carl.D.Sorensen
Labels: Patch
Comment #3 on issue 1486 by carl.d.s...@gmail.com: Lyrics above the first
staff in a system are spaced too closely for the first system
http://code.google.com/p/lilypond/issues/detail?id=1486
Patch posted to Rietveld
http://codere
Comment #7 on issue 1228 by pkx1...@hotmail.com: \override RestCollision
#'positioning-done = #merge-rests-on-positioning
http://code.google.com/p/lilypond/issues/detail?id=1228
added http://codereview.appspot.com/4005046/
___
bug-lilypond mailing
On 22 January 2011 22:49, Trond wrote:
>
> I have a problem with excessive spacing in the middle of my score. Changing
> the
> key from c minor to c major fixes it, even when changing to major _after_ the
> spacing issue. Is this a bug?
>
> \version "2.12.3"
> \include "english.ly"
>
> \score {
>
> I'm not top posting.
I have a problem with excessive spacing in the middle of my score. Changing the
key from c minor to c major fixes it, even when changing to major _after_ the
spacing issue. Is this a bug?
\version "2.12.3"
\include "english.ly"
\score {
<<
\new ChordNames \chordm
Comment #8 on issue 37 by mts...@gmail.com: collision notehead and beams
http://code.google.com/p/lilypond/issues/detail?id=37
Newest patchset here, which has a regtest:
http://codereview.appspot.com/3928041
___
bug-lilypond mailing list
bug-lilypond
Comment #7 on issue 37 by percival.music.ca: collision notehead and beams
http://code.google.com/p/lilypond/issues/detail?id=37
I believe that the patch in comment 5 is old, and should not be considered
for pushing.
___
bug-lilypond mailing list
b
Updates:
Labels: Priority-Medium
Comment #1 on issue 1488 by percival.music.ca: [PATCH]harmonics and slides
(issue3590041)
http://code.google.com/p/lilypond/issues/detail?id=1488
It looks like there's lots of good work in this patch, but the latest
version seems to have some mixed p
Updates:
Status: Started
Owner: reinhold.kainhofer
Comment #1 on issue 1484 by percival.music.ca: [PATCH] Compound time
signature support in lilypond
http://code.google.com/p/lilypond/issues/detail?id=1484
Reinhold has a few changes he'd like to make to this patch.
_
Updates:
Owner: reinhold.kainhofer
Labels: Priority-Medium
Comment #1 on issue 1435 by percival.music.ca: [PATCH] PartCombine: Keep
track of the state in the Part_combine_engraver (issue3334043)
http://code.google.com/p/lilypond/issues/detail?id=1435
Positive feedback so far o
Updates:
Owner: reinhold.kainhofer
Comment #3 on issue 1485 by percival.music.ca: [PATCH] Allow \markuplines
to be assigned to a variable
http://code.google.com/p/lilypond/issues/detail?id=1485
Reinhold has a few changes he'd like to make to this patch.
_
Comment #1 on issue 1424 by benko@gmail.com: [PATCH]coloratio, black
mensural notation
http://code.google.com/p/lilypond/issues/detail?id=1424
full patchset at
http://codereview.appspot.com/3797046/
___
bug-lilypond mailing list
bug-lilypond@g
Comment #6 on issue 1228 by pkx1...@hotmail.com: \override RestCollision
#'positioning-done = #merge-rests-on-positioning
http://code.google.com/p/lilypond/issues/detail?id=1228
I did get one 'programming error' initially
---snip---
Drawing systems...
programming error: unknown grob in dot c
On Sat, Jan 22, 2011 at 07:11:08PM +0100, Xavier Scheuer wrote:
> On 22 January 2011 19:03, Graham Percival wrote:
> > Please do *not* confuse the issue by calling an idea a "patch".
> > It is not at all helpful.
>
> Wilbert's code ( .ily attachment) works fine but I guess it should be
> include
On 22 January 2011 19:03, Graham Percival wrote:
>
> I don't see a patch. Please create a patch (ideally with git
> format-origin, but I'm willing to work with a plain old diff).
>
> Please do *not* confuse the issue by calling an idea a "patch".
> It is not at all helpful.
You are right.
Wilber
Comment #18 on issue 1472 by k-ohara5...@oco.net: Collision between MMR and
key signature
http://code.google.com/p/lilypond/issues/detail?id=1472
Re: (16) the patch at http://codereview.appspot.com/4095041/ (mostly a
revert of an earlier patch) is the right thing to do. Then note spacing,
On Sat, Jan 22, 2011 at 06:58:26PM +0100, Xavier Scheuer wrote:
> I see Graham doing the "housekeeping" in old (pending) PATCHES related
> to open issues.
> One issue that I'm following that has a pending PATCH for 5 months now.
I don't see a patch. Please create a patch (ideally with git
format-
Hi there,
I see Graham doing the "housekeeping" in old (pending) PATCHES related
to open issues.
One issue that I'm following that has a pending PATCH for 5 months now.
Issue 1228: \override RestCollision #'positioning-done =
#merge-rests-on-positioning
http://code.google.com/p/lilypond/issues/d
On Sat, Jan 22, 2011 at 6:30 AM, Carl Sorensen wrote:
>
>
>
> On 1/22/11 3:36 AM, "Reinhold Kainhofer" wrote:
>
> > Am Freitag, 21. Januar 2011, um 19:13:54 schrieb lilyp...@googlecode.com
> :
> >> At any rate, I think that with the understanding that we need to 1) use
> >> alignAboveContext for
Comment #3 on issue 1376 by percival.music.ca: Ambitus engraver progerror
when a same pitch has different accidentals
http://code.google.com/p/lilypond/issues/detail?id=1376
I cleaned up the indentation of Felipe's patch, and added it to the regtest.
Attachments:
0001-Fix-issue-1376.
Comment #2 on issue 1485 by percival.music.ca: [PATCH] Allow \markuplines
to be assigned to a variable
http://code.google.com/p/lilypond/issues/detail?id=1485
Sorry! ignore that; I was in the wrong browser window. :(
___
bug-lilypond mailing lis
Updates:
Status: Accepted
Labels: Priority-Low
Comment #1 on issue 1485 by percival.music.ca: [PATCH] Allow \markuplines
to be assigned to a variable
http://code.google.com/p/lilypond/issues/detail?id=1485
Updated patches.
Attachments:
0001-Fix-issue-1376.patch 1.1 K
Updates:
Labels: -Patch
Comment #4 on issue 1073 by percival.music.ca: convert-ly and accented
characters
http://code.google.com/p/lilypond/issues/detail?id=1073
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-l
Updates:
Labels: -Patch Abandoned_patch
Comment #8 on issue 1193 by percival.music.ca: [PATCH] Enhancement:
internal ledger lines
http://code.google.com/p/lilypond/issues/detail?id=1193
There appears to be no action on this patch, so I'm moving it into
the "abandoned" category.
_
Updates:
Status: Fixed
Labels: fixed_2_13_47
Comment #3 on issue 1253 by percival.music.ca: programming error:
(de)crescendo on items with specified volume.
http://code.google.com/p/lilypond/issues/detail?id=1253
Thanks, pushed.
Attachments:
0001-Better-wording-for-sp
Updates:
Status: Fixed
Labels: fixed_2_13_45
Comment #2 on issue 1415 by percival.music.ca: [PATCH] Clef support for cue
notes (issue2726043)
http://code.google.com/p/lilypond/issues/detail?id=1415
This was pushed in 29640aafbf7ad7b2191813c4c16d282f15a127fd
Updates:
Status: Fixed
Labels: fixed_2_13_41
Comment #2 on issue 1414 by percival.music.ca: [PATCH]Allow music
identifiers in \addlyrics (no need for braces any more)(Issue2740044)
http://code.google.com/p/lilypond/issues/detail?id=1414
This was pushed in dfb68d00300d837d72360
Comment #17 on issue 1472 by mts...@gmail.com: Collision between MMR and
key signature
http://code.google.com/p/lilypond/issues/detail?id=1472
Sorry - you're right Keith, my bad.
Forgot to compile using make before my make check.
Compiles w/ a clean make check.
I do not know this part of the
Comment #16 on issue 1472 by percival.music.ca: Collision between MMR and
key signature
http://code.google.com/p/lilypond/issues/detail?id=1472
I just tried another regtest comparison and looked at it in more detail,
but I couldn't see anything like comment 14.
However, I gather from a re
"Graham Percival" wrote in message
news:20110122145258.GA17491@futoi...
On Sat, Jan 22, 2011 at 01:24:26PM +, James Lowe wrote:
There seems to be an inconsistency with setting horizontal beams.
\override Beam #'damping = #+inf.0
IIRC, this is a hack rather than an "officially supported" t
Status: Accepted
Owner:
Labels: Type-Other Priority-Medium Frog Maintainability
New issue 1489 by percival.music.ca: regtests should (normally) end on a
barline
http://code.google.com/p/lilypond/issues/detail?id=1489
It would be nice if all regtests ended with a complete bar. The horizo
"Graham Percival" wrote in message
news:AANLkTi=i2eeTj8nBcbg9JjsoiL-ApT5uZjQ12Pt8R=w...@mail.gmail.com...
Could somebody check if this is a regression? (look in some old
regtests, like 2.12.3)
I'm really not buying the vertical placement...
input/regression/figured-bass.ly
Cheers,
- Graham
Could somebody check if this is a regression? (look in some old
regtests, like 2.12.3)
I'm really not buying the vertical placement...
input/regression/figured-bass.ly
Cheers,
- Graham
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.g
On Sat, Jan 22, 2011 at 07:30:05AM -0700, Carl Sorensen wrote:
>
>
>
> On 1/22/11 3:36 AM, "Reinhold Kainhofer" wrote:
>
> > Am Freitag, 21. Januar 2011, um 19:13:54 schrieb lilyp...@googlecode.com:
> >> At any rate, I think that with the understanding that we need to 1) use
> >> alignAboveCon
On Sat, Jan 22, 2011 at 01:24:26PM +, James Lowe wrote:
> There seems to be an inconsistency with setting horizontal beams.
> \override Beam #'damping = #+inf.0
IIRC, this is a hack rather than an "officially supported" thing
(whatever that might mean).
> We have a snippet where we state that
On 1/22/11 3:36 AM, "Reinhold Kainhofer" wrote:
> Am Freitag, 21. Januar 2011, um 19:13:54 schrieb lilyp...@googlecode.com:
>> At any rate, I think that with the understanding that we need to 1) use
>> alignAboveContext for lyrics above a staff, and 2) make space for lyrics,
>> with top-system
Hello,
There seems to be an inconsistency with setting horizontal beams.
We have a snippet where we state that
\override Beam #'damping = #+inf.0
Should generate horizontal beams in all cases.
However the simple example attached shows some odd inconsistencies.
All the notes are identical per
Am Freitag, 21. Januar 2011, um 19:13:54 schrieb lilyp...@googlecode.com:
> At any rate, I think that with the understanding that we need to 1) use
> alignAboveContext for lyrics above a staff, and 2) make space for lyrics,
> with top-system-spacing, system-system-spacing, system-bottom-spacing, an
42 matches
Mail list logo
