Re: lilypond errors on a guitar minor sixth chord
2017-04-15 2:36 GMT+02:00 Stan Mulder :
> Thomas,
>
> Got it. I used your first solution with the addendum. If at some point in
> the future I need more chords, I will construct a more extensive file for
> guitar chords. I did construct a fingering file for plectrum banjo a while
> back. It's got 25 chords for each of 12 keys, but I don't have any
> inversions.
>
> Thanks for the clarification on the reply-all. I wasn't sure what to do. Is
> there some place on the web were I can see other discussions?
>
> Stan
>
> On 04/14/2017 06:25 AM, Thomas Morley wrote:
>>
>> 2017-04-14 5:18 GMT+02:00 Stan Mulder :
>>>
>>>
>>> (1)
>>> Define it yourself, search the NR for 'storePredefinedDiagram'. Leading
>>> to:
>>>
>>> \version "2.19.56"
>>>
>>> \language "english"
>>>
>>> \storePredefinedDiagram #default-fret-table \chordmode {e-flat:m6}
>>> #guitar-tuning
>>> #"x;x;1-1-(;3-3;1-1-);3-3;"
>>>
>>> \include "predefined-guitar-fretboards.ly"
>>>
>>> \new FretBoards \chordmode { e-flat:m6 }
>>>
>>>
>> %% That should rather be:
>> #"x;x;1-1-(;3-3;1-1-);3-4;"
>
>
Aaargh, this fret-diagram shows a major-chord.
I shouldn't post anything being overtired ...
Try:
\language "english"
\storePredefinedDiagram #default-fret-table \chordmode {e-flat:m6}
#guitar-tuning
#"x;x;1-1-(;3-3;1-1-);2-2;"
\include "predefined-guitar-fretboards.ly"
<<
\new FretBoards \chordmode { e-flat:m6 }
\new Staff \chordmode { e-flat:m6 }
>>
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond errors on a guitar minor sixth chord
Am 15.04.2017 um 02:36 schrieb Stan Mulder: > Thanks for the clarification on the reply-all. I wasn't sure what to do. > Is there some place on the web were I can see other discussions? There are several archives, f. e. http://lists.gnu.org/archive/html/lilypond-user/ (this is the mailing lists’ own archive on gnu.org) http://lilypond.1069038.n5.nabble.com/ http://www.mail-archive.com/lilypond-user@gnu.org/ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond errors on a guitar minor sixth chord
Thomas,
Got it. I used your first solution with the addendum. If at some point
in the future I need more chords, I will construct a more extensive file
for guitar chords. I did construct a fingering file for plectrum banjo a
while back. It's got 25 chords for each of 12 keys, but I don't have any
inversions.
Thanks for the clarification on the reply-all. I wasn't sure what to do.
Is there some place on the web were I can see other discussions?
Stan
On 04/14/2017 06:25 AM, Thomas Morley wrote:
2017-04-14 5:18 GMT+02:00 Stan Mulder :
(1)
Define it yourself, search the NR for 'storePredefinedDiagram'. Leading to:
\version "2.19.56"
\language "english"
\storePredefinedDiagram #default-fret-table \chordmode {e-flat:m6}
#guitar-tuning
#"x;x;1-1-(;3-3;1-1-);3-3;"
\include "predefined-guitar-fretboards.ly"
\new FretBoards \chordmode { e-flat:m6 }
%% That should rather be:
#"x;x;1-1-(;3-3;1-1-);3-4;"
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond errors on a guitar minor sixth chord
2017-04-14 12:25 GMT+02:00 Thomas Morley :
> Sollution(s):
>
> (1)
> Define it yourself, search the NR for 'storePredefinedDiagram'. Leading to:
>
> \version "2.19.56"
>
> \language "english"
>
> \storePredefinedDiagram #default-fret-table \chordmode {e-flat:m6}
> #guitar-tuning
> #"x;x;1-1-(;3-3;1-1-);3-3;"
%% That should rather be:
#"x;x;1-1-(;3-3;1-1-);3-4;"
>
> \include "predefined-guitar-fretboards.ly"
>
> \new FretBoards \chordmode { e-flat:m6 }
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond errors on a guitar minor sixth chord
2017-04-14 5:18 GMT+02:00 Stan Mulder :
>
> Thomas,
>
> Here's your example, but with fretboards added. The error is there.
> Apparently it has to do with fretboards. Also, I am running 2.19.59:
>
> \version "2.19.56"
> \language "english"
> \include "predefined-guitar-fretboards.ly"
>
> m = \chordmode {
> \override FretBoard.fret-diagram-details.dot-radius = #0.4
> \override FretBoard.fret-diagram-details.number-type = #'arabic
> b-flat4 bf/f g4:dim/e e-flat:m6
> }
> <<
> \new ChordNames \m
> \new FretBoards \m
> \new Staff { \accidentalStyle forget \m }
> >>
>
> Error:
[...]
Hi Stan,
please always reply to all, unless real private topics are discussed.
I now get the _warning_ myself.
So this is a good show-case about minimals. Obviously your
code-example should have pointed to FretBoards:
\version "2.19.59"
\language "english"
\include "predefined-guitar-fretboards.ly"
\new FretBoards \chordmode { e-flat:m6 }
Would have done it.
That said,
Some basics:
Lilypond creates FretBoards (without predefined-guitar-fretboards.ly)
by looking at the actual chord-pitches.
Which are < ef' gf' bf' c'' > in this case. Here LilyPond thinks it's
not doable and indeed it would be very hard to do something like:
\new FretBoards { < ef'\4-4 gf'\3-2 bf'\2-3 c''\1-1 > }
If predefined-guitar-fretboards.ly is included, LilyPond looks there
whether a fret-diagram-definition for the chord is stored there.
If found it's taken otherwise lily falls back to look at the actual
chord-pitches.
In predefined-guitar-fretboards.ly are definitions stored for all
chords of type:
major, minor, 7, m7, dim, aug, maj7, dim7, 9
Thus Lilypond does not find m6-chords, falls back to the pitches,
can't find a sensible fret-diagram, prints what's possible and finally
emitts the warning about the missing part(s).
Sollution(s):
(1)
Define it yourself, search the NR for 'storePredefinedDiagram'. Leading to:
\version "2.19.56"
\language "english"
\storePredefinedDiagram #default-fret-table \chordmode {e-flat:m6}
#guitar-tuning
#"x;x;1-1-(;3-3;1-1-);3-3;"
\include "predefined-guitar-fretboards.ly"
\new FretBoards \chordmode { e-flat:m6 }
(2)
Look at
http://lists.gnu.org/archive/html/lilypond-user/2017-02/msg00500.html
and follow the link to Philomenos
Although I have to admit I never tried it myself.
(3)
Extend predefined-guitar-fretboards.ly
That would mean to create a patch for the missing chords.
Though I'm not sure to which amount such a patch would be accepted.
Currently only the "most common" chords are stored there. Ofcourse
it's debattable which chords are "most common"...
And if we extend the file, what comes in what not?
11, 13, b5, inversions, added bass-pitches, etc etc
The Philomenos-files obviously try to cover most possible, so their
files are of huge size ...
I'd say too huge to ship them with default LilyPond.
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond errors on a guitar minor sixth chord
2017-04-13 19:57 GMT+02:00 Stan Mulder :
> I would seem that lilypond doesn't like minor sixth chords. All my guitar
> fretboards seem to be fine, but I get errors on all chords with a minor
> sixth. Here's some of the code:
>
> b-flat4 bf/f g4:dim/e e-flat:m6
>
> Here's the corresponding error complaining about the "m6"
>
> warning: No string for pitch # (given frets (11 11 8))
>
> b-flat4 bf/f g4:dim/e
>
> e-flat:m6
>
> [8][16][24]
>
> If i remove the sixth and just make it an "e-flat:m", there's no error.
>
> I thought a minor sixth was pretty standard. Or am I misinterpreting the
> error?
>
> I have \include "predefined-guitar-fretboards.ly" at the top of the file...
>
> I'm using \version "2.19.49"
>
> Stan
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
Can't confirm.
Compiling:
\version "2.19.56"
\language "english"
\include "predefined-guitar-fretboards.ly"
m = \chordmode { b-flat4 bf/f g4:dim/e e-flat:m6 }
<<
\new ChordNames \m
\new Staff { \accidentalStyle forget \m }
>>
gives a clean run, no warnings/errors and the attached (cropped) image.
The problem must be somewhere else.
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
lilypond errors on a guitar minor sixth chord
I would seem that lilypond doesn't like minor sixth chords. All my guitar fretboards seem to be fine, but I get errors on all chords with a minor sixth. Here's some of the code: b-flat4 bf/f g4:dim/e e-flat:m6 Here's the corresponding error complaining about the "m6" warning: No string for pitch # (given frets (11 11 8)) b-flat4 bf/f g4:dim/e e-flat:m6 [8][16][24] If i remove the sixth and just make it an "e-flat:m", there's no error. I thought a minor sixth was pretty standard. Or am I misinterpreting the error? I have \include "predefined-guitar-fretboards.ly" at the top of the file... I'm using \version "2.19.49" Stan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: strange lilypond errors in 2.15.24
Hi Saul,
2012/1/12 Saul Tobin :
> I think you commented something like that on an earlier thread. It was a very
> helpful approach, so thank you for the suggestion. I've done precisely that
> with this problem, but, as I described in the original post and my most recent
> reply, each section of the code compiles fine by itself.
>
> Saul
>
> On Wednesday, January 11, 2012 10:38:41 AM you wrote:
>> - Original Message -
>> From: "Shevek"
>> To:
>> Sent: Wednesday, January 11, 2012 6:20 PM
>> Subject: Re: strange lilypond errors in 2.15.24
>>
>> > Francisco Vila wrote:
>> >> With the typos corrected and some content inside braces I obtain no
>> >> errors or warnings.
>> >
>> > The example also compiles fine for me. As I noted in my original post,
>> > that
>> > is one of the odd things about the error I'm getting. The line I marked
>> > causes a crash in the context of my project, but when I made a simple
>> > example, it gives me no problems. Similarly, in the other project, I
>> > can't trace the crash to any specific lines of code.
>>
>> The way I approach issues like this is to take out half the notes and check
>> to see whether it can compile, and continue to do this until it will. The
>> problem must lie in the bit just removed. It can be laborious, but I've
>> personally always found errors in my code.
>>
>> --
>> Phil Holmes
sometimes it is _very_ difficult to debug a large file. :(
If the way Phil (and others) suggested shows no result, you can try to
make something like a "dummy-file". I.e. delete all music, overrides
etc and introduce first a simple line of music, with \repeat unfold
... into the most simplified score-set-up.
Second: add successive the needed commands to the score-setup.
Third: replace one by one the \repeat unfold music with the original
etc
In the attached file I made a 20-staff-score. Then I tested to add
lyrics and chords to each staff. Third I added alignBelowContext and
alignAboveContext to chords respectively lyrics.
If you compile it, you get a 100-pages-pdf without problems, at least
with "2.15.20"
The only other way would be to post the entire file hoping someone
with much leisure time can help you.
HTH,
Harm
\version "2.15.20"
#(set-global-staff-size 10)
m = \new Voice = "mel" \relative c' {
\repeat unfold 100 { c1 \break }
}
lyr = \lyricmode { \repeat unfold 100 { bla } }
chrds = \chords {
\repeat unfold 100 c
}
\score {
\new StaffGroup <<
<<
\new Staff = "staff" \m
\context ChordNames \with { alignBelowContext = #"staff" } \chrds
\new Lyrics\with { alignAboveContext = #"staff" } \lyricsto "mel" \lyr
>>
<<
\new Staff = "staff" \m
\context ChordNames \with { alignBelowContext = #"staff" } \chrds
\new Lyrics\with { alignAboveContext = #"staff" } \lyricsto "mel" \lyr
>>
<<
\new Staff = "staff" \m
\context ChordNames \with { alignBelowContext = #"staff" } \chrds
\new Lyrics\with { alignAboveContext = #"staff" } \lyricsto "mel" \lyr
>>
<<
\new Staff = "staff" \m
\context ChordNames \with { alignBelowContext = #"staff" } \chrds
\new Lyrics\with { alignAboveContext = #"staff" } \lyricsto "mel" \lyr
>>
<<
\new Staff = "staff" \m
\context ChordNames \with { alignBelowContext = #"staff" } \chrds
\new Lyrics\with { alignAboveContext = #"staff" } \lyricsto "mel" \lyr
>>
<<
\new Staff = "staff" \m
\context ChordNames \with { alignBelowContext = #"staff" } \chrds
\new Lyrics\with { alignAboveContext = #"staff" } \lyricsto "mel" \lyr
>>
<<
\new Staff = "staff" \m
\context ChordNames \with { alignBelowContext = #"staff" } \chrds
\new Lyrics\with { alignAboveContext = #"staff" } \lyricsto "mel" \lyr
>>
<<
\new Staff = "staff" \m
\context ChordNames \with { alignBelowContext = #"staff" } \chrds
\new Lyrics\with { alignAboveContext = #"staff" } \lyricsto "mel" \lyr
>>
<<
\new Staff = "staff" \m
\context ChordNames \with { alignBelowContext = #"staff" } \chrds
\new Lyrics\with {
Re: strange lilypond errors in 2.15.24
I think you commented something like that on an earlier thread. It was a very helpful approach, so thank you for the suggestion. I've done precisely that with this problem, but, as I described in the original post and my most recent reply, each section of the code compiles fine by itself. Saul On Wednesday, January 11, 2012 10:38:41 AM you wrote: > - Original Message - > From: "Shevek" > To: > Sent: Wednesday, January 11, 2012 6:20 PM > Subject: Re: strange lilypond errors in 2.15.24 > > > Francisco Vila wrote: > >> With the typos corrected and some content inside braces I obtain no > >> errors or warnings. > > > > The example also compiles fine for me. As I noted in my original post, > > that > > is one of the odd things about the error I'm getting. The line I marked > > causes a crash in the context of my project, but when I made a simple > > example, it gives me no problems. Similarly, in the other project, I > > can't trace the crash to any specific lines of code. > > The way I approach issues like this is to take out half the notes and check > to see whether it can compile, and continue to do this until it will. The > problem must lie in the bit just removed. It can be laborious, but I've > personally always found errors in my code. > > -- > Phil Holmes -- Saul Tobin http://SaulTobin.com/ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: strange lilypond errors in 2.15.24
Francisco Vila wrote:
>
>
> I don't see how can we help if we can not reproduce the error.
>
>
The thing is that I've attempted to use process of elimination to identity
the source of the error, to little success. As far as I can tell, there is
no single line or combination of lines that causes the error. For example,
in one project, there are, in addition to a multitude of staves without
chord symbols, three staves (Guitar, Piano, and Bass) that contain
constructs like:
<<
\new ChordNames = "Guit_chords" \with {
alignAboveContext = "Guitar"
} \chordmode {
...
When I comment out all the lines containing alignAboveContext, the crash
goes away. If I comment out, for example, the Piano and Bass staves, but
leave the Guitar staff with the alignAboveContext lines uncommented, the
crash also goes away. So the problem can't simply be the lines with
alignAboveContext.
Perhaps it's something about the way I was using that construct in multiple
staves? Okay, so I comment out all the other instruments' staves, leaving
just the Guitar, Piano, and Bass, but with alignAboveContext lines
uncommented. The crash goes away. So the crash only occurs when I have at
least two out of three of Guitar, Piano, or Bass, and I also have other
instruments.
As with the other project I described in the original post, it appears that
somehow Lilypond is choking once a certain amount of musical material is
reached. For example, I tried commenting out everything but Guitar and
Piano, which compiles, and then adding additional instrument staves one by
one. Guitar + Piano + 1 additional staff compiles fine, but Guitar + Piano +
2 additional staves crashes. I notice that the more instruments I add, the
fewer measures into the piece Lilypond gets before crashing.
--
View this message in context:
http://old.nabble.com/strange-lilypond-errors-in-2.15.24-tp33110205p33125221.html
Sent from the Gnu - Lilypond - 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 lilypond errors in 2.15.24
2012/1/11 Shevek : > > > Francisco Vila wrote: >> >> With the typos corrected and some content inside braces I obtain no >> errors or warnings. >> > The example also compiles fine for me. As I noted in my original post, that > is one of the odd things about the error I'm getting. The line I marked > causes a crash in the context of my project, but when I made a simple > example, it gives me no problems. Similarly, in the other project, I can't > trace the crash to any specific lines of code. I don't see how can we help if we can not reproduce the error. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: strange lilypond errors in 2.15.24
Francisco Vila wrote: > > With the typos corrected and some content inside braces I obtain no > errors or warnings. > The example also compiles fine for me. As I noted in my original post, that is one of the odd things about the error I'm getting. The line I marked causes a crash in the context of my project, but when I made a simple example, it gives me no problems. Similarly, in the other project, I can't trace the crash to any specific lines of code. -- View this message in context: http://old.nabble.com/strange-lilypond-errors-in-2.15.24-tp33110205p33123081.html Sent from the Gnu - Lilypond - 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 lilypond errors in 2.15.24
2012/1/11 Shevek : > Yes indeed. I noticed those typographical errors in my post soon after > posting, and, as you can see, edited the post to fix them. BTW What do you mean by "edited the post"? This is a mailing list from my point of view and I didn't see any fixes, sorry. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: strange lilypond errors in 2.15.24
2012/1/11 Shevek :
>
>
> Francisco Vila wrote:
>>
>>> \global = {
>>> % stuff
>>> }
>> should be
>> global = {
>>
>>> \guitar = {
>> should be
>> guitar = {
>>> % stuff
>>> <<
>>> \context ChordNames = "chords" \with {
>>> alignAboveContext = "Guitar" % commenting out
>>> this line solves the error
>>> } \chordnames {
>> should be
>> } \chordmode {
>>
>>
> Yes indeed. I noticed those typographical errors in my post soon after
> posting, and, as you can see, edited the post to fix them. I apologize for
> not proofreading carefully enough. Typos aside, the errors are still
> occurring as I described in the original post, and they are not caused by
> typos. I'd appreciate any input on this.
With the typos corrected and some content inside braces I obtain no
errors or warnings. Here is, the corrected code for clarity and a
sample of what do I obtain from it.
%BEGIN
global = {
% stuff
}
guitar = {
% stuff
<<
\context ChordNames = "chords" \with {
alignAboveContext = "Guitar" % commenting
out this line solves the error
} \chordmode { g
% stuff
}
{
% stuff
}
>>
% stuff
}
\score {
<<
% stuff
\new StaffGroup = "Rhythm" <<
\new Staff = "Guitar" << \global \guitar >>
% more stuff
>>
>>
\layout {}
}
%END
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
<>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: strange lilypond errors in 2.15.24
Francisco Vila wrote:
>
>> \global = {
>> % stuff
>> }
> should be
> global = {
>
>> \guitar = {
> should be
> guitar = {
>> % stuff
>> <<
>> \context ChordNames = "chords" \with {
>> alignAboveContext = "Guitar" % commenting out
>> this line solves the error
>> } \chordnames {
> should be
> } \chordmode {
>
>
Yes indeed. I noticed those typographical errors in my post soon after
posting, and, as you can see, edited the post to fix them. I apologize for
not proofreading carefully enough. Typos aside, the errors are still
occurring as I described in the original post, and they are not caused by
typos. I'd appreciate any input on this.
--
View this message in context:
http://old.nabble.com/strange-lilypond-errors-in-2.15.24-tp33110205p33119216.html
Sent from the Gnu - Lilypond - 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 lilypond errors in 2.15.24
2012/1/10 Shevek :
> \global = {
> % stuff
> }
should be
global = {
>
> \guitar = {
should be
guitar = {
> % stuff
> <<
> \context ChordNames = "chords" \with {
> alignAboveContext = "Guitar" % commenting out
> this line solves the error
> } \chordnames {
should be
} \chordmode {
and some content such as
g
> % stuff
> }
> {
> % stuff
> }
> >>
> % stuff
> }
>
> \score {
> <<
> % stuff
> \new StaffGroup = "Rhythm" <<
> \new Staff = "Guitar" << \global \guitar >>
> % more stuff
> >>
> >>
> \layout {}
> }
>
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: strange lilypond errors in 2.15.24
On my windows system, the sample you supplied doesn't compile - the use of
\global= and \guitar= are shown as errors. Replacing those without the
backslash it won't compile - \chordnames. Getting rid of that gives no output.
Putting something in as music I get a successful compilation. So not sure
what's going on with your system...
Phil Holmes
- Original Message -
From: Shevek
To: lilypond-user@gnu.org
Sent: Tuesday, January 10, 2012 10:03 AM
Subject: strange lilypond errors in 2.15.24
In another thread someone recommended that I try using the development
version of Lilypond, in order to take advantage of the improvements to chord
symbols. I finally got around to it, and the chord improvements look fantastic,
but I'm getting some enigmatic compile errors in my files, despite having run
convert-ly. In both cases, the error looks something like the following:
Parsing...
Interpreting music... [8][16][24][32][40][48][56][64]
LilyPond [genie2.ly] exited with exit status 1.
The number of parsed measures is the same every time, but it varies between
files and even after commenting certain sections of code. Even with
#(debug-enable 'debug) I get no additional error information. Needless to say,
these files compiled fine with 2.14.
In one instance, a multifile project with 1000+ lines, I managed to trace the
error to the following situation:
\global = {
% stuff
}
\guitar = {
% stuff
<<
\context ChordNames = "chords" \with {
alignAboveContext = "Guitar" % commenting out this
line solves the error
} \chordnames {
% stuff
}
{
% stuff
}
>>
% stuff
}
\score {
<<
% stuff
\new StaffGroup = "Rhythm" <<
\new Staff = "Guitar" << \global \guitar >>
% more stuff
>>
>>
\layout {}
}
Commenting out the alignAboveContext line solves the compile error. I
constructed a tiny example along the lines of the above, however, and it
compiles just fine with 2.15.24. So the alignAboveContext line is causing the
error...but it's also not the problem?
Even weirder, I get the same error in a different project, which is a single
file less than 400 lines long, and which contains no dynamically created
contexts. I experimented with commenting out sections of music, to see which
line was causing the error. Turns out the first half compiles fine...and so
does the second half. Arbitrary subsets up to about 75% of the piece compile
fine, so it's not something about the halfway point either. As far as I can
tell, Lilypond just crashes whenever the total amount of musical material
crosses a certain threshold. Commenting out a section just in the RH of the
piano, for example, lets the LH part be a little longer before it causes an
error. This behavior is especially odd, as the first project I mentioned is
vastly more involved notationally and compiles fine with 10 times the total
musical material of the second project, as long as I comment out the
alignAboveContext lines.
Since the error message is totally non-specific, it's entirely possible these
two errors are for completely different reasons. Indeed my diagnostic
hypotheses for each project each seem to exclude the other project.
Ideas about these very strange errors?
--
View this message in context: strange lilypond errors in 2.15.24
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
--
___
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
strange lilypond errors in 2.15.24
In another thread someone recommended that I try using the development
version of Lilypond, in order to take advantage of the improvements to chord
symbols. I finally got around to it, and the chord improvements look
fantastic, but I'm getting some enigmatic compile errors in my files,
despite having run convert-ly. In both cases, the error looks something like
the following:
Parsing...
Interpreting music... [8][16][24][32][40][48][56][64]
LilyPond [genie2.ly] exited with exit status 1.
The number of parsed measures is the same every time, but it varies between
files and even after commenting certain sections of code. Even with
#(debug-enable 'debug) I get no additional error information. Needless to
say, these files compiled fine with 2.14.
In one instance, a multifile project with 1000+ lines, I managed to trace
the error to the following situation:
\global = {
% stuff
}
\guitar = {
% stuff
<<
\context ChordNames = "chords" \with {
alignAboveContext = "Guitar" % commenting out
this line solves the error
} \chordnames {
% stuff
}
{
% stuff
}
>>
% stuff
}
\score {
<<
% stuff
\new StaffGroup = "Rhythm" <<
\new Staff = "Guitar" << \global \guitar >>
% more stuff
>>
>>
\layout {}
}
Commenting out the alignAboveContext line solves the compile error. I
constructed a tiny example along the lines of the above, however, and it
compiles just fine with 2.15.24. So the alignAboveContext line is causing
the error...but it's also not the problem?
Even weirder, I get the same error in a different project, which is a single
file less than 400 lines long, and which contains no dynamically created
contexts. I experimented with commenting out sections of music, to see which
line was causing the error. Turns out the first half compiles fine...and so
does the second half. Arbitrary subsets up to about 75% of the piece compile
fine, so it's not something about the halfway point either. As far as I can
tell, Lilypond just crashes whenever the total amount of musical material
crosses a certain threshold. Commenting out a section just in the RH of the
piano, for example, lets the LH part be a little longer before it causes an
error. This behavior is especially odd, as the first project I mentioned is
vastly more involved notationally and compiles fine with 10 times the total
musical material of the second project, as long as I comment out the
alignAboveContext lines.
Since the error message is totally non-specific, it's entirely possible
these two errors are for completely different reasons. Indeed my diagnostic
hypotheses for each project each seem to exclude the other project.
Ideas about these very strange errors?
--
View this message in context:
http://old.nabble.com/strange-lilypond-errors-in-2.15.24-tp33110205p33110205.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond errors in log file
Thank you everyone for your helpful tips - I've tried out a couple of programs, and I think I like jedit the best for now. -- View this message in context: http://old.nabble.com/Lilypond-errors-in-log-file-tp32119309p32127716.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond errors in log file
Hi Sarah, Glad you found it of use... ! :) Further to other respondents' comments... I use jedit. which is a multi-platform editor with plugin support for lilypond (and a whole lot of other stuff as well), and which has syntax highlighting and a pdf viewer which updates whenever you run the lp command. Hope this helps Regards Bill ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Lilypond errors in log file
hello, From: lilypond-user-bounces+james.lowe=datacore@gnu.org [lilypond-user-bounces+james.lowe=datacore@gnu.org] on behalf of Sarah Christian [sarahkchrist...@gmail.com] Sent: 24 July 2011 15:35 To: Marc Hohl Cc: lilypond-user@gnu.org Subject: Re: Lilypond errors in log file Thank you, yes, I did find the mismatched <<, and was able to compile the file. (It was produced by the Musescore software). I have since started over and am teaching myself lilypond now, and I'm finding it exceedingly easy. I do have a bit of a programming background though, so I tend to like typing better than point and click GUI interfaces. Right now though, I'm just using Notepad to edit my files. I would like a better text editor like emacs or something, but I'll need to devote some time to get it set up. If you have any recommendations for an easy-to-setup tool, let me know, thanks! (I'm on windows 7) --- http://notepad-plus-plus.org/ works for me. James ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond errors in log file
Thank you, yes, I did find the mismatched <<, and was able to compile the file. (It was produced by the Musescore software). I have since started over and am teaching myself lilypond now, and I'm finding it exceedingly easy. I do have a bit of a programming background though, so I tend to like typing better than point and click GUI interfaces. Right now though, I'm just using Notepad to edit my files. I would like a better text editor like emacs or something, but I'll need to devote some time to get it set up. If you have any recommendations for an easy-to-setup tool, let me know, thanks! (I'm on windows 7) >> >> >> >> >> >> >> >> >> ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond errors in log file
Am 23.07.2011 02:12, schrieb sarah-k:
Hi all - I apologize because I'm sure this answer can be found somewhere, but
I am VERY new at this, and I don't have lots of time to research this.
I've exported a MuseScore file to an ly file, and all appears fine, except
that I'm getting the following errors when trying to create the PDF:
# -*-compilation-*-
Processing `C:/Users/Sarah/Desktop/Le Violette.ly'
Parsing...
C:/Users/Sarah/Desktop/Le Violette.ly:192:0: error: syntax error, unexpected
'}'
} %% end of score-block
C:/Program Files/LilyPond/usr/share/lilypond/current/ly/init.ly:73:66:
error: syntax error, unexpected $end
(ly:parser-error parser (_ "expected error, but none found"
This error indicates that one (or more) of the { ... } or << ... >>
constructs are not balanced.
At a quick glace, it looks as if you have a ">>" which has no opening
couterpart.
Which editor are you using? Many of them have syntax highlighting
for lilypond files which makes it easier to find these errors.
HTH,
Marc
error: failed files: "C:\\Users\\Sarah\\Desktop\\Le Violette.ly"
I will attempt to upload the ly file to this message. I know that the first
error can be resolved by removing a bracket (specifically the one that is
closing the \score bracket), but when I removed it, it didn't solve the
unexpected $end error.
Can anyone point me in the right direction? Thanks!
http://old.nabble.com/file/p32119309/Le%2BViolette.ly Le+Violette.ly
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond errors in log file
Thank you so much - that is exactly what I needed!
On Fri, Jul 22, 2011 at 11:12 PM, Bill Mooney wrote:
> Hi Sarah,
> There appears to be a mismatched << immediately after the \score { at line
> 136.
> Commenting it out lets your file compile - whether the result is what you
> want, I don't know! :)
> Regards
> Bill
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond errors in log file
Hi Sarah,
There appears to be a mismatched << immediately after the \score { at
line 136.
Commenting it out lets your file compile - whether the result is what
you want, I don't know! :)
Regards
Bill
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Lilypond errors in log file
Hi all - I apologize because I'm sure this answer can be found somewhere, but I am VERY new at this, and I don't have lots of time to research this. I've exported a MuseScore file to an ly file, and all appears fine, except that I'm getting the following errors when trying to create the PDF: # -*-compilation-*- Processing `C:/Users/Sarah/Desktop/Le Violette.ly' Parsing... C:/Users/Sarah/Desktop/Le Violette.ly:192:0: error: syntax error, unexpected '}' } %% end of score-block C:/Program Files/LilyPond/usr/share/lilypond/current/ly/init.ly:73:66: error: syntax error, unexpected $end (ly:parser-error parser (_ "expected error, but none found" error: failed files: "C:\\Users\\Sarah\\Desktop\\Le Violette.ly" I will attempt to upload the ly file to this message. I know that the first error can be resolved by removing a bracket (specifically the one that is closing the \score bracket), but when I removed it, it didn't solve the unexpected $end error. Can anyone point me in the right direction? Thanks! http://old.nabble.com/file/p32119309/Le%2BViolette.ly Le+Violette.ly -- View this message in context: http://old.nabble.com/Lilypond-errors-in-log-file-tp32119309p32119309.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond errors with gcc 4.6
Hi, In the future, please send messages like this to -devel. I don't think everyone on -user wants to see these nasty linker errors... On 2011-03-29, Bernardo Barros wrote: > I think we might need some little changes to compile lilypond with gcc 4. > I'm getting the following errors with latest git. > > http://pastebin.com/gjsLv0Fe I did a test run with Arch [testing], and yes, I can (mostly) reproduce. [snip] > ./out/skyline-pair.o: In function `std::list std::allocator >::_M_erase(std::_List_iterator)': > /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.0/../../../../include/c++/4.6.0/bits/stl_list.h:1532: > undefined reference to `std::__detail::_List_node_base::_M_unhook()' I don't see any errors from `./out/skyline-pair.o'. There are also fewer errors in my log than in yours. See the attached log. My guess is that the gcc 4.6.0 rebuild is buggy. Let's wait to see if this makes it into core or not. :) Thanks, Patrick ./out/accidental-placement.o: In function `std::list >::_M_erase(std::_List_iterator)': /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.0/../../../../include/c++/4.6.0/bits/stl_list.h:1532: undefined reference to `std::__detail::_List_node_base::_M_unhook()' ./out/accidental-placement.o: In function `std::list >::_M_transfer(std::_List_iterator, std::_List_iterator, std::_List_iterator)': /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.0/../../../../include/c++/4.6.0/bits/stl_list.h:1508: undefined reference to `std::__detail::_List_node_base::_M_transfer(std::__detail::_List_node_base*, std::__detail::_List_node_base*)' ./out/accidental-placement.o: In function `std::list >::_M_insert(std::_List_iterator, Building const&)': /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.0/../../../../include/c++/4.6.0/bits/stl_list.h:1516: undefined reference to `std::__detail::_List_node_base::_M_hook(std::__detail::_List_node_base*)' ./out/skyline.o: In function `std::list >::reverse()': /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.0/../../../../include/c++/4.6.0/bits/stl_list.h:1416: undefined reference to `std::__detail::_List_node_base::_M_reverse()' ./out/skyline.o: In function `std::list >::_M_erase(std::_List_iterator)': /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.0/../../../../include/c++/4.6.0/bits/stl_list.h:1532: undefined reference to `std::__detail::_List_node_base::_M_unhook()' ./out/skyline.o: In function `std::list >::swap(std::list >&)': /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.0/../../../../include/c++/4.6.0/bits/stl_list.h:1179: undefined reference to `std::__detail::_List_node_base::swap(std::__detail::_List_node_base&, std::__detail::_List_node_base&)' ./out/skyline.o: In function `std::list >::_M_insert(std::_List_iterator, Box const&)': /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.0/../../../../include/c++/4.6.0/bits/stl_list.h:1516: undefined reference to `std::__detail::_List_node_base::_M_hook(std::__detail::_List_node_base*)' ./out/skyline.o: In function `std::list >::_M_transfer(std::_List_iterator, std::_List_iterator, std::_List_iterator)': /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.0/../../../../include/c++/4.6.0/bits/stl_list.h:1508: undefined reference to `std::__detail::_List_node_base::_M_transfer(std::__detail::_List_node_base*, std::__detail::_List_node_base*)' ./out/tie-performer.o: In function `std::list >::_M_insert(std::_List_iterator, Head_audio_event_tuple const&)': /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.0/../../../../include/c++/4.6.0/bits/stl_list.h:1516: undefined reference to `std::__detail::_List_node_base::_M_hook(std::__detail::_List_node_base*)' ./out/tie-performer.o: In function `std::list >::_M_erase(std::_List_iterator)': /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.0/../../../../include/c++/4.6.0/bits/stl_list.h:1532: undefined reference to `std::__detail::_List_node_base::_M_unhook()' ./out/tie-performer.o: In function `std::list >::_M_transfer(std::_List_iterator, std::_List_iterator, std::_List_iterator)': /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.0/../../../../include/c++/4.6.0/bits/stl_list.h:1508: undefined reference to `std::__detail::_List_node_base::_M_transfer(std::__detail::_List_node_base*, std::__detail::_List_node_base*)' collect2: ld returned 1 exit status make[1]: *** [out/lilypond] Error 1 make: *** [all] Error 2 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
LilyPond errors with gcc 4.6
I think we might need some little changes to compile lilypond with gcc 4. I'm getting the following errors with latest git. http://pastebin.com/gjsLv0Fe 8<8<8<8<8<8<8< make -C ../flower && true make[2]: Entering directory `/home/smoge/src/archaudio/experimental/lilypond-git/src/lilypond-build/flower' make PACKAGE=LILYPOND package=lilypond -C include all && true make[3]: Entering directory `/home/smoge/src/archaudio/experimental/lilypond-git/src/lilypond-build/flower/include' true make[3]: Leaving directory `/home/smoge/src/archaudio/experimental/lilypond-git/src/lilypond-build/flower/include' make[2]: Leaving directory `/home/smoge/src/archaudio/experimental/lilypond-git/src/lilypond-build/flower' g++ -o out/lilypond ./out/instrument-name-engraver.o ./out/hyphen-engraver.o ./out/tweak-engraver.o ./out/sequential-iterator.o ./out/horizontal-bracket.o ./out/translator-dispatch-list.o ./out/slur-score-parameters.o ./out/grob.o ./out/span-arpeggio-engraver.o ./out/dynamic-performer.o ./out/parse-scm.o ./out/tie.o ./out/bend-engraver.o ./out/beam-collision-engraver.o ./out/tab-note-heads-engraver.o ./out/note-head-scheme.o ./out/audio-item.o ./out/paper-score.o ./out/constrained-breaking.o ./out/rest-collision.o ./out/spanner-scheme.o ./out/multi-measure-rest-engraver.o ./out/hara-kiri-group-spanner.o ./out/bar-number-engraver.o ./out/parenthesis-engraver.o ./out/freetype.o ./out/breathing-sign-engraver.o ./out/completion-rest-engraver.o ./out/font-size-engraver.o ./out/rest-engraver.o ./out/translator-group.o ./out/semi-tie-column.o ./out/file-name-map.o ./out/line-spanner.o ./out/spring.o ./out/program-option.o ./out/stem-tremolo.o ./out/pitch.o ./out/volta-repeat-iterator.o ./out/fretboard-engraver.o ./out/separation-item.o ./out/staff-symbol-referencer.o ./out/stream-event-scheme.o ./out/lily-lexer.o ./out/bezier-bow.o ./out/midi-item.o ./out/page-breaking-scheme.o ./out/output-property-engraver.o ./out/lily-version.o ./out/repeat-tie-engraver.o ./out/box.o ./out/stem.o ./out/dimensions-scheme.o ./out/music-scheme.o ./out/note-heads-engraver.o ./out/paper-outputter.o ./out/chord-tremolo-engraver.o ./out/skyline-pair.o ./out/performance-scheme.o ./out/staff-collecting-engraver.o ./out/page-turn-engraver.o ./out/engraver-scheme.o ./out/completion-note-heads-engraver.o ./out/font-interface.o ./out/bar-engraver.o ./out/text-interface.o ./out/enclosing-bracket.o ./out/nested-property.o ./out/music-output.o ./out/arpeggio.o ./out/font-config-scheme.o ./out/footnote-engraver.o ./out/spacing-engraver.o ./out/sustain-pedal.o ./out/note-column.o ./out/piano-pedal-bracket.o ./out/module-scheme.o ./out/lyric-combine-music-iterator.o ./out/new-fingering-engraver.o ./out/audio-element-info.o ./out/font-metric.o ./out/note-spacing-engraver.o ./out/freetype-error.o ./out/accidental-placement.o ./out/music-iterator.o ./out/rhythmic-head.o ./out/grob-array.o ./out/context.o ./out/dispatcher.o ./out/scale.o ./out/general-scheme.o ./out/percent-repeat-iterator.o ./out/tie-engraver.o ./out/grid-line-interface.o ./out/open-type-font.o ./out/slur-configuration.o ./out/repeated-music.o ./out/lookup.o ./out/global-ctor.o ./out/spacing-options.o ./out/simple-music-iterator.o ./out/paper-book.o ./out/program-option-scheme.o ./out/mensural-ligature-engraver.o ./out/lyric-performer.o ./out/piano-pedal-engraver.o ./out/modified-font-metric.o ./out/slur-performer.o ./out/guile-init.o ./out/stencil-scheme.o ./out/tuplet-engraver.o ./out/grace-music.o ./out/skyline.o ./out/spacing-interface.o ./out/note-head-line-engraver.o ./out/paper-outputter-scheme.o ./out/break-align-engraver.o ./out/relative-octave-music.o ./out/ledger-line-engraver.o ./out/least-squares.o ./out/double-percent-repeat-engraver.o ./out/directional-element-interface.o ./out/lily-lexer-scheme.o ./out/drum-note-engraver.o ./out/music-sequence.o ./out/music.o ./out/item-scheme.o ./out/relative-octave-check.o ./out/part-combine-iterator.o ./out/keyword.o ./out/translator-ctors.o ./out/vertical-align-engraver.o ./out/arpeggio-engraver.o ./out/beam-concave.o ./out/percent-repeat-item.o ./out/ligature-engraver.o ./out/lyric-hyphen.o ./out/simple-spacer.o ./out/book.o ./out/auto-change-iterator.o ./out/grob-interface-scheme.o ./out/key-signature-interface.o ./out/rest.o ./out/accidental.o ./out/grace-engraver.o ./out/figured-bass-position-engraver.o ./out/spanner.o ./out/pfb.o ./out/ottava-bracket.o ./out/break-alignment-interface.o ./out/trill-spanner-engraver.o ./out/page-marker.o ./out/collision-engraver.o ./out/figured-bass-engraver.o ./out/spanner-break-forbid-engraver.o ./out/note-performer.o ./out/minimal-page-breaking.o ./out/dot-column-engraver.o ./out/spacing-loose-columns.o ./out/breathing-sign.o ./out/music-wrapper-iterator.o ./out/grid-point-engraver.o ./out/paper-def.o ./out/staff-grouper-interface.o ./out/output-def.o ./out/episema-engraver.o ./out/midi-walker.o ./out/font-select.o ./out/self-alignment-i
Re: lilypond errors
On 20-Jun-05, at 10:59 PM, Arthur Dyck wrote: lilypond (GNU LilyPond) 2.0.1 This is a very old version of lilypond. I recommend either using 2.5.31, or wait a week or so and use 2.6.0. The installation should be much easier with these versions. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond errors
Arthur Dyck wrote: >I have installed Lilypond and its requirements on my system running Mandrake >10.0. The files were installed using Web Urpmi. I have used KWrite to >create the test.ly in your tutorial. When I try to run lilypond test.ly, I >get the following error. Can you please tell me how to fix this? > >lilypond (GNU LilyPond) 2.0.1 >Running usr...ERROR: In procedure dynamic-link: >ERROR: file: "libguile-srfi-srfi-13-14-v-1", message: >"libguile-srfi-srfi-13-14-v-1.so: cannot open shared object file: No such >file or directory" > > >lilypond: error: LilyPond failed on input file test (exit status 2) >lilypond: warning: Running LilyPond failed. Rerun with --verbose for a trace. >[EMAIL PROTECTED] arthur]$ > > >Thanks. > >Arthur Dyck > > > Have you installed the guile, libguile and libguile12-devel packages? I bet that would take care of the problem. --Daniel ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
lilypond errors
I have installed Lilypond and its requirements on my system running Mandrake 10.0. The files were installed using Web Urpmi. I have used KWrite to create the test.ly in your tutorial. When I try to run lilypond test.ly, I get the following error. Can you please tell me how to fix this? lilypond (GNU LilyPond) 2.0.1 Running usr...ERROR: In procedure dynamic-link: ERROR: file: "libguile-srfi-srfi-13-14-v-1", message: "libguile-srfi-srfi-13-14-v-1.so: cannot open shared object file: No such file or directory" lilypond: error: LilyPond failed on input file test (exit status 2) lilypond: warning: Running LilyPond failed. Rerun with --verbose for a trace. [EMAIL PROTECTED] arthur]$ Thanks. Arthur Dyck ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
