Re: No midi with lilypond-book

[Clifford Racz]

If this might help a developer to trace the problem (or someone might be 
able to point out how to make a work-around) it appears that the problem 
is due to one of the functions in lilypond-book-preamble.ly:

-------------------------------------------------------------------------------
%Example produces midi but breaks the book layout of the graphics
\version "2.10.33"
%The following statements are equivalent to the book preamble
%\include "lilypond-book-preamble.ly"
% BEGIN book-preamble statements
%#(set! toplevel-score-handler print-score-with-defaults)
#(set! toplevel-music-handler
  (lambda (p m)
   (if (not (eq? (ly:music-property m 'void) #t))
        (print-score-with-defaults
         p (scorify-music m p)))))

#(ly:set-option (quote no-point-and-click))
#(define inside-lilypond-book #t)
#(define version-seen #t)
% END book-preamble statements
\score {
  \context PianoStaff <<
    \new Staff = "treble" << \relative c'' { a b c d e f g a' } >>
  >>
  \layout { }
  \midi { }
}
-------------------------------------------------------------------------------
%Example not producing midi but book layout is fine
\version "2.10.33"
%The following statements are equivalent to the book preamble
%\include "lilypond-book-preamble.ly"
% BEGIN book-preamble statements
#(set! toplevel-score-handler print-score-with-defaults)
#(set! toplevel-music-handler
  (lambda (p m)
   (if (not (eq? (ly:music-property m 'void) #t))
        (print-score-with-defaults
         p (scorify-music m p)))))

#(ly:set-option (quote no-point-and-click))
#(define inside-lilypond-book #t)
#(define version-seen #t)
% END book-preamble statements
\score {
  \context PianoStaff <<
    \new Staff = "treble" << \relative c'' { a b c d e f g a' } >>
  >>
  \layout { }
  \midi { }
}
-------------------------------------------------------------------------------

Clifford Racz wrote:
> I am using v. 2.10.33 and I am getting no midi output when using 
> LilyPond-book (i.e. \include "lilypond-book-preamble.ly" ).
> Is there a fix for this issue?