Re: Strange error from define-syntax

[David Kastrup]

"John Schlomann"  writes:

> define-macro works perfectly for me, even though the Guile manual seems to
> somewhat disparage its use.

Well, it's not the modern Scheme way but at the current point of time
LilyPond works best with Guile 1.8.

-- 
David Kastrup

RE: Strange error from define-syntax

[John Schlomann]

define-macro works perfectly for me, even though the Guile manual seems to
somewhat disparage its use.

Thank you, David.

John

> -Original Message-
> From: David Kastrup [mailto:d...@gnu.org]
> Sent: Thursday, May 28, 2020 2:02 PM
> To: John Schlomann
> Cc: 'Lilypond-User Mailing List'
> Subject: Re: Strange error from define-syntax
> 
> "John Schlomann"  writes:
> 
> > Thank you, David, for your quick response. I'm not sure what you mean by
> > "stick to macros". I thought define-syntax was the way to define a
macro.
> > What am I missing?
> 
> define-macro and defmacro apparently.
> 
> --
> David Kastrup

Re: Strange error from define-syntax

[David Kastrup]

"John Schlomann"  writes:

> Thank you, David, for your quick response. I'm not sure what you mean by
> "stick to macros". I thought define-syntax was the way to define a macro.
> What am I missing?

define-macro and defmacro apparently.

-- 
David Kastrup

Re: Strange error from define-syntax

[Valentin Villenave]

On 5/28/20, John Schlomann  wrote:
> Thank you, David, for your quick response. I'm not sure what you mean by
> "stick to macros". I thought define-syntax was the way to define a macro.
> What am I missing?

I think David may have been referring to LilyPond macros; have a look
at that for example:
http://lilypond.org/doc/v2.21/Documentation/extending-big-page#interfaces-for-programmers

Cheers,
-- V.

RE: Strange error from define-syntax

[John Schlomann]

Thank you, David, for your quick response. I'm not sure what you mean by
"stick to macros". I thought define-syntax was the way to define a macro.
What am I missing?

John

