pd-externals / midifile

Read and write MIDI files (.mid) with Pd

midifile

Read and write MIDI files (.mid). Open midifile-help.pd with Pd to get detailed information about supported methods.

Author: Martin Peach

midifile's Issues

midifile considers realtime message, which are not part of midi files

data that [midirealtimein] reports shouldn't be part of midi files...

Having problems getting [midifile] to work

This isn't really an "issue", I don't think, but I'm having problems getting [midifile] to work. I've had no luck creating MIDI files, except for the most trivial of examples. If I try to play back the file, I just get a stream of error messages like the following:

midifile: No running status on track 0 at 957

And if I try to play it back using [cyclone/seq], I get the following error messages:

seq's warning: missing running status in midi file... skip to end of track
seq's warning: no valid miditracks

I've posted this question on the forum as well as the mailing list, but haven't been able to resolve the problem. Is there some place I can find examples, other than what's in the help file for [midifile]? Maybe if I can look at how other people are using it, I can figure out what I'm doing wrong. I've tried Google, but didn't come up with anything.

I'm using the latest version available through Deken, v20200615, (although I don't know if there's a later version that isn't available in Deken yet), under Pd 0.52.1 and Windows 7 (64-bit).

Thanks.

Tasklist:

• The original issue has been determined to be a problem with my patch, not with [midifile]. Sorry!
• The wrong number is reported by [midifile] for the number of bytes written to the file. It always seems to be 1 or 2 bytes greater than the actual number of bytes in the file.
• When reading a file, [track n( messages seem to be ignored. All tracks are played.
• At least under Windows, an error message is sometimes displayed in the Pd console about delete permission for the temporary files that are generated when writing to a MIDI file.
• Errors in help file: the [route_events] subpatch of [midifile_read] shows CC messages as being in the range of 176 to 192 inclusive, but 192 is a Program Change message. Also, any messages except Note On, Note Off, Control Change and System Exclusive messages are considered System messages. So Aftertouch, Channel Pressure, Pitch Bend, Channel Mode, etc., aren't being routed properly. It's not clear to me whether or not these messages are actually being written to an output file, I haven't looked at the source code very closely. But IMHO, the help file should indicate whether or not they're supported.

midifile should use "canvas_open" to open files

it's just better as it also searches for files in the search paths

Errors in help file for [midifile] object

Errors in help file: the [route_events] subpatch of [midifile_read] shows CC messages as being in the range of 176 to 192 inclusive, but 192 is a Program Change message. Also, any messages except Note On, Note Off, Control Change and System Exclusive messages are considered System messages. So Aftertouch, Channel Pressure, Pitch Bend, Channel Mode, etc., aren't being routed properly. It's not clear to me whether or not these messages are actually being written to an output file, I haven't looked at the source code very closely. But IMHO, the help file should indicate whether or not they're supported.