This is interesting; however, I wonder whether it is really relevant to
the problem we are trying to solve here.
As I understand it, we want to:
* Get a list of parameters from the engine in order to populate the
* Send parameter changes to the engine.
* Listen for parameter changes and other events coming from the engine.
There is two-way communication but it does not closely depend on an
action-query-response-query-response-action sequence. In other words we
are using both schemas Paul described--- sending control events and
listening for external events--- without both really needing to be
Or am I misunderstanding something?
On Wed, May 04, 2011 at 09:53:59AM -0400, Paul Davis wrote:
Linux-audio-user mailing list