[gmpi] Re: 3.11 topic: Dynamic plugin structure

> Whether we do "/channel[0]/osc/shape" or "/channel0/osc/shape" or
> "/channel/0/osc/shape" or something else altogether doesn't really matter.
> We can define sane semantics for most of them and can write a parser for
> any of them.

Agree.  My hope is that host parses the names just once when the plugin
loads, then builds a structure similar to what Chris proposed.

 For actual DSP work (sending parameter events from host->plugin) I am
hoping for a more compact parameter identifier.

for example

32bit integer plain indexes (like VST) or
32bit integer 'handles' (like AU)

I know this is an implementation detail, and not really relevant, but I
detect some resistance to the OSC-style naming convention based on the
(justified) perception that parsing long strings in the DSP engine is
inefficient.

Best Regards,
jeff



----------------------------------------------------------------------
Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules:  Please stay on topic.  You are responsible for your own
words.  Please respect your fellow subscribers.  Please do not
redistribute anyone else's words without their permission.

Archive: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts: