LilyPond is the best tool to search for the error. If you add a bar check after each measure, i.e. add a | on the line before each new % MEASURE, you will get a warning message pointing out exactly the line in the score where you have a problem (I really recommend you to do it yourself, other readers who don't have the patience can look at the end of the email).
Also, I don't understand why you add curly braces around each bar, they don't do anything useful.
/Mats
Kevin C. Baird wrote:
Hi. In the attached file, The Lilypond output of measure 16 (a 9/8 bar) only allows 8.5 8ths in the measure, causing the final legal 16th note to spill over into measure 17.
I've attached the .ly file and the output of 'apt-cache show lilypond' on my Debian testing i386 system.
Please let me know if I can provide other useful information.
Thank you.
------------------------------------------------------------------------
_______________________________________________ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond
-- ============================================= Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe =============================================
P.S. For the record, the problem is in bar 5, which is one 16:th too long.
_______________________________________________ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond
