simultaneous tempo-change events

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

Re: simultaneous tempo-change events

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

Re: Changing the direction of a tuplet bracket

\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

[Doc] Minor: link to tuplet section

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

Ambiguous (de)crescendo in MIDI error

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

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

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

Re: New feature suggestion

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

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

be changed. 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

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

Some C9 chords should be Cadd9

} \layout { } } 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

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

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

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: Enhancement: using \barNumberCheck inside a \repeat with articulate.ly

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

appoggiatura with articulate.ly, 2.19.19

\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

. \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

Problem with 2.19.22

-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

Re: Problem with 2.19.22

...@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

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

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 failur

force-hshift and dotted rhythms, 2.19.57

\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) ___ bu

Re: force-hshift and dotted rhythms, 2.19.57

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. Th

2.19.56 Learning Manual, part 2

> > 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/mail

2.19.56 Learning Manual correction.

both)." --- Knute Snortum (via Gmail) ___ 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

rdNames \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) __

Possible bug: avoid-slur and TrillSpanners

id the trill spanner. --- 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

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.

Re: Ski Emoji Error

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

Re: UNC file names

ypond "\\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

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: getting score information

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.

Re: Bad URLs

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 > > > > >

Bad URLs

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

Re: Example of LilyPond real-world usage

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

Re: Error with Grace note on Beginning of Staffs

bal \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. > &g

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

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

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

% 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

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

an 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

Ugly beaming with magnifyStaff and stopStaff

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/

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

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 bu

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

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.

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

e-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

Error when slashedGrace follows grace

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.

Re: Possible Additions to List of Publications

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

Stems wrong direction when change staff is first

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

Cyclic dependencies with \afterGrace and cross-staff notes

d \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

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

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

Re: Ugly ties in chord clusters

t; \relative { > \override Score.SpacingSpanner.shortest-duration-space = #3 > ~ q > } > Do you mean without the override? With the override, the ties look fine. -- Knute Snortum

Minimum tie length not honored after a break

the chord. This may be related to issue: https://gitlab.com/lilypond/lilypond/-/issues/4279 -- Knute Snortum

Re: Minimum tie length not honored after a break

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.

offset and TupletNumbers

ming 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?

Re: PDF hyperlinks pointing to internal LilyPond code

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" > > > > { \acciaccat

Re: PDF hyperlinks pointing to internal LilyPond code

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.

Re: Incorrect transposition via musicxml2ly

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: Incorrect transposition via musicxml2ly

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: musicxml2ly chord names

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) > >

Re: musicxml2ly chord names

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: PDF hyperlinks pointing to internal LilyPond code

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 y

\alternative fails if \repeat unfold proceeds it

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

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

g 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

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 >

Re: Chord names collide with span bar

t; >> > } > ``` > > > 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

Chord names collide with span bar

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

Re: Chord names collide with span bar

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

Re: Chord names collide with span bar

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

Re: Chord names collide with span bar

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 \

Re: Chord names collide with span bar

l-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

Programming 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