@ 147f569 - PortMidi.Reader now passes a buffer_size to the underlying nif, saving MIDI messages from being lost. This buffer_size is set to 256 by default, and can be configured at application level: config :portmidi, buffer_size: 1024
@ ed9e3bb - PortMidi.Reader now emits messages as lists, no more as simple tuples. Sometimes there could be only one message, but a list is always returned. The tuples have also changed structure, to include timestamps, that were previously ignored: [{{status, note1, note2}, timestamp}, ...]
@ d202f7a - PortMidi.Writer now accepts good old message tuples ({status, note1, note2}), event tuples, with timestamp ({{status, note1, note2}, timestamp}) or lists of event tuples ([{{status, note1, note2}, timestamp}, ...]). This is the preferred way for high throughput, and can be safely used as a pipe from an input device.
@ 147f569-PortMidi.Readernow passes abuffer_sizeto the underlying nif, saving MIDI messages from being lost. Thisbuffer_sizeis set to 256 by default, and can be configured at application level:config :portmidi, buffer_size: 1024@ ed9e3bb-PortMidi.Readernow emits messages as lists, no more as simple tuples. Sometimes there could be only one message, but a list is always returned. The tuples have also changed structure, to include timestamps, that were previously ignored:[{{status, note1, note2}, timestamp}, ...]@ d202f7a-PortMidi.Writernow accepts good old message tuples ({status, note1, note2}), event tuples, with timestamp ({{status, note1, note2}, timestamp}) or lists of event tuples ([{{status, note1, note2}, timestamp}, ...]). This is the preferred way for high throughput, and can be safely used as a pipe from an input device.