The Receiver C API can be used to get asynchronous messages from native code running in other threads.

• Lua objects implementing the Receiver C API can receive asynchronous messages.
• Native C code invoking the Receiver C API can send asynchronous messages from any thread.

Lua objects implementing the Receiver C API must have an associated meta table entry _capi_receiver delivered by the C API function receiver_get_capi() and the associated C API function toReceiver() must return a valid pointer for the given receiver object. For further documentation see receiver_capi.h.

• mtmsg buffer objects are implementing the Receiver C API. If invoked, the arguments are appended to the buffer as a new message.

• mtstates state objects are implementing the Receiver C API. If invoked, the state's callback function is invoked with the message arguments.

• ljack client objects are sending JACK status messages to a registered receiver object, see ljack.client_open() and ljack/example02.lua.

• auproc MIDI receiver processor objects are sending midi messages that were received from an auproc-capi connector to a registered receiver object, see auproc.new_midi_receiver() and ljack/example03.lua.

• auproc AUDIO receiver processor objects are sending audio messages that were received from an auproc-capi connector to a registered receiver object, see auproc.new_audio_receiver() and ljack/example08.lua.

This is free and unencumbered software released into the public domain.

Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.