Re: Vertical spacing regression !?
On Thu, 2010-06-24 at 14:05 +0200, Arno Waschk wrote:
On Sun, 20 Jun 2010 18:41:47 +0200, Joe Neeman joenee...@gmail.com wrote:
On Sun, 2010-06-20 at 16:19 +0200, Arno Waschk wrote:
dear list,
the following:
\version 2.13.23
\include deutsch.ly
TempoMark={ \time 4/4 \repeat unfold 20 {s1*5 \mark \default} }
celloPart = \new Staff \with {} { \relative c''{ \repeat unfold 19
{\repeat unfold 5{c8[c c c c c c c]}
\mark BLABLA
} c1 }}
rechtsPart = \new Staff \with {} {\relative c'{ \repeat unfold 399 {c4}
f4 }}
linksPart = \relative c, {s1*100}
#(set-global-staff-size 22.5)
\score {
\celloPart
\rechtsPart
\layout {
\context{\RemoveEmptyStaffContext
\override VerticalAxisGroup #'remove-first = ##t
} } }
gives here (latest lilypond from git as of 20th June 2010 3pm MESZ) the
problem of three warnings couldn't fit music on page,
and the last systems of page 2 and 3 being cut off by the lower end of
the
paper.
this disappear when one either comments out the \mark ... line, or
uses
lilypond 2.12.
this seems like a regression bug, no?
could not yet find something similar on the issue tracker.
I'm pretty sure this is an instance of bug 1062.
Cheers,
Joe
Hi, is there a workaround other than downgrading to 2.13.18?
You can always use page-breaking-between-system-spacing to fool the page
breaker into using more pages:
\paper {
page-breaking-between-system-spacing #'padding = #5
}
Or you can set max-systems-per-page, or add a manual page break. Or you
can wait until 2.13.26, since the bug is fixed in git.
I mean, couldn't Lilypond easily push the last line on the next page when
the couldn't fit music on page warning is issued, until the whole thing
is solved completely?
In specific situations, maybe, but lilypond can't do it in general
without breaking \pageBreak, min-systems-per-page, page-count and other
commands.
The annotate-spacing output (for me) seems to show that lilypond is aware
of correct spacing anyway...
Yes, but we don't know the _exact_ height of each system until after
page-breaking is done (otherwise, we would have to do all the layout for
every conceivable page-breaking solution and that would take far too
long).
Cheers,
Joe
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Vertical spacing regression !?
oops, with lilypond from git i am getting compiling times higher by a
factor 10, and huge distances between staves! Bug of feature?
yours, arno
On Fri, 25 Jun 2010 15:50:24 +0200, Joe Neeman joenee...@gmail.com wrote:
On Thu, 2010-06-24 at 14:05 +0200, Arno Waschk wrote:
On Sun, 20 Jun 2010 18:41:47 +0200, Joe Neeman joenee...@gmail.com
wrote:
On Sun, 2010-06-20 at 16:19 +0200, Arno Waschk wrote:
dear list,
the following:
\version 2.13.23
\include deutsch.ly
TempoMark={ \time 4/4 \repeat unfold 20 {s1*5 \mark \default} }
celloPart = \new Staff \with {} { \relative c''{ \repeat unfold 19
{\repeat unfold 5{c8[c c c c c c c]}
\mark BLABLA
} c1 }}
rechtsPart = \new Staff \with {} {\relative c'{ \repeat unfold 399
{c4}
f4 }}
linksPart = \relative c, {s1*100}
#(set-global-staff-size 22.5)
\score {
\celloPart
\rechtsPart
\layout {
\context{\RemoveEmptyStaffContext
\override VerticalAxisGroup #'remove-first = ##t
} } }
gives here (latest lilypond from git as of 20th June 2010 3pm MESZ)
the
problem of three warnings couldn't fit music on page,
and the last systems of page 2 and 3 being cut off by the lower end
of
the
paper.
this disappear when one either comments out the \mark ... line, or
uses
lilypond 2.12.
this seems like a regression bug, no?
could not yet find something similar on the issue tracker.
I'm pretty sure this is an instance of bug 1062.
Cheers,
Joe
Hi, is there a workaround other than downgrading to 2.13.18?
You can always use page-breaking-between-system-spacing to fool the page
breaker into using more pages:
\paper {
page-breaking-between-system-spacing #'padding = #5
}
Or you can set max-systems-per-page, or add a manual page break. Or you
can wait until 2.13.26, since the bug is fixed in git.
I mean, couldn't Lilypond easily push the last line on the next page
when
the couldn't fit music on page warning is issued, until the whole
thing
is solved completely?
In specific situations, maybe, but lilypond can't do it in general
without breaking \pageBreak, min-systems-per-page, page-count and other
commands.
The annotate-spacing output (for me) seems to show that lilypond is
aware
of correct spacing anyway...
Yes, but we don't know the _exact_ height of each system until after
page-breaking is done (otherwise, we would have to do all the layout for
every conceivable page-breaking solution and that would take far too
long).
Cheers,
Joe
--
Arno Waschk
a...@arnowaschk.de
+491723149605
+436508950949
-- Eggert Bordellballade Berlin Neukölln 15./16./24./25. April
-- Schlingensief Via Intioll.Bruxelles, Hamburg, München Mai/Juni
-- Schlingensief S.M.A.S.H. Mühlheim, Berlin August/Oktober
-- Feldman Patterns chrom. F Berlin
-- Maxwell Davies, Sciarrino Berlin Staatsoper Oktober
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: \cueDuring with 2 quoted voices
Added as http://code.google.com/p/lilypond/issues/detail?id=1151
--
Phil Holmes
Bug Squad
Xavier Scheuer x.sche...@gmail.com wrote in message
news:aanlktikbpakbm7qyaplqrrlnsw6h1eth-emwztf1d...@mail.gmail.com...
2010/6/11 -Eluze elu...@gmail.com:
in the snippet below, stems of quoted notes are connected:
\version 2.13.23
bass = \context Voice = bass \relative c''' { g4 g g g g4 g g g }
sop = \context Voice = sop \relative c' { b4 b b b b4 b b b }
first = \context Voice = 1 \relative c' {
c4 d c d
\cueDuring #sop #UP
\cueDuring #bass #DOWN
{ R1 }
}
\addQuote #sop \sop
\addQuote #bass \bass
{\first}
is it possible to have them pointing in the respective direction?
And I suppose you also want the whole-measure rest to be in the center
line of the staff... :p
Actually I think there should be a Grand CueDuring Improvement
Project, to enhance cued voices possibilities.
For example it is currently impossible to have the CueVoice DOWN
(i.e. the multi-measure rest up) but with the stems UP (actually
NEUTRAL) instead of DOWN (as a \voiceTwo).
http://lists.gnu.org/archive/html/lilypond-user/2009-09/msg00762.html
Or to include the features of namedCueDuring and cleffedCueDuring
directly into LilyPond... http://lsr.dsi.unimi.it/LSR/Item?id=388
Cheers,
Xavier
--
Xavier Scheuer x.sche...@gmail.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Vertical spacing regression !?
On Fri, 2010-06-25 at 17:17 +0200, Arno Waschk wrote: oops, with lilypond from git i am getting compiling times higher by a factor 10, and huge distances between staves! Bug of feature? It doesn't sound like a feature. Can you figure out when it was introduced? Cheers, Joe ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Dependencies in Lilypond
Hey all, Sorry for the silence w/ respect to this issue: I've been trying to make due w/o dependencies on my waveform patch and, finally, it looks like I'll need glpk to make it happen: I was able to dispense with gsl, but the linear programming algorithms I'm using are too involved to copy and paste a chunk of code into lilypond. To that end, I have three questions: 1) How would I create a separate branch? 2) Would it be worth it simply to include glpk in my patch? It requires no dependencies itself to compile and it is lightweight, so it could become part of lilypond, but I don't know if that's how things roll chez GNU. 3) Would it be possible as a middleground of sorts to create an optional dependency in lilypond? That is, look for glpk and compile the waveforms stuff only if it is found? I figured out a way to write that bit of code in the configure file if said maneuver is ok. ~Mike On 6/8/10 4:08 PM, Graham Percival gra...@percival-music.ca wrote: On Tue, Jun 08, 2010 at 03:46:47PM +0200, Jan Nieuwenhuizen wrote: Op dinsdag 08-06-2010 om 12:55 uur [tijdzone +0200], schreef Mike Solomon: [cc: lilypond-devel, for the archives] Hi Mike, 1) Can I add a new dependency, and if so, where would I indicate the necessity of said dependency? configure.in (write/copy and paste a test) Documentation/included/compile.itexi and in GUB, in gub/specs/lilypond.py (add as dependency) gub/specs/libgsl.py (write new recipe) However, be aware that we've frozen the dependencies (see issue 963), so your patch almost certainly won't be accepted for 2.14. That's no reason to halt work, of course; your patch could still be merged on to a separate branch it git. Alternatively, since this is AFAIK the first time we've tried to have a dependency freeze, I could unfreeze it for a week, let everybody update everything, and *then* call a freeze. I would still be **extremely** unhappy if lilybuntu broke, but if there was an overwhelming desire to add new dependencies, we could investigate creating a cutpaste series of apt-get commands to add/upgrade the required packages on lilybuntu. I don't think we should allow patches that break lilybuntu beyond cutpaste fixing until lilybuntu 2 is out, though. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Changing conducting signs
On Wed, Jun 16, 2010 at 5:47 AM, Carl Sorensen c_soren...@byu.edu wrote: On 6/16/10 1:58 AM, flup2 phili...@philmassart.net wrote: I would like to know if somebody knows how conductng signs ( http://lsr.dsi.unimi.it/LSR/Item?id=259 http://lsr.dsi.unimi.it/LSR/Item?id=259 ) are created by Lilypond. In a lot of books (Kurt Stone for instance) I noticed that beats divided by 3 are noted by a full triangle, no a two-parts triangle like Lilypond does. Is this a bug in LilyPond? Does anybody ever want the incomplete triangle? The thing that is printed is *called* a triangle. It would be trivial for me to make it be a closed triangle. Good catch, Carl. It's a regression, and I've logged it here: http://code.google.com/p/lilypond/issues/detail?id=1153 Thanks, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Add \path markup command, and use it for \eyeglasses. (issue1730044)
On 2010/06/22 03:50:24, Carl wrote: On 2010/06/21 22:39:53, Patrick McCarty wrote: On 2010/06/20 11:07:37, Carl wrote: Is it possible to have the path command estimate reasonable extents, rather than using (0 . 0) and (0 . 0)? Since we know the thickness of the line, and we have a list of points, it seems we should be able to keep track of the maximum and minimum X and Y coordinates during the path creation. This should be possible, but I'm not sure how to implement it, especially when relative coordinates are involved. My first thought would be to start with currentx=currenty= xmax=xmin=ymax=ymin = 0. For an absolute move, set currentx = move x, currenty = move y. For a relative move, set currentx += movex, currenty += movey. If currentx xmax, xmax=currentx. If currenty ymax, ymax=currenty. If currentx xmin, xmin = currentx. If currenty ymin, ymin = currenty. For curves, go one point at a time. The control points bound the curve, so you can use the control points as if they were curve points. When you're done with all the points, add half the thickness to xmax and ymax, and subtract half the thickness from xmin and ymin. I haven't tried it, but it seems to me it should work. Hi Carl, Thanks for your help. I've uploaded a new patch set that (more or less) follows your algorithm above, and also changes the interface again (according to Han-Wen's and Jan's comments). Let me know what you think. Thanks, Patrick http://codereview.appspot.com/1730044/show ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
