midi-0.1.6: Handling of MIDI messages and files



Channel messages



data T Source




data Body Source


Voice T 
Mode T 


get :: C parser => Int -> Channel -> Int -> Fallible parser TSource

Parse a MIDI Channel message. Note that since getting the first byte is a little complex (there are issues with running status), the code, channel and first data byte must be determined by the caller.

getWithStatus :: C parser => Int -> Fallible (T parser) TSource

Parse an event. Note that in the case of a regular MIDI Event, the tag is the status, and we read the first byte of data before we call get. In the case of a MIDIEvent with running status, we find out the status from the parser (it's been nice enough to keep track of it for us), and the tag that we've already gotten is the first byte of data.

put :: C writer => T -> writerSource

putWithStatus :: C writer => T -> T writerSource

data Channel Source

This definition should be in Message.Channel, but this results in a cyclic import.

data Controller Source

We do not define Controller as enumeration with many constructors, because some controllers have multiple names and some are undefined. It is also more efficient this way. Thus you cannot use case for processing controller types, but you can use Data.List.lookup instead.

 maybe (putStrLn "unsupported controller") putStrLn $
 lookup ctrl $
    (portamento, "portamento") :
    (modulation, "modulation") :

decodeStatus :: Int -> (Int, Channel)Source

for internal use