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/11 Shevek s...@saultobin.com:
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
attachment: document.png___
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 s...@saultobin.com: 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
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 s...@saultobin.com: 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:
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:
pre
\new ChordNames = Guit_chords \with {
alignAboveContext = Guitar
} \chordmode {
...
/pre
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
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 s...@saultobin.com To: lilypond-user@gnu.org 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
Hi Saul,
2012/1/12 Saul Tobin s...@saultobin.com:
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 s...@saultobin.com
To: lilypond-user@gnu.org
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 { 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
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
Re: strange lilypond errors in 2.15.24
2012/1/10 Shevek s...@saultobin.com:
\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
