libfluidsynth
2.4.5
|
Functions for managing MIDI drivers. More...
Lifecycle Functions for MIDI Driver_linebr@{ | |
fluid_midi_driver_t * | new_fluid_midi_driver (fluid_settings_t *settings, handle_midi_event_func_t handler, void *event_handler_data) |
Create a new MIDI driver instance. More... | |
void | delete_fluid_midi_driver (fluid_midi_driver_t *driver) |
Delete a MIDI driver instance. More... | |
Functions for managing MIDI drivers.
The available MIDI drivers depend on your platform. See MIDI driver settings for all available configuration options.
To create a MIDI driver, you need to specify a source for the MIDI events to be forwarded to via the fluid_midi_event_t callback. Normally this will be either a MIDI Router via fluid_midi_router_handle_midi_event() or the synthesizer via fluid_synth_handle_midi_event().
But you can also write your own handler function that preprocesses the events and forwards them on to the router or synthesizer instead.
void delete_fluid_midi_driver | ( | fluid_midi_driver_t * | driver | ) |
Delete a MIDI driver instance.
driver | MIDI driver to delete |
fluid_midi_driver_t* new_fluid_midi_driver | ( | fluid_settings_t * | settings, |
handle_midi_event_func_t | handler, | ||
void * | event_handler_data | ||
) |
Create a new MIDI driver instance.
settings | Settings used to configure new MIDI driver. See MIDI driver settings for available options. |
handler | MIDI handler callback (for example: fluid_midi_router_handle_midi_event() for MIDI router) |
event_handler_data | Caller defined data to pass to 'handler' |
Which MIDI driver is actually created depends on the midi.driver option.