Ksp reference Manual

MIDI Object Commands
145
KSP Reference Manual

---

mf_insert_event()
mf_remove_event()
save_midi_file()
16.5. mf_get_buffer_size()
mf_get_buffer_size()
Returns the size of the MIDI event buffer
Remarks
• The maximum buffer size is 1,000,000 events, including both active and inactive events.
• Inserting a MIDI event will decrease the buffer size by one. Removing an event will increase it
by one.
See Also
mf_insert_file()
mf_set_buffer_size()
mf_reset()
mf_insert_event()
mf_remove_event()
save_midi_file()
16.6. mf_reset()
mf_reset()
Resets the MIDI object, sets the event buffer to zero, and removes all events
Remarks
• This command purges all MIDI data. Use with caution.
• This command is also asynchronous, and thus calls the 
async_complete
callback.
See Also
mf_insert_file()
mf_set_buffer_size()
mf_reset()
mf_insert_event()
mf_remove_event()
save_midi_file()
MIDI Object Commands
146
KSP Reference Manual

---

16.7. mf_insert_event()
mf_insert_event(,
,mand>,,)
Activates an inactive MIDI event in the MIDI object. However,
because the command and position are defined in this com-
mand, it can be considered as an insertion.

The track into which the event will be inserted
The position at which the event will be inserted, in
ticks

Defines the command type of the event, can be one of
the following:
$MIDI_COMMAND_NOTE_ON
$MIDI_COMMAND_POLY_AT
$MIDI_COMMAND_CC
$MIDI_COMMAND_PROGRAM_CHANGE
$MIDI_COMMAND_MONO_AT
$MIDI_COMMAND_PITCH_BEND

The first byte of the command

The second byte of the command
Remarks
• It is not possible to insert MIDI events without first setting an event buffer size with the
mf_set_buffer_size()
command.
• Using this command when the buffer is full, i.e. has a size of zero, will do nothing.
• You can retrieve the event ID of the inserted event in a variable by writing:
:= mf_insert_event(,
,,,)
See Also
mf_insert_file()
mf_set_buffer_size()
mf_get_buffer_size()
mf_reset()
mf_remove_event()
save_midi_file()