> -Original Message-
> From: David Kastrup [mailto:d...@gnu.org]
> Sent: Thursday, May 28, 2020 11:54 AM
> To: John Schlomann
> Cc: 'Lilypond-User Mailing List'
> Subject: Re: Strange error from define-syntax
> 
> "John Schlomann"  writes:
> 
> > Dear Ponders & Schemers,
> >
> >
> >
> > I wanted to try creating a simple Scheme macro. I've never done this
> before,
> > so I may well be going about it all wrong, but the error I get doesn't
make
> > sense.
> >
> >
> >
> > Here is a minimal non-working example:
> >
> >
> >
> > \version "2.20.0"
> >
> >  #(use-modules (ice-9 syncase))
> >
> >
> >
> >  #(define-syntax set-default
> >
> >(syntax-rules ()
> >
> > ((set-default name value)
> >
> >  (if (eqv? name 'UNDEF) name value)
> >
> >)))
> >
> >
> >
> >  #(define some-setting 44)
> >
> >  #(set-value some-setting 99)
> >
> >  #(ly:message "some-setting = ~a\n" some-setting)
> >
> >
> >
> > This gives the error:
> >
> > Wrong number of arguments to # > (arg)>>
> >
> >
> >
> > Huh? I also tried define-syntax-rule, which came up unbound. Any
insights
> > into what I'm doing wrong would be welcome.
> 
> syntax-case doesn't work in LilyPond since LilyPond defines \void as a
> music function and the Guile 1.8 implementation of syntax-case falls
> apart if 'void has a value.
> 
> You are not doing anything wrong other than expecting syntax-case to
> work.  Stick to macros instead of define-syntax.  Sorry for that.
> 
> --
> David Kastrup

Re: Strange error from define-syntax

[David Kastrup]

"John Schlomann"  writes:

> Dear Ponders & Schemers,
>
>  
>
> I wanted to try creating a simple Scheme macro. I've never done this before,
> so I may well be going about it all wrong, but the error I get doesn't make
> sense.
>
>  
>
> Here is a minimal non-working example:
>
>  
>
> \version "2.20.0"
>
>  #(use-modules (ice-9 syncase))
>
>  
>
>  #(define-syntax set-default
>
>(syntax-rules ()
>
> ((set-default name value)
>
>  (if (eqv? name 'UNDEF) name value)
>
>)))
>
>  
>
>  #(define some-setting 44)
>
>  #(set-value some-setting 99)
>
>  #(ly:message "some-setting = ~a\n" some-setting)
>
>  
>
> This gives the error:
>
> Wrong number of arguments to # (arg)>>
>
>  
>
> Huh? I also tried define-syntax-rule, which came up unbound. Any insights
> into what I'm doing wrong would be welcome.

syntax-case doesn't work in LilyPond since LilyPond defines \void as a
music function and the Guile 1.8 implementation of syntax-case falls
apart if 'void has a value.

You are not doing anything wrong other than expecting syntax-case to
work.  Stick to macros instead of define-syntax.  Sorry for that.

-- 
David Kastrup

Re: Strange error from \new Voice

[David Wright]

On Fri 10 Apr 2020 at 09:58:57 (+0200), Michael Gerdau wrote:
> > When working with addlyrics it was outside the \new staff construct like
> > here:
> > 
> > tenorVoicePart = \new Staff \with {
> >   instrumentName = "Tenor"
> >   midiInstrument = "choir aahs"
> > } { \clef "treble_8" \tenorVoice }
> > \addlyrics { \verseVoice }
> > 
> > Now, it is within
> > 
> > Soprano = \new Staff \with {
> >   instrumentName = "Sopran"
> > } <<
> >   \new Voice = "SI" { \voiceOne \SopranoVoiceI }
> >   \new Voice = "SII" { \voiceTwo \SopranoVoiceII }
> >   \new Lyrics \lyricsto "SI" { \VerseSopranoVoiceI }
> >>>
> > 
> > That should be mentioned.
> 
> I'm surprised that works. I always do it like this:
> Soprano = <<
>   \new Staff \with {
> instrumentName = "Sopran"
>   } <<
> \new Voice = "SI" { \voiceOne \SopranoVoiceI }
> \new Voice = "SII" { \voiceTwo \SopranoVoiceII }
>   >>
>   \new Lyrics \lyricsto "SI" { \VerseSopranoVoiceI }
> >>
> 
> That's what's documented under the link that Joram already provided.

I shall attempt to explain (corrections welcomed).

The OP posted¹:

Soprano = \new Staff \with {
  instrumentName = "Sopran"
} <<
  \new Voice = "SI" { \voiceOne \SopranoVoiceI }
  \new Voice = "SII" { \voiceTwo \SopranoVoiceII }
>>
\addlyrics { \VerseSopranoVoiceI }²

\addlyrics nowadays works on the Staff (2.18.2 would fail here³), and
sets the lyrics with one syllable per musical moment, whichever voice
it occurs in. See my example from earlier today. Of course, that's not
what the OP wanted, because it doesn't respect ties and slurs etc in
either voice.

Your first post suggested:

Soprano = \new Staff \with {
  instrumentName = "Sopran"
} <<
  \new Voice = "SI" { \voiceOne \SopranoVoiceI }
  \new Voice = "SII" { \voiceTwo \SopranoVoiceII }
>>
\new Lyrics \lyricsto "SI" { \VerseSopranoVoiceI }

LP now tries to set a score consisting solely of Lyrics (because
\new Lyrics is actually at top-level), at which it fails.

In your last post, you've written:

Soprano = <<
  \new Staff \with {
instrumentName = "Sopran"
  } <<
\new Voice = "SI" { \voiceOne \SopranoVoiceI }
\new Voice = "SII" { \voiceTwo \SopranoVoiceII }
  >>
  \new Lyrics \lyricsto "SI" { \VerseSopranoVoiceI }
>>

Now the outer << >> brackets bundle the lyrics together with the
Staff, which contains notes, so LP has no problem setting them.

Similarly, the example that surprised you, above, has the Voices
and Lyrics bracketed together, so no problem.

¹ The marginal indentation is for clarity, but all these examples
  are top-level and would be pushed leftwards.

² I have "corrected" the OP's indentation. Originally, this line was
  indented by two spaces, making it look as if it was inside
  something, whereas it's really just the end of the \new Staff's
  definition.

³ 2.18.2 understands \new Voice { … } \addlyrics { … }

  2.20   understands \new Voice { … } \addlyrics { … }
and also \new Staff { … } \addlyrics { … }

Cheers,
David.

Re: Strange error from \new Voice

[David Wright]

On Thu 09 Apr 2020 at 18:41:40 (+0200), Noeck wrote:
> Am 09.04.20 um 18:18 schrieb Bernhard Kleine:
> > This would be worth mentioning in the manual!
> 
> glad it works. What exactly would you mention in the manual?
> 
> 1) How to use the \lyricsto construct? It is explained here:
> 
> https://lilypond.org/doc/v2.20/Documentation/notation/common-notation-for-vocal-music.html#aligning-lyrics-to-a-melody
> 
> 2) That you have to use the correct characters ("" instead of „“)?
>Well, that’s trivial, isn’t it? I mean you cannot use a ` for a '
>or a { for a (.
> 
> 3) That \addlyrics can fail in some cases and \lyricsto is more robust?
>There is a small sentence saying
> 
> > The command \addlyrics cannot handle polyphonic settings. … For these cases 
> > one should use \lyricsto.

Yes, this warning comes twice, firstly on p267, quoted here, and later
on p292, "The \addlyrics function only works with Voice lyrics and so
cannot be used with NullVoice."

But what doesn't appear to be well explained is this recent construct:

  \new Staff <<
\new Voice { \voiceOne \soprano }
\new Voice { \voiceTwo \alto }
  >>
  \addlyrics { \textj }

An example of two different methods is attached.

Cheers,
David.
\version "2.19.44"
\language english

\paper {
  #(set-paper-size "a5landscape")
  systems-per-page = 2
  ragged-right = ##f
  ragged-last-bottom = ##t
  indent = 0
}

global = {
  \key g \major
  \time 4/4
  s1 * 4
  \bar "||"
}

align = \relative {
  b'4 g d d d g8~ g g4 fs g4 b e,8 fs g~ g c4 b b( a)
}

soprano = \relative {
  b'4 g d d d g g fs g b e,8 fs g4 c b b( a)
}

alto = \relative {
  d'4 b c c b b8 cs d4 d d b e d8 e fs4 g g( fs)
}

texti = \lyricmode {
  \set stanza = "1."
  Come, thou long -- ex -- pec -- ted __ Jes -- us,
  Born to set __ _ thy __ peo -- ple free; __
}

textj = \lyricmode {
  \set stanza = "1."
  Come, thou long -- ex -- pec -- ted __ _ Jes -- us,
  Born to set __ _ thy __ _ peo -- ple free; __ _
}

\new Staff <<
  \clef treble \global
  \new Voice { \voiceOne \soprano }
  \new Voice { \voiceTwo \alto }
  \new NullVoice = valign { \voiceOne \align }
  \new Lyrics \lyricsto valign { \texti }
>>
\layout { }

\new Staff <<
  \clef treble \global
  \new Voice { \voiceOne \soprano }
  \new Voice { \voiceTwo \alto }
>>
\addlyrics { \textj }
\layout { }


staff-align.pdf
Description: Adobe PDF document

Re: Strange error from \new Voice

[Michael Gerdau]

> When working with addlyrics it was outside the \new staff construct like
> here:
> 
> tenorVoicePart = \new Staff \with {
>   instrumentName = "Tenor"
>   midiInstrument = "choir aahs"
> } { \clef "treble_8" \tenorVoice }
> \addlyrics { \verseVoice }
> 
> Now, it is within
> 
> Soprano = \new Staff \with {
>   instrumentName = "Sopran"
> } <<
>   \new Voice = "SI" { \voiceOne \SopranoVoiceI }
>   \new Voice = "SII" { \voiceTwo \SopranoVoiceII }
>   \new Lyrics \lyricsto "SI" { \VerseSopranoVoiceI }
>>>
> 
> That should be mentioned.

I'm surprised that works. I always do it like this:
Soprano = <<
  \new Staff \with {
instrumentName = "Sopran"
  } <<
\new Voice = "SI" { \voiceOne \SopranoVoiceI }
\new Voice = "SII" { \voiceTwo \SopranoVoiceII }
  >>
  \new Lyrics \lyricsto "SI" { \VerseSopranoVoiceI }
>>

That's what's documented under the link that Joram already provided.

Kind regards,
Michael
-- 
 Michael Gerdau   email: m...@qata.de
 GPG-keys available on request or at public keyserver



signature.asc
Description: OpenPGP digital signature

Re: Strange error from \new Voice

[Bernhard Kleine]

When working with addlyrics it was outside the \new staff construct like
here:

tenorVoicePart = \new Staff \with {
  instrumentName = "Tenor"
  midiInstrument = "choir aahs"
} { \clef "treble_8" \tenorVoice }
\addlyrics { \verseVoice }

Now, it is within

Soprano = \new Staff \with {
  instrumentName = "Sopran"
} <<
  \new Voice = "SI" { \voiceOne \SopranoVoiceI }
  \new Voice = "SII" { \voiceTwo \SopranoVoiceII }
  \new Lyrics \lyricsto "SI" { \VerseSopranoVoiceI }
>>
 

That should be mentioned.

Am 09.04.2020 um 18:41 schrieb Noeck:
>
> Am 09.04.20 um 18:18 schrieb Bernhard Kleine:
>> This would be worth mentioning in the manual!
> Hi Bernhard,
>
> glad it works. What exactly would you mention in the manual?
>
> 1) How to use the \lyricsto construct? It is explained here:
>
> https://lilypond.org/doc/v2.20/Documentation/notation/common-notation-for-vocal-music.html#aligning-lyrics-to-a-melody
>
> 2) That you have to use the correct characters ("" instead of „“)?
>Well, that’s trivial, isn’t it? I mean you cannot use a ` for a '
>or a { for a (.
>
> 3) That \addlyrics can fail in some cases and \lyricsto is more robust?
>There is a small sentence saying
>
>> The command \addlyrics cannot handle polyphonic settings. … For these cases 
>> one should use \lyricsto.
> Best,
> Joram
>
-- 
spitzhalde9
D-79853 lenzkirch
bernhard.kle...@gmx.net
www.b-kleine.com, www.urseetal.net
Ich darf auch auf mein neues Buch "Falter in Lenzkirch" aufmerksam machen 
(Infos bei mir)
-
thunderbird mit enigmail
GPG schlüssel: D5257409
fingerprint:
08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09




signature.asc
Description: OpenPGP digital signature

Re: Strange error from \new Voice

[Noeck]

Am 09.04.20 um 18:18 schrieb Bernhard Kleine:
> This would be worth mentioning in the manual!

Hi Bernhard,

glad it works. What exactly would you mention in the manual?

1) How to use the \lyricsto construct? It is explained here:

https://lilypond.org/doc/v2.20/Documentation/notation/common-notation-for-vocal-music.html#aligning-lyrics-to-a-melody

