I was looking at ways to extract MIDI notes from MIDI files (since my class is likely to have a hard time with typing MIDI note numbers into a [text] -- it may be easier for them to create short sequences in a DAW and load them in Pd).

But, for interactive media art projects, it would be nice to be able to get the notes independent of timing (to substitute randomized timing, or timing derived from interactive control data).

It seems that [cyclone/seq] (and [mrpeach/midifile]) both tie data access to the timing. At best, I can "tick" through the file but there is no way to anticipate on which tick the next event will occur. (I guess this is a limitation of the data format -- if each note is represented as a pair of messages, then you can only get the on/off status, but not "notes" as discrete entities.)

Anyway, just wondering if there were other options for digging into MIDI files.

hjh

@ddw_music This outputs the note/velocity pairs of a midi file almost instantly. For larger midi files it will take a while though.

You can filter for the channel afterwards if it is necessary.

@ddw_music With [midifile] this should be somewhat similar, but i don't remember exactly what the output looks like:

OK, so the approach would be to scan the MIDI file completely and populate a [text] or something, to be able to get the data on demand.

Probably the [until] the idea could apply to [seq] as well: [until] --> [tick( --> [seq].

I might consider it later, but at the moment, I think I won't pursue it further.

hjh

@ddw_music Yes!