Re: Issue 1592 in lilypond: regtest for midi output

[lilypond]

Comment #5 on issue 1592 by address@hidden: regtest for midi output
http://code.google.com/p/lilypond/issues/detail?id=1592

We certainly don't want to depend on the midi2ly loop.  Midi output bugs in  
dynamics are not caught this way, nor were the disastrous issues we had  
this Spring, because midi2ly was working on the same misconceptions about  
MIDI as were the midi-output routines.

It seems desired behavior for `make check` is to test the two  
transformations individually.

The .ly files input/regression/midi-*.ly create midi output, which can be  
run through lilymidi --pretty and compared as text.

The files in input/regression/midi/* (except for one) actually test  
midi2ly.  These could be replaced by the corresponding (binary) .midi files  
as the git-tracked input, run through midi2ly -> lilypond and then we check  
at the engraved output as usual.