2) That you have to use the correct characters ("" instead of „“)?
   Well, that’s trivial, isn’t it? I mean you cannot use a ` for a '
   or a { for a (.

3) That \addlyrics can fail in some cases and \lyricsto is more robust?
   There is a small sentence saying

> The command \addlyrics cannot handle polyphonic settings. … For these cases 
> one should use \lyricsto.

Best,
Joram

Re: Strange error from \new Voice

[Bernhard Kleine]

Am 09.04.2020 um 17:18 schrieb Noeck:
>
> Am 09.04.20 um 17:04 schrieb Bernhard Kleine:
>> \new Lyrics \lyricsto „SI“
> Did you copy that verbatim or use the correct "normal quotes":
>
> \new Lyrics \lyricsto "SI"
>
> Just to rule out that simple problem.
>
> Joram

This is what is there :

Soprano = \new Staff \with {
  instrumentName = "Sopran"
} <<
  \new Voice = "SI" { \voiceOne \SopranoVoiceI }
  \new Voice = "SII" { \voiceTwo \SopranoVoiceII }
  >>
  \new Lyrics \lyricsto "SI" { \VerseSopranoVoiceI }

I tested also 

Soprano = \new Staff \with {
  instrumentName = "Sopran"
} <<
  \new Voice = "SI" { \voiceOne \SopranoVoiceI }
  \new Voice = "SII" { \voiceTwo \SopranoVoiceII }
  \new Lyrics \lyricsto "SI" { \VerseSopranoVoiceI }
>>

And this worked! This would be worth mentioning in the manual!


-- 
spitzhalde9
D-79853 lenzkirch
bernhard.kle...@gmx.net
www.b-kleine.com, www.urseetal.net
Ich darf auch auf mein neues Buch "Falter in Lenzkirch" aufmerksam machen 
(Infos bei mir)
-
thunderbird mit enigmail
GPG schlüssel: D5257409
fingerprint:
08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09




signature.asc
Description: OpenPGP digital signature

Re: Strange error from \new Voice

[Noeck]

Am 09.04.20 um 17:04 schrieb Bernhard Kleine:
> \new Lyrics \lyricsto „SI“

Did you copy that verbatim or use the correct "normal quotes":

\new Lyrics \lyricsto "SI"

Just to rule out that simple problem.

Joram

Re: Strange error from \new Voice

[Bernhard Kleine]

this results in an error: the output is in the appendix.

Preprocessing graphical objects...

programming error: No spring between column 0 and next one

continuing, cross fingers

programming error: No spring between column 0 and next one

continuing, cross fingers

programming error: didn't find a vertical alignment in this system

continuing, cross fingers

programming error: No spring between column 0 and next one

continuing, cross fingers



Am 09.04.2020 um 15:10 schrieb Michael Gerdau:
> \new Lyrics \lyricsto „SI“

--
spitzhalde9
D-79853 lenzkirch
bernhard.kle...@gmx.net
www.b-kleine.com, www.urseetal.net
Ich darf auch auf mein neues Buch "Falter in Lenzkirch" aufmerksam machen
(Infos bei mir)
-
thunderbird mit enigmail
GPG schlüssel: D5257409
fingerprint:
08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09



testMendelssohn.pdf
Description: Adobe PDF document

Re: Strange error from \new Voice

[Michael Gerdau]

Replace \addlyrics... by \new Lyrics \lyricsto „SI“...

Kind regards,
Michael 

Mobil gesendet

> Am 09.04.2020 um 15:03 schrieb Bernhard Kleine :
> 
> I have the following extract from Mendelssohn Bartholdy. I noticed that
> the parentheses in measure seven were not respected and the text was
> wrongly applied. When eleminating the line "  \new Voice = "SII" {
> \voiceTwo \SopranoVoiceII }" the text was correct. Please can you
> explain and propose a remedy?
> 
> Thank you!
> 
> \version "2.20.0"
> \language "deutsch"
> \header {
>   title = "Der 100. Psalm"
>   tagline = "Bermhard Kleine 2020"
> }
> \paper {
>   #(set-paper-size "a4")
> }
> \layout {
>   \context {
> \Voice
> \consists "Melody_engraver"
> \override Stem #'neutral-direction = #'()
>   }
>  }
> global = {
>   \key c \major
>   \time 4/4
>   \autoBeamOff
> }
> SopranoVoiceI = \relative c'' {
>   \global
>   \dynamicUp
>   g2\f g4 g | c2 c4 d | e1\fermata g,4 g8 g a4 g | f2 e |
>   c'4 c8 c c4 c | c (d) e c | h a g h | e2. (d4~| d ) c2 c4 | c1 |
> h2.\fermata
> }
> VerseSopranoVoiceI = \lyricmode {
>   Jauch -- zet dem Herrn al -- le Welt! Die -- net dem Herrn mit Freu --
> den.
>   Die -- net dem Herrn mit Freu -- den, kommt vor sein An -- ge -- sicht
> mit Froh -- lok -- ken.
>   Er -- ken -- net,
> }
> SopranoVoiceII = \relative c'' {
>   \global
>   \dynamicUp
>   % Die Noten folgen hier.
>   s1*11
> }
> Soprano = \new Staff \with {
>   instrumentName = "Sopran"
> } <<
>   \new Voice = "SI" { \voiceOne \SopranoVoiceI }
>   \new Voice = "SII" { \voiceTwo \SopranoVoiceII }
>   >>
>   \addlyrics { \VerseSopranoVoiceI }
> \score {
>   <<
> \Soprano
>   >>
>   \layout { }
> }
> 
> -- 
> spitzhalde9
> D-79853 lenzkirch
> bernhard.kle...@gmx.net
> www.b-kleine.com, www.urseetal.net
> Ich darf auch auf mein neues Buch "Falter in Lenzkirch" aufmerksam machen 
> (Infos bei mir)
> -
> thunderbird mit enigmail
> GPG schlüssel: D5257409
> fingerprint:
> 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
> 
> 

Re: Strange error with no traceable cause.

[David Kastrup]

Karlin High  writes:

> On 6/5/2018 4:02 PM, Thomas Morley wrote:
>>> For running gdb do:
>>>
>>> gdb path/to/lilypond-executable
>>>
>>> For example: gdb lilypond-git/build/out/bin/lilypond
>>> You will get some infos about gdb returned, finally it ends with
>>> (gdb)
>>>
>>> Then type:
>>> run path/to/the/ly-file
>> I forgot, type:
>>
>> bt
>>
>> to get the stack and then:
>>
>>> Post the output.
>
> Watching and learning about gdb... Does this work for "standard"
> LilyPond distributions? Or only for compiled-from-source with
> debugging symbols or something?

The backtrace usually at least is good for the function names even
without debug information.

-- 
David Kastrup

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

Re: Strange error with no traceable cause.

[Karlin High]

On 6/5/2018 4:02 PM, Thomas Morley wrote:

For running gdb do:

gdb path/to/lilypond-executable

For example: gdb lilypond-git/build/out/bin/lilypond
You will get some infos about gdb returned, finally it ends with
(gdb)

Then type:
run path/to/the/ly-file

I forgot, type:

bt

to get the stack and then:


Post the output.


Watching and learning about gdb... Does this work for "standard" 
LilyPond distributions? Or only for compiled-from-source with debugging 
symbols or something?

--
Karlin High
Missouri, USA

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

Re: Strange error with no traceable cause.

[Thomas Morley]

2018-06-05 22:45 GMT+02:00 Thomas Morley :
> 2018-06-05 22:35 GMT+02:00  :
>>  Mensagem Original 
>> Ativo 5 de jun de 2018 17:30, David Kastrup < d...@gnu.org> escreveu:
>>
>> crimsonsunr...@protonmail.com writes:
>>
>>> Well, I don't have any experience with gdb, so I wouldn't know what to
>>> do. The strange thing seems to be that, if the score is engraved using
>>> Frescobaldi's verbose output ( which has a separate engrave button ),
>>> the error doesn't happen.
>>
>> That's not unusual for such garbage collection errors: triggering them
>> requires a garbage collection occuring at an inopportune point of time
>> and the time depends on how much memory is being temporarily used. With
>> verbose output, more memory is churned through because of the storage
>> the formatting of the verbose output requires, and thus garbage
>> collection happens at different points of time than without verbose
>> output.
>>
>> That makes these kind of error annoyingly hard to track down: they
>> vanish and reappear with completely unrelated changes in usage and the
>> actual error message is triggered at a time far from the problem.
>>
>> --
>> David Kastrup
>>
>> The most I can do is see if I can upload the files so other people can see
>> if the same error happens on other machines.
>
>
> For running gdb do:
>
> gdb path/to/lilypond-executable
>
> For example: gdb lilypond-git/build/out/bin/lilypond
> You will get some infos about gdb returned, finally it ends with
> (gdb)
>
> Then type:
> run path/to/the/ly-file

I forgot, type:

bt

to get the stack and then:

> Post the output.
>
>
> Cheers,
>   Harm

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

Re: Strange error with no traceable cause.

[Thomas Morley]

2018-06-05 22:35 GMT+02:00  :
>  Mensagem Original 
> Ativo 5 de jun de 2018 17:30, David Kastrup < d...@gnu.org> escreveu:
>
> crimsonsunr...@protonmail.com writes:
>
>> Well, I don't have any experience with gdb, so I wouldn't know what to
>> do. The strange thing seems to be that, if the score is engraved using
>> Frescobaldi's verbose output ( which has a separate engrave button ),
>> the error doesn't happen.
>
> That's not unusual for such garbage collection errors: triggering them
> requires a garbage collection occuring at an inopportune point of time
> and the time depends on how much memory is being temporarily used. With
> verbose output, more memory is churned through because of the storage
> the formatting of the verbose output requires, and thus garbage
> collection happens at different points of time than without verbose
> output.
>
> That makes these kind of error annoyingly hard to track down: they
> vanish and reappear with completely unrelated changes in usage and the
> actual error message is triggered at a time far from the problem.
>
> --
> David Kastrup
>
> The most I can do is see if I can upload the files so other people can see
> if the same error happens on other machines.


For running gdb do:

gdb path/to/lilypond-executable

For example: gdb lilypond-git/build/out/bin/lilypond
You will get some infos about gdb returned, finally it ends with
(gdb)

Then type:
run path/to/the/ly-file

Post the output.


Cheers,
  Harm

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

Re: Strange error with no traceable cause.

[crimsonsunrise]

 Mensagem Original 
Ativo 5 de jun de 2018 17:30, David Kastrup escreveu:

crimsonsunr...@protonmail.com writes:

> Well, I don't have any experience with gdb, so I wouldn't know what to
> do. The strange thing seems to be that, if the score is engraved using
> Frescobaldi's verbose output ( which has a separate engrave button ),
> the error doesn't happen.

That's not unusual for such garbage collection errors: triggering them
requires a garbage collection occuring at an inopportune point of time
and the time depends on how much memory is being temporarily used. With
verbose output, more memory is churned through because of the storage
the formatting of the verbose output requires, and thus garbage
collection happens at different points of time than without verbose
output.

That makes these kind of error annoyingly hard to track down: they
vanish and reappear with completely unrelated changes in usage and the
actual error message is triggered at a time far from the problem.

--
David Kastrup

The most I can do is see if I can upload the files so other people can see if 
the same error happens on other machines.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Strange error with no traceable cause.

[David Kastrup]

crimsonsunr...@protonmail.com writes:

> Well, I don't have any experience with gdb, so I wouldn't know what to
> do. The strange thing seems to be that, if the score is engraved using
> Frescobaldi's verbose output ( which has a separate engrave button ),
> the error doesn't happen.

That's not unusual for such garbage collection errors: triggering them
requires a garbage collection occuring at an inopportune point of time
and the time depends on how much memory is being temporarily used.  With
verbose output, more memory is churned through because of the storage
the formatting of the verbose output requires, and thus garbage
collection happens at different points of time than without verbose
output.

That makes these kind of error annoyingly hard to track down: they
vanish and reappear with completely unrelated changes in usage and the
actual error message is triggered at a time far from the problem.

-- 
David Kastrup

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

Re: Strange error with no traceable cause.

[crimsonsunrise]

 Mensagem Original 
Ativo 5 de jun de 2018 16:43, David Kastrup escreveu:

crimsonsunr...@protonmail.com writes:

> ​Sent with ProtonMail Secure Email.​
>
> ‐‐‐ Original Message ‐‐‐
>
> On 5 June 2018 2:33 PM, David Kastrup  wrote:
>
>> crimsonsunr...@protonmail.com writes:
>>
>> > I'm working on a large score using 2.21.0, parts all separated into
>> >
>> > different files and such, suddenly, after adding a bar for the 3rd
>> >
>> > clarinet, this shows up:
>> >
>> > Parsing...
>> >
>> > Interpreting music...[8][16]ERROR: In procedure ly:trampoline:
>> >
>> > ERROR: Wrong type argument in position 3 (expecting Translator):
>> >
>> > #
>> >
>> > I have no idea why this is happening. All the other parts add fine
>> >
>> > but, as soon as the bar is added for that particular instrument, the
>> >
>> > error shows up.
>> >
>> > However, if you engrave with verbose output on Frescobaldi
>> >
>> > enabled...the error doesn't show up. Disable that and do normal
>> >
>> > engraving...Same error.
>> >
>> > Any ideas on what's causing it or it might be a Fescobaldi bug?
>>
>> This is an error in the internals of the memory organization of
>>
>> LilyPond. Which platform are you using this on, and which version of
>>
>> Guile has been compiled into it?
>>
>> Basically the output of
>>
>> ldd `which lilypond`
>>
>> should be sufficient for answering this question if you have no clue
>>
>> what I am talking about.
>>
>>
>> --
>>
>> David Kastrup
>
> Output of ldd `which lilypond`:
>
> linux-vdso.so.1 (0x7ffd29e4c000)
> libdl.so.2 => /usr/lib/libdl.so.2 (0x7f47a901a000)
> libguile.so.17 => /usr/lib/libguile.so.17 (0x7f47a8d1d000)

[...]

64bit Linux, Guile 1.8. That is a combination that really should work.
Any chance to be running this under gdb and/or create a backtrace from a
core dump?

Basically it would be nice to figure out what kind of code this is
happening in in order to figure out what kind of memory became collected
prematurely. The actual bug unfortunately is not really connected with
the code executed at this time: it triggers an indeterminate time before
that and the responsible code is code that someone forgot to write.

But at least knowing what kind of data structure might be affected would
be a kind of clue how to narrow done the missing code.

--
David Kastrup

--

Well, I don't have any experience with gdb, so I wouldn't know what to do. The 
strange thing seems to be that, if the score is engraved using Frescobaldi's 
verbose output ( which has a separate engrave button ), the error doesn't 
happen.

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

Re: Strange error with no traceable cause.

[David Kastrup]

crimsonsunr...@protonmail.com writes:

> ​Sent with ProtonMail Secure Email.​
>
> ‐‐‐ Original Message ‐‐‐
>
> On 5 June 2018 2:33 PM, David Kastrup  wrote:
>
>> crimsonsunr...@protonmail.com writes:
>> 
>> > I'm working on a large score using 2.21.0, parts all separated into
>> > 
>> > different files and such, suddenly, after adding a bar for the 3rd
>> > 
>> > clarinet, this shows up:
>> > 
>> > Parsing...
>> > 
>> > Interpreting music...[8][16]ERROR: In procedure ly:trampoline:
>> > 
>> > ERROR: Wrong type argument in position 3 (expecting Translator):
>> > 
>> > #
>> > 
>> > I have no idea why this is happening. All the other parts add fine
>> > 
>> > but, as soon as the bar is added for that particular instrument, the
>> > 
>> > error shows up.
>> > 
>> > However, if you engrave with verbose output on Frescobaldi
>> > 
>> > enabled...the error doesn't show up. Disable that and do normal
>> > 
>> > engraving...Same error.
>> > 
>> > Any ideas on what's causing it or it might be a Fescobaldi bug?
>> 
>> This is an error in the internals of the memory organization of
>> 
>> LilyPond. Which platform are you using this on, and which version of
>> 
>> Guile has been compiled into it?
>> 
>> Basically the output of
>> 
>> ldd `which lilypond`
>> 
>> should be sufficient for answering this question if you have no clue
>> 
>> what I am talking about.
>> 
>> 
>> --
>> 
>> David Kastrup
>
> Output of ldd `which lilypond`:
>
> linux-vdso.so.1 (0x7ffd29e4c000)
>   libdl.so.2 => /usr/lib/libdl.so.2 (0x7f47a901a000)
>   libguile.so.17 => /usr/lib/libguile.so.17 (0x7f47a8d1d000)

[...]

64bit Linux, Guile 1.8.  That is a combination that really should work.
Any chance to be running this under gdb and/or create a backtrace from a
core dump?

Basically it would be nice to figure out what kind of code this is
happening in in order to figure out what kind of memory became collected
prematurely.  The actual bug unfortunately is not really connected with
the code executed at this time: it triggers an indeterminate time before
that and the responsible code is code that someone forgot to write.

But at least knowing what kind of data structure might be affected would
be a kind of clue how to narrow done the missing code.

-- 
David Kastrup

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

Re: Strange error with no traceable cause.

[crimsonsunrise]

​Sent with ProtonMail Secure Email.​

‐‐‐ Original Message ‐‐‐

On 5 June 2018 2:33 PM, David Kastrup  wrote:

> crimsonsunr...@protonmail.com writes:
> 
> > I'm working on a large score using 2.21.0, parts all separated into
> > 
> > different files and such, suddenly, after adding a bar for the 3rd
> > 
> > clarinet, this shows up:
> > 
> > Parsing...
> > 
> > Interpreting music...[8][16]ERROR: In procedure ly:trampoline:
> > 
> > ERROR: Wrong type argument in position 3 (expecting Translator):
> > 
> > #
> > 
> > I have no idea why this is happening. All the other parts add fine
> > 
> > but, as soon as the bar is added for that particular instrument, the
> > 
> > error shows up.
> > 
> > However, if you engrave with verbose output on Frescobaldi
> > 
> > enabled...the error doesn't show up. Disable that and do normal
> > 
> > engraving...Same error.
> > 
> > Any ideas on what's causing it or it might be a Fescobaldi bug?
> 
> This is an error in the internals of the memory organization of
> 
> LilyPond. Which platform are you using this on, and which version of
> 
> Guile has been compiled into it?
> 
> Basically the output of
> 
> ldd `which lilypond`
> 
> should be sufficient for answering this question if you have no clue
> 
> what I am talking about.
> 
> 
> --
> 
> David Kastrup

Output of ldd `which lilypond`:

linux-vdso.so.1 (0x7ffd29e4c000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x7f47a901a000)
libguile.so.17 => /usr/lib/libguile.so.17 (0x7f47a8d1d000)
libltdl.so.7 => /usr/lib/libltdl.so.7 (0x7f47a8b13000)
libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 
(0x7f47a88ff000)
libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x7f47a86b8000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x7f47a8464000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x7f47a814d000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x7f47a7f0a000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x7f47a7c41000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x7f47a78b8000)
libm.so.6 => /usr/lib/libm.so.6 (0x7f47a7523000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7f47a730b000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x7f47a70ed000)
libc.so.6 => /usr/lib/libc.so.6 (0x7f47a6d31000)
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 
(0x7f47a9932000)
libgmp.so.10 => /usr/lib/libgmp.so.10 (0x7f47a6a9e000)
libcrypt.so.1 => /usr/lib/libcrypt.so.1 (0x7f47a6866000)
libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0x7f47a65b4000)
libthai.so.0 => /usr/lib/libthai.so.0 (0x7f47a63aa000)
libfribidi.so.0 => /usr/lib/libfribidi.so.0 (0x7f47a618e000)
libffi.so.6 => /usr/lib/libffi.so.6 (0x7f47a5f85000)
libpcre.so.1 => /usr/lib/libpcre.so.1 (0x7f47a5d13000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x7f47a5ae1000)
libuuid.so.1 => /usr/lib/libuuid.so.1 (0x7f47a58da000)
libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x7f47a56ca000)
libpng16.so.16 => /usr/lib/libpng16.so.16 (0x7f47a5494000)
libz.so.1 => /usr/lib/libz.so.1 (0x7f47a527d000)
libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0x7f47a5051000)
libdatrie.so.1 => /usr/lib/libdatrie.so.1 (0x7f47a4e49000)

I'm running it on Archlinux x64.

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

Re: Strange error with no traceable cause.

[David Kastrup]

crimsonsunr...@protonmail.com writes:

> I'm working on a large score using 2.21.0, parts all separated into
> different files and such, suddenly, after adding a bar for the 3rd
> clarinet, this shows up:
>
> Parsing...
>
> Interpreting music...[8][16]ERROR: In procedure ly:trampoline:
>
> ERROR: Wrong type argument in position 3 (expecting Translator):
> #
>
> I have no idea why this is happening. All the other parts add fine
> but, as soon as the bar is added for that particular instrument, the
> error shows up.
>
> However, if you engrave with verbose output on Frescobaldi
> enabled...the error doesn't show up. Disable that and do normal
> engraving...Same error.
>
> Any ideas on what's causing it or it might be a Fescobaldi bug?

This is an error in the internals of the memory organization of
LilyPond.  Which platform are you using this on, and which version of
Guile has been compiled into it?

Basically the output of

ldd `which lilypond`

should be sufficient for answering this question if you have no clue
what I am talking about.

-- 
David Kastrup

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

Re: Strange error

[Br. Samuel Springuel]

On 2016-12-18 1:12 PM, David Kastrup wrote:

I beg to differ.  Have you actually tried compiling the result or just
glanced over it?


I just glanced it over and didn't see any changes in the code.  Doing it 
again now that I know what to look for, I do indeed spot the change. 
Guess that's what I get for being in a rush the first time.


--
✝
Br. Samuel, OSB
St. Anselm’s Abbey
Washington, DC
(R. Padraic Springuel)

PAX ☧ ΧΡΙΣΤΟΣ

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

Re: Strange error

[David Kastrup]

"Br. Samuel Springuel"  writes:

> On 2016-12-18 12:24 PM, Malte Meyn wrote:
>> Try an additional \with:
>>
>> \new Staff \with \timeless { c' }
>
> That does indeed work, but isn't that redundant programming?

timeless = \with { }

\new StaffGroup { \new Staff \timeless { c' } }

timeless = { g' }

\new StaffGroup { \new Staff \timeless { c' } }

It was impossible to know just where the \new Staff ended unless you
knew the exact value and type of \timeless.

And \timeless may be a scheme function call rather than a fixed value.

Editors don't have such knowledge, and other utilities don't have that
knowledge.  And LilyPond only has such knowledge in certain situations.
And since timeless may get reassigned, this knowledge may be temporary.

-- 
David Kastrup

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

Re: Strange error

[David Kastrup]

"Br. Samuel Springuel"  writes:

> When I compile the following snippet I get an error under 2.19.53 that
> wasn't there under 2.18.2:
>
> \version "2.19.53"
>
> timeless = \with {
>   \remove "Time_signature_engraver" }
>
> \new Staff \with {
>   \remove "Time_signature_engraver" }
> { c' }
>
> \new Staff \timeless
> { c' }
>
> Running the snippet through convert-ly (after changing the \version
> statement) changes nothing.

I beg to differ.  Have you actually tried compiling the result or just
glanced over it?

-- 
David Kastrup

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

Re: Strange error

[Br. Samuel Springuel]

On 2016-12-18 12:24 PM, Malte Meyn wrote:

Try an additional \with:

\new Staff \with \timeless { c' }


That does indeed work, but isn't that redundant programming?

--
✝
Br. Samuel, OSB
St. Anselm’s Abbey
Washington, DC
(R. Padraic Springuel)

PAX ☧ ΧΡΙΣΤΟΣ

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

Re: Strange error

[Malte Meyn]

Am 18.12.2016 um 18:03 schrieb Br. Samuel Springuel:

When I compile the following snippet I get an error under 2.19.53 that
wasn't there under 2.18.2:

\version "2.19.53"

timeless = \with {
\remove "Time_signature_engraver" }

\new Staff \with {
\remove "Time_signature_engraver" }
{ c' }

\new Staff \timeless
{ c' }


Try an additional \with:

\new Staff \with \timeless { c' }

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

Re: Strange error(?) message when invoking lilypond-book

[David Kastrup]

Speldosa  writes:

> I'm running OS X 10.11 and LilyPond version 2.18.2-1. I'm trying to invoke
> lilypond-book via terminal by typing the following (I've tried getting the
> path option to work, but I've given up after a gazillion tries):
>
> /Applications/LilyPond.app/Contents/Resources/bin/lilypond-book
> Test.lytex
>
> What I'm served with after running this command is the following:
>
> File "/Applications/LilyPond.app/Contents/Resources/bin/lilypond-book",
> line 590
> os.mkdir (global_options.output_dir, 0777)
> ^
> SyntaxError: invalid token
>
> Am I even supposed to see this? Is this a valid error message (in that case,
> it's not making a lot of sense)? I've been able to locate the origin in the
> source code, but that doesn't help me very much.
>
> Anybody got any ideas?

LilyPond does not support Python 3 yet.  Python 3 syntax for octal
numbers is 0o777 instead of 0777.  I would be surprised if this were the
only problem, though, so you better try to change the scripts to use
some Python 2 interpreter.

-- 
David Kastrup

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

Re: Strange error(?) message when invoking lilypond-book

[Speldosa]

Thanks! Running the same terminal code with "python2" at the beginning did
the trick!



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Strange-error-message-when-invoking-lilypond-book-tp183876p183884.html
Sent from the User mailing list archive at Nabble.com.

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

Re: strange error message - cannot open .ly file

[Thomas Scharkowski]

 Original-Nachricht 

\version "2.19.29"
\language "italiano"
\header {  title = "禱願"  subtitle = "Prayer Willing"  poet = "雨打芭蕉"  % Remove 
default LilyPond tagline  tagline = ##f}
\paper {  #(set-paper-size "letter")}
\layout {  \context {\Voice\consists "Melody_engraver"\override 
Stem #'neutral-direction = #'()  }}
global = {  \key do \major  \numericTimeSignature  \time 2/4  \tempo 4=100}
chordNames = \chordmode {  \global  % Chords follow here.  }
melody = \relative do'' {  \global  mi''4. re8 |%m01  do8. re16 sol16 |%m02  }
verse = \lyricmode {  % Lyrics follow here.  }
\score {  <<\new ChordNames \chordNames\new Staff { \melody }\addlyrics { 
\verse }  >>  \layout { }  \midi { }}


Hi,

in the example you provided some curly braces are commented out.
HTH

Thomas

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

Re: strange error message - cannot open .ly file

[Simon Albrecht]

Hi Ming,

On 30.10.2015 01:01, MING TSANG wrote:

Hi lilyponders:

Frecobaldi can open the file, yet when I hit to run lilypond, I got 
strange error message:


I can’t confirm that either: I get two failed barchecks, but else it 
compiles fine. It would seem odd that Lily didn’t recognise the version 
statement when there is one. Can you check again, and in case it doesn’t 
work still, follow ?


Thanks, Simon



Starting lilypond-windows.exe 2.19.29 [06_prayer-willing_禱願.ly]...
Processing `K://06_prayer-willing_�/�.ly'
Parsing...
warning: cannot open file: `K://06_prayer-willing_�/�.ly'
K:/粤曲 /06_prayer-willing_?願.ly:1 
: warning: no \version statement 
found, please add

\version "2.19.29"
for future compatibility
Success: compilation successfully completed
Completed successfully in 0.7".


The lily file ..
\version "2.19.29"

\language "italiano"

\header {
  title = "禱願"
  subtitle = "Prayer Willing"
  poet = "雨打芭蕉"
  % Remove default LilyPond tagline
  tagline = ##f
}

\paper {
#(set-paper-size "letter")
}

\layout {
  \context {
\Voice
\consists "Melody_engraver"
\override Stem #'neutral-direction = #'()
  }
}

global = {
  \key do \major
\numericTimeSignature
  \time 2/4
  \tempo 4=100
}

chordNames = \chordmode {
  \global
  % Chords follow here.
}

melody = \relative do'' {
  \global
  mi''4. re8 |%m01
  do8. re16 sol16 |%m02
}

verse = \lyricmode {
  % Lyrics follow here.
}

\score {
  <<
\new ChordNames \chordNames
\new Staff { \melody }
\addlyrics { \verse }
  >>
  \layout { }
  \midi { }
}



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



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

Re: strange error message - cannot open .ly file

[MING TSANG]

Thank you David,simon, Jacques & Thomas:
Turn out it was the file name that cause the problem.As suggest by David, 1..  
I rename the .ly file not using any utf-8 code and it complies fine.2..  I 
change the first utf-8 character  "禱" to another "主" and the file complies fine 
as well3.. the file name with utf-8 "禱" when comply generate the strange error 
-- no version statement found.
Question:  can be be resolved? Or nothing we can do?
Immanuel,ming. 
  From: David Wright <lily...@lionunicorn.co.uk>
 To: MING TSANG <tsan...@rogers.com> 
Cc: Lilypond-user Mailinglist <lilypond-user@gnu.org> 
 Sent: Friday, October 30, 2015 9:38 AM
 Subject: Re: strange error message - cannot open .ly file
   
On Fri 30 Oct 2015 at 00:01:44 (+), MING TSANG wrote:
> Hi lilyponders:

Hi, please post text, not HTML, and if you can't avoid that, please
post source code etc as attachments rather than inline.



> Frecobaldi can open the file, yet when I hit to run lilypond, I got strange
> error message:
> 
> Starting lilypond-windows.exe 2.19.29 [06_prayer-willing_禱願.ly]...
> Processing `K://06_prayer-willing_�/�.ly'
> Parsing...
> warning: cannot open file: `K://06_prayer-willing_�/�.ly'
> K:/粤曲/06_prayer-willing_?願.ly:1: warning: no \version statement found,
> please add
> \version "2.19.29"
> for future compatibility
> Success: compilation successfully completed
> Completed successfully in 0.7".

Well I can't see any evidence that LP compiled anything: nothing of
any substance occurs before the "Success" line.

So it looks as if your filenames are defeating either the operating
system or the application that you're using. It might be worth using
filenames containing only ASCII characters to see if the problem
goes away. Using Unicode *within* the source should be OK: I get some
likely-looking glyphs when I compile your source in 2.18.2.

Cheers,
David.


  \version "2.19.30"

\language "italiano"

\header {
  title = "禱願"
  subtitle = "Prayer Willing"
  poet = "雨打芭蕉"
  % Remove default LilyPond tagline
  tagline = ##f
}

\paper {
  #(set-paper-size "letter")
}

\layout {
  \context {
\Voice
\consists "Melody_engraver"
\override Stem #'neutral-direction = #'()
  }
}

global = {
  \key do \major
  \numericTimeSignature
  \time 2/4
  \tempo 4=100
}

chordNames = \chordmode {
  \global
  % Chords follow here.
  
}

melody =   {
  \global
  mi''4. re''8 |%m01
  do''8 re''16 sol''16 mi''16 re''16 mi''16 sol''  |%m02
  
}

verse = \lyricmode {
  % Lyrics follow here.
  
}

\score {
  <<
\new ChordNames \chordNames
\new Staff { \melody }
\addlyrics { \verse }
  >>
  \layout { }
  \midi { }
}
\version "2.19.30"

\language "italiano"

\header {
  title = "禱願"
  subtitle = "Prayer Willing"
  poet = "雨打芭蕉"
  % Remove default LilyPond tagline
  tagline = ##f
}

\paper {
  #(set-paper-size "letter")
}

\layout {
  \context {
\Voice
\consists "Melody_engraver"
\override Stem #'neutral-direction = #'()
  }
}

global = {
  \key do \major
  \numericTimeSignature
  \time 2/4
  \tempo 4=100
}

chordNames = \chordmode {
  \global
  % Chords follow here.
  
}

melody =   {
  \global
  mi''4. re''8 |%m01
  do''8 re''16 sol''16 mi''16 re''16 mi''16 sol''  |%m02
  
}

verse = \lyricmode {
  % Lyrics follow here.
  
}

\score {
  <<
\new ChordNames \chordNames
\new Staff { \melody }
\addlyrics { \verse }
  >>
  \layout { }
  \midi { }
}
\version "2.19.30"

\language "italiano"

\header {
  title = "禱願"
  subtitle = "Prayer Willing"
  poet = "雨打芭蕉"
  % Remove default LilyPond tagline
  tagline = ##f
}

\paper {
  #(set-paper-size "letter")
}

\layout {
  \context {
\Voice
\consists "Melody_engraver"
\override Stem #'neutral-direction = #'()
  }
}

global = {
  \key do \major
  \numericTimeSignature
  \time 2/4
  \tempo 4=100
}

chordNames = \chordmode {
  \global
  % Chords follow here.
  
}

melody =   {
  \global
  mi''4. re''8 |%m01
  do''8 re''16 sol''16 mi''16 re''16 mi''16 sol''  |%m02
  
}

verse = \lyricmode {
  % Lyrics follow here.
  
}

\score {
  <<
\new ChordNames \chordNames
\new Staff { \melody }
\addlyrics { \verse }
  >>
  \layout { }
  \midi { }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: strange error message - cannot open .ly file

[David Wright]

On Fri 30 Oct 2015 at 00:01:44 (+), MING TSANG wrote:
> Hi lilyponders:

Hi, please post text, not HTML, and if you can't avoid that, please
post source code etc as attachments rather than inline.

> Frecobaldi can open the file, yet when I hit to run lilypond, I got strange
> error message:
> 
> Starting lilypond-windows.exe 2.19.29 [06_prayer-willing_禱願.ly]...
> Processing `K://06_prayer-willing_�/�.ly'
> Parsing...
> warning: cannot open file: `K://06_prayer-willing_�/�.ly'
> K:/粤曲/06_prayer-willing_?願.ly:1: warning: no \version statement found,
> please add
> \version "2.19.29"
> for future compatibility
> Success: compilation successfully completed
> Completed successfully in 0.7".

Well I can't see any evidence that LP compiled anything: nothing of
any substance occurs before the "Success" line.

So it looks as if your filenames are defeating either the operating
system or the application that you're using. It might be worth using
filenames containing only ASCII characters to see if the problem
goes away. Using Unicode *within* the source should be OK: I get some
likely-looking glyphs when I compile your source in 2.18.2.

Cheers,
David.

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

Re: strange error message - cannot open .ly file

[lily...@lionunicorn.co.uk]

On Fri 30 Oct 2015 at 14:03:30 (+), MING TSANG wrote:
> Thank you David,simon, Jacques & Thomas:
> 
> Turn out it was the file name that cause the problem.
> As suggest by David, 
> 1..  I rename the .ly file not using any utf-8 code and it complies fine.
> 2..  I change the first utf-8 character  "禱" to another "主" and the file
> complies fine as well
> 3.. the file name with utf-8 "禱" when comply generate the strange error -- no
> version statement found.
> 
> Question:  can be be resolved? Or nothing we can do?

AFAICT the newer versions of frescobaldi, eg 2.18.1 in Debian's
stretch, use python3, and that should handle UTF8 natively. The older
version in Debian's stable (jessie) is 2.0.13 which uses python2, and
so UTF has to be handled with extra code (easy, but necessary).
But it's odd that particular characters should troublesome but not
others.

LilyPond itself probably cares little about the filename it's given
because all it has to do with it is reflect it on the console.
I've tested the jessie version (2.18.2) with filenames consisting
of SPACE, NBSP, strings like ¶‱™ ⇈☂✂♠♫ (which has a NBSP in the
middle) and also your title and poet thus:

lilypond 雨打芭蕉xxx禱願
lilypond 禱願xxx雨打芭蕉

I don't know what platform you're running this on. If it's MS, it
could be their use of UTF16 that's causing a problem.

Attached are the files for a run based on your troublesome character
(if I captured the correct one):

禱   source file
lilyerr  console output
lilyout  output from displayLilyMusic
禱.pdf   output file

Because my xterms have limited fonts available, there's also a
screenshot of these files altogether in emacs.

Cheers,
David.
\version "2.18.2"
\header { tagline = ##f }
filename = \markup { "禱" }
notes = \relative {
  f4. f8 f4 f2. |
  d4. d8 d4 d2. |
  f4. f8 f4 f2. |
  d4. d8~ d d~ d4 d2 |
  f4. f8 f4 f2. |
  d4. d8 d4 d2. |
  c4. c8~ c c~ c c~ c4 c4 |
  f1 r2 _\filename
}
\score {
  {
\clef bass
\key f \major
\time 3/2
\notes
\void \displayLilyMusic { a ^\filename }
  }
  \layout { }
  \midi { \tempo 2=84 }
}
GNU LilyPond 2.18.2
Processing `禱'
Parsing...
Interpreting music...[8]
Preprocessing graphical objects...
Interpreting music...
MIDI output to `禱.midi'...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `禱.ps'...
Converting to `./禱.pdf'...
Success: compilation successfully completed

{ a2^\markup \line { "禱"} }


pdfsPaRzD83Pa.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: strange error message - cannot open .ly file

[Michael Gerdau]

> Turn out it was the file name that cause the problem.As suggest by
> David, 1..  I rename the .ly file not using any utf-8 code and it
> complies fine.2..  I change the first utf-8 character  "禱" to another "主"
> and the file complies fine as well3.. the file name with utf-8 "禱" when
> comply generate the strange error -- no version statement found.
> Question:  can be be resolved? Or nothing we can do?

From your description it seems to be a frescobaldi problem.

What happens if you try to compile the LP source on the cmdline ?

Kind regards,
Michael
-- 
 Michael Gerdau   email: m...@qata.de
 GPG-keys available on request or at public keyserver

signature.asc
Description: This is a digitally signed message part.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: strange error message - cannot open .ly file

[Jacques Menu]

Hello Ming,

Your example runs fine with 2.19.30.

JM

> Le 30 oct. 2015 à 10:07, Thomas Scharkowski  a 
> écrit :
> 
>  Original-Nachricht 
>> \version "2.19.29"
>> \language "italiano"
>> \header {  title = "禱願"  subtitle = "Prayer Willing"  poet = "雨打芭蕉"  % 
>> Remove default LilyPond tagline  tagline = ##f}
>> \paper {  #(set-paper-size "letter")}
>> \layout {  \context {\Voice\consists "Melody_engraver"\override 
>> Stem #'neutral-direction = #'()  }}
>> global = {  \key do \major  \numericTimeSignature  \time 2/4  \tempo 4=100}
>> chordNames = \chordmode {  \global  % Chords follow here.  }
>> melody = \relative do'' {  \global  mi''4. re8 |%m01  do8. re16 sol16 |%m02  
>> }
>> verse = \lyricmode {  % Lyrics follow here.  }
>> \score {  <<\new ChordNames \chordNames\new Staff { \melody }
>> \addlyrics { \verse }  >>  \layout { }  \midi { }}
> 
> Hi,
> 
> in the example you provided some curly braces are commented out.
> HTH
> 
> Thomas
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


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

Re: strange error message - cannot open .ly file

[Michael Gerdau]

> Turn out it was the file name that cause the problem.As suggest by
> David, 1..  I rename the .ly file not using any utf-8 code and it
> complies fine.2..  I change the first utf-8 character  "禱" to another "主"
> and the file complies fine as well3.. the file name with utf-8 "禱" when
> comply generate the strange error -- no version statement found.
> Question:  can be be resolved? Or nothing we can do?

FWIW I can compile all 3 files you attached to your last email on
my Linux system using the current stable frescobaldi and LP 2.19.30

Kind regards,
Michael
-- 
 Michael Gerdau   email: m...@qata.de
 GPG-keys available on request or at public keyserver

signature.asc
Description: This is a digitally signed message part.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: strange error after reducing music rhythm by an half

[Marc Hohl]

Am 27.12.2012 22:31, schrieb Federico Bruni:

Hi

while transcribing a piece of music, I realized that it may work 
better if written with a different rhythm, so I used the Frescobaldi 
option which reduces the rhythms by an half. Then I removed all the 
bar checks.


But I cannot compile this modified file and I don't have a clue of the 
reason why. Below you find the verbose output and the error message. 
Is it enough to figure out what the error can be?


[...]
 313: 29* [ly:pitch-tones ...
 313: 30* [list-ref (#Pitch e'  #Pitch b  #Pitch g  ...) {7}]

translation-functions.scm: In procedure list-ref in expression 
(list-ref tuning (1- string)):

translation-functions.scm: Argument 2 out of range: 7
It looks as if lilypond finds a call for a seventh string on your 
(probably) six-string guitar
tablature. Perhaps frescobaldi tried to convert a string number into a 
reduced rhythm?

Or you removed some character while removing the bar checks?

I had a similar error message long time ago, and it took me about half 
an hour until I found
out that I did some guitar trickery being tested on a four-string-bass 
tablature, but this does

not seem to be the case here.

HTH a bit,

Marc


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




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

Re: strange error after reducing music rhythm by an half

[Federico Bruni]

Il 27/12/2012 22:40, Marc Hohl ha scritto:

 313: 29* [ly:pitch-tones ...
 313: 30* [list-ref (#Pitch e'  #Pitch b  #Pitch g  ...) {7}]

translation-functions.scm: In procedure list-ref in expression
(list-ref tuning (1- string)):
translation-functions.scm: Argument 2 out of range: 7

It looks as if lilypond finds a call for a seventh string on your
(probably) six-string guitar
tablature. Perhaps frescobaldi tried to convert a string number into a
reduced rhythm?


Yes, exactly: if the note has no duration or it's not included inside 
, Fresco converts it: for example g\4 was turned into g\8

I'll tell Wilbert to take \ into account

Thanks!
--
Federico

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

RE: Strange error in compiling 2.13.0

[Nick Payne]

I got the same warning message, see
http://www.nabble.com/New-warning-msg-2.13-td22658865.html.

 

I didn't get any response on it. I went back to using 2.12.2.

 

Nick

 

From: lilypond-user-bounces+nick.payne=internode.on@gnu.org
[mailto:lilypond-user-bounces+nick.payne=internode.on@gnu.org] On Behalf
Of Father Gordon Gilbert
Sent: Friday, 3 April 2009 07:43
To: lilypond-user@gnu.org
Subject: Strange error in compiling 2.13.0

 

Hi all,

I am coming across a strange error when I compile a file on my Windoze box
with 2.13.0, using jEdit 4.3pre16.  My compile looks like this:


LilyPond ready.
%lilypond %args C:\Documents and Settings\Fr Gorden
Gilbert\Desktop\LilyPond Files\TurnYourEyesUponJesusChords.ly
Processing `C:/Documents and Settings/Fr Gorden Gilbert/Desktop/LilyPond
Files/TurnYourEyesUponJesusChords.ly'
Parsing...
Interpreting music... [8][16][24][32]
Preprocessing graphical objects...
(lilypond.exe:300): GLib-WARNING **: Passing a non-NULL package to
g_win32_get_package_installation_directory() is deprecated and it is
ignored.
Interpreting music... 
MIDI output to `TurnYourEyesUponJesusChords.mid'...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `TurnYourEyesUponJesusChords.ps'...
Converting to `./TurnYourEyesUponJesusChords.pdf'...
Processing time: 29 seconds

Does anybody have any idea what that GLib-WARNING **: Passing ... etc means?
It doesn't seem to affect the time or quality of the compile, but it's
curious.  If *I* should ignore it, that's fine, but I was just wondering ...

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: strange error message with tuplet

[M Watts]

Stefan Thomas wrote:

Dear lilypond-users,
when compiling one of my scores I get the following error message,
which I don't understand:

musik/musik_ab115.ly:63:16: warning: No tuplet to end
 s8\fp\  s\f\
\times 4/6 { s32*5\p\ s 32\!}  \pedtrem  s4...\ff
\startTextSpan s32 \stopTextSpan  }%lautleise 115-118
Why  there is no no tuplet to end?


Not sure what that's about -- with 2.12.2, running your line as a 
minimal example produces warnings that the crescendi are too short, but 
that's all.


Using visible notes, not spacer notes, produces  error-free output here:

c4\fp\  c\f\ \times 4/6 { c32*5\p\ c32\!} c4...\ff



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: strange error -beam and tremolo

[Trevor Daniels]

Seems to work ok in the latest development version, 2.11.52, so
I guess you're using an earlier version.  The development
version is now at least as stable as 2.10, so it might be worth
upgrading, although you will need to run convert-ly on your files.

Trevor

- Original Message - 
From: Mehmet Okonsar [EMAIL PROTECTED]

To: Lilypond Users Group lilypond-user@gnu.org
Sent: Tuesday, July 22, 2008 10:44 AM
Subject: strange error -beam and tremolo



the following gives a trange error:

{r8[ c'8:32]}

Preprocessing graphical objects...ERROR: Wrong type (expecting real 
number):

#unknown-type (0x170227 . 0x74616c75636c6163) @ 0x7fc8e91def00

I want to have a beam starting on a rest and a tremolo on the note..

Esenlikler! Best regards!
Mehmet Okonsar
pianist, composer, conductor
==
www.okonsar.com
==
Bugunku ozdeyisiniz:
Your fortune for today is:
==
Surprise due today.  Also the rent.


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user





___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: strange error when creating context

[Werner LEMBERG]

 Now the strange warning comes, saying it can't create the
 CHordMarks context.

This comes from the MIDI processing (and admittedly, there is no
indication for that in the warning message).  You can ignore it
safely.


Werner



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: strange error causes Lilypond refuse to compile

[Graham Percival]

(for your other email)
I would attempt to isolate and fix these problems before playing
with virtual memory.


I must admit that the error message looks like a problem with
memory allocation, but I think the solution to this lies in either
your tweaks, or in a bug with 2.11.49.  Unfortunately, tracking
down the cause will likely not be easy.

I took a quick look at your files, and I couldn't see anything
obviously wrong -- you've done a good job of separating your
tweaks from your music definition.  I can think of a few
possibilities:
- lilypond has trouble with your tweaks (I'm testing
  MarkLine right now, but commenting that out doesn't stop the
  problems)
- lilypond has trouble dealing with large paper sizes.  (nope, not
  this; commenting out the paper line doesn't fix it)
- maybe it's the number of StaffGroup nestings?  What happens if
  you comment out a bunch of lines in your -score file and have
everything inside a single GrandStaff or StaffGroup?
- maybe one or your tweaks happens to require a lot of CPU power
  to calculate?  What if you remove all your tweaks?  (ie in your
defs, change all the definitions to be
  blah = {
%
%
%
}

- if you try compiling your score with certain instruments removed
  (ie comment out all the winds, then percussion, then strings,
etc), does the problem go away?


Sorry I can't help more; I've tried a few things without any
change, but I can't spend more time on it.
- Graham

On Sun, 22 Jun 2008 14:03:13 +0800 (CST)
hhpmusic [EMAIL PROTECTED] wrote:

 Hello,
   I'm again trapped in my symphony for the earthquake. I finished the
 introduction and now come to the first theme. Before writing the
 first theme, the score was compiled well. But now, only after 8 bars,
 the score can't be compiled any more. The log file shows the
 following strange error: Parsing...terminate called after throwing an
 instance of 'std::bad_alloc' what():  St9bad_alloc Then a warning
 window comes up, but my screen reader can't read it. What's wrong
 with my score? Is the problem only because of my machine? Sincerely
 Haipeng 
  


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: strange error

[Graham Percival]

I'm 95% certain that you missed a } or  somewhere, but I don't
have the time to analyze your file to see where it is.

HTH,
- Graham

On Sat, 1 Mar 2008 09:39:43 +0800 (CST)
hhpmusic [EMAIL PROTECTED] wrote:

 Hi, I'm coping the opening of my violin concerto (just an experiment
 to try braille music software in 2006). The log file gives an error
 of init.ly, which I can't deal with. I checked my input file, and
 can't make sure everything is right. Could you please tell me what
 the error means?
 
 Haipeng
 
  


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: strange error

[Ledocq-Boccart]

Hi,

Just a suggestion...
If not yet the case, using jedit as code editor could maybe make it 
easier for checking missing { or } (pairs of linked brackets are 
highlighted when mouse cursor is positionned just after the character).

http://www.jedit.org
Also check separately each instrument score lines using %  in front of 
line code;

or for several lines %{ line code to isolate
line code to isolate
...
line code to isolate
%}

Have a look in manual under

http://lilypond.org/doc/v2.10/Documentation/user/lilypond-big-page#Working-on-text-files

success!

Charlie



Graham Percival a écrit :

I'm 95% certain that you missed a } or  somewhere, but I don't
have the time to analyze your file to see where it is.

HTH,
- Graham

On Sat, 1 Mar 2008 09:39:43 +0800 (CST)
hhpmusic [EMAIL PROTECTED] wrote:

  

Hi, I'm coping the opening of my violin concerto (just an experiment
to try braille music software in 2006). The log file gives an error
of init.ly, which I can't deal with. I checked my input file, and
can't make sure everything is right. Could you please tell me what
the error means?

Haipeng

 




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user



  



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

RE: strange error

[Trevor Daniels]

Hi Haipeng

Line 20 - missing  before Andante.  Should be:
  toptextA = \markup { \bold \italic Andante }
This is the mistake which causes the error in init.ly.

There are a couple of other minor errors:

Line 39 - incorrect string ae\!.  Maybe should be:
\repeat tremolo 16 { f\ ees } \repeat tremolo 4 { f ees } \times 4/6
{ f16 ees f ees f aes\! } |

Line 72 definition should be bassoons, not bassoon.

The file then compiles, but there are still several warnings about bar
checks and unterminated crescendos, which you can probably fix easily
yourself.

Trevor D
  -Original Message-
  From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
hhpmusic
  Sent: 01 March 2008 01:40
  To: lilypond-user
  Subject: strange error


  Hi, I'm coping the opening of my violin concerto (just an experiment to
try braille music software in 2006). The log file gives an error of init.ly,
which I can't deal with. I checked my input file, and can't make sure
everything is right. Could you please tell me what the error means?

  Haipeng







--
  已 经 超 过 100 万 台 电 脑 安 装 了 网 易 有 道 免 费 英 汉 词 典 ， 点
击 此 处 可 以 快 速 下 载
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: strange error in converted file

[Arvid Grøtting]

Arvid Grøtting [EMAIL PROTECTED] writes:

 I've run across a strange error in a file converted from 1.6.9 to
 2.2.1.

Never mind; it was in a context redefinition (to get midi from voice
contexts) that I don't need right now.

-- 

Arvid



___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user