You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm in the process of writing native-oriented client app now, and it is getting complicated to find out the right way to establish connection to service, namely how to set up shared memory buffers in the right order. Since it's been changing, it was definitely left undocumented which is not good at all. It has to be changed.
The text was updated successfully, but these errors were encountered:
How-to documentation on query plugin services, bind service, instantiate plugin, prepare buffers, activate, process, deactivate, terminate, and unbind service. Some native parts are already summarized on README.
documenting them means we will have the relevant API parts sorted out.
atsushieno
added a commit
to atsushieno/aap-midi-device-service
that referenced
this issue
Apr 20, 2021
I'm done with aap-juce adoption too (both plugin and hosting). Now that it is only about the public plugin API matter (libandroidaudioplugin is not public), I can close this particular issue.
I'm in the process of writing native-oriented client app now, and it is getting complicated to find out the right way to establish connection to service, namely how to set up shared memory buffers in the right order. Since it's been changing, it was definitely left undocumented which is not good at all. It has to be changed.
The text was updated successfully, but these errors were encountered: