Programming error

[Knute Snortum]

I am getting a programming error with the following code:

%%%
\version "2.24.3" % 2.25.14 too

rightHand = \relative {
  c''4( c c c | \break
  g4 g \tuplet 3/2 4 { c,8) \change Staff = "lower" g[ g] } g4 |
}

\new PianoStaff <<
  \new Staff = "upper" \rightHand
  \new Staff = "lower" { \clef bass s1 * 2 }
>>
%%%

The output is:

/home/foo/bar/calc-in-progress-error.ly:4:7 <0>: programming error: cyclic
dependency: calculation-in-progress encountered for Slur.stencil

c''4

( c c c | \break

/home/foo/bar/calc-in-progress-error.ly:4:7 <1>: continuing, cross fingers

The situation seems to take several situations all together: A broken slur,
a tuplet, a change of staff, and explicit beaming. Take any of those away
and the error disappears.

--
Knute Snortum

Re: Chord names collide with span bar

[Knute Snortum]

On Thu, Mar 21, 2024 at 2:30 PM Werner LEMBERG  wrote:

>
> I think I've found the real fix for the problem.  Suddenly remembering
> that we already have the `Span_bar_stub_engraver` to handle exactly
> such situations I wondered why it works for lyrics but not for chord
> names.  Comparing the definitions of the two contexts in
> `engraver-init.ly` I found out that the `Pure_from_neighbor_engraver`
> was missing, and adding it seems to do the trick.
>
>
> ```
> \version "2.25.13"
>
> \layout {
>   \context {
> \ChordNames
> \consists Pure_from_neighbor_engraver
>   }
> }
>
> \score {
>   \new GrandStaff <<
> \new Staff \relative { c''4 c c c | c c c c }
> \new ChordNames \chordmode { c2. q8. des16:maj9 | q1 }
> \new Staff { \improvisationOn b'4 4 4 8. 16~ | 4 4 4 4 }
>   >>
> }
> ```
>
>
> Since I don't have experience with chord names I ask users who need
> this feature to check whether it works as expected in general.
>

It works like a charm in my source!  Thanks for researching this.


--
Knute Snortum

Re: Chord names collide with span bar

[Knute Snortum]

On Wed, Mar 20, 2024 at 8:54 AM Aaron Hill  wrote:

> Oh, I think I found another option:
>
> 
> \version "2.25.13"
>
> #(ly:set-option 'debug-skylines #t)
> \layout {
>\context { \Score
>  \override NonMusicalPaperColumn.show-horizontal-skylines = ##t
>}
>\context { \ChordNames
>  \consists "Bar_engraver"
>  \override BarLine.bar-extent = #'(0 . 1)
>  \override BarLine.transparent = ##t
>    }
> }
>
>
Yes, that fixes everything!  Thank you so much.

-- 
Knute Snortum

Re: Chord names collide with span bar

[Knute Snortum]

On Wed, Mar 20, 2024 at 8:01 AM Aaron Hill  wrote:

> ly:separation-item::print no longer exists, as all grobs support the
> properties show-horizontal-skylines and show-vertical-skylines.
>
> So, swap out that \override with:
>
> 
>\override NonMusicalPaperColumn.show-horizontal-skylines = ##t
> 
>
>
Ah, I see this is just for debugging.  Thank you.  Your solution helps when
put into my bigger project.  Some -- but not all -- of the bars are now
wide enough.

Re: Chord names collide with span bar

[Knute Snortum]

On Wed, Mar 20, 2024 at 8:07 AM Jean Abou Samra  wrote:

> Le mercredi 20 mars 2024 à 15:56 +0100, Jean Abou Samra a écrit :
> > Le mercredi 20 mars 2024 à 07:51 -0700, Knute Snortum a écrit :
> > > Your solution requires version 2.22 and I'm using 2.24
> > > (with the \alternative command so it's not easy to change)
> >
> > The old \alternative syntax is still supported in 2.24.
>
>
> Ah, sorry. Somehow, I “autocorrected” your reply as
> “Your solution requires version 2.24 and I'm on 2.22”.
> Forget about it.
>

Not a problem!

-- 
Knute Snortum

Re: Chord names collide with span bar

[Knute Snortum]

On Tue, Mar 19, 2024 at 4:34 PM Aaron Hill  wrote:

> ...
>


> Curious.  The skylines look interesting, almost like the SpanBar is not
> being factored in, only the parts of the BarLine.
>
> Below, I attempted to add some virtual height to the ChordName, and it
> seemed to allow the ChordName to push the BarLine (and SpanBar) to the
> right:
>
> 
> \version "2.22.0"
>
> #(ly:set-option 'debug-skylines #t)
> \layout {
>\context { \Score
>  \override NonMusicalPaperColumn.stencil =
>#ly:separation-item::print
>}
>\context { \ChordNames
>  \override ChordName.extra-spacing-height =
>#'(0 . 2)
>}
> }
>
> \score {
>\new GrandStaff <<
>  \new Staff \relative { c''4 c c c | c c c c }
>  \new ChordNames \chordmode { c2. q8. des16:maj9 | q1 }
>  \new Staff { \improvisationOn b'4 4 4 8. 16~ | 4 4 4 4 }
>>>
> }
> 
>
> Still sounds like a defect of some sort, as the default behavior should
> probably be handling things.  But perhaps this trick above might be
> useful in whatever score you are working on as a stopgap.


Aaron,

Thank you so much for this fix and for entering an issue!  There is just
one thing that is a problem for me.  Your solution requires version 2.22
and I'm using 2.24 (with the \alternative command so it's not easy to
change).  When I your solution convert to 2.24 (no changes) I get an error
executing the file:

/home/foo/bar/chords-bar-line.ly:7:9 <0>: error: Guile signaled an error
for the expression beginning here

#

ly:separation-item::print

Unbound variable: ly:separation-item::print


--

Knute Snortum

Chord names collide with span bar

[Knute Snortum]

I ran into something today -- it's not quite a bug; more of an "ugly."  In
some situations, chord names collide with the span bar of a Grand or Piano
Staff.  Here is an example:

\version "2.25.13"

\score {
  \new GrandStaff <<
\new Staff \relative { c''4 c c c | c c c c }
\new ChordNames \chordmode { c2. q8. des16:maj9 | q1 }
\new Staff { \improvisationOn b'4 4 4 8. 16~ | 4 4 4 4 }
  >>
}

--
Knute Snortum

Line break after parenthesized crescendo with a spanner style of none creates programming errors

[Knute Snortum]

This is a weird one and hopefully I've properly distilled the MWE.  Here's
what I think is happening:

If you have a parenthesized crescendo with a spanner style of none, when
the line breaks, it creates two small parentheses under the new line and
throws two programming errors.  Here's the MWE:

\version "2.25.13"

music = \relative {
  c''4 c c c | \break
  c4 c c c |
}

dynamics = {
  \override DynamicTextSpanner.style = #'none
  s2. s4\parenthesize\cresc |
  s4 s2.\! |
}

<<
  \new Staff \music
  \new Dynamics \dynamics
>>

The output looks like this:

Processing `/home/knute/Documents/LilyPond/ChopinFF/Op34/test-for-errors.ly'

Parsing...

Interpreting music...

Preprocessing graphical objects...

Finding the ideal number of pages...

Fitting music on 1 page...

Drawing systems...

programming error: Improbable offset for stencil: inf staff space

Setting to zero.

continuing, cross fingers

programming error: Improbable offset for stencil: -inf staff space

Setting to zero.

continuing, cross fingers

Converting to `test-for-errors.pdf'...

Success: compilation successfully complete


--
Knute Snortum

Re: \alternative fails if \repeat unfold proceeds it

[Knute Snortum]

On Sat, Feb 24, 2024 at 11:26 AM Jean Abou Samra  wrote:

> Le samedi 24 février 2024 à 11:05 -0800, Knute Snortum a écrit :
> > I've run into something that I think is a bug -- or I'm not understanding
> > something.  It happens when you are in a \repeat volta section and use a
> > \repeat unfold just before the \alternative section.
> >
> > \version "2.25.13"
> >
> > \relative {
> >   c''4 c c c |
> >   \repeat volta 2 {
> > \repeat unfold 2 { d4 d d d }
> > % d4 d d d % uncomment me and everything's fine
>
>
> That's legacy \alternative syntax kicking in for backwards compatibility.
> The \alternative gets attached to \repeat unfold. Try inserting {} here.
>

That works, thanks!  Do you think this deserves a "Known issues and
warnings" section in
https://lilypond.org/doc/v2.24/Documentation/notation/long-repeats#alternative-endings
?


--
Knute Snortum

\alternative fails if \repeat unfold proceeds it

[Knute Snortum]

I've run into something that I think is a bug -- or I'm not understanding
something.  It happens when you are in a \repeat volta section and use a
\repeat unfold just before the \alternative section.

\version "2.25.13"

\relative {
  c''4 c c c |
  \repeat volta 2 {
\repeat unfold 2 { d4 d d d }
% d4 d d d % uncomment me and everything's fine
\alternative {
  \volta 1 { e4 e e e }
  \volta 2 { f4 f f f }
}
  }
  g4 g g g
}

The work around is to have one line of non-repeated notes just before the
\alternative section.

--
Knute Snortum

Re: musicxml2ly chord names

[Knute Snortum]

On Mon, Jan 29, 2024 at 12:55 AM Silvain Dupertuis <
silvain-dupert...@bluewin.ch> wrote:

> I could write an issue... but the webpage did recomment to write a message
> first
>

This is now issue https://gitlab.com/lilypond/lilypond/-/issues/6694


--
Knute Snortum

Re: musicxml2ly chord names

[Knute Snortum]

On Sun, Jan 28, 2024 at 8:50 AM Silvain Dupertuis <
silvain-dupert...@bluewin.ch> wrote:

> These first 2 lines of the dictionary for chords in musicxml2ly
> contains a faulty 5 for simple major and minor chords
> (I discovered it with a conversion from a MuseScore sheet converted into
> xml)
>
> chordkind_dict = {
>  'major': ':5',
>  'minor': ':m5',
>
> should be
>
> chordkind_dict = {
>  'major': '',
>  'minor': ':m',
>
> a:5 results in a two notes chord 
>

Could you supply a short musicxml file that demonstrates this?  I would do
it, but I don't know musicxml.

That, or you could enter an issue at
https://gitlab.com/lilypond/lilypond/-/issues

Re: Incorrect transposition via musicxml2ly

[Knute Snortum]

On Sun, Jan 28, 2024 at 10:30 AM Alexander Slávik <
slavik.alexan...@seznam.cz> wrote:

> > I can write this up as an issue unless you want to...
>
> Please do so; thanks!
>

It is now https://gitlab.com/lilypond/lilypond/-/issues/6693.  I hope I
explained it sufficiently.


--
Knute Snortum

Re: Incorrect transposition via musicxml2ly

[Knute Snortum]

On Sun, Jan 28, 2024 at 12:01 AM Alexander Slávik <
slavik.alexan...@seznam.cz> wrote:

> Seems like this didn't get much attention…
>

It looks like a bug to me.  I can write this up as an issue unless you want
to...


--
Knute Snortum

Re: PDF hyperlinks pointing to internal LilyPond code

[Knute Snortum]

On Fri, Jan 26, 2024 at 11:53 AM Werner LEMBERG  wrote:

>
> >> > The hyperlinks of both the acciaccatura and the appoggiatura
> >> > slurs point to ly/grace-init.ly, which is kind of logical, but
> >> > also confusing from a user perspective.
> >>
> >> I think this a bug, so please open an issue.
> >
> > I apologise.
>
> Why?
>

I told Michael to post to the user list but he actually was reporting a
bug.

Re: PDF hyperlinks pointing to internal LilyPond code

[Knute Snortum]

I apologise.

--
Knute Snortum



On Fri, Jan 26, 2024 at 11:33 AM Werner LEMBERG  wrote:

>
> > I would like to hear your opinions on this one:
> >
> >  snip
> > \version "2.25.10"
> >
> > { \acciaccatura { c'8 } d'4 }
> > { \appoggiatura { c'8 } d'4 }
> > 
> >
> > The hyperlinks of both the acciaccatura and the appoggiatura slurs
> > point to ly/grace-init.ly, which is kind of logical, but also
> > confusing from a user perspective.
>
> I think this a bug, so please open an issue.
>
>
> Werner
>
>

Re: PDF hyperlinks pointing to internal LilyPond code

[Knute Snortum]

Hi Michael,

These sorts of questions should go to another list,

lilypond-u...@gnu.org

This list is only for reporting bugs.

--
Knute Snortum



On Fri, Jan 26, 2024 at 5:48 AM Michael Käppler via bug-lilypond <
bug-lilypond@gnu.org> wrote:

> Hi all,
> I would like to hear your opinions on this one:
>
>  snip
> \version "2.25.10"
>
> { \acciaccatura { c'8 } d'4 }
> { \appoggiatura { c'8 } d'4 }
> 
>
> The hyperlinks of both the acciaccatura and the appoggiatura slurs point
> to ly/grace-init.ly, which is kind of logical, but also confusing from a
> user perspective.
>
> Shouldn't they both point to the user code?
>
> Michael
>
>

Re: Ugly ties in chord clusters

[Knute Snortum]

On Mon, Dec 25, 2023 at 10:31 AM fa61bd7a-bab1-4a88-80e0-a065116a0a04---
via bug-lilypond  wrote:

>Hi LilyPond developers,
>
>In dense chord clusters, ties sometimes fail to keep at least one staff
>space away from each other.
> \version "2.24.2"
> \relative {
>   \override Score.SpacingSpanner.shortest-duration-space = #3
>   ~ q
> }
>

Do you mean without the override?  With the override, the ties look fine.

--
Knute Snortum

Re: Minimum tie length not honored after a break

[Knute Snortum]

On Fri, Dec 8, 2023 at 10:58 PM Jean Abou Samra  wrote:

> It's just a separate property. Try setting minimum-length-after-break.
>

Thanks, that works.

Minimum tie length not honored after a break

[Knute Snortum]

Consider the following snippet:

%%%

\version "2.25.10"

\paper {
  ragged-right = ##t
}

\layout {
  \context {
\Voice
\override Tie.minimum-length = 5
  }
}

\relative {
  1~ | \break
  q4 r4 r2 |
}
%%%

The minimum tie length is not honored after the break in the ais note of
the chord.

This may be related to issue:

https://gitlab.com/lilypond/lilypond/-/issues/4279

--
Knute Snortum

offset and TupletNumbers

[Knute Snortum]

Is this bug #6618?

%%%
\version "2.25.10"

{
  \omit TupletBracket
  \tuplet 3/2 { c''4 c''8 }
  \offset Y-offset 1 TupletNumber
  \tuplet 3/2 { c''4 c''8 }
}

% programming error: TupletBracket.positions requested before line breaking
% continuing, cross fingers
% programming error: TupletBracket.Y-offset accessed before line breaking
% continuing, cross fingers

%%%

In version 2.24.3, the behavior is a little different.  The Y-offset is
correct but the X-offset gets set to 0 or some other incorrect value (see
attached) and no programming error output.  Is this a separate issue?

--
Knute Snortum

Re: Cyclic dependencies with \afterGrace and cross-staff notes

[Knute Snortum]

On Mon, Aug 14, 2023 at 10:58 AM Knute Snortum  wrote:

> On Mon, Aug 14, 2023 at 7:26 AM Knute Snortum  wrote:
>
>> Hi all.  I've encountered a problem when using \afterGrace and
>> cross-staff notes.  It may  be related to these issues:
>>
>
> I was wrong.  It's not the \afterGrace, it's the \trillSpan.  Here's my
> updated MWE:
>

This could also be related to:

https://gitlab.com/lilypond/lilypond/-/issues/6598

Re: Cyclic dependencies with \afterGrace and cross-staff notes

[Knute Snortum]

On Mon, Aug 14, 2023 at 7:26 AM Knute Snortum  wrote:

> Hi all.  I've encountered a problem when using \afterGrace and cross-staff
> notes.  It may  be related to these issues:
>

I was wrong.  It's not the \afterGrace, it's the \trillSpan.  Here's my
updated MWE:

\version "2.24.2"

rightHand = \relative {
  c''1 \startTrillSpan |
  c8 \stopTrillSpan g e c \change Staff = "lower" g e c g |
}

leftHand = \relative {
  \clef bass
  s1 |
  s1 |
}

\score {
  \new PianoStaff <<
\new Staff = "upper" \rightHand
    \new Staff = "lower" \leftHand
  >>
}

--
Knute Snortum

Cyclic dependencies with \afterGrace and cross-staff notes

[Knute Snortum]

Hi all.  I've encountered a problem when using \afterGrace and cross-staff
notes.  It may  be related to these issues:

https://gitlab.com/lilypond/lilypond/-/issues/6171
https://gitlab.com/lilypond/lilypond/-/issues/6197

Here is the MWE:

%%%
\version "2.25.7"

rightHand = \relative {
  c''1~ \startTrillSpan |
  \afterGrace 15/16 c1 { b16[ \stopTrillSpan c] } |
  c8 g e c \change Staff = "lower" g e c g |
}

leftHand = \relative {
  \clef bass
  c4 c c c |
  c4 c c c |
  s1 |
}

\score {
  \new PianoStaff <<
\new Staff = "upper" \rightHand
\new Staff = "lower" \leftHand
  >>
}
%%%

This produces several programming errors:

programming error: cyclic dependency: calculation-in-progress encountered
for VerticalAxisGroup.adjacent-pure-heights

continuing, cross fingers

--
Knute Snortum

Stems wrong direction when change staff is first

[Knute Snortum]

I have found what I believe is a new bug.  If you have a PianoStaff and the
right hand's notes are first in the bottom staff, the stems go down and
merge with the left hand.  Here is my MWE which will maybe clear things
up.  I've attached the output.

\version "2.25.2"

\score {
  \new PianoStaff <<
\new Staff = "upper" \relative {
  \voiceOne
  \change Staff = "lower"
  g8[
  \change Staff = "upper"
  g']
}
\new Staff = "lower" \relative {
  \clef bass
  \voiceFour
  c8[ c']
}
  >>
}

--
Knute Snortum

one-page-breaking algorithm and ragged-last-bottom error

[Knute Snortum]

Using one-page-breaking and ragged-last-bottom together produces a
fatal error.  I can see that these two properties don't make sense
together, but ragged-last-bottom should just be ignored or some
graceful warning issued.

\version "2.23.9"

\paper {
  ragged-last-bottom = ##f
  page-breaking = #ly:one-page-breaking
}

{ \repeat unfold 20 { c''4 4 4 4 } }

--
Knute Snortum

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Possible Additions to List of Publications

[Knute Snortum]

Did you mean to send this to lilypond-u...@gnu.org?  It seems like it
would be more appropriate there.

--
Knute Snortum

On Wed, Jun 8, 2022 at 4:21 PM Hendursaga via bug-lilypond
 wrote:
>
> Hello 'ponders!
>
> On a whim, after looking through the publications page[0], I decided to 
> search for other, interesting papers that are related to LilyPond. Here's a 
> few I've found:
>
> 1) Shaffer, Kris. "Make Stunning Schenker Graphs with GNU Lilypond". Linux J. 
> 2005, no.140 (2005).
> 2) Nápoles López, Néstor, Gabriel Vigliensoni, and Ichiro Fujinaga. "The 
> effects of translation between symbolic music formats: A case study with 
> Humdrum, Lilypond, MEI, and MusicXML." In Music Encoding Conference, Vienna, 
> Austria. 2019.
> 3) Colbert-Pollack, Seth, "RNN monophonic sheet music generation with 
> LilyPond" (2018). IPHS 300: Artificial Intelligence for the Humanities: Text, 
> Image, and Sound. Paper 2. https://digital.kenyon.edu/dh_iphs_ai/2
> 4) Duckworth, Richard. "Microtonal Notation: LilyPond as a score editor for 
> Bohlen-Pierce Scales."
> 5) Sinclair, Stephen, Michael Droettboom, and Ichiro Fujinaga. "Lilypond for 
> pyScore: Approaching a universal translator for music notation." In ISMIR, 
> pp. 387-388. 2006.
> 6) Gordini, Tommaso, and Davide Liessi. "LilyPond: un music engraver 
> integrabile con LATEX."
>
> Not sure what exactly are the criteria for inclusion, but they all clearly 
> relate, at least. Any of these look good?
>
> Cheers,
>
> Hendursaga
>
> [0] https://lilypond.org/publications.html
> [1] https://dl.acm.org/doi/fullHtml/10./1103141.1103142
> [2] 
> http://www.x-lab.info/papers/effects_of_translation/effects_of_translation.pdf
> [3] 
> https://digital.kenyon.edu/cgi/viewcontent.cgi?article=1003=dh_iphs_ai
> [4] 
> http://www.tara.tcd.ie/bitstream/handle/2262/75007/SMI%20DKIT%20140612_2DOC.pdf
> [5] https://archives.ismir.net/ismir2006/paper/000156.pdf
> [6] https://guitex.org/home/images/ArsTeXnica/AT018/gordini-liessi.pdf
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Error when slashedGrace follows grace

[Knute Snortum]

The following snippet will cause an error in version 2.22.2:

%%%
\version "2.22.2"

\relative {
  c''2. \grace { b16[ c] } \slashedGrace { d8 } c4\trill |
}
%%%

This error does not show up in 2.23.9, so I don't know if there's any
action to take, but I thought I'd document it here.

--
Knute Snortum

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Temporary staff too long when grace notes are in the permanent staff

[Knute Snortum]

On Mon, Apr 4, 2022 at 4:05 PM David Kastrup  wrote:
> I see absolutely nothing that would suggest that LilyPond doesn't
> exactly engrave what you are asking for here.  No bug, no ugly.
>
> > Is there any work-around?
>
> Not a workaround but correct input: you want to stop the staff 3 eighths
> of grace notes before the next beat, so your ossia needs to stop _then_:
>
>
> Now that \stopStaff is placed at the time where you actually want to
> have the staff end, that's exactly where the staff _does_ end.
>
> And what you see now in terms of stems deserves the title "bug, or at
> least ugly".
>
> But at least the staff length is what you want, and you tell LilyPond
> properly about it.  So you get to complain about the real bug instead...

Thanks for this explanation.  I tried something similar to what you
suggested and ran into the same problem you did.  It's already an
issue:

https://gitlab.com/lilypond/lilypond/-/issues/6307

--
Knute Snortum

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Temporary staff too long when grace notes are in the permanent staff

[Knute Snortum]

If I have a temporary staff, like an ossia, and if the next notes in
the permanent staff after a \stopStaff are grace notes, the temporary
staff extends too long, over the grace notes.  Here is a MWE and
picture attached:

%%%
\version "2.23.7"

rightHand = \relative {
  d''4 d8 b \grace { c,8[ d f] } b4 r |
}

ossia = \relative {
  \stopStaff s4 \startStaff d''16 c b8 \stopStaff s2 |
}

<<
  \new Staff \with {
\remove "Time_signature_engraver"
\hide Clef
\hide KeySignature
\magnifyStaff #2/3
  } {
\ossia
  }
  \new Staff \rightHand
>>
%%%

Seems like a bug, or at least an "ugly."  Is there any work-around?

--
Knute Snortum
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Slur to wrong note when slur is inside a chord with a staccato mark

[Knute Snortum]

When you try to slur to a note inside a chord and that chord has a
staccato mark, the slur ends on the top note, not the target note.

%%%
\version "2.23.7"

\relative {
  a'16( b c -.
}
%%%

--
Knute Snortum

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

strict-note-spacing, grace, and spacer cause programming error

[Knute Snortum]

If you use strict-note-spacing (or strict-grace-spacing) with grace
notes that contain a spacer, a programming error is encountered.  Here
is a MWE:

%%%
\version "2.23.6"

\relative c {
  g4
  \newSpacingSection
  \override Score.SpacingSpanner.strict-note-spacing = ##t
  \grace { e8[ d s16 b8 g e] } c4
}
%%%

The error message is,

programming error: Cannot determine neighbors for floating column

--
Knute Snortum

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Ugly beaming with magnifyStaff and stopStaff

[Knute Snortum]

I have run into a bug while writing an ossia section in my score.  The
beams right before the stopStaff are too "fat" and the stems don't
reach the beam.  Here is a MWE:

%%%
\version "2.23.6"

\new Staff \with { \magnifyStaff #2/3 } {
  \relative {
c''16 c \stopStaff s4. s2 |
  }
}
%%%

This could be seen as just ugly, but this kind of thing must be fairly
common in ossia sections and there is no easy work-around that I know
of.

--
Knute Snortum

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Error with Grace note on Beginning of Staffs

[Knute Snortum]

That's one of the oldest bugs in LilyPond.  The work-around is to put
a grace with a spacer in the other staff too.

%%%
\version "2.22.0"
global= { \time 3/4 }
\score {
  \new GrandStaff <<
   \new Staff \relative { \global \acciaccatura b'8 c16 }
   \new Staff \relative  { \global \grace s8 r4}
>> }
%%%

--
Knute Snortum

On Sun, Sep 19, 2021 at 6:38 AM Martin Steindl
 wrote:
>
> Hello,
>
> I stumbled on a weird display error when using \acciaccatura (or any
> other grace note) on the beginning of a staff in a multi-staff environment.
>
> Somehow, the time signature (and the key -- not shown in example) is
> displayed before _and_ after the \acciaccatura.
>
> Greetings
>
> Martin
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Example of LilyPond real-world usage

[Knute Snortum]

You probably should post this to the lilypond-list, not the bug list.

--
Knute Snortum


On Thu, Mar 4, 2021 at 7:08 AM Peter Anglea  wrote:
>
> Hello, I wanted to make the LilyPond community aware of a real-world use 
> case. I’m not sure if this is the kind of thing you would like to link from 
> the Productions page of the website, or not, but this is a website that is 
> very much powered by LilyPond.
>
> I’ve developed a web app for church musicians called Doxology 
> (https://doxology.app <https://doxology.app/>). I have here a growing catalog 
> of Christian hymns both ancient and modern which can be downloaded in various 
> formats (hymn sheet, lead sheet, or projection slides). Each file can be 
> transposed and customized as desired (for example, showing chord names, 
> changing the capo, etc.). The sheet music is engraved dynamically according 
> to the user input and delivered via download. All of this is done exclusively 
> with LilyPond.
>
> I believe that LilyPond has a lot of potential and I’d like to put this 
> forward as an example of what’s possible. I have a lot to learn about it 
> still, but just over the past 2-3 years or so, I’ve been able to learn enough 
> in my spare time to create this website. Maybe it will inspire other, similar 
> projects. I welcome your input and feedback.
>
> Thanks for your consideration,
> Peter Anglea
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Bad URLs

[Knute Snortum]

Wow.  It all seems fine now.  Must have been a glitch in the matrix.
Sorry for the noise.

---
Knute Snortum
(via Gmail)

On Wed, Aug 5, 2020 at 4:30 AM James  wrote:
>
> Hello Knute
>
> On 27/07/2020 18:56, Knute Snortum wrote:
> > Everywhere in
> >
> >
> > https://lilypond.org/doc/v2.21/Documentation/contributor/index_19#Requirements
> >
> > where it says
> >
> >  Also see (contributor)Starting with Git section ‘Starting with Git’ in
> > Contributor’s Guide.
> >
> > The URL should be
> >
> >
> > https://lilypond.org/doc/v2.21/Documentation/contributor/index_11#Starting-with-Git
> >
> > ---
> > Knute Snortum
> > (via Gmail)
>
> I don't understand this.
>
> In my case I don't have any of these '/index_xx...' strings in my URLs
>
> Where are they coming from?
>
> i.e.
>
> https://lilypond.org/doc/v2.21/Documentation/contributor/index_19#Requirements
>
> gets me a 404
>
> whereas
>
> https://lilypond.org/doc/v2.21/Documentation/contributor/#Requirements
>
> works fine.
>
> ?
>
> James
>

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Bad URLs

[Knute Snortum]

Everywhere in


https://lilypond.org/doc/v2.21/Documentation/contributor/index_19#Requirements

where it says

Also see (contributor)Starting with Git section ‘Starting with Git’ in
Contributor’s Guide.

The URL should be


https://lilypond.org/doc/v2.21/Documentation/contributor/index_11#Starting-with-Git

---
Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: getting score information

[Knute Snortum]

This is a mailing list to report bugs.  You want this mailing list instead:


lilypond-u...@gnu.org

---
Knute Snortum
(via Gmail)


On Mon, Oct 7, 2019 at 12:11 PM jaap de wolff  wrote:

> Hello,
>
>
>
> At this moment I am in the process of creating a lilypond musicxml module.
>
> The module is written in scheme, and at this moment the module is able to
> handle simple music.
>
>
>
> At this moment I am able to handle both
>
>
>
> simplemusic = {}
>
>
>
> \musicxml \simplemusic
>
>
>
> And
>
>
>
> simplemusic = {}
>
>
>
> simplescore = \score (
>
> \simplemusic
>
> \layout {}
>
> }
>
> \musicxml \simplescore
>
>
>
> First question:
>
>
>
> I want to be able to do:
>
> simplemusic = {}
>
>
>
> \score (
>
> \simplemusic
>
> \layout {}
>
> \musicxml {}
>
> \midi {}
>
> }
>
>
>
> Can anyone give a hint how to do this?
>
>
>
> Second question:
>
>
>
> When doing \musicxml \simplescore the scheme function gets an object of the
> type ly:score.
>
>
>
> By digging in code I found out that from this score music can be extracted
> using ly:score-music
>
> Also header can be extracted using ly:score-header and output-defs using
> ly:score-output-defs
>
>
>
> The extracted music can be used without a problem.
>
> However I can not figure out how to use the extracted header and
> output-defs.
>
>
>
> I want to be able to extract information like composer and title to put in
> musicxml
>
>
>
> Does anyone have suggestions?
>
>
>
> Jaap de Wolff
>
>
>
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

\markup command doesn't seem to honor \paper values

[Knute Snortum]

It seems that when you use a \markup command the values in the \paper block
aren't honored.  Here is a minimal example:

%%% Start
\version "2.19.81"

chordNames = \chordmode {
  c1 f g a:m \break
  c f g:7 c \break
}
words = \lyricmode {
  Here_are some random lyrics
  These are more lyrics
}

\paper {
  indent = 0
  ragged-right = ##t

  system-system-spacing = #'((basic-distance . 0)
 (minimum-distance . 0)
 (padding . 1)
 (stretchability . 0))
}

\markup {
  \score {
<<
  \new ChordNames \chordNames
  \new Lyrics \words
>>
\layout { \context { \ChordNames } }
  }
}
%%% End

The question may arise, Why would you want to do this?  Which leads to the
not-so-minimal example:

%%% Start
\version "2.19.81"

chordNames = \chordmode {
  c1 f g a:m \break
  c f g:7 c \break
}
words = \lyricmode {
  Here_are some random lyrics
  These are more lyrics
}

\paper {
  indent = #0
  ragged-right = ##t

  % padding here controls space between lyrics and next line
  system-system-spacing = #'((basic-distance . 0)
 (minimum-distance . 0)
 (padding . 1)
 (stretchability . 0))
}

% Single column outside of markup is spaced according to \paper variables
\score {
  <<
\new ChordNames \chordNames
\new Lyrics \words
  >>
  \layout { \context { \ChordNames } }
}

% Two columns inside markup do not respect \paper spacing variables
\markup {
  \vspace #3
  \score {
<<
  \new ChordNames \chordNames
  \new Lyrics \words
>>
\layout { \context { \ChordNames } }
  }
  \hspace #8
  \score {
<<
  \new ChordNames \chordNames
  \new Lyrics \words
>>
\layout { \context { \ChordNames } }
  }
}
%%% End

Here you can see that the desired output would be in columns.  So the
questions would be: is this a bug?  Is there a better way to do this?


---
Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Ski Emoji Error

[Knute Snortum]

On Tue, Apr 24, 2018 at 8:08 AM, Jay Anderson  wrote:

> On Tue, Apr 24, 2018 at 6:10 AM, James Lowe  wrote:
> >
> > > Probably depends on the Ghostscript version?  Looks fine here:
> >
> > Well it looks OK but I get the same 'error' with gs version 9.22 so I
> > compiled and installed 9.23 and I no longer get this 'failed files'
> message.
> >
>
> I'm unable to download 2.19.81 (download links are broken). Does it include
> a newer version of ghostscript?


http://lilypond.org/download/binaries/  Don't know about ghostscript.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: UNC file names

[Knute Snortum]

>
> > My tests on Windows 10 indicate that lilypond.exe can't handle UNC
> > notation.  This is true even of a local file.
> >
> > First I "type" the file and it works fine with UNC.  Then I try to launch
> > LilyPond with the same file name and it can't find the file.
> >
> > Bug or future feature?
> >
>
> We had a few Windows-related issue - I think they are still needing some
> documentation in the 'running' doc - where some commands needed double
> quotes around the 'path to file name' and some single quotes.
>
> Could you try that and see if that helps?
>

No combination of slash or quote types worked for me.

C:\Users\Knute\Desktop
>lilypond "//KNUTE-HP/Users/Knute/Desktop/test.ly"
GNU LilyPond 2.19.81
warning: cannot find file: `//KNUTE-HP/Users/Knute/Desktop/test.ly'
fatal error: failed files: "//KNUTE-HP/Users/Knute/Desktop/test.ly"

C:\Users\Knute\Desktop
>lilypond '//KNUTE-HP/Users/Knute/Desktop/test.ly'
GNU LilyPond 2.19.81
warning: cannot find file: `'//KNUTE-HP/Users/Knute/Desktop/test.ly''
fatal error: failed files: "'//KNUTE-HP/Users/Knute/Desktop/test.ly'"

C:\Users\Knute\Desktop
>lilypond '\\KNUTE-HP\Users\Knute\Desktop\test.ly'
GNU LilyPond 2.19.81
warning: cannot find file: `'\\KNUTE-HP\Users\Knute\Desktop\test.ly''
fatal error: failed files: "'KNUTE-HP\\Users\\Knute\\Desktop\\test.ly'"

C:\Users\Knute\Desktop
>lilypond "\\KNUTE-HP\Users\Knute\Desktop\test.ly"
GNU LilyPond 2.19.81
warning: cannot find file: `\\KNUTE-HP\Users\Knute\Desktop\test.ly'
fatal error: failed files: "KNUTE-HP\\Users\\Knute\\Desktop\\test.ly"

---
Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

UNC file names

[Knute Snortum]

My tests on Windows 10 indicate that lilypond.exe can't handle UNC
notation.  This is true even of a local file.

First I "type" the file and it works fine with UNC.  Then I try to launch
LilyPond with the same file name and it can't find the file.

Bug or future feature?

*** Start command line
C:\Users\Knute\Desktop
>type \\KNUTE-HP\Users\Knute\Desktop\test.ly
\version "2.19.81"

{ c'4 d' e' f' }
C:\Users\Knute\Desktop
>lilypond \\KNUTE-HP\Users\Knute\Desktop\test.ly
GNU LilyPond 2.19.81
warning: cannot find file: `\\KNUTE-HP\Users\Knute\Desktop\test.ly'
fatal error: failed files: "KNUTE-HP\\Users\\Knute\\Desktop\\test.ly"
*** End command line

---
Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Possible bug: avoid-slur and TrillSpanners

[Knute Snortum]

On Sat, Apr 21, 2018 at 10:54 AM, James Lowe <pkx1...@runbox.com> wrote:

> Knute
>
> On Sat, 21 Apr 2018 06:26:50 -0700, Knute Snortum <ksnor...@gmail.com>
> wrote:
>
> >  In this example...
> >
> > %%% Start
> > \version "2.19.81"
> > \language "english"
> >
> > {
> >   \override TrillSpanner.avoid-slur = #'inside
> >   \override TrillSpanner.outside-staff-priority = ##f
> >   c''1( | c''2. \startTrillSpan c''4 \stopTrillSpan | c''1) |
> > }
> > %%% End
> >
> > ...the slur doesn't avoid the trill spanner.
> >
> >
>
> Is this https://sourceforge.net/p/testlilyissues/issues/397  ?
>
> Regards
>
> James
>

I don't think so. This has to do with TrillSpanner.avoid-slur,  not a
pitched trill.

---
Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Possible bug: avoid-slur and TrillSpanners

[Knute Snortum]

 In this example...

%%% Start
\version "2.19.81"
\language "english"

{
  \override TrillSpanner.avoid-slur = #'inside
  \override TrillSpanner.outside-staff-priority = ##f
  c''1( | c''2. \startTrillSpan c''4 \stopTrillSpan | c''1) |
}
%%% End

...the slur doesn't avoid the trill spanner.


---
Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: force-hshift and dotted rhythms, 2.19.57

[Knute Snortum]

Well, I'd say it's a regression, because if you change the version to
2.18.2, it looks like the attached. The dot follows the note head.
 (2.19.57 is an improvement as the bass clef lines up with the lower
right-hand voice.)  I would think that a NoteColumn would include the dot.
But if there's a better way to do this, let me know.


---
Knute Snortum
(via Gmail)

On Fri, Mar 24, 2017 at 3:47 PM, Andrew Bernard <andrew.bern...@gmail.com>
wrote:

> Hi Knute,
>
> I have often seen this. I just move the dot as well. I thought dots had a
> more or less independent life. The same occurs when moving dotted rests.
>
> Whether this is a big or not, I can't really say.
>
> Andrew
>
>
>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

force-hshift and dotted rhythms, 2.19.57

[Knute Snortum]

I have found a behavior in 2.19.57 that I believe is a bug.  It involves
force-hshift and the dot of a dotted rhythm.  Consider the following input
file:

\version "2.19.57"
\language "english"

global = {
  \time 6/8
  \key af \major
}

rightUpper = { bf'4. \override NoteColumn.force-hshift = -3 af' }
rightLower = { r8 <c' gf'> q q q q }
leftHand = { af,8  q q q q }

rightHand = <<
  \new Voice { \voiceOne \rightUpper }
  \new Voice { \voiceTwo \rightLower }
>>

\score {
  \new PianoStaff <<
\new Staff { \global \rightHand }
\new Staff { \global \clef bass \leftHand }
  >>
}

I've made the shift large to exaggerate the problem.  The note head and
stem of the af' move to the left, but the dot does not shift all the way.
See attached.

---
Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

2.19.56 Learning Manual, part 2

[Knute Snortum]

>
> 3.3.4 Modifying context properties
> ...
> Similarly, if the property name is mis-spelt...


It looks like misspelt is misspelt!

---
Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

2.19.56 Learning Manual correction.

[Knute Snortum]

3.3.2 Creating contexts

In an input file a score block, introduced with a \score command, contains
a single music expression and an associated output definition (either a
\layout or a \midi block).
I'm thinking the last part of the sentence should be "(either a \layout or
a \midi block or both)."

---
Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Command line option to have barcheck failures cause errors instead of warnings

[Knute Snortum]

It seems like a good idea to me.  There often isn't a good reason to have a
good compile with barcheck failures.


Knute Snortum
(via Gmail)

On Thu, Dec 3, 2015 at 3:13 PM, Urs Liska <u...@openlilylib.org> wrote:

> Hi,
>
> there was the request for a way to have barcheck failures cause errors
> instead of warnings:
> http://lists.gnu.org/archive/html/lilypond-user/2015-12/msg00074.html
>
> I think this is a valid use case as very often you don't actually want
> to have the compiled score when it contains barcheck failures, erroring
> out with a useful message pointing to the input location can be a
> time-saver.
>
> This could be controlled by a command line option (e.g.
> -derror-on-barcheck).
>
> Before giving it a try and preparing a patch I would like to get some
> feedback if this idea seems good.
>
> Best
> Urs
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Problem with 2.19.22

[Knute Snortum]

LilyPond 2.19.21 will process the attached file without error but 2.19.22
prints the following:

Parsing...C:/Program Files
(x86)/LilyPond-latest/usr/share/lilypond/current/scm/
music-functions.scm:1987:3: In procedure map-some-music in expression
(map-some-
music (lambda # #) (expand-repeat-chords! # music) ...):
C:/Program Files
(x86)/LilyPond-latest/usr/share/lilypond/current/scm/music-func
tions.scm:1987:3: Wrong number of arguments to #procedure map-some-music
(map?
music)
-- 
--
Knute Snortum
(sent from Gmail)
\version 2.19.21
\language english

\header {
  title= Les Trois Valses Distinguées du Précieux Dégoûté
  subtitle = III. Ses Jambes
  composer = Erik Satie (1866-1925)
  dedication   = à René CHALUPT
  style= Avant-garde
  license  = Creative Commons Attribution-ShareAlike 4.0
  enteredby= Knute Snortum
  lastupdated  = 2015-Jun-21
  date = 1914
  source   = Paris: Rouart, Lerolle  Cie., 1916. Plate R.L. 10,166  Cie.

  mutopiatitle   = Ses Jambes
  mutopiacomposer= SatieE
  mutopiainstrument  = Piano
  maintainer = Knute Snortum
  maintainerEmail= knute (at) snortum (dot) net
  maintainerWeb  = http://www.musicwithknute.com/;
}

% --
% --- Changes from the score ---
% --

% Bar 5: missing bass clef
% Bar 14: extra quarter rest
% Bar 34: third beat, inner voice, add same chord as second beat

% 
% --- Preamble ---
% 

\markup {
  \column {
\line { \hspace #32 Le premier soin du propriétaire, quand il est arrivé à }
\line { \hspace #30 sa ferme, doit etre de saluer ses Pénates domestiques; }
\line { \hspace #30 puis le meme jour, s'il en a le loisir, qu'il fasse le }
\line { \hspace #30 tour de son domaine; qu'il voie l'état des cultures; les } 
\line { \hspace #30 travaux achevés, ceux qui ne le sont pas. }
\line { \hspace #28 (CATON: De ne rustica traduction A. JEANROY et A. PEUCH) }
\line { \null }
  }
}

% ---
% --- Definitions ---
% ---

staffUp = \change Staff = upper
staffDown = \change Staff = lower

forceHShiftOne = \once \override NoteColumn.force-hshift = -1
forceHShiftTwo = \once \override NoteColumn.force-hshift = -0.3

tweakF = \once \override DynamicText.extra-offset = #'(-1.75 . -4) 
tweakTempo = \once \override TextScript.extra-offset = #'(-2 . 2)
tweakFTwo = \once \override DynamicText.extra-offset = #'(0 . -4) 
tweakDanse = \once \override TextScript.extra-offset = #'(0 . -1.5)
tweakPp = \once \override DynamicText.extra-offset = #'(-3 . -2) 
tweakRest = \once \override Rest.extra-offset = #'(0.5 . 0)
tweakP = \once \override DynamicText.extra-offset = #'(-1 . -3)
tweakFTwo = \once \override DynamicText.extra-offset = #'(0 . -1) 

shapeOne = \shape #'((0 . 1.5) (0 . 1.5) (0 . 1.5) (0 . 1.5)) Slur 

% --- Text
fier = \markup { \upright Il en est très fier. }
danseOne = \markup { \upright Elles ne dansent }
danseTwo = \markup { \upright que des danse de choix. }
plates = \markup { \upright Ce sont de belles jambes plates. }
noir = \markup { \upright Le soir, elles sont vêtues de noir. }
porter = \markup { \upright Il veut les porter sous son bras. }
glissent = \markup { \upright Elles glissent, toutes mélancoliques. }
indig = Les voici indignées, très en colère.

% --- Musical terms
determine = \markup { \large \bold \upright Déterminé }
mains = des deux mains
rebond = rebondissez sommairement
toussez = Ne toussez pas

% -
% --- Music ---
% -

highVoice = \relative {
  a' d4- ( cs e b g' |
  a d4- cs e b g' ) |
  a c!4- (  bf d c f |
  a c4-  bf d c f ) |
  fs,8 ( gs b!4 fs!8 gs! |
  b4 e,8 fs a4 |
  e8 fs a4 ) s4 |
  s2. |
  
  \barNumberCheck 9
  s2. * 4 |
  \staffDown
  b,4 ( cs e |
  b4 cs e ) |
  \staffUp
  a4 ( b d |
  a4 b d ) |
  
  \barNumberCheck 17
  fs'8 ( a ) r4 fs!8 ( a ) |
  r4 fs8 ( a ) r4 |
  fs,8 ( a ) r4 fs!8 ( a ) |
  r4 fs8 ( a ) r4 |
  cs,2 ( fs4 ~ |
  fs4 cs 2 |
  b2 d4 ~ |
  d4 b2 ) |
  
  \barNumberCheck 25
  b8 ( g f?4 b8 g |
  f?4 b8 g f?4 ) |
  a8 ( f? e4 a8 f? |
  e4 a8 f? e4 ) |
  a, b4 ( bf c b e ) |
  a b4 ( bf c b e ) |
  \staffDown
  g a4 ( gs b a d ) |
  g a4 ( gs b a d ) |
  \staffUp
  
  \barNumberCheck 33
  r4 ( fs''8 cs' fs4 ) |
  r4 ( e,8 b'? d4 ) |
  r4 ( fs,8 cs' fs4 ) |
  r4 ( e,8 b'? d4 ) |
}

upperMiddle = \relative {
  s2. * 8 |
  
  \barNumberCheck 9
  s2. * 4
  \staffDown
  \forceHShiftOne g2. |
  \forceHShiftOne g2. |
  \staffUp
  f'!4 g a |
  f4 g a |
  
  \barNumberCheck 17
  b4 ( cs e |
  b4 cs e |
  a,4 b d |
  a4 b d ) |
  e,4 ( fs a |
  e4 fs a ) |
  d,4 ( e g  |
  d4 e g ) |
  
  \barNumberCheck 25
  r4 b,2- |
  b2- b4- |
  r4 a2- |
  a2- a4- |
  s2. * 4 |
  
  \barNumberCheck 33
  s4 bf' d bf! d | 
  s4 bf c! q |
  s4 bf d bf! d | 
  s4 bf c! q |
}

lowerMiddle = \relative {
  s2. * 8 |
  
  \barNumberCheck 9
  c!8 ( d fs4 c8 d |
  fs4 c8 d fs!4 |
  c8 d fs4 c8 d

Re: Problem with 2.19.22

[Knute Snortum]

This source file...

\version 2.19.22

\include articulate.ly

\score {
  \articulate 
\new Staff { c' c' c' c' }
  
  \midi {}
}

...produces this output:

Parsing...C:/Program Files
(x86)/LilyPond-latest/usr/share/lilypond/current/scm/music-functions.scm:1987:3:
In procedure map-some-music in expression (map-some-music (lambda # #)
(expand-repeat-chords! # music) ...):
C:/Program Files
(x86)/LilyPond-latest/usr/share/lilypond/current/scm/music-functions.scm:1987:3:
Wrong number of arguments to #procedure map-some-music (map? music)

On Tue, Jun 30, 2015 at 11:43 AM David Kastrup d...@gnu.org wrote:

 David Kastrup d...@gnu.org writes:

  Knute Snortum ksnor...@gmail.com writes:
 
  LilyPond 2.19.21 will process the attached file without error but
 2.19.22
  prints the following:
 
  Parsing...C:/Program Files
  (x86)/LilyPond-latest/usr/share/lilypond/current/scm/
  music-functions.scm:1987:3: In procedure map-some-music in expression
  (map-some-
  music (lambda # #) (expand-repeat-chords! # music) ...):
  C:/Program Files
  (x86)/LilyPond-latest/usr/share/lilypond/current/scm/music-func
  tions.scm:1987:3: Wrong number of arguments to #procedure
 map-some-music
  (map?
  music)
 
  Running convert-ly -ed on the file should fix it.

 Sorry, talked too soon.  This is indeed a problem in LilyPond itself.
 Will take a look.

 --
 David Kastrup

 ___
 bug-lilypond mailing list
 bug-lilypond@gnu.org
 https://lists.gnu.org/mailman/listinfo/bug-lilypond

-- 
--
Knute Snortum
(sent from Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement: using \barNumberCheck inside a \repeat with articulate.ly

[Knute Snortum]

Moving the include fixed the appoggiatura problem, but the barNumberChecks
still emit warnings.



Knute Snortum
(via Gmail)

On Sun, May 10, 2015 at 12:16 AM, Federico Bruni fedel...@gmail.com wrote:

 I _think_ that this bug report explains the problems you reported here and
 in the previous thread:
 https://code.google.com/p/lilypond/issues/detail?id=3696

 I suggest using the workaround (I see it as a sort of best practice for
 using articulate.ly):

 move the include after the \score block with layout and before the \score
 with midi


 Il giorno sab 9 mag 2015 alle 19:13, Knute Snortum ksnor...@gmail.com
 ha scritto:

 If you are using articulate.ly, you can't have a \barNumberCheck inside a
 \repeat even if it's a volta. I believe this is because \articulate does a
 \repeat unfold so it's not a bug per se, but it's a pretty important
 enhancement (IMO) since a lot of baroque music uses trills and repeats.

 \version 2.19.19
 \language english
 \include articulate.ly

 music = \repeat volta 2 {
   \relative c'' {
 c1 \prall |
 \barNumberCheck #2
 d1 |
   }
 }

 \score {
   \music
   \layout {}
 }

 \score {
   \articulate 
 \music
   
   \midi {}
 }

 Knute Snortum
 (via Gmail)
 ___
 bug-lilypond mailing list
 bug-lilypond@gnu.org
 https://lists.gnu.org/mailman/listinfo/bug-lilypond



___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

appoggiatura with articulate.ly, 2.19.19

[Knute Snortum]

If you use an appoggiatura with articulate.ly, even if you have different
score blocks, the appoggiatura is not rendered correctly.

\version 2.19.19
\language english
\include articulate.ly

music = \relative c'' { \appoggiatura cs8 d1 }

\score {
  \music
  \layout {}
}

\score {
  \articulate 
\music
  
  \midi {}
}

Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Enhancement: using \barNumberCheck inside a \repeat with articulate.ly

[Knute Snortum]

If you are using articulate.ly, you can't have a \barNumberCheck inside a
\repeat even if it's a volta. I believe this is because \articulate does a
\repeat unfold so it's not a bug per se, but it's a pretty important
enhancement (IMO) since a lot of baroque music uses trills and repeats.

\version 2.19.19
\language english
\include articulate.ly

music = \repeat volta 2 {
  \relative c'' {
c1 \prall |
\barNumberCheck #2
d1 |
  }
}

\score {
  \music
  \layout {}
}

\score {
  \articulate 
\music
  
  \midi {}
}

Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Possible bug: using articulate.ly, acciaccatura, and \barNumberCheck

[Knute Snortum]

I have a possible bug here.  This may be another Yeah, we know there are
problems with acciaccatura.

When using articulate.ly and \barNumberCheck, you can get into a pickle
where the bar check never reports correctly.  In my sample, the bar number
should be bar 3, but you get a warning saying it's bar 2.  Strangely, when
you change it to bar two, it says it got bar 3.

Here is my sample with a couple bars before for context.

\version 2.19.19
\language english
\include articulate.ly

rh = \relative c'' {
  \time 3/4
  a e'2. \prall |
  R1 * 3/4 \fermataMarkup |

  % --- The following gets an error: Barcheck failed
  \barNumberCheck #3
   { \acciaccatura { e'16 f } g8 f16 e e8 e e e }
 \\
 { \grace { s8 } c2. }
   |
}

lh = \relative c, {
  \time 3/4
  \clef bass
  a a'2. |
  R1 * 3/4 \fermataMarkup |

  \barNumberCheck #3
  c c'4 q q |
}

\score {
  \articulate 
\new PianoStaff 
  \new Staff \rh
  \new Staff \lh

  
  \layout {
  }
  \midi {
  }
}

Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Some C9 chords should be Cadd9

[Knute Snortum]

Great workaround, thanks.


Knute Snortum
(via Gmail)

On Mon, Dec 8, 2014 at 9:45 PM, Keith OHara k-ohara5...@oco.net wrote:

 Knute Snortum ksnortum at gmail.com writes:
 
  Way back in Lilypond 2.14 if you wrote c:9^7 you would get Cadd9, but
 now
  you get C9.  This makes it indistinguishable from c:9.
 

 Thanks, Knute
 I thought I remembered the change that caused this, so I added
  https://code.google.com/p/lilypond/issues/detail?id=4222
 with a link back to the cause.
 The workaround is easy (below) but probably the explicit add should be
 default output, with the brief option available to those who want it

   \new ChordNames \with {additionalPitchPrefix = add }
   \chordmode {
 c1:9^7 % Cadd9   root-3-5-9
 c1:9   % C9  root-3-5-7-9
   }




 ___
 bug-lilypond mailing list
 bug-lilypond@gnu.org
 https://lists.gnu.org/mailman/listinfo/bug-lilypond

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Some C9 chords should be Cadd9

[Knute Snortum]

Way back in Lilypond 2.14 if you wrote c:9^7 you would get Cadd9, but now
you get C9.  This makes it indistinguishable from c:9.

I propose that c:9^7 should render as Cadd9.  See code and attached
proposed output.

\version 2.19.15

\score {
  \new ChordNames \chordmode {
c1:9^7
c1:9
  }
  \layout {
  }
}

Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Build issue in Fedora due to font changes

[Knute Snortum]

Try posting your question here:

lilypond-u...@gnu.org


Knute Snortum
(via Gmail)

On Mon, Nov 24, 2014 at 5:09 AM, Jon Ciesla limburg...@gmail.com wrote:

 On Fri, Nov 14, 2014 at 6:55 AM, Jon Ciesla limburg...@gmail.com wrote:

 
 
  On Mon, Nov 10, 2014 at 10:05 AM, Jon Ciesla limburg...@gmail.com
 wrote:
 
  With the latest release of the UFW fonts, they've dropped the Cyrillic
  glyphs due to poor quality. I see that both 2.18.x and 2.19.x still need
  ufw's ru fonts, and so lilypond fails to build in rawhide.  Is there
  another font set, preferably one in Fedora already, that you'd
 recommend or
  are planning to migrate to?
 
  The Fedora BZ for reference:
  https://bugzilla.redhat.com/show_bug.cgi?id=1160132
 
  Thanks,
  Jon Ciesla, Fedora lilypond maintainer.
 
  --
  http://cecinestpasunefromage.wordpress.com/
  
  in your fear, seek only peace
  in your fear, seek only love
 
  -d. bowie
 
 
  Has anyone had a chance to take a look at this?
 
  Thanks,
  J
 
  Sorry for the noise, but have I possibly asked this question in the wrong
 place?  This was what I was directed to do by the website.


  --
  http://cecinestpasunefromage.wordpress.com/
  
  in your fear, seek only peace
  in your fear, seek only love
 
  -d. bowie
 



 --
 http://cecinestpasunefromage.wordpress.com/
 
 in your fear, seek only peace
 in your fear, seek only love

 -d. bowie
 ___
 bug-lilypond mailing list
 bug-lilypond@gnu.org
 https://lists.gnu.org/mailman/listinfo/bug-lilypond

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Ottava dash-fraction = #0.0 produces dots, not no line

[Knute Snortum]

I'm not top posting

The section on the 2.18 version of OttavaBracket...

http://www.lilypond.org/doc/v2.18/Documentation/internals/ottavabracket

...looks like this:

  dash-fraction (number):
0.3
Size of the dashes, relative to dash-period. Should be between 0.0 (no
line) and 1.0 (continuous line).

But this code...
%% --- Start
\version 2.18.2

\relative c,, {
  \clef bass
  \ottava #-1
  \override Staff.OttavaBracket.dash-fraction = #0.0
  c4 c c c
}
%% --- End

...produces a dotted line, not no line as the documentations states.
 Either the documentation or the behavior should be changed.

Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: New feature suggestion

[Knute Snortum]

Just my two cent's worth:

Adding an n modifier isn't saying that C Sharp is C Natural, it's an
assertion.  Yes, I really mean natural.  No, I didn't just forget the
sharp.


Knute Snortum
(via Gmail)


On Tue, Aug 26, 2014 at 5:22 AM, David Nalesnik david.nales...@gmail.com
wrote:

 On Tue, Aug 26, 2014 at 2:11 AM, Keith OHara k-ohara5...@oco.net wrote:

  David Nalesnik david.nalesnik at gmail.com writes:
 
   In the US, I hear people calling c-sharp c often enough.  This
 usage
  is
   certainly not good practice in music theory classes (where I correct it
   whenever I can).  I can't say anything about informal usage.
 
  The original question here was about calling, in the key of D major,
  the note c-natural by the name c-natural.
  Here I think we would not require the student to say c, in English.
 

 Of course not.

 Sorry, I think I was responding to the tendency of students to call C sharp
 in the key of D major C, which is obviously wrong!

 cn is nice--I would say C natural, and why not make it explicit?

 --David
 ___
 bug-lilypond mailing list
 bug-lilypond@gnu.org
 https://lists.gnu.org/mailman/listinfo/bug-lilypond

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1129: Font styles return to default when font size changed

[Knute Snortum]

Hilary, you might want to post the problem to lilypond-user.  By that I
mean, post what you want to do and ask for a workaround.


Knute Snortum
(via Gmail)


On Fri, Aug 8, 2014 at 1:35 AM, tisimst tisimst.lilyp...@gmail.com wrote:

 On Fri, Aug 8, 2014 at 2:21 AM, Hilary Snaden [via Lilypond]
 ml-node+s1069038n165395...@n5.nabble.com wrote:
  Is this likely to be resolved? Perhaps a more fully-functioning
  workaround?
 
  I'm not nearly clever enough to do either myself, and it looks as
  though
  I must generate a series of scores with manually-set page numbers
  (and
  blank pages) and combine them with pdftk.
 
  --
  Hilary
 
  ___
  bug-lilypond mailing list
  [hidden email]
  https://lists.gnu.org/mailman/listinfo/bug-lilypond
 
 
  If you reply to this email, your message will be added to the
  discussion below:
 
 http://lilypond.1069038.n5.nabble.com/Issue-1129-Font-styles-return-to-default-when-font-size-changed-tp165395.html
  To start a new topic under Bugs, email
  ml-node+s1069038n58488...@n5.nabble.com
  To unsubscribe from Lilypond, click here.
  NAML
 
 Hilary,

 What exactly are you wanting to do? Maybe there's a workaround...

 -Abraham




 --
 View this message in context:
 http://lilypond.1069038.n5.nabble.com/Issue-1129-Font-styles-return-to-default-when-font-size-changed-tp165395p165396.html
 Sent from the Bugs mailing list archive at Nabble.com.
 ___
 bug-lilypond mailing list
 bug-lilypond@gnu.org
 https://lists.gnu.org/mailman/listinfo/bug-lilypond

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Ambiguous (de)crescendo in MIDI error

[Knute Snortum]

Something that is seen a lot in 19th and 20th century music is a crescendo
or decrescendo without going to a specific dynamic.  The performer is given
the freedom to decide how much to change the dynamics.  This causes an
error message: programming error: Impossible or ambiguous (de)crescendo in
MIDI.

%%% BEGIN
\version 2.19.10

\score {
  \relative c' {
c1 \p | c4 \ d e f | g \ f e d | c1 \p
  }
  \layout {}
  \midi {}
}
%%% END

This error message should be a warning and give some line number to the
offending code.

Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

[Doc] Minor: link to tuplet section

[Knute Snortum]

Maybe this section...

http://www.lilypond.org/doc/v2.18/Documentation/learning/advanced-rhythmic-commands#tuplets

...should have a link to this section:

http://lilypond.org/doc/v2.18/Documentation/notation/writing-rhythms#tuplets

Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Changing the direction of a tuplet bracket

[Knute Snortum]

\tupletUp

Got it.  Thanks to all.


Knute Snortum
(via Gmail)


On Tue, Jun 17, 2014 at 3:56 PM, James pkx1...@gmail.com wrote:

  On 17/06/14 22:47, Javier Ruiz-Alma wrote:

  *I want to change the direction of a tuplet bracket (up in this case).
  *

 Try \tupletUp ahead of where you wish to implement the change in
 direction…there’s also \tupletDown, \tupletNeutral





 *I read the manual on tuplets and it says *


 *Tuplet brackets may be manually placed above or below the staff;
 see Direction and placement
 http://lilypond.org/doc/v2.18/Documentation/notation/direction-and-placement.
 But neither the tuplet nor the direction section has an example*



 I agree, the NR section you refer to could be made clearer.  You are given
 a link for manual placement, while the positioning commands are just a few
 lines down on the primary page under the heading “Predefined commands”.


 ___
 lilypond-user mailing 
 listlilypond-user@gnu.orghttps://lists.gnu.org/mailman/listinfo/lilypond-user

  Thanks.

 Added as http://code.google.com/p/lilypond/issues/detail?id=3956

 James

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: simultaneous tempo-change events

[Knute Snortum]

That's fine.  It just took me a couple of minutes to figure out that it was
the compile last measures feature making the warning.  Maybe a note in the
documents saying that the feature can produce oddities.


Knute Snortum
(via Gmail)


On Sun, Jun 1, 2014 at 11:46 PM, Phil Holmes m...@philholmes.net wrote:

 Knute Snortum ksnor...@gmail.com wrote in message news:CALmeJxQT5HNp+
 4wpqov2bamnapwkkw6i6ohc4fia1zcrjx6...@mail.gmail.com...

  The following will emit this spurious warning: Two simultaneous
 tempo-change events, junking this one

 %
 \version 2.18.2


 showLastLength = R1


 \relative c' {

  \tempo 4 = 80

  c4 c c c

  \tempo 4 = 90

  c4 c c c

 }

 --
 Knute Snortum
 (via Gmail)


 In my experience, all of the skip typesetting features of LilyPond have
 some idiosyncrasies.  I'm not convinced it's worth worrying about this.

 --
 Phil Holmes



 ___
 bug-lilypond mailing list
 bug-lilypond@gnu.org
 https://lists.gnu.org/mailman/listinfo/bug-lilypond

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

simultaneous tempo-change events

[Knute Snortum]

The following will emit this spurious warning: Two simultaneous
tempo-change events, junking this one

%
\version 2.18.2


showLastLength = R1


\relative c' {

  \tempo 4 = 80

  c4 c c c

  \tempo 4 = 90

  c4 c c c

}

-- 
Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond