> Understanding the dev side and not the user side, that is the world
That is quite possible -- the API that a "host" (session handler) uses
to communicate with "clients" / "plugins" / whatever says nothing
about how that "host" calls those API functions, how it structures
disk storage, etc.
Note that for developers there is also API documentation, which
explains some things better:
This one looks unfortunately very thin at the moment...
Linux-audio-dev mailing list