Documentation

The datatypes for MIDI Files and MIDI Events

An empty MIDI file. Tempo is set to one tick per quarter note.

Convert all NoteOn p 0 to NoteOff p 64. The latter one is easier to process.

Convert all NoteOff p 64 to NoteOn p 0. The latter one can be encoded more efficiently using the running status.

Merge all tracks into a single track according to the MIDI file type.

Apply a function to each track.

Process and remove all SetTempo events. The result is an event list where the times are measured in seconds.

Show the T with one event per line, suited for comparing MIDIFiles with diff. Can this be replaced by showFile?

A hack that changes the velocities by a rational factor.

Change the time base.

Sort MIDI note events lexicographically. This is to make MIDI files unique and robust against changes in the computation. In principle Performance.merge should handle this but due to rounding errors in Float the order of note events still depends on some internal issues. The sample rate of MIDI events should be coarse enough to assert unique results.

Old versions of Haskore.Interface.MIDI.Write wrote ProgramChange and SetTempo once at the beginning of a file in that order. The current version supports multiple ProgramChanges in a track and thus a ProgramChange is set immediately before a note. Because of this a ProgramChange is now always after a SetTempo. For checking equivalence with old MIDI files we can switch this back.