Open sound control

[jpcima]

The idea is to implement a control interface for sfizz, that permits access to engine information in read/write/both. The benefit is to avoid creating a large amount of API for various kinds of properties.

A suggestion is to keep OSC protocol details to be handled outside of the library.

• sfizz does not deal with message encoding or decoding
• sfizz does not do message buffering internally

1. a message sending API
2. a message broadcast API (a global callback)
3. a message reply mechanism (a callback associated with a particular client)

/*1.*/ void sfizz_send_osc(
            const char* path, sfizz_osc_client_t* client, const char* arg_signature, const sfizz_osc_arg_t* args);
/*2.*/ void sfizz_set_osc_broadcast_callback(
            void* broadcast_data,
            void (*broadcast)(void* broadcast_data, const char* path, const char* arg_signature, const sfizz_osc_arg_t* args));
/*3.*/ struct sfizz_osc_client_t {
  void *client_data;
  void (*reply)(void* client_data, const char* path, const char* arg_signature, const sfizz_osc_arg_t* args);
};

Notes

• a reply is sent in response to a message received which is an access in read mode (eg. /cc/12/label)
• a broadcast is sent in response to an internal change in the engine (eg. new sfz file just loaded, keyswitch happened, etc)

[paulfd]

Only thing missing is the callback now?