Re: Page breaking fails for multiline embedded score
Quoting Neil Puttock : If you do this, you'll have to change the \score command to a markup-list command, since a markup command can only return a single stencil Well, you just described all the problems this leads to; so why not relax the rule of markup command returning a single stencil? That means modifying interpret-markup-list (or who takes the leaf stencils? wordwrap-internal-markup-list maybe?) to not assume that what are now stencils to be combined, are in fact single stencils; test for stencil? and on the #t branch, add the stencil to the list like it does now, on the #f branch the return value is a list of stencils, add them all. Do you think this approach is reasonable? ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1009 in lilypond: \transpose causes crash (std::logic_error)
Updates: Labels: -Priority-Critical Priority-High Comment #5 on issue 1009 by percival.music.ca: \transpose causes crash (std::logic_error) http://code.google.com/p/lilypond/issues/detail?id=1009 I can't speak to Neil's suggestion. As for this issue's priority, I think we've identified a gap in the classification. I hereby declare that issues which: 1. produce no output, and 2. fail to give a reasonable user a clue about what's wrong shall be priority-high. I think the "defect" type is valid. Yes, the fix is as simple as printing out a more informative message. That's no reason to lower the priority. I've updated the CG accordingly. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Page breaking fails for multiline embedded score
On 10 February 2010 13:24, Boris Shingarov wrote: > The fix, I believe, is to not perform the > (stack-stencils Y DOWN baseline-skip ...) application; instead, leave just > the (map paper-system-stencil ...) so each system becomes its own member of > the markup list; then let the word wrapper place them vertically. Because > the score line-breaking was already done by the Constrained breaker, I hope > the (less intelligent) word wrapper will not screw the line layout (I don't > see how, they are all page-wide lines). If you do this, you'll have to change the \score command to a markup-list command, since a markup command can only return a single stencil. This is problematic, since moving the parser rule will cause \markup \score to break; OTOH, if we leave the rule in simple_markup, \markuplines \score won't work, even though the documentation will list \score as a markup-list command. I don't think it's enough just to map the stencils: they still need some degree of baseline-skip, otherwise they'll be stacked as close as possible. I think `space-lines' would be the most appropriate way to keep them positioned nicely (using the existing default for baseline-skip). Cheers, Neil ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1009 in lilypond: \transpose causes crash (std::logic_error)
Comment #4 on issue 1009 by n.puttock: \transpose causes crash (std::logic_error) http://code.google.com/p/lilypond/issues/detail?id=1009 I don't get an exception under Ubuntu 9.10 x64, but the warning message is a bit weird: warning: transposition by b��' makes alteration larger than double The garbled pitch string changes each time the snippet's compiled, which is hardly surprising when you look in pitch.cc and see that trying to convert Rational (-3/2) into a valid alteration results in a memory access outside the array holding the alteration strings (the index is -2). We have a private method Pitch::normalize (), which ensures valid octaves and alterations; why don't we use it in this case (even if it has to be made public)? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1009 in lilypond: \transpose causes crash (std::logic_error)
Comment #3 on issue 1009 by d...@gnu.org: \transpose causes crash
(std::logic_error)
http://code.google.com/p/lilypond/issues/detail?id=1009
I have a hard time picturing what transposing { a b c d } from disis to
c should result in. A scale in disis contains
disis eisis fisisis gisis aisis bisis cisisis disis
c in this scale would transpose to beseses in a c scale. There is no
such thing as beseses. Incidentally, there is no such thing as cisisis
either, but Lilypond should only balk when it has to produce something
impossible, not just think about it.
Since transposition does not just deal with absolute pitches but with
enharmonicity as well, there is no way to properly transpose this in the
demanded manner. Aborting is the sanest choice.
Now let's look at the other scales/transforms
aisis: { a b c d } -> { ceses beses eseses deses }
bisis: { a b c d } -> { beseses ceses deseses eseses }
cisis: { a b c d } -> { aeses beses ceses deses }
disis: { a b c d } -> { geses aeses beseses ceses }
eisis: { a b c d } -> { feses geses aeseses beseses }
fisis: { a b c d } -> { eses fes geses aeses }
gisis: { a b c d } -> { deses eses feses geses }
You'll see that Lilypond only balks at those transforms which contain
impossible notes.
There are no notes Lilypond could produce. Aborting is the right
choice. The best thing you can hope to do is to produce a nicer error
message.
The notation manual contains under "Transpose" a snippet that transposes
using "minimal accidentals". It is conceivable that employing this
snippet will avert the abort.
Anyway, there is no valid output possible for the given input. Aborting is
the only
sensible thing to do. The only thing that could possibly be improved is
the error
message when aborting.
So this is not priority "Critical", but "Low", and it is not a "Defect" but
an
enhancement request.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1009 in lilypond: \transpose causes crash (std::logic_error)
lilyp...@googlecode.com writes:
> Comment #2 on issue 1009 by Carl.D.Sorensen: \transpose causes crash
> (std::logic_error)
> http://code.google.com/p/lilypond/issues/detail?id=1009
>
> disis (without the comma) causes terminate to be called the same as
> disis, (with the comma)
>
> aisis, bisis, disis, and eisis all cause terminate to be called.
>
> cisis, fisis, and gisis do not cause terminate to be called.
I have a hard time picturing what transposing { a b c d } from disis to
c should result in. A scale in disis contains
disis eisis fisisis gisis aisis bisis cisisis disis
c in this scale would transpose to beseses in a c scale. There is no
such thing as beseses. Incidentally, there is no such thing as cisisis
either, but Lilypond should only balk when it has to produce something
impossible, not just think about it.
Since transposition does not just deal with absolute pitches but with
enharmonicity as well, there is no way to properly transpose this in the
demanded manner. Aborting is the sanest choice.
Now let's look at the other scales/transforms
aisis: { a b c d } -> { ceses beses eseses deses }
bisis: { a b c d } -> { beseses ceses deseses eseses }
cisis: { a b c d } -> { aeses beses ceses deses }
disis: { a b c d } -> { geses aeses beseses ceses }
eisis: { a b c d } -> { feses geses aeseses beseses }
fisis: { a b c d } -> { eses fes geses aeses }
gisis: { a b c d } -> { deses eses feses geses }
You'll see that Lilypond only balks at those transforms which contain
impossible notes.
There are no notes Lilypond could produce. Aborting is the right
choice. The best thing you can hope to do is to produce a nicer error
message.
The notation manual contains under "Transpose" a snippet that transposes
using "minimal accidentals". It is conceivable that employing this
snippet will avert the abort.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1009 in lilypond: \transpose causes crash (std::logic_error)
Comment #2 on issue 1009 by Carl.D.Sorensen: \transpose causes crash (std::logic_error) http://code.google.com/p/lilypond/issues/detail?id=1009 disis (without the comma) causes terminate to be called the same as disis, (with the comma) aisis, bisis, disis, and eisis all cause terminate to be called. cisis, fisis, and gisis do not cause terminate to be called. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Page breaking fails for multiline embedded score
Neil's recent modification to (define-builtin-markup-command (score ...) ...), in scm/define-markup-commands.scm, fixes the bug where only the first system was printed, and now we can have multi-line embedded scores, by vertically stacking the stencils instead of just selecting the first one. While this is a definite improvement over the old buggy behavior, the fact that the whole embedded score appears as one monolithic stencil to the markup-list word wrapper, leads to a problem with page breaking: namely, the embedded score can not be broken across pages. Use case 1: There is half a page of markup, followed by a page worth of embedded score. Lilypond will produce a half-empty first page containing markup, and the score will follow on the next page. What the user expects to see, is the embedded score to be broken across pages. Use case 2: Even worse, a very long embedded score can not be broken across pages at all; it is not possible at all to print an embedded score that does not fit on one page. The fix, I believe, is to not perform the (stack-stencils Y DOWN baseline-skip ...) application; instead, leave just the (map paper-system-stencil ...) so each system becomes its own member of the markup list; then let the word wrapper place them vertically. Because the score line-breaking was already done by the Constrained breaker, I hope the (less intelligent) word wrapper will not screw the line layout (I don't see how, they are all page-wide lines). ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1009 in lilypond: \transpose causes crash (std::logic_error)
Updates: Labels: -Priority-Medium Priority-Critical Comment #1 on issue 1009 by percival.music.ca: \transpose causes crash (std::logic_error) http://code.google.com/p/lilypond/issues/detail?id=1009 To be honest, I'm not totally certain if this should be Critical, since it's not a crash. But throwing an exception isn't the best of things, so I'll mark it as such for now. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1008 in lilypond: Some warning/error messages are not prefixed with 'warning:'/'error:'
Updates: Labels: Warning Comment #1 on issue 1008 by percival.music.ca: Some warning/error messages are not prefixed with 'warning:'/'error:' http://code.google.com/p/lilypond/issues/detail?id=1008 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [2.13] Problem with two consecutive interruped lyrics
У ср, 2010-02-10 у 12:14 +0100, David Kastrup пише: > > For example, system has upper singes paused in the first half and > > lower singers paused in the second half of system. Then this > > "squeezing" is just great. > > In your given example, it looks like an utterly wrong thing to do to > make two different lyrics contexts superimposed on one another, at the > very least as long as we are staying on one line. Yes, that example is too dumb. I've attached extract from real score, which demonstrates an issue. 2.12 (and 2.10 as far?.. not sure though) places stave closer making lyrics on one baseline, which is excellent. I know, i can re-assign lyrics to "different contexts", but actually there are scores which just _want a lot_ lilypond to place lyrics on one baseline. Now i'm trying (well... not right now, most probably) to make "minimal example". Thanks. Sorry, would you mind such attachments (along with cross-posting)? Probably, it's incorrect in some sense, sorry, excuse me. (fragment by M. Dyletsky, followed by fragment by S. Pekalytsky, mid.18th century; excuse my english, please, too) -- Dmytro O. Redchuk <>___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \transpose causes crash (std::logic_error)
У ср, 2010-02-10 у 12:08 +0100, Mats Bengtsson пише:
> I notice that you classified it as priority-medium. I haven't followed
> the recent discussions on bug classifications, but at least previously
> all crashes were always classified as very serious.
Thank You for Your comment.
Yes, i was in doubt --- it's "defect", clearly, but it's not a
segfault... "If unsure set to medium" won.
Please, how would _You_ classify that? High or Critical?
Thanks!
>
>/Mats
>
> On Wed, 2010-02-10 at 10:12 +0200, Dmytro O. Redchuk wrote:
> > У вт, 2010-02-09 у 22:43 +, Kirill пише:
> > > The following snippet reproduces the bug.
> >
> > Thank You, added as 1009:
> > http://code.google.com/p/lilypond/issues/detail?id=1009
> >
> > > \version "2.12.3"
> > > \new Score
> > > {
> > > \transpose disis, c {a b c d}
> > > }
> > >
> > > (Interestingly enough, \transpose ceses, c {...} does not cause the
> > > crash.)
> > >
> > > Best,
> > >
> > > Kirill Sidorov
> >
>
--
Dmytro O. Redchuk
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \transpose causes crash (std::logic_error)
I notice that you classified it as priority-medium. I haven't followed
the recent discussions on bug classifications, but at least previously
all crashes were always classified as very serious.
/Mats
On Wed, 2010-02-10 at 10:12 +0200, Dmytro O. Redchuk wrote:
> У вт, 2010-02-09 у 22:43 +, Kirill пише:
> > The following snippet reproduces the bug.
>
> Thank You, added as 1009:
> http://code.google.com/p/lilypond/issues/detail?id=1009
>
> > \version "2.12.3"
> > \new Score
> > {
> > \transpose disis, c {a b c d}
> > }
> >
> > (Interestingly enough, \transpose ceses, c {...} does not cause the crash.)
> >
> > Best,
> >
> > Kirill Sidorov
>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [2.13] Problem with two consecutive interruped lyrics
У ср, 2010-02-10 у 11:54 +0200, Dmytro O. Redchuk пише: > And now: *SORRY* --- i have to look closer on this "issue". Now in some > cases 2.13 behaves exactly as 2.12, so i will try to do more tests and > look closer to real scores where this is the problem. Well... it seems to heavily depend on what's exactly in that "voice" which has no lyrics temporarily (rests? notes? spaces?..). Reinhold, good news, this maybe not a problem for you, if you, let's say do not type different voices on the same staff. I will do some checks. This *is* the problem for me. Now i'm almost lost, because testing with different "little examples" shows different results with the same version, or the same result with different versions. :O( > *Sorry*, and thank You! -- Dmytro O. Redchuk ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [2.13] Problem with two consecutive interruped lyrics
Am Mittwoch, 10. Februar 2010 10:23:47 schrieb Trevor Daniels: > Dmytro O. Redchuk wrote Wednesday, February 10, 2010 8:31 AM > > > Well, i'd like to ask again: so, it looks like it will never be > > possible > > so far? With the new "spacing engine"? > > > > (i've attached two images, again, by 2.12.3 and 2.13.12, with > > skylines) > > Are the attached images the right way round? The one > called 2.13.12 looks right to me and 2.12.3 looks wrong. > Or have I misunderstood the problem? Yes, you have misunderstood the problem: Typically, one staff has only the first two notes, the second staff has only the last two notes. In this case, you don't want to waste the space for two lyrics lines, but compress them into one. 2.12 did that automatically, 2.13 doesn't seem to allow it (I haven't checked it myself, though)... Hmm, I haven't checked that, but if that's the case, then I also have a problem with some of my old choir music that I typeset a while ago :( So, a solution would be really good. Cheers, REinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [2.13] Problem with two consecutive interruped lyrics
У ср, 2010-02-10 у 09:23 +, Trevor Daniels пише: > Dmytro O. Redchuk wrote Wednesday, February 10, 2010 8:31 AM > > > > Well, i'd like to ask again: so, it looks like it will never be > > possible > > so far? With the new "spacing engine"? > > > > (i've attached two images, again, by 2.12.3 and 2.13.12, with > > skylines) > > Are the attached images the right way round? The one > called 2.13.12 looks right to me and 2.12.3 looks wrong. > Or have I misunderstood the problem? No, "both are right", but "2.12.3 is much better" for me. My problem is that lilypond 2.13.* does not squeeze stave and lyrics lines "as close as possible" and system takes more (unneeded) space. For example, system has upper singes paused in the first half and lower singers paused in the second half of system. Then this "squeezing" is just great. 2.12 (and 2.10 if i can remember) could do this better, i mean to align different lyrics contexts "on one baseline". And now: *SORRY* --- i have to look closer on this "issue". Now in some cases 2.13 behaves exactly as 2.12, so i will try to do more tests and look closer to real scores where this is the problem. *Sorry*, and thank You! > > Trevor -- Dmytro O. Redchuk ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [2.13] Problem with two consecutive interruped lyrics
Dmytro O. Redchuk wrote Wednesday, February 10, 2010 8:31 AM Well, i'd like to ask again: so, it looks like it will never be possible so far? With the new "spacing engine"? (i've attached two images, again, by 2.12.3 and 2.13.12, with skylines) Are the attached images the right way round? The one called 2.13.12 looks right to me and 2.12.3 looks wrong. Or have I misunderstood the problem? Trevor ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [2.13] Problem with two consecutive interruped lyrics
У пт, 2010-02-05 у 21:17 +0200, Dmytro O. Redchuk пише:
> Hi.
Hi again!-)
(Sorry, Cc'ing to bug-lilypond)
Well, i'd like to ask again: so, it looks like it will never be possible
so far? With the new "spacing engine"?
(i've attached two images, again, by 2.12.3 and 2.13.12, with skylines)
If so, if "it will never be possible", then i can not file this as a
bug :O)
But... "too bad"?.. :O(
I've experienced this "issue" in real scores, and it makes these scores
much worse. Is there any... hope?-) Or, at least, workaround?
Thank you!
> I have a score with two stave and two lyrics lines both of which have
> "long pauses" --- let's say, a half of staff singing and next half ---
> silence.
>
> And i want to place both lyrics lines between these two stave. The
> problem is that 2.12 could place both lyric lines at the same baseline
> (twolyrics-2.12.3.png, attached), however i can not force 2.13 to do the
> same (twolyrics-2.13.12.png).
>
> Snippet (one measure):
>
> % ---8<-
>
> melody = \relative c'' {
> c c c c
> }
>
> upperLyr = \lyricmode {
> la la _ _
> }
>
> lowerLyr = \lyricmode {
> _ _ la la
> }
>
> \score {
> \new ChoirStaff <<
> \new Staff = "upper" {
> \new Voice = "upper" {
> \melody
> }
> }
> \new Lyrics \lyricsto "upper" \upperLyr
> \new Staff = "lower" {
> \new Voice = "lower" {
> \melody
> }
> }
> \new Lyrics \with {
> alignAboveContext = "lower"
> } \lyricsto "lower" \lowerLyr
> >>
> }
>
> % ---8<-
>
> So, two images illustrate my "problem", please help.
>
> I've tried with affinity and spacing parameters but failed. I could make
> a gap a bit smaller, not more.
>
> Thanks!
>
--
Dmytro O. Redchuk
<><>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1009 in lilypond: \transpose causes crash (std::logic_error)
Status: Accepted
Owner:
Labels: Priority-Medium Type-Defect
New issue 1009 by brownian.box: \transpose causes crash (std::logic_error)
http://code.google.com/p/lilypond/issues/detail?id=1009
Reported by Kirill
(http://lists.gnu.org/archive/html/bug-lilypond/2010-02/msg00134.html):
\version "2.13.12"
{
\transpose disis, c { a b c d }
}
(Interestingly enough, \transpose ceses, c {...} does not cause the crash.)
The same with 2.12.3.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \transpose causes crash (std::logic_error)
У вт, 2010-02-09 у 22:43 +, Kirill пише:
> The following snippet reproduces the bug.
Thank You, added as 1009:
http://code.google.com/p/lilypond/issues/detail?id=1009
> \version "2.12.3"
> \new Score
> {
> \transpose disis, c {a b c d}
> }
>
> (Interestingly enough, \transpose ceses, c {...} does not cause the crash.)
>
> Best,
>
> Kirill Sidorov
--
Dmytro O. Redchuk
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \transpose causes crash (std::logic_error)
У вт, 2010-02-09 у 22:43 +, Kirill пише:
> The following snippet reproduces the bug.
Please, which OS do You use?
> \version "2.12.3"
> \new Score
> {
> \transpose disis, c {a b c d}
> }
>
> (Interestingly enough, \transpose ceses, c {...} does not cause the crash.)
>
> Best,
>
> Kirill Sidorov
--
Dmytro O. Redchuk
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
