JoelHobson
commented
9 years ago Awesome, I look forward to the PRs :+1:. If we go with FileIO (see my comment on #31)... I'm not sure about going with track IDs on the track events or not. It might actually simplify working with midi data, since distributing the events to different tracks can be handled by the write functions. On the other hand, keeping the events grouped by track in their own arrays seems like it might be a little easier to reason about while you're working on a file. Honestly, I could go either way with this.
rafaqz
I think that a stream-based API would work well for MIDI, and would work for both file I/O and reading/writing from devices.
Related to #31,
loading a MIDI file (or connecting to a MIDI device) would give you aMIDIStream, from which you could read/write vectors ofMIDIEventsOne question is how to handle multi-track files. I'm not sure whether it makes more sense to have them be separate streams, or whether the
MIDIEvents should just have a track ID as a field.Right now I'm just spit-balling some ideas, so feel free to ignore (of course). Sometime in the next few weeks I'm actually hoping to interface with some MIDI hardware, so I'll be able to contribute some PRs then.