Eluze,
I follow your suggestion and I came up with smaller file about 268 lines.
I attach the .ly file and the error message log file. Please refer to red text below log file.
Emanuel,
Ming.
Starting lilypond-windows.exe 2.17.26 [how-beautiful-your-nameTEST.ly]...
Processing `C:/Users/Tsang/Dropbox/Lyndon/LiLy/how-beautiful-your-name/how-beautiful-your-nameTEST.ly'
Parsing...
Interpreting music...
MIDI output to `how-beautiful-your-nameTEST-soprano.mid'...
Interpreting music...
programming error: Impossible or ambiguous (de)crescendo in MIDI.
continuing, cross fingers
MIDI output to
`how-beautiful-your-nameTEST-alto.mid'...
Interpreting music...
programming error: Impossible or ambiguous (de)crescendo in MIDI.
continuing, cross fingers
MIDI output to `how-beautiful-your-nameTEST-tenor.mid'...
Interpreting music...
programming error: Impossible or ambiguous (de)crescendo in MIDI.
continuing, cross fingers
Interpreting music...[8][8]
Preprocessing graphical objects...
MIDI output to `how-beautiful-your-nameTEST-bass.mid'...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `how-beautiful-your-nameTEST-bass.ps'...
Converting to `./how-beautiful-your-nameTEST-bass.pdf'...
Interpreting
music...[8][8]
Preprocessing graphical objects...
Interpreting music...
MIDI output to `how-beautiful-your-nameTEST.mid'...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `how-beautiful-your-nameTEST.ps'...
Converting to `./how-beautiful-your-nameTEST.pdf'...
Success: compilation successfully completed
Completed successfully in 14.2".
From: MING TSANG <address@hidden>
To: "address@hidden" <address@hidden>
Cc: "address@hidden" <address@hidden>
Sent: Friday, September 27, 2013 8:33:56 AM
Subject: Re: programming error
Hi, Eluze:
Yes, it probably doesn't 5o+ measure to show the problem, but I don't know when and where the "programming error" suddenly appears. The compile run seems producing .pdf ok.
I will follow you suggestion and try identify when and where that error first appears.
Emanuel,
Ming
1. Re:programming error (Eluze)
----------------------------------------------------------------------
Message: 1
Date: Thu, 26 Sep 2013 05:19:37 -0700 (PDT)
From: Eluze <
address@hidden>
To:
address@hiddenSubject: Re: programming error
Message-ID: <
address@hidden>
Content-Type: text/plain; charset=UTF-8
MING TSANG
wrote
> Sorry, I attached a .ly file with \include private files. ?I remove those
> and the following can compile. ?
great - it's compiling mow!
but I wouldn't say this is minimal - the next step now is to reduce your
code to get near the offending code.
but - which of the 2 problems do you want to solve first?
I suggest to attack the lyrics problem:
for this you should comment *all* the verses and re-include them one by one
- this will quickly show in which verse the warning occurs! and it's even
easier if you get rid of all the other stuff which isn't directly involved:
instrumentName, shortInstrumentName, midiInstrument, Dynamics etc.
also: do you need over 50 measures to show the problem?
hth
Eluze
--
how-beautiful-your-nameTEST.